[OBSPROC-13] Set a minimum required content of targetDB to create pfsDesign Created: 26/Oct/21 Updated: 11/Nov/21 Resolved: 11/Nov/21 |
|
| Status: | Done |
| Project: | PFS observation processing/procedure |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | monodera | Assignee: | monodera |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | targetDB |
| Sprint: | PreEngRun4 |
| Reviewers: | monodera |
| Description |
|
For November 2021 engineering run, we would like to create a pfsDesign by querying targets to targetDB and run scripts. The current proposal for the targetDB schema has a complexity for handling duplications, but for the engineering run a simpler schema should be enough. We would like to first create a working example of this simplified version. |
| Comments |
| Comment by monodera [ 28/Oct/21 ] |
|
The commissioning script (https://github.com/Subaru-PFS/ets_fiberalloc/tree/commissioning_demo) requests the following entries to make pfsDesign.
The Object Type here is set as cosmology. I guess I will skip Redshift and Object Type for the commissioning on Nov 2021. |
| Comment by monodera [ 02/Nov/21 ] |
|
I pushed a branch as https://github.com/Subaru-PFS/ets_target_database/tree/commissioning_2021nov (identical to tickets/ Attached is the current schema.schema_targetdb.pdf |
| Comment by monodera [ 11/Nov/21 ] |
|
I will add "pfs_ {mag,flux}_ {grizy}" in the schema. |
| Comment by monodera [ 11/Nov/21 ] |
|
schema_targetdb-nov2021run-20211110.pdf The schema diagram above shows the one for the Nov 2021 commissioning run. It contains flux information in grizy bands so that we can make some flexible selection based on brightness and color. |