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
** Feature request**
In fielding comments on the discreteness/periodicity in the FlexZBoost point estimates from members of the Clusters and LSS working groups, it occurred to me that having a metric that could quantify such "discreteness" effects at some level might be useful. For point estimate modes It think this would be looking for noticeably over-represented single value peaks, as we do evaluate the mode on a fixed grid, and thus many values will be identical. It might be slightly more complex for things like the mode or median, as values may not be identical. I don't have a particular metric/algorithm in mind, so comments with specific suggestions would certainly be welcome. This is also not a RAIL v1.0 requirement, just an enhancement that would be nice to have
Before submitting
Please check the following:
[ x ] I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.
The text was updated successfully, but these errors were encountered:
** Feature request**
In fielding comments on the discreteness/periodicity in the FlexZBoost point estimates from members of the Clusters and LSS working groups, it occurred to me that having a metric that could quantify such "discreteness" effects at some level might be useful. For point estimate modes It think this would be looking for noticeably over-represented single value peaks, as we do evaluate the mode on a fixed grid, and thus many values will be identical. It might be slightly more complex for things like the mode or median, as values may not be identical. I don't have a particular metric/algorithm in mind, so comments with specific suggestions would certainly be welcome. This is also not a RAIL v1.0 requirement, just an enhancement that would be nice to have
Before submitting
Please check the following:
The text was updated successfully, but these errors were encountered: