DM-47165: Update astrom/photoCal for early ComCam data.

[ctslater]

No description provided.

[erykoff]

I think for the time being we want to have both here, or we can fix this when we fix the photoCal code which is fundamentally broken because it uses band if colorTerms are off and uses filter if colorTerms are on and that's insane. I think the RFC was about cleaning that up, but it's definitely wrong at the moment (by definition). If we want to calibrate empty/white the lines should be:

    ("empty", "monster_SynthLSST_r"),
    ("white", "monster_SynthLSST_r"),

(One for filter, the other for band).

[erykoff]

And if we are never photocalibrating empty those can be left off.

[ctslater]

Ok thanks, I'll add all-of-the-mappings for now and I left a note with your explanation why and the RFC.

[laurenam]

Did you note the comment about also updating LoadReferenceObjectsConfig.pixelMargin in the docstring for that config:

    maxOffsetPix = pexConfig.RangeField(
        doc="Maximum allowed shift of WCS, due to matching (pixel). "
            "When changing this value, the "
            "LoadReferenceObjectsConfig.pixelMargin should also be updated.",
        dtype=int,
        default=250,
        max=4000,
    )

Also, I think the padding in for the visit definition may need to be considered if things are really bad:
https://github.com/lsst/obs_base/blob/2b7fa98c38048493aa6c69f9e8fa92a242ee93f2/python/lsst/obs/base/defineVisits.py#L276-L289

[ctslater]

Thank you! Added config.astromRefObjLoader.pixelMargin=500 for consistency,