Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:DRP S18-6, DRP F18-1, DRP F18-2, DRP F18-3, DRP F18-4, DRP F18-5
-
Team:Data Release Production
Description
The classifier pickles need to be kept somewhere that the butler can find them and it needs to know about them. The resulting catalogue also needs to live somewhere butler accessible it could either overwrite the deepCoadd_obj files that Tim Morton [X] makes (one I've double check it isn't doing anything silly) or it could go into a new data type but it would be mostly a duplicate of the deepCoadd_obj with a few extra columns added in another extension.
Attachments
Activity
Naming procedures and save locations were discussed (quite a long time ago) with Jim Bosch and Paul Price and everything should be inline with what you suggested.
Thank you for agreeing to review this.
Thanks for your patience! These additions mostly look fine, but as I said over on GitHub, I'd like to know if there's a better way to handle classifier versioning than relying on the file path template. I'm not familiar with other instances of a version keyword in a template and I'd rather avoid setting such a precedent if possible.
Marking as reviewed pending a change from "version" to "label" (see discussion on GitHub). If that doesn't work for you for any reason, happy to chat further!
I'm going to call (the maybe temporary) star galaxy output deepCoadd_sg to be in line with deepCoadd_qa.