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
DM-23331: Add support for default config files in obs_subaru #27
Conversation
Now that obs_subaru has default fgcmcal configs, the way the tests had been setting test configs no longer worked. Now the default configs are read in from files, which can override the ones in obs_subaru appropriate for the test data.
This addition guarantees that the reference catalog will not have index mismatches with certain configurations. This also allows more flexibility when running with different fit configurations.
@@ -179,9 +179,6 @@ def getTargetList(parsedCmd): | |||
""" | |||
return [parsedCmd.butler] | |||
|
|||
def precall(self, parsedCmd): | |||
return True | |||
|
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.
Note that this will also lead to config-checking. Will that cause a --clobber-config
to be necessary when doing multiple iterations with different configs, or is that no longer how things work?
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.
So this is for the output products, which should only be run once, so that's not a problem. (Well, you can run it more than once, but then you would need to clobber which is intended). The fit cycle has its own config checking code to deal with that issue, and that's still in place.
python/lsst/fgcmcal/utilities.py
Outdated
|
||
Returns | ||
------- | ||
refMag : `np.array` |
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.
The actual type is np.ndarray
; np.array
is just a function that makes one.
FGCM now can support listing bands in the config that are unused in a given run. Tests have been added to ensure that this works as expected, and fixes have been put in accordingly.
d8d9351
to
ae80f89
Compare
Update tests accordingly, and also update FGCM code to elegantly handle missing bands.