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
The seasonal binning and averaging is not very flexible. Currently, there are 1D and 2D binning functions that only allow medians to be calculated. I think the best way to improve this is to write an ND median/ave/other stat function. The statistical function could be provided as an input, allowing people to do clever things like find the moments from a Gaussian fit the the data in the desired bin. Then all the stat functions could go into utils.stats, and the seasonal binning part would live in ssnl. And if we do ND, then we won't have to keep re-writting things when we eventually want 3D or 4D binning.
The text was updated successfully, but these errors were encountered:
jklenzing
changed the title
Streamlining seasonal averaging
ENH: Streamlining seasonal averaging
Sep 18, 2019
We can and should do those things. In the meantime, the return_bins keyword returns all the data in each bin to the user. Users can then apply whatever they want until pysatSeasons gets upgraded.
Migrating from pysat/pysat#165. From @aburrell.
The seasonal binning and averaging is not very flexible. Currently, there are 1D and 2D binning functions that only allow medians to be calculated. I think the best way to improve this is to write an ND median/ave/other stat function. The statistical function could be provided as an input, allowing people to do clever things like find the moments from a Gaussian fit the the data in the desired bin. Then all the stat functions could go into utils.stats, and the seasonal binning part would live in ssnl. And if we do ND, then we won't have to keep re-writting things when we eventually want 3D or 4D binning.
The text was updated successfully, but these errors were encountered: