Fix Version/s: None
Single frame processing currently uses GaussianFlux as part of the extendedness calculation, but the GaussianFlux is not included in the SourceTable, so users won't be able to easily test the S/G performance with the final data products. We should add GaussianFlux to the SourceTable for DP0.2, though since it's not required by the DPDD we can reconsider later whether to keep this for future data releases.
- mentioned in
It seems like we can keep it simple, gaussianFlux and gaussianFluxErr?
I like simple. Available to review. tested with
pipetask run -b /repo/dc2 -i 2.2i/runs/test-med-1/w_2021_44/DM-32391 -o u/yusra/DC2/DM-32666 -d "" --register-dataset-types -p $OBS_LSST_DIR/pipelines/imsim/DRP.yaml#transformSourceTable -d "detector=188 AND visit=228092"
pipetask run -b /repo/main/butler.yaml -i HSC/runs/RC2/w_2021_34/DM-31524 -o u/yusra/RC2/w40 -d "" --register-dataset-types -p $OBS_SUBARU_DIR/pipelines/DRP.yaml#transformSourceTable,consolidateSourceTable -j 10 &>sourcetales_w40.log &
Jenkins going https://ci.lsst.codes/job/stack-os-matrix/35457/display/redirect
All looks good, I pulled up the tables and the columns are there. Thanks for taking care of this.
I hate naming things. Do you have an opinion on what these columns should be called? Or shall I take it to dm-naming things?