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

Instrument view: max value of colour map is wrong #1419

Closed
NickDraper opened this issue Apr 24, 2009 · 1 comment
Closed

Instrument view: max value of colour map is wrong #1419

NickDraper opened this issue Apr 24, 2009 · 1 comment
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@NickDraper
Copy link
Contributor

Load the merlin definition (probably best on windows to get graphics card support).

Default colour map max is 3.72233e+06

This appears to come from index 69632 detector 11.

According to the XML definition this is correctly marked as a monitor.

We used to have code in the colour map vaule selection to exclude monitors from the min and max value selection. Monitors were always coloured with the max value in the colour map.

This code looks to not be working any more.

We need this for demonstrations at the ICNS. Deadline for this is end of Tuesday.

@NickDraper
Copy link
Contributor Author

This issue was originally trac ticket 571

@NickDraper NickDraper added the High Priority An issue or pull request that if not addressed is severe enough to postponse a release. label Jun 3, 2015
@NickDraper NickDraper added this to the Iteration 17 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

2 participants