July 16^th, 2001 APT Visit Planner Meeting at 3:00pm in N310

Please send email to apt-vp@stsci.edu for any comments or corrections about these minutes.

Attendees

Requirements Draft

Continue Issues Discussion from Last Week

Although links are not explicitly mentioned in the APT requirements, Rob and Gary will be considering how edit and display groups of objects in the APT framework which includes links.
Also, the spreadsheet editor will be able to manipulate links either as special requirements on visits or otherwise.

^th

Miscellaneous concerns and issues.

Here are points that came up in our subsequent discussion. I had trouble keeping up with all the ideas, so I would much appreciate anyone sending me more ideas not recorded here or any elaboration that you feel is important to be shared.

Some tool interact immediately with the spreadsheet such as using the VTT to set the orient.
Others wait for a calculation to be done after pressing a button such as the ETC for computing an exposure time.

We have a concern about users modifying data in the spreadsheet that have nothing to do with the current tool, but impact other tools. Should the spreadsheet editor be able to set certain fields to read only if the fields are not used with the current tool.

A related concern is the impact of data changing while running one tool (either changed by the tool or the user) that impacts other tools. (This will be discussed at the APT framework review.)
The concern is not so much whether or not the other tool knows that data has changed because APT is designed for this. The concern is that the user needs to be made aware that the other tool needs to be rerun.

Improvements that the VP will give over RPS2 are improvements to speed, usability, the ability to easily add or remove constraints.

There was much talk about having separate VP and orbit planner tools.
There is significant interaction between them through the SCHED parameter and the target visibility data.
But, it is certainly not clear what alternatives would work better.

Our next meeting will be Monday, July 23^rd at 3:00pm in N310.

Information about the APT Visit Planner Project is available at

http://ra.stsci.edu/apst/apt/apt-visit-planner/

Agenda (minutes)

Please send email to apt-vp@stsci.edu if you would like to add anything to the agenda.

Requirements Draft

Continue Issues Discussion from Last Week
Issues from use case handout ( http://ra.stsci.edu/apst/apt/apt-visit-planner/meetings/meeting-2001-07-02.html#usecases )
- Modifying constraints
- Context changes (How does the OPT handle this?)
Other issues
- What happens when a visit is modified either when the VP is the current tool or not? (How does the OPT handle this?)
- Would the user like to select which constraints to check?
- What happens if the orbit structure is modified?

Information about the APT Visit Planner Project is available at

Back to APT Visit Planner Page.

July 16th, 2001 APT Visit Planner Meeting at 3:00pm in N310

July 16^th, 2001 APT Visit Planner Meeting at 3:00pm in N310