Skip to content

Conversation

@erykoff
Copy link
Contributor

@erykoff erykoff commented Nov 12, 2025

No description provided.

@jrmullaney jrmullaney self-requested a review November 12, 2025 20:39
Copy link

@jrmullaney jrmullaney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of doc requests.


Returns
-------
result : `lsst.pipe.base.Struct`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm worried that "weight" is non-obvious, so I was wondering whether the columns could be listed here, with a description for each. Most would be trivial ("visit": "visit ID"), but then we'd have a description for "weight".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now you're asking for me to document long standing undocumented things ... and unfortunately this is a place where nobody would look. I'm not sure what to do.

)
coadd_input_summary_tract = lsst.pipe.base.connectionTypes.Output(
name="coadd_input_summary_tract",
doc="Summarized coadd inputs (by tract and band).",
Copy link

@jrmullaney jrmullaney Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you make this more descriptive? e.g., "Table listing the visit and detectors that cover each patch within a tract; also includes weight, good pixel count, band."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't even know where these show up, but I don't want to put too much in. How about:

        doc="Summary table aggregating coaddInputs from multiple coadds (including "
            "all coaddInputs tables in a tract for a single band).",

-------
result : `lsst.pipe.base.Struct`
Result struct containing:
``coadd_input_summary`` : `astropy.table.Table`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above re: column descriptions.

)
coadd_input_summary = lsst.pipe.base.connectionTypes.Output(
name="coadd_input_summary",
doc="Summarized coadd inputs.",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this could use the same treatment (see suggestion above).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

        doc="Summary table aggregating coaddInputs from all coadds, including all "
            "tracts and bands.",

@erykoff erykoff merged commit 5bf09c0 into main Nov 13, 2025
10 checks passed
@erykoff erykoff deleted the tickets/DM-53028 branch November 13, 2025 00:47
coadd_input_summary_tract["visit"][counter : counter + ndet] = detectors["visit"]
coadd_input_summary_tract["detector"][counter : counter + ndet] = detectors["ccd"]
coadd_input_summary_tract["weight"][counter : counter + ndet] = detectors["weight"]
coadd_input_summary_tract["goodpix"][counter : counter + ndet] = detectors["goodpix"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies for not volunteering to review earlier. Is goodpix useful here? The cell-based coadd variant will have everything else but that and it'd be good to keep the output agnostic to the flavor of the coadd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants