DM-24575: Add some more exposure metadata fields #350
Conversation
timj
force-pushed
the
tickets/DM-24575
branch
3 times, most recently
from
14fe350
to
6a80486
Compare
There was a problem hiding this comment.
I think we should add all of these to visit as well, and add code to DefineVisitsTask to copy/average/whatever them from the constituent exposures.
As it is, an expanded data ID for calexp or src can't contain any of these values, because those are all visit-based, not exposure-based, and that's a bit of a problem, because people are probably interested in that metadata at least as often as they're interested in exposure metadata.
| name: object | ||
| type: string | ||
| length: 64 | ||
| doc: Object of interest for this observation or survey field name. |
There was a problem hiding this comment.
This is probably not worth fighting, because I get how ubiquitous it is... but "object" is super overloaded everywhere. Is "target" taken, or does that imply something different in an important context?
There was a problem hiding this comment.
I'm confused because I made the change to target_name this morning.... Maybe I didn't push. I also added them to visit.
There was a problem hiding this comment.
Yes, that's exactly what I did. Sorry. If you look on the obs_base ticket you'll see that it has target_name.
There was a problem hiding this comment.
Do you mean also to add ra/dec?
No description provided.