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

NeXus/HDF5 data input allowing selection of data paths #1639

Open
toqduj opened this issue Jul 23, 2020 · 7 comments
Open

NeXus/HDF5 data input allowing selection of data paths #1639

toqduj opened this issue Jul 23, 2020 · 7 comments
Labels
Cross Package Issue This issue involves a package other than SasView/sasview

Comments

@toqduj
Copy link
Contributor

toqduj commented Jul 23, 2020

I'm seeing a lot of cases where SasView doesn't read NeXus files, likely due to inconsistencies between the various files. As a back-up plan, would it be an idea to allow the user to configure which data paths of the input file map to (1D or 2D) Q, I, ISigma (and maybe QSigma)? This dialog could come up if the standard HDF load methods fail..

@smk78
Copy link
Contributor

smk78 commented Jul 24, 2020

Do you mean NeXus or NXcanSAS?

@toqduj
Copy link
Contributor Author

toqduj commented Jul 27, 2020

NXcanSAS specifically. I've got someone's GRASP-processed datafiles which are not being read by SasView. Ideally, I would just point SasView at the locations where qx, qy, I ISigma and the mask are stored, instead of writing an HDF5-to-HDF5 converter.

@smk78
Copy link
Contributor

smk78 commented Jul 27, 2020

So the likely possibilities here are that i) GRASP is not writing compliant NXcanSAS, or ii) something we did recently has broken NXcanSAS loading for some files (though I just tried generating and loading some 1D and 2D NXcanSAS in Mantid and it reads into SasView fine).

Can you upload an example file? Is it 1D or 2D reduced?

@butlerpd
Copy link
Member

I would be very surprised if GRASP is outputting NXcanSAS. I strongly suspect it is putting out standard NeXus with some "extensions" as defined by Charles Dewhurst. ILL converted to NeXus slightly before NXcanSAS was approved I am guessing?We should ask @gonzalezma to look into that.

@butlerpd
Copy link
Member

or perhaps better yet Lionel Porcar?

@gonzalezma
Copy link
Contributor

gonzalezma commented Jul 27, 2020 via email

@toqduj
Copy link
Contributor Author

toqduj commented Sep 15, 2020

well, I suspect that with every flavor of instrument, there will be yet another slight variant on how the HDF5 files are written in the end. Having the (backup) option of setting the HDF5 data paths to the matrices would future-proof this a bit...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cross Package Issue This issue involves a package other than SasView/sasview
Projects
None yet
Development

No branches or pull requests

5 participants