You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if the result of the batch slicing (1D I(Q) or I(phi) etc.) shall be plotted for all selected graphs in one 1D plot window, one first has to first save them, second, select them in the data explorer, third plot them together
---> this is very unintuitive, gets messy for too many graphs in the batch, and is therefore not very practical
(ii) Still missing options and improvement ideas:
allow a "batch plot" in the batch slicer window to directly plot all 1D graphs in one window (see also Batch Slicing plotting #2067)
make this possible for not only I(Q), I(phi), but also as function of any sample environment parameter (e.g. to plot box sum intensity of several graphs versus rocking angle) (see issue Utilizing Metadata from NXcanSAS data files #2083)
Discussed during the code camp: Before it should be decided on moving the batch slicer option, following should be done first:
Step 1 - Jeff inserts the trend-option for sample environment parameters (or any other trend a user would like to dsplay)
Step 2 - for such a trend open the possibility to batch plot - i.e., having all plots in one view with tabs for opening the other graphs of that trend (Lucas comment: dynamical insert, not having all open at the same time)
--> with batch slicing all plots of one trend, and then plotting the resulting 1D curves alltogether in one plot, or also opening the possibility to plot as funciton of trend parameter
Step 3 - Annika will change the current slicer option to
Step 4 - test if then the current batch slicer needs to be improved and/or shifted to perspectives
In this issue I ...
(i) test the functionality of the current batch slicer and report problems.
(ii) raise still missing wishes on this option and raise improvement ideas
Here the results:
(i) Current batch slicer problems:
---> this is very unintuitive, gets messy for too many graphs in the batch, and is therefore not very practical
(ii) Still missing options and improvement ideas:
The text was updated successfully, but these errors were encountered: