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
Within the ISIS SANS reduction we sometimes load data and monitors separately by interrogating the history of the loaded data workspace (SANSUtility.getFilePathFromWorkspace()), finding out which file the data originated from, then going back and loading the monitors from the file.
Unfortunately, our method of interrogating the history is problematic. I have seen the following error message:
Invalid value for property Filename (list of str lists)
"Y:\cycle_13_5\SANS2D00023098.raw":
File "Y:\cycle_13_5\SANS2D00023098.raw" not found
Which stems from the fact that I was using added data files given to me by Richard, which originated from a directory I no longer have access to.
Richard has also seen the following:
CloneWorkspace started
CloneWorkspace successful, Duration 0.28 seconds
RuntimeError: Failed while looking for file in workspace: __CurrentMask
at line 10928 in '`<Interface>`'
caused by line 1007 in 'C:/MantidInstall/scripts/SANS\ISISCommandInterface.py'
caused by line 455 in 'C:/MantidInstall/scripts/SANS\SANSUtility.py'
caused by line 440 in 'C:/MantidInstall/scripts/SANS\SANSUtility.py'
caused by line 431 in 'C:/MantidInstall/scripts/SANS\SANSUtility.py'
Which may or may not be the exact same problem, but speaks to the fact that loading data and monitors separately like this should be avoided if possible.
The text was updated successfully, but these errors were encountered:
Within the ISIS SANS reduction we sometimes load data and monitors separately by interrogating the history of the loaded data workspace (
SANSUtility.getFilePathFromWorkspace()
), finding out which file the data originated from, then going back and loading the monitors from the file.Unfortunately, our method of interrogating the history is problematic. I have seen the following error message:
Which stems from the fact that I was using added data files given to me by Richard, which originated from a directory I no longer have access to.
Richard has also seen the following:
Which may or may not be the exact same problem, but speaks to the fact that loading data and monitors separately like this should be avoided if possible.
The text was updated successfully, but these errors were encountered: