Ticket #11402 (assigned)

Opened 6 years ago

Last modified 5 years ago

In autoreduce, the last variable settings used in a reduction should count as the 'new defaults'

Reported by: Lottie Greenwood Owned by: Lottie Greenwood
Priority: major Milestone: Backlog
Component: Framework Keywords:
Cc: anders.markvardsen@… Blocked By:
Blocking: Tester:

Description

Currently if a variable is set as 'a' in the default reduce_vars.py script, and then changed to 'b' for x runs, if you then change variables for x+1 runs onwards, it reverts back to 'a' again. Ideally it would instead default to 'b' at this point, because the users will not want to reset all the defaults back to their own configuration just to change it slightly.

Make it so the new default settings for an instrument are whatever the edited runs previously had.

Change History

comment:1 Changed 6 years ago by Lottie Greenwood

  • Status changed from new to assigned

comment:2 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​12241

Note: See TracTickets for help on using tickets.