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

Do not store Error values while they are just sqrt(counts) #1045

Closed
NickDraper opened this issue Jul 29, 2008 · 2 comments
Closed

Do not store Error values while they are just sqrt(counts) #1045

NickDraper opened this issue Jul 29, 2008 · 2 comments
Assignees
Labels
Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Maintenance Unassigned issues to be addressed in the next maintenance period.

Comments

@NickDraper
Copy link
Contributor

This issue was originally [TRAC 197](http://trac.mantidproject.org/mantid/ticket/197)

A simple boolean flag for the spectra or whole workspace could hold this.


Keywords: Memory

@NickDraper
Copy link
Contributor Author

@NickDraper (2014-02-14T11:07:55):
bulk move to assigned at the into of the triage step

@NickDraper NickDraper added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@KarlPalmen KarlPalmen added the Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. label Aug 27, 2015
@KarlPalmen KarlPalmen added the Maintenance Unassigned issues to be addressed in the next maintenance period. label Oct 1, 2015
@NickDraper
Copy link
Contributor Author

This should not be done, there is not drive for the small amount of (temporary) memory saving this gives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
None yet
Development

No branches or pull requests

2 participants