[PIPE2D-803] Support per-observatory opdb databases Created: 01/Apr/21 Updated: 13/Jan/22 |
|
| Status: | Open |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We currently have two "observatories" which populate and generate opdbs: LAM and Subaru. So the DRPs at any reduction sites (tiger@princeton, LAM, others) need to be able to access multiple opdbs. This could be as simple as providing the name of the opdb database for the data reduction scripts. |
| Comments |
| Comment by cloomis [ 01/Apr/21 ] |
|
To be more specific, I propose that we have two databases: opdb-Subaru and opdb-LAM, and that the replication and reduction systems learn to switch as needed. price? |
| Comment by price [ 07/Apr/21 ] |
|
I agree in principle, but given that the Subaru opdb will ultimately be the only one, I suggest opdb and opdb-lam. |