Skip to content

Conversation

@leeskelvin
Copy link
Collaborator

No description provided.

Copy link
Member

@BrunoSanchez BrunoSanchez left a comment

Choose a reason for hiding this comment

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

It looks good to me. I would have to build the docs before I approve, but these are minimal changes that shouldn't really break it.
I left a simple comment/question, but maybe this "silent" mode doesn't really matter.


# Generate injection IDs (if not provided) and injection flag column.
injection_data = vstack(injection_catalogs)
injection_data = vstack(injection_catalogs, metadata_conflicts="silent")
Copy link
Member

Choose a reason for hiding this comment

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

I don't know what motivates this change?
Was this raising bunch of unwanted warnings? I am ok with it but it is "silencing" conflicts.
In any case, injection catalogs have metadata at all?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, it was generating a large number of warnings which were polluting the log. As we don't use the metadata, these can be safely ignored.

@leeskelvin
Copy link
Collaborator Author

Built docs can be found here: https://s3df.slac.stanford.edu/people/lskelvin/source_injection/lsst.source.injection/index.html

These don't have the style sheet formatting of pipelines.lsst.io, but the content is the same.

Astropy can attempt to merge multiple Table objects together, e.g.,
via vstack. If these astropy tables have conflicting metadata keys then
astropy will generate a warning. This warning is not useful and the
metadata is not used during any stage of source injection processing. We
suppress these warnings here to avoid spamming the output logs.
@leeskelvin leeskelvin merged commit 9b9edf2 into main Jan 22, 2026
13 checks passed
@leeskelvin leeskelvin deleted the tickets/DM-53819 branch January 22, 2026 00:55
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.

3 participants