Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IntegrateMDHistoWorkspace should have keep binning + axis limits option #12471

Closed
OwenArnold opened this issue Apr 24, 2015 · 1 comment
Closed
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Vates
Milestone

Comments

@OwenArnold
Copy link
Contributor

This ticket is blocks : TRAC11626

Currently you can set P{n}Bins to be [] or [min,max] where [] means exactly keep the binning and [min,max] means integrate between limits.

Russell Ewings has asked for this to occur as a mode in the LineViewer (11626), but the problem comes when you specify the start and stop within the range of the original data. In this case, you want to keep the existing binning, but you also want to exclude any data between the limits. If you do not do this, it will not be possible to reproduce the slice as drawn in the plots.

I suggest that having a [start, 0, stop] syntax should also be allowed. Only zero's would be accepted and would indicate that the current binning should apply.


Keywords: vates

@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 11633

@OwenArnold OwenArnold added Framework Issues and pull requests related to components in the Framework Vates labels Jun 3, 2015
@OwenArnold OwenArnold self-assigned this Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 3.4 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Vates
Projects
None yet
Development

No branches or pull requests

1 participant