Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:8
-
Epic Link:
-
Sprint:DRP S19-1, DRP S19-2
-
Team:Data Release Production
Attachments
Issue Links
- duplicates
-
DM-8703 Decouple makeCoaddTempExpTask.createTempExp() from Butler
- Invalid
-
DM-15236 Refactor MakeCoaddTempExp s.t. run doesn't touch disk
- Invalid
- is triggered by
-
RFC-285 Revise front-end for warping
- Implemented
-
RFC-551 Rename MakeCoaddTempExpTask to MakeWarpTask
- Implemented
- is triggering
-
DM-17062 Apply jointcal/FGCM in Gen3 ForcedPhotCcd
- Invalid
The command to test this
{{pipetask -b /project/yusra/ci_hsc/DATA/butler.yaml
-i shared/ci_hsc -o test/warp -d "Tract.tract=0 and Patch.patch=69 and Visit.visit=903986" run -t makeCoaddTempExp.MakeWarpTask --configfile MakeWarpTask:makeWarpTask.py}}
I don't like the makeCoaddTempExp.MakeWarpTask part. And it makes me want to start the new makeWarp.py module. How awful would it be to have a makeCoaddTempExp.py and a makeWarp.py living side by side?