The current literal processing of this data set by v14.0 results in only 3 out of 9 CCDs (10-18 are the current ones being used in this testing reference set) processed for visit 1768367. icSrc catalogs are generated, but the matching fails for 6 of the CCDs for this visit.

I'm planning to do a literal update of what validation_data_decam looks like for processing with v14_0 in DM-13204.  But I anticipate that there might be some further discussions of getting those other CCD processed.

Russell: could you review the validation_data_decam part of this ticket?

This is a reprocessed version of `validation_data_decam` with v14.0 of the DM stack. Note that this processing results in only 3 CCDs successfully processed for visit 0176837 (the others fail in the matching step). Under the previous reference v12.0 processing all 9 CCDs considered were successfully processed. All CCDs are successfully processed for the second visit, 0176846.

This correctly captures the default behavior of v14_0 of the stack and obs_decam, but is clearly not what we want longer term.

I would like to defer a reprocessing that actually recovers these CCDs to DM-13201.

I put a few comments on github. The main one was that the ups table is empty, so the directions for setup don't actually seem to work.

I'm also a bit worried about your use of setPhotocalConfigFromEups. I would expect the code to be clearer if you just set the desired options manually. However, I'm not really sure what that function is intended for, and whether it is meant to be the standard way to configure astrometric catalogs. Paul Price might have an opinion about this.

validation_data_decam now updated. Thanks Russell Owen

Can this be closed?

Only did validation_data_decam was done.

validation_data_cfht and validation_data_hsc were not done. This is now superseded by DM-14716, which will provide v16.0 versions for all three.