[INSTRM-815] Provide additional opDB columns from FITS headers Created: 16/Nov/19 Updated: 19/Dec/19 Resolved: 16/Dec/19 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | spt_operational_database |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | hassan | Assignee: | karr |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 1 | ||||||||
| Description |
|
In relation to |
| Comments |
| Comment by karr [ 13/Dec/19 ] |
|
List of FITS header keywords that I use in my analysis, or that we varied as part of the engineering runs, exptime
|
| Comment by Kiyoto Yabe [ 13/Dec/19 ] |
|
Do you like the exactly same names for the database column as those here? |
| Comment by karr [ 13/Dec/19 ] |
|
We should probably use the same format as the other variables (ie, out_tmp instead of out-tmp). The current ones would work, or if we went them to be more descriptive, we could use something like the following. exptime |
| Comment by Kiyoto Yabe [ 14/Dec/19 ] |
|
OK, thank you. I will propose something and ask you to confirm. |
| Comment by Kiyoto Yabe [ 19/Dec/19 ] |
|
I changed the column names of mcs_exposure more descriptively like this:
Is this all fine with you?
|