Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Story Points:1
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Afterburner for DP0.2 to recover from DM-35322.
Aborted plan is to use the fact that photocalibs are flat (1 parameter) per detector for imsim to write a very specialized cheap task that only works for this particular rescue case.
Going forward with plan to make a set of data products that look exactly like they would if we did it right the first time.
Need a good name for the "final" table: recoveredForcedSourceOnDiaObjectTable? finalForcedSourceOnDiaObjectTable?
Attachments
Activity
Convo on obs_lsst PR and what to name the tables: https://lsstc.slack.com/archives/C8EEUGDSA/p1657814390731469
OK Colin, thanks for starting the review. I'm embarrassed that the PR wasn't ready the first time you looked. Per convo ^^^ I added a DRP-afterburner.yaml to obs_lsst with just the new task that writes out to the same name as the old one.
I am worried that we'll end up accidentally mixing old and new files somehow, but I am cool with this being an experiment for the future as one possible way to fix a data product.
Looks good, I was able to run it and see that mergedForcedSourceOnDiaObject has good values from all of the plugins.
Colin Slater
added a comment - Looks good, I was able to run it and see that mergedForcedSourceOnDiaObject has good values from all of the plugins. Only merged to v23.0.x. Serves no purpose on main.
This is ready for review. I tested on the IDF with:
pipetask run -b s3://butler-us-central1-panda-dev/dc2/butler-external.yaml -o u/yusra/DM-35338 -d "instrument='LSSTCam-imSim' AND skymap='DC2' AND tract=3828 AND patch=5" -p $OBS_LSST_DIR/pipelines/imsim/DRP.yaml#step8 --extend-run --skip-existing -j 4takes anywhere between 3s and 10s per detector. 3e6 detectors.
what should we call these tables?