Batch Slicer requires plotting of all 2D data sets to use in batch (Trac #1140)

[butlerpd]

The current implementation of batch slicing requires all 2D data that is going to be included in the batch run of a slicer process be plotted (e.g. sent to "new plot" They they show up as OPTIONS to be included in the batch. This can work for small sets, but recently we tried this on a time resolved series that was binned into 90 (and could be a few hundred) 2D time bins. Having to plot all 90 is less than optimal to be kind. Ideally this should work like batch fitting where all 2D data sets that are selected in the data manager can be selected. This may or may not be something to worry about for 4.2 release as it is mostly a GUI item at this point? but if it can be done straightforwardly it would be good to fix for the release.

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

{
    "status": "assigned",
    "changetime": "2018-08-19T01:36:55",
    "_ts": "2018-08-19 01:36:55.103543+00:00",
    "description": "The current implementation of batch slicing requires all 2D data that is going to be included in the batch run of a slicer process be plotted (e.g. sent to \"new plot\"  They they show up as OPTIONS to be included in the batch.  This can work for small sets, but recently we tried this on a time resolved series that was binned into 90 (and could be a few hundred) 2D time bins.  Having to plot all 90 is less than optimal to be kind.  Ideally this should work like batch fitting where all 2D data sets that are selected in the data manager can be selected. This may or may not be something to worry about for 4.2 release as it is mostly a GUI item at this point?  but if it can be done straightforwardly it would be good to fix for the release.",
    "reporter": "butler",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView GUI Enhancements",
    "time": "2018-07-20T13:05:29",
    "component": "SasView",
    "summary": "Batch Slicer requires plotting of all 2D data sets to use in batch",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView 5.0.0",
    "owner": "krzywon",
    "type": "enhancement"
}

[butlerpd]

Trac update at 2018/08/07 14:20:47:

• butler commented:

Looks like it won't be straightforward in fact so moving to 4.3 for now and see if we get a lot of complaints that require fixing sooner.

• butler changed owner from "" to "krzywon"
• butler changed status from "new" to "assigned"

[butlerpd]

Trac update at 2018/08/19 01:36:55:

• butler commented:

Not a priority for this release. May be best to focus on this for the new 5.0 rather than waste resources on fixing this on 4.3.

Going to move to 5.0 for now.

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