Description:
Several interpolators are used inside PRIDE, mostly to speed up access to precomputed information. The current solution for interpolation relies on scipy.interpolate.interp1d which is deprecated in favor of more concrete choices.
To ensure that the choice of interpolators is consistent across the program, it would be desirable to:
- Create an internal interface to generate interpolators through a function in
pride.utils, and replace all explicit uses of scipy.interpolate.interp1d with calls to this interface function
- Study the different options for interpolation, and select one that we are sure fulfills our needs. An associated entry with a justification for this choice should be added to the API, making this information available to users
Suggestions for implementation:
- Create an interface for scipy's utility to generate interpolation functions in
pride.utils
- Replace all explicit calls to scipy.interpolate... with calls to this interface
Additional context:
No response
Description:
Several interpolators are used inside PRIDE, mostly to speed up access to precomputed information. The current solution for interpolation relies on
scipy.interpolate.interp1dwhich is deprecated in favor of more concrete choices.To ensure that the choice of interpolators is consistent across the program, it would be desirable to:
pride.utils, and replace all explicit uses ofscipy.interpolate.interp1dwith calls to this interface functionSuggestions for implementation:
pride.utilsAdditional context:
No response