You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of our EU JRA work we’ve been developing an exchange NeXus definition to help PSI and ISIS share data and software, unfortunately I’m currently unable to read these files in Mantid. The file format is based on the version 2 NeXus definition (described in the attached document) and an example is attached. This definition is now (more or less) complete and is being used at PSI, so it would be good if an algorithm could be coded capable of reading these files. Getting this working would also be quite helpful to our EU project work as it would be good to show PSI data files exchanged and analysed in Mantid for the final report due around the end of the year.
Looking at the available algorithms I’m uncertain whether a version of ‘LoadMuonNeXus’ is available designed for version 2 files (the algorithm tree is a little strange). However, I suspect even if this exists some modification will be required to correctly read these files – particularly recognising revised entry names and distinguishing between mandatory and optional entries. You’ll notice that very few elements are mandatory in the new files (indicated in bold type in the definition), so a reader should require these items present and then attempt to read other entries that contain additional metadata if it exists (likely in the ISIS files).
I am hoping it will be possible to give some effort to this problem over the next month or so. Initially, it would be sufficient just to read mandatory items to enable us to read the attached example file. Later I could give you some example ISIS files containing additional (optional) metadata.
The text was updated successfully, but these errors were encountered:
From Stephen Cottrell:
As part of our EU JRA work we’ve been developing an exchange NeXus definition to help PSI and ISIS share data and software, unfortunately I’m currently unable to read these files in Mantid. The file format is based on the version 2 NeXus definition (described in the attached document) and an example is attached. This definition is now (more or less) complete and is being used at PSI, so it would be good if an algorithm could be coded capable of reading these files. Getting this working would also be quite helpful to our EU project work as it would be good to show PSI data files exchanged and analysed in Mantid for the final report due around the end of the year.
Looking at the available algorithms I’m uncertain whether a version of ‘LoadMuonNeXus’ is available designed for version 2 files (the algorithm tree is a little strange). However, I suspect even if this exists some modification will be required to correctly read these files – particularly recognising revised entry names and distinguishing between mandatory and optional entries. You’ll notice that very few elements are mandatory in the new files (indicated in bold type in the definition), so a reader should require these items present and then attempt to read other entries that contain additional metadata if it exists (likely in the ISIS files).
I am hoping it will be possible to give some effort to this problem over the next month or so. Initially, it would be sufficient just to read mandatory items to enable us to read the attached example file. Later I could give you some example ISIS files containing additional (optional) metadata.
The text was updated successfully, but these errors were encountered: