-
Notifications
You must be signed in to change notification settings - Fork 20
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
Problems with nexus parser #106
Comments
Hi @KGoetz91! In the default search interface, only the properties under There are two approaches to solving this:
I think option 1 will be an easier. Maybe you could provide me with an example of the nexus files that you are interested in, and I could draft you an initial app to get started? I could then also add a page about this procedure in our online docs. @domna: Do you have any comments on this? I guess it would quite a hard task to map each application definition to the |
Hi @KGoetz91, I agree with @lauri-codes's view that creating an app for nexus would be the way to make the data searchable. However, we will provide a general NeXus search app eventually and currently also support extracting the chemical formula into the results section (and hence make your data searchable in the periodic table viewer). We may also further extend which informations we compile into the results section. If there is something you urgently need we can try to find the correct place to put it into the Additionally, I see that your data is not even parsed into the |
We have installed a nomad oasis in our lab environment and are trying to upload nexus format data.
The upload works and the parser recognises the data files, we are able to view the data in the oasis. However none of the metadata included in the nexus file is incorporated in a searchable way. I included some screenshots of a simple nxs file we created from the nexus homepage to include an instrument and chemical formula.
However the two metadata entries are not incorporated. Are we doing something wrong on our side or is there something missing in the parser/normalisers?
The text was updated successfully, but these errors were encountered: