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
it needs to invoke the canSAS style sheet: cansasxml-html.xsl for formatting and to allow programs like Excel to load the data and metadata in a sensible manner;
although I realize that XML ignores line breaks, canSAS took a conscious decision that all the values associated with a given data point would be formatted on one line in the XML file. So whereas you have
the I and Idev data are not always 'a.u.'! If Mantid has properly reduced the data (which means detector efficiency files, transmissions, direct beams, scale factor, etc) have all been specified then these parameters will have units of '1/cm'.
I also notice that it's not picking out the name of the detector bank correctly, or the source-detector distance (it's just using the first detector pixel).
The text was updated successfully, but these errors were encountered:
Original Reporter: Russell Taylor
From Steve King:
it needs to invoke the canSAS style sheet: cansasxml-html.xsl for formatting and to allow programs like Excel to load the data and metadata in a sensible manner;
although I realize that XML ignores line breaks, canSAS took a conscious decision that all the values associated with a given data point would be formatted on one line in the XML file. So whereas you have
we write
This is to aid human-readability of the file;
the I and Idev data are not always 'a.u.'! If Mantid has properly reduced the data (which means detector efficiency files, transmissions, direct beams, scale factor, etc) have all been specified then these parameters will have units of '1/cm'.
I also notice that it's not picking out the name of the detector bank correctly, or the source-detector distance (it's just using the first detector pixel).
The text was updated successfully, but these errors were encountered: