search

mantidproject / mantid

Main repository for Mantid code
https://www.mantidproject.org
GNU General Public License v3.0
210 stars 121 forks source link

Missing log values #35507

Open jfkcooper opened 1 year ago

jfkcooper commented 1 year ago

Describe the bug

Nexus files have an entry raw_data_1/user_1/name which gives the names of the users. There is also a field for affiliation, but this may be being entered incorrectly as I think it is blank currently.

When the nexus file is loaded into mantid, this user name information is no longer available in the loaded workspace (at least not in the logs or any place I thought to look). This is wanted due to #31073.

To Reproduce

Load in any ISIS nexus file in Mantid and try to find raw_data_1/user_1/name Open the same nexus in something like HDFView (or even h5py) and find the raw_data_1/user_1/name

Expected behavior

Both ways of loading the nexus should have access to the same information

Platform/Version (please complete the following information):

rbauststfc commented 1 year ago

@thomashampson, if it's OK with you, I think we're going to pick this one up in LSS as part of #35098 and #31073 (a new output save file format for Reflectometry that will include more metadata from the ISIS NeXus file). Over time, there are likely to be more metadata values that are in the ISIS NeXus file but aren't currently being loaded in Mantid that we'll want to include in the saved output, so I'm trying to think through how we might need to handle that. If you have some time, it would be really handy if we could have a chat about obstacles/options for that sometime soon.

github-actions[bot] commented 5 months ago

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.