-
Type:
Story
-
Status: Open (View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:None
-
Story Points:1
DAMD-97 will audit datamodel.txt for missing 2D pipeline products and add anything that's missing. However, it's not clear whether we need python I/O implementations in the datamodel package for the "Class II" products (not commonly used by science users, e.g., the sky flux models and flux calibration vectors; see DAMD-97). One clear reason to add a python I/O implementation would be if it is anticipated that the science database will include these products.
Could you please report whether you anticipate the science database including "Class II" pipeline products?
- relates to
-
-
- Done
-
We do not need the I/O interfaces now, but we may want to have them in the future. We will make all data products including intermediate pipeline products available at the science database. Science users will not use, e.g., calibration files, very often as you say, but if they find I/O interfaces useful, then we can consider implementing them. So, my answer to your question is; let's leave it as a future question, unless we need to freeze the datamodel package now for good.