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
@biprateep I encountered an error in the integrate_flux function when the value at the start or the end of a flux window is masked. In that case the interpolation function bounds are shorter than the flux window and an error is returned.
I managed to reproduce the error with this simple example:
Returns: ValueError: A value in x_new is above the interpolation range.
I can 'fix' the issue by setting bounds_error=False, fill_value='extrapolate' in the interpolation of this function but that might be a bit risky (I guess the most extreme extrapolation issues will already be avoided as a max of 20% of the pixels can be masked for the interpolation to even happen).
Do you have any thoughts on what might be a better solution?
The text was updated successfully, but these errors were encountered:
I also encountered the issue that when one spectrum can not be normalised the stacking crashes. which is understandable but we might want to include some functionality that filters out those rare spectra with >20% masked within the flux window and then continues stacking with the spectra that can be normalised.
@biprateep I encountered an error in the integrate_flux function when the value at the start or the end of a flux window is masked. In that case the interpolation function bounds are shorter than the flux window and an error is returned.
I managed to reproduce the error with this simple example:
Returns:
ValueError: A value in x_new is above the interpolation range.
I can 'fix' the issue by setting
bounds_error=False, fill_value='extrapolate'
in the interpolation of this function but that might be a bit risky (I guess the most extreme extrapolation issues will already be avoided as a max of 20% of the pixels can be masked for the interpolation to even happen).Do you have any thoughts on what might be a better solution?
The text was updated successfully, but these errors were encountered: