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

Gropuing file obtained from instrument window can not be read by LoadDetectorsGroupingFile algorithm #6976

Closed
abuts opened this issue Nov 15, 2012 · 1 comment
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@abuts
Copy link
Member

abuts commented Nov 15, 2012

Tried on Wish

 1) Load a workspace (e.g. wish) and show the instrument view (e.g.
 Y-projection)
 2) In instrument view go to pick->pixel selection
 3)Select an area of interest by clicking on a place and dragging the 
    mouse pointer selecting an area.
    Menu appears after releasing the mouse button.
    Choose Create Grouping file->include (or exclude) does not matter
 4) File selection menu appears prompting to pick/name 
    a grouping file.
 5) Save grouping file into desired location. 

When one tries to read this grouping file by LoadDetectorsGroupingFile
the algorithm fails with error, there are no instrument name specified in the grouping file.

If one manually edit the resulting grouping file and sets the instrument name as (tried on Wish):

<detector-grouping instrument="WISH">

The error changes to:

Error in execution of algorithm LoadDetectorsGroupingFile:
SAXParseException: No element found in line 6 column 0. Unable to parse File:

@abuts
Copy link
Member Author

abuts commented Jun 3, 2015

This issue was originally trac ticket 6130

@abuts abuts added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@abuts abuts added this to the Release 2.5 milestone Jun 3, 2015
@abuts abuts closed this as completed 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