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

Need output of parameters to a file for later use (Trac #48) #276

Closed
sasview-bot opened this issue Mar 30, 2019 · 6 comments
Closed

Need output of parameters to a file for later use (Trac #48) #276

sasview-bot opened this issue Mar 30, 2019 · 6 comments
Labels
Enhancement Feature requests and/or general improvements Major Big change in the code or important change in behaviour Reports Concerns report functionality

Comments

@sasview-bot
Copy link

sasview-bot commented Mar 30, 2019

It would be nice to have access to the parameters of the fit as well as the errors on them in a file. Perhaps as part of the header when saving points or the way it is done for batch mode CSV file.

Request from Richard Heenan entered by Paul Butler on a gotomeeting with Steve King and Sarah Rogers

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

{
    "status": "closed",
    "changetime": "2017-04-08T15:44:58",
    "_ts": "2017-04-08 15:44:58.741332+00:00",
    "description": "It  would be nice to have access to the parameters of the fit as well as the errors on them in a file.  Perhaps as part of the header when saving points or the way it is done for batch mode CSV file.\n\nRequest from Richard Heenan entered by Paul Butler on a gotomeeting with Steve King and Sarah Rogers",
    "reporter": "anonymous",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "Reporting Enhancements",
    "time": "2012-04-05T15:03:53",
    "component": "SasView",
    "summary": "Need output of parameters to a file for later use",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView WishList",
    "owner": "",
    "type": "enhancement"
}
@sasview-bot sasview-bot added this to the SasView WishList milestone Mar 30, 2019
@sasview-bot sasview-bot added Enhancement Feature requests and/or general improvements Incomplete Migration Major Big change in the code or important change in behaviour Reports Concerns report functionality and removed Incomplete Migration labels Mar 30, 2019
@butlerpd
Copy link
Member

Trac update at 2012/04/05 18:24:58: butlerpd commented:

Here is another option. This is a sample ASCII file output from FISH:

T 1 P 6 S 1 C 0 N 0
W 1 K 0 IP 1 MS 1 IY 0 0 0 XB 0 0 121 3 3
Gaussian coil for polymers
1 14 1 Const 5.105376E+01 4.866E-01 1.0 6.02E-01
2 14 2 Rg 6.268164E+01 3.913E-01 1.0 8.38E-01
3 3 11 BKG A -2.378664E-01 1.054E-02 1.0 -4.65E-03
4 15 51 SMEAR 0.000000E+00 0.000E+00 0.0 0.00E+00
5 15 2 NSIMP 2.100000E+01 0.000E+00 0.0 0.00E+00
6 99 1 SCALE 1.000000E+00 0.000E+00 0.0 0.00E+00
1 1 67600 E CALC 2 BKG 3 POL 4 SSE= 4.547E+01

@sasview-bot
Copy link
Author

Trac update at 2012/04/05 21:26:50: jhjcho commented:

We have the report with saving as txt.
Is this ticket different from it? <jae

@butlerpd
Copy link
Member

Trac update at 2012/05/06 16:04:57: butlerpd changed milestone from "" to "WishList"

@butlerpd
Copy link
Member

Trac update at 2015/01/30 01:23:44: butler changed workpackage from "" to "Reporting Enhancements"

@ajj
Copy link
Member

ajj commented Mar 30, 2019

Trac update at 2017/01/17 13:05:47: ajj changed component from "SansView" to "SasView"

@butlerpd
Copy link
Member

Trac update at 2017/04/08 15:44:58:

  • butler commented:

We can copy parameter to clipboard as comma delimited (for xcel) or as latex for a document. The former can be pasted into xcel which puts the parameter name in the top row and the value in the bottom row. We of course could ask for lots more but with the many enhancements that have ensued since this ticket was created and the upcoming new GUI we should think carefully about exactly what we want and make a new ticket. Will close this one for now.

  • 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
Enhancement Feature requests and/or general improvements Major Big change in the code or important change in behaviour Reports Concerns report functionality
Projects
None yet
Development

No branches or pull requests

3 participants