Ticket #9140 (assigned)
Control how Rebin2D handles integration across NaN bins
Reported by: | Nick Draper | Owned by: | Steven Hahn |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #9141 | Tester: |
Description
Associated with #9139 if an integration includes a NaN we cannot normalise for it as the average currently does.
The suggestion from Ross Stewart is that any integration including a NaN is a NaN.
We probably want to include how we handle this as an option though as a parameter so we can choose between ignoring NaN's and propagating NaN's
Attachments
Change History
comment:2 Changed 7 years ago by Owen Arnold
- Status changed from new to infoneeded
- Owner changed from Michael Reuter to Owen Arnold
What should the default be? Please add sketch of expected outputs.
comment:3 Changed 7 years ago by Nick Draper
To prevent unexpected surprises the default would need to be the current behaviour
comment:5 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
- Owner changed from Owen Arnold to Michael Reuter
comment:6 Changed 6 years ago by Nick Draper
- Milestone changed from Release 3.2 to Backlog
Moved to Backlog at the code freeze of release 3.2
Note: See
TracTickets for help on using
tickets.