You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> @teutoburg should we add a test to prevent such problems in the future when we get new traces?
Absolutely. The issue here (or not really an issue but just something to be aware of) is that the SpectralTraceList assumes that the names of the efficiency extensions are identical to those of the trace definitions. See also the docstring of SpectralEfficiency.
So actually, all IRDB packages that use traces and efficiencies should have a standardized test that simply checks if those match.
Absolutely. The issue here (or not really an issue but just something to be aware of) is that the
SpectralTraceList
assumes that the names of the efficiency extensions are identical to those of the trace definitions. See also the docstring ofSpectralEfficiency
.So actually, all IRDB packages that use traces and efficiencies should have a standardized test that simply checks if those match.
Originally posted by @teutoburg in #176 (comment)
The text was updated successfully, but these errors were encountered: