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

cannot read canSAS1D file written out by SasView (Trac #938) #1018

Closed
butlerpd opened this issue Mar 30, 2019 · 3 comments
Closed

cannot read canSAS1D file written out by SasView (Trac #938) #1018

butlerpd opened this issue Mar 30, 2019 · 3 comments
Assignees
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Milestone

Comments

@butlerpd
Copy link
Member

butlerpd commented Mar 30, 2019

Load data. Right click on data and choose save as and choose cansas1D xml instead of txt then save. Now choose "load" and try to load that same file. Instead of loading 4 unit errors are thrown. It seems because in order to plot nicely the axis labels are wrapped in latex formatting and so written out that way as well.

The following errors occured whilst loading 044753_t1_out.xml:
	Error: CanSAS reader: unexpected "Idev" unit [\rm{Intensity} | cm^{-1}]; expecting [1/cm]
	Error: CanSAS reader: unexpected "Q" unit [\rm{Q} | A^{-1}]; expecting [1/A]
	Error: CanSAS reader: unexpected "Qdev" unit [\rm{Q} | A^{-1}]; expecting [1/A]
	Error: CanSAS reader: unexpected "I" unit [\rm{Intensity} | cm^{-1}]; expecting [1/cm]

Migrated from http://trac.sasview.org/ticket/938

{
    "status": "closed",
    "changetime": "2017-05-30T03:30:49",
    "_ts": "2017-05-30 03:30:49.211847+00:00",
    "description": "Load data.  Right click on data and choose save as and choose cansas1D xml instead of txt then save.  Now choose \"load\" and try to load that same file. Instead of loading 4 unit errors are thrown.  It seems because in order to plot nicely the axis labels are wrapped in latex formatting and so written out that way as well.\n{{{\nThe following errors occured whilst loading 044753_t1_out.xml:\n\tError: CanSAS reader: unexpected \"Idev\" unit [\\rm{Intensity} | cm^{-1}]; expecting [1/cm]\n\tError: CanSAS reader: unexpected \"Q\" unit [\\rm{Q} | A^{-1}]; expecting [1/A]\n\tError: CanSAS reader: unexpected \"Qdev\" unit [\\rm{Q} | A^{-1}]; expecting [1/A]\n\tError: CanSAS reader: unexpected \"I\" unit [\\rm{Intensity} | cm^{-1}]; expecting [1/cm]\n\n}}}",
    "reporter": "butler",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView Bug Fixing",
    "time": "2017-04-08T15:19:33",
    "component": "SasView",
    "summary": "cannot read canSAS1D file written out by SasView",
    "priority": "blocker",
    "keywords": "",
    "milestone": "SasView 4.1.1",
    "owner": "krzywon",
    "type": "defect"
}
@butlerpd butlerpd added this to the SasView 4.1.1 milestone Mar 30, 2019
@butlerpd butlerpd added Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour Incomplete Migration and removed Incomplete Migration labels Mar 30, 2019
@butlerpd
Copy link
Member Author

Trac update at 2017/04/08 15:29:55: butler changed milestone from "SasView 4.2.0" to "Milestone 4.1.1"

@sasview-bot
Copy link

Trac update at 2017/04/09 09:41:56: krzywon commented:

In changeset 527a190:

#!CommitTicketReference repository="sasview" revision="527a1907e8dcf230cf6e6cdc74ed054c69493d0a"
Loading XML files saved through no longer throwing errors. see #1018

@butlerpd
Copy link
Member Author

Trac update at 2017/05/30 03:30:49:

  • butler commented:

testing instalable of release candidate 4.1.1 from official Jenkins server indicates this is indeed fixed. Interestingly xml data plots have ugly ascii labels by default while text files have latex formatted labels. All data should plot the same. This may be because of the suggestion above that the label formatting is done by the loader rather than the plotter? That would be wrong.

At any rate this error is fixed and am closing the ticket in preparation for a final release.

  • butler changed resolution from "" to "fixed"
  • butler changed status from "new" to "closed"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Projects
None yet
Development

No branches or pull requests

3 participants