[INSTRM-991] Provide functional requirement and use cases of the opDB standard library from the viewpoint of ETS Created: 20/May/20  Updated: 10/Nov/20  Resolved: 10/Nov/20

Status: Done
Project: Instrument control development
Component/s: spt_operational_database
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kiyoto Yabe Assignee: mxhf
Resolution: Done Votes: 0
Labels: opDB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks INSTRM-735 Establish a library for database inte... Done

 Description   

Description: As we discussed in previous ICS/MCS-PFI telecon, I will collect the functional requirements and possible use cases in each site of software development to figure out what kind of function we need in the standard library to access opDB and how we should generalized it. Please provide a list of your required function for this library and example of major use cases from the view point of fiber assignment software (ETS).

Examples in the survey simulator will be sent to the ETS developers hopefully soon for their reference, but below are possible examples for MCS/PFI-related tables: * 

 insert (pandas/numpy/…) array of measured data into `mcs_data`

  •  get information from `cobra_geometry`
  •  get target information joining `cobra_status`, `pfs_config_fiber`, and `target`
  • ...

 
If you can provide any performance requirements (speed/stability/…), that would be great.
 
I will compile the requirements and update the proposal of the standard library:
https://sumire.pbworks.com/w/file/fetch/139861650/PFS-DAT-IPM003007-01_opdb_proposal_library.pdf
 


Generated at Sat Feb 10 16:30:45 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.