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

LoadISISNexus is broken when monitors are defined in the middle of the detectors #5579

Closed
martyngigg opened this issue Feb 3, 2012 · 2 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework

Comments

@martyngigg
Copy link
Member

This issue was originally TRAC 4732

The INES instrument at ISIS have 164 spectra with the monitors defines as 145-148. LoadISISNexus assumes that monitors occur in blocks at the start or end of the detector list and so loads the data incorrectly. Any of the INS nxs files will show this problem

@martyngigg
Copy link
Member Author

@NickDraper (2012-04-30T14:12:58):
Moved at end of release 2.1


@NickDraper (2012-08-10T12:43:39):
Moved at the end of release 2.2


@NickDraper (2012-10-28T11:38:50):
Moved to milestone 2.4


@NickDraper (2013-04-29T09:49:39):
Moved to r2.6 at the end of r2.5


@martyngigg (2013-07-15T08:46:44):
Batch move to 2.7


@NickDraper (2014-02-14T11:04:56):
Bulk move to assigned at the introduction of the triage step

@martyngigg martyngigg added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg
Copy link
Member Author

This is now duplicated by #15482.

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
Projects
None yet
Development

No branches or pull requests

1 participant