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

SaveCanSAS1D refinements #1970

Closed
mantid-builder opened this issue Feb 11, 2010 · 1 comment
Closed

SaveCanSAS1D refinements #1970

mantid-builder opened this issue Feb 11, 2010 · 1 comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@mantid-builder
Copy link
Collaborator

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

    `<Idata>`
      `<Q unit="1/A">`0.011`</Q>`
      `<I unit="a.u">`212.981`</I>`
      `<Idev unit="a.u">`2.99406`</Idev>`
    `</Idata>`
    

    we write

    `<Idata>``<Q unit="1/A">`0.011`</Q>``<I unit="a.u">`212.981`</I>``<Idev unit="a.u">`2.99406`</Idev>``</Idata>`
    
    
    

    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).

@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 1122

@mantid-builder mantid-builder added the High Priority An issue or pull request that if not addressed is severe enough to postponse a release. label Jun 3, 2015
@mantid-builder mantid-builder added this to the Iteration 23 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

1 participant