Fix Version/s: None
Process the RC2 dataset with the w_2022_04 weekly.
|Status||To Do [ 10001 ]||In Progress [ 3 ]|
For jointcal, in order to best match current Gen3 defaults, I am running with the config override file:
(also attached to
Did something go wrong with this run? I don't see an objectTable_tract output for any of the tract trying:
ls -al /datasets/hsc/repo/rerun/RC/w_202_*/DM-*/deepCoadd-results/merged/*/objectTable*.parq
(I don't need it and am not planning on following this up, I was just trying to confirm that gen2to3 conversion caught everything that succeeded for
Huh...nothing deeper than I don't appear to have run them (I guess I got distracted with the parity checks that did not include these tables and forgot to to back and finish off the processing. Well-spotted!) I guess I jumped the gun on checking off the boxes in the weekly reprocessing spreadsheet (https://docs.google.com/spreadsheets/d/1KTwTetVJoRBXAb3tQKL3-XzYadRndyoIxY3dTyT85qk/edit#gid=0, sorry Brock Brendal [X]). I just ran them, so all should be in place now, but I'm not sure it's worth updating/re-running the gen2to3 conversion.
Run is now complete. Saw the same set of errors and warnings as reported in
DM-31477, DM-31815, DM-32419, & DM-32766 (no new ones noticed).
Logs can be found at (or linked here):
FGCM plots and logs are linked here
pipe_analysis plots: gen2, gen3 + gen2 vs gen3.
matchedVisitMetrics output linked here
Modulo the [s]tellar locus issue of
DM-34286 (which also seems to apply to the [s]kyObject* metrics), the metrics were successfully dispatched, ingested to SQuaSH, and now appear on the DRP metrics monthly Gen 2 (HSC RC2) dashboard in chronograph.
Since you've already looked into this one, would you mind doing the final cursory check & approval?
|Reviewers||Dan Taranu [ dtaranu ]|
|Status||In Progress [ 3 ]||In Review [ 10004 ]|
The plots certainly appear to be there, as do the objectTable_tract datasets.
I think the missing datasets could be ingested fairly easily by re-running the gen2to3 conversion script, but I'm not completely sure that it would work without issue and concur that there isn't any reason to try. If someone does find a compelling need, please correct me.
|Status||In Review [ 10004 ]||Reviewed [ 10101 ]|
|Resolution||Done [ 10000 ]|
|Status||Reviewed [ 10101 ]||Done [ 10002 ]|
Note that I had to comment out the following line in the fgcm fgcmOutputProductsRC2new.py config file:
as the defaultFilter has been deprecated (
DM-26231). I don't think this will have any consequences (can you confirm Eli Rykoff?)