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

Normailisation Defaults. Visualisation only. #12186

Closed
2 tasks done
OwenArnold opened this issue Mar 12, 2015 · 0 comments
Closed
2 tasks done

Normailisation Defaults. Visualisation only. #12186

OwenArnold opened this issue Mar 12, 2015 · 0 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Vates
Milestone

Comments

@OwenArnold
Copy link
Contributor

This issue was originally TRAC 11347

This ticket is blocked by :

Rules suggested are:

  • When loading histogram data from MD workspaces in visualisation should always use n-events normalisation.
  • When looking at full MDEventWorkspaces, should use volume normalisation providing the workspace is not histogrammed
  • Is there a need to use NoNormalisation at all?

Needs approval before working on this by SNS and ISIS.

1 Weeks work, as testing should be very thorough. Should also update the VSI to do the same thing as the SliceViewer.


Keywords: VATES-vis

@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.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 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

2 participants