[INSTRM-735] Establish a library for database interaction. Created: 21/Aug/19 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: | chyan | Assignee: | Kiyoto Yabe |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
We should have an interface for accessing database information instead of putting database query command in every actor. After having this library, all we need to be is import this package, then we can retrieve data from operation database. |
| Comments |
| Comment by cloomis [ 21/Aug/19 ] |
|
I vote for either spt_operational_database or pfs_utils, with a slight preference for the first. |
| Comment by Kiyoto Yabe [ 21/Aug/19 ] |
|
Yes, `spt_operational_database` would be straightforward. |
| Comment by Kiyoto Yabe [ 26/Aug/20 ] |
|
I have pushed example implementation to the branch. You can see an example notebook [here|https://github.com/Subaru-PFS/spt_operational_database/blob/tickets/INSTRM-735/examples/test/opdb_api_implementation_example.ipynb]. Currently, usage for only SpS is available, so it may be of interest of only arnaud.lefur, but any comments are welcome. |
| Comment by Kiyoto Yabe [ 10/Nov/20 ] |
|
The branch has been merged, and further requests should be filed as separate tickets. |