Add a NaN policy for criteria aggregation

[baptistehamon]

Addressing a Problem?

Currently, there isn't any way for user to specify how aggregate should handle NaN, while in some use cases it can be useful to have this option.

Potential Solution

All backend aggregation methods used in aggregate have a parameter to set how NaN should be treated Then, adding a parameter (nan_policy or dropna ...) to aggregate and passing it to the under layer aggregation methods would solve this issue. There is a little bit more work for limfactor method.

Additional Context

No response

Contribution

• I would be willing/able to open a Pull Request to contribute this feature.

Code of Conduct

• I agree to follow this project's Code of Conduct

[Nandini01042004]

Hi 👋 I’d like to work on this issue.
My plan is to add a parameter (e.g., nan_policy with options like ignore, propagate, omit) to aggregate() and pass it to the backend aggregation methods.
Could you confirm if that’s aligned with what you expect?

[baptistehamon]

Hi,
Sounds good to me, I'm letting you start working on that ;)
Let me know if you have any questions!