Ticket #7831 (closed: invalid)
A Mantid Processed Workspace that does not load
| Reported by: | Nick Draper | Owned by: | Nick Draper |
|---|---|---|---|
| Priority: | major | Milestone: | Release 3.3 |
| Component: | Framework | Keywords: | |
| Cc: | Emmanuel, FARHI, (farhi@… | Blocked By: | |
| Blocking: | Tester: | Harry Jeffery |
Description
The attached archive contains two NeXus files.
- IRS21360_graphite002_ipg.nxs is an example filde from mantid
- iFit_iD445176.nxs is a re-generated file for mantid, after processing the IRS example file above.
Mantid LoadNexus works with the first, but aborts for the 2nd with error: LoadNexus-[Notice] LoadNexus started LoadNexusProcessed-[Error] Error in execution of algorithm LoadNexusProcessed: LoadNexusProcessed-[Error] Error opening data in group "data" LoadNexus-[Error] Error in execution of algorithm LoadNexus: LoadNexus-[Error] Error opening data in group "data"
I have checked the whole NeXus tree structure and attributes, and can hardly find differences. Would you be so kind to tell me what's wrong with the 2nd file, and in particular what is this 'data' group which does not exist in the 2nd file ?
Is there a clean documentation indicating how to produce a nexus 'Mantid processed workspace' with required and optional fields, in particular when the IDF is not available ? The NeXus XML indicated as URL attribute does not exist.
Many thanks, Emmanuel.
Change History
comment:2 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:3 Changed 6 years ago by Nick Draper
- Owner changed from Roman Tolchenov to Nick Draper
- Status changed from assigned to verify
- Resolution set to invalid
this is too old to be useful now, more progress has been made at the ILL making this redundant.
Move tickets to Backlog that did not get into R3.0