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

Saving cuts with non-S(q,w) intensity option not working #980

Closed
mducle opened this issue Mar 18, 2024 · 1 comment
Closed

Saving cuts with non-S(q,w) intensity option not working #980

mducle opened this issue Mar 18, 2024 · 1 comment
Assignees
Labels

Comments

@mducle
Copy link
Member

mducle commented Mar 18, 2024

Original reporter (to be notified): ISIS/Mo

Describe the bug

After plotting a 1D cut and selecting a different intensity option than the default (S(q,w)), if I save the cut, the saved data is the original intensity and not the one I selected.

To Reproduce
Steps to reproduce the behavior:

  1. Open a file in MSlice (e.g. MAR21335_Ei60meV.nxs from the test suite)
  2. Make a 1D cut (e.g. along DeltaE from 5 to 55 step 0.3 integrating along |Q| from 4 to 10).
  3. In the plot window, go to the Intensity menu and select GDOS. Put in 5 K as the temperature.
  4. Then click the "Floppy disk" icon and select Ascii as the file format (bottom right).
  5. Save to file - and plot the file with an external program (e.g. gnuplot or load it with numpy.loadtxt and plot it manually) - check that the lower energy peak (around 20meV) is more intense than the high energy peak - in the GDOS cut the two peaks are roughly the same height.

Expected behavior
The saved data file should reflect what is seen on the screen.

Screenshots
N/A

MSlice Version (please complete the following information):

  • MSlice Version 2.6.0 from Mantid 6.9.20240315.0914 (nightly).

Additional context
When plotting the GDOS cut, an MDworkspace (not hidden) is created in the Mantid workspace window, which contains the correct (GDOS) data - after running ConvertMDHistoToMatrixWorkspace this can be saved with SaveAscii but this is a bit hard to use...

@mducle mducle added the bug label Mar 18, 2024
@SilkeSchomann SilkeSchomann self-assigned this Jul 8, 2024
@SilkeSchomann
Copy link
Collaborator

This problem was fixed by #987 and is not present anymore in Mantid 6.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants