Run All Issues

These PR's were grouped together in one study because they described user issues with processing with multple tools and/or selections.  The actions referred to are described below.

48682 Investigate making OP, VP and RunAll opsconcept clearer

Summary:  Users think that the orbit planner will process all selected visits.

Addressed by Action(s):  1a, 1b, 1c.

 
50282 Create an "Autofill All" option

Summary:  Processing all visits through the OP is easy via Run All, but autofilling all visits is a pain.

Addressed by Action(s):  1a, 1b, 1c, 2.

 
50667 Find a way to allow subset of tools to be run on a group of visits

Summary:  For large proposals, it can be a real waste of time and memory to run all the visits through the visit planner when you just wanted orbit planner output.

Addressed by Action(s):  1a, 1b, 1c. 

 
50785 RunAll doesn't do anything if you are below the visit level

Summary:  Users aren't clear about what Run All will do, and don't realize that they need to select which objects it will apply to.

Addressed by Action(s):  3, 4.

 

Proposed Actions (3-4 weeks effort)

Since the first 3 PRs above involve various problems running the Orbit Planner, we (Gary, Jesse, Rob and Tom) decided to upgrade the Orbit Planner in several ways rather than add a lot of complexity to the more general Run All function.  We suggest the following actions to address the above PR's:

  1. Independent of Run All, the Orbit Planner should be able to process multiple visits.

    1. (0w) Just like today, when a visit or visit descendent is selected in the hierarchy, the Orbit Planner will treat that visit as the current visit.  That visit's orbits would be displayed, and the Orbit Planner buttons would apply to that visit.  Also like today, when a target or other non-ancestor of a visit is selected, the Orbit Planner's current visit will remain unchanged.

    2. (2w) When multiple visits, or a visit ancestor, are selected in the hierarchy, the Orbit Planner will not display any particular visit's orbits.  Instead it will display a list of the selected visits, and whether each is up-to-date with respect to the Orbit Planner.  The Orbit Planner buttons will apply to all selected visits. Selecting exps would still select that visit.

      Examples:

      1. If visits 01, 02 and 03 are selected, the Orbit Planner's Auto-Adjust button will auto-adjust visits 01, 02 and 03. 

      2. If the Proposal is selected, the Orbit Planner's Clear Orbit Numbers button will clear the orbit numbers for every exposure in the proposal.

       

    3. (1w) The Orbit Planner will avoid sending visit data to Trans for up-to-date visits.  This has always been an efficiency issue with Run All.  It may be more important with multiple visit processing.  (See PR 51097.)

    4. (1d) Ideally, the orbit planner will give some indication of what it is doing while processing multiple visits.

  2. (1d) The Orbit Planner will add support for command-line auto-adjust runs.

  3. (2d) When visit decendent(s) is/are selected in the hierarchy, and Run All is clicked, the Orbit Planner will run on the visit(s) containing the object(s).  There will be no support for Auto-Adjust or other Orbit Planner functions via Run All.

  4. (1d) Clicking on Run All will result in a pop-up message summarizing what the Run All will do (i.e., what tools will be run on what objects) with an option to proceed or cancel.  Also, rename the Run All button to Run All Tools.

 

New Related PRs

51096 OP should be able to display mulitple visits.
51097 OP should avoid sending data to Trans for up-to-date visits.