Ticket #9131 (assigned)

Opened 7 years ago

Last modified 5 years ago

SANS Diagnostic Time Integral default value

Reported by: Gesner Passos Owned by: Peter Parker
Priority: major Milestone: Backlog
Component: SANS Keywords:
Cc: Blocked By:
Blocking: #2687 Tester:

Description

  • Open SANS Interface
  • Go to Diagnostic Tab
  • Browse: systemtests/Data/SANS2D/SANS2D00002500.nxs
  • Click on TimeIntegral

Nothing happens.

The issue is that no operation is given to the range.isEmpty() inside TimeIntegralClicked. (compare with IntegralClicked).

The default operation should just call SumSpectra with all the default values, except IncludedMontitors=False.

Change History

comment:1 Changed 7 years ago by Gesner Passos

  • Blocking 2687 removed

(In #2687) As first step, it should implement #9131. Give the TimeIntegral a default operation.

The second step is to correct its behavior, or at least, document that it behaves differently from the previous 2 commnads. HorizontalIntegral and VerticalIntegral defines the ranges as Columns and Rows. While, TimeIntegral uses the input as spectrum numbers + the first spectrum of the bank. Hence, you can plot the TimeIntegral of 36864, but you can not plot VerticalIntegral of 193.

It is first necessary to ask Richar and Steven what they want. Do they want to sum the time channels for boxes (as suggested in the description of this ticket), for lines and for rows? Or they want to be able to access spectrum directly?

BTW, the time integral seems to be useless given that we have this functionality in InstrumentView, with much better user interactivity. This should be discussed as well.

comment:2 Changed 7 years ago by Gesner Passos

  • Blocking 2687 added

comment:3 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

comment:4 Changed 7 years ago by Nick Draper

  • Owner changed from Gesner Passos to Peter Parker

Ownership handed over to Peter

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 9974

Note: See TracTickets for help on using tickets.