-
Notifications
You must be signed in to change notification settings - Fork 41
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
Generalize 1D and 2D data (Trac #719) #841
Comments
Trac update at
|
Trac update at
Jurrian says this is partly done but more work is required if this is to really be achieved. Moving this to 4.2 rather than closing at this point.
|
Trac update at |
@krzywon. Can you comment on this? should we close this in favor of other issues that cover similar ground (such as your universal units project)? etc or should we leave this open under wishlist for doing things like incorporating DLS fitting (and/or NSE) which would be g1r or I(Qt) vs tau? |
The goal of this ticket is to incorporate 1D and 2D data into a single class that replaces the Data1D and Data2D classes. This would require many changes to how data is handled and treated not only in sascalc, but in the gui as well. Wish list is the right place for this for now. |
@wimbouwman comments
|
Currently, 1D data is specifically x->q and y->Iq, but it need not be.
the data types should be made as general as possible, so that new 1D data formats can be added in more easily.
This is most directly applicable to SESANS integration, but also for future flexibility of Sasview.
Migrated from http://trac.sasview.org/ticket/719
The text was updated successfully, but these errors were encountered: