Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ip_isr, obs_base, pipe_tasks
-
Labels:
-
Urgent?:No
Description
Conversation on the RFC-775 proposal revealed that pipe_tasks depends on ip_isr via more than just Gen2 ProcessCcdTask's usage of IsrTask. In particular, Tim Jenness says:
The read curated calibs routine should clearly not be there – obs_base has to import pipe_tasks to use the routine and that seems completely broken.
This is mostly tangential to RFC-775, so I think it's better to make it a separate ticket rather than part of its implementation.
Attachments
Issue Links
- relates to
-
- Done
Activity
I am dealing with this in DM-35035. I have moved the curated calibrations reading code to obs_base. Now that we don't have to support gen2 I was able to change the code to use the StorageClass python type for the curated calibration class and that does not need any special dependency on ip_isr.
The real difficulty is working out where to put the code. obs_base uses it but it's entirely for ip_isr serializations.
ip_isr depends on meas_algorithms which depends on obs_base via obs_test (which maybe goes away when gen2 goes away). Putting it in ip_isr (once the circular dependency goes away) then leads to obs_base depending on half the world again.