-
Notifications
You must be signed in to change notification settings - Fork 2
DM-53819: Apply miscellaneous fixes to source_injection #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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") |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
|
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.
b05916e to
e6f9631
Compare
No description provided.