Generalize 1D and 2D data (Trac #719)

[sasview-bot]

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

{
    "status": "new",
    "changetime": "2017-10-27T17:33:33",
    "_ts": "2017-10-27 17:33:33.714602+00:00",
    "description": "Currently, 1D data is specifically x->q and y->Iq, but it need not be.\nthe data types should be made as general as possible, so that new 1D data formats can be added in more easily. \nThis is most directly  applicable to SESANS integration, but also for future flexibility of Sasview.",
    "reporter": "jhbakker",
    "cc": "",
    "resolution": "",
    "workpackage": "SESANS Integration",
    "time": "2016-10-07T01:16:43",
    "component": "SasView",
    "summary": "Generalize 1D and 2D data",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView 4.3.0",
    "owner": "",
    "type": "enhancement"
}

[ricleal]

Trac update at 2016/10/09 17:10:56: ricardo commented:

Xarray (http://xarray.pydata.org/) being labelled arrays with metadata might be a viable option.
See example here: https://github.com/ricleal/PythonCode/blob/master/Xarray/Xarray%20tests.ipynb

[butlerpd]

Trac update at 2016/10/13 02:14:55:

• butler commented:

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.

• butler changed milestone from "SasView 4.1.0" to "SasView 4.2.0"

[butlerpd]

Trac update at 2017/10/27 17:33:33: butler changed milestone from "SasView 4.2.0" to "SasView 4.3.0"

[butlerpd]

@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?
Will move to wishlist for now.

[krzywon]

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.

[smk78]

@wimbouwman comments

I don’t expect in the near future any 2D data.