-
Please send email to
apt-vp@stsci.edu for any comments or corrections about these
minutes.
- Attendees
Jesse, Leslie, Tony, Steve, Chris, Tricia, Rusty
- Tony has stepped in as our Spike Expert.
- 00.3
We concluded we should just highlight the visit row in the
spreadsheet corresponding to which SWC is selected. We can make
it more sophisticated if there is a desire for it in feedback
in the first release.
- Target Visibility
The behavior will be to get data from the Orbit Planner if available.
If the data is not available from the Orbit Planner, then we'll use
a default value for the SCHED parameter and give the user an obvious
warning about what is happening.
- Printing
The Spike GUI has a verbose option to print all data or print only
what is displayed.
For now, let's have a requirement to print everything and get user
feedback to refine the requirement.
- Computation Requirements
When the user switches to the VP, the computations should be
immediately updated. If any changes are made while the VP is the
active tool, then the computations are updated only when the user
presses the update button.
- Minimum Requirements
- We should include roll range reports.
- The requirement for handling target visibility should be
included.
- HST Specifics
We should mimic RPS2. In general, we'd like to display only
those constraints which are not suitable all the time.
- Chris will be running the show for the VP requirements at the next
APT requirements review. I'll need to get a "final" version of the
requirements to him as well as mock ups. And, I'll need to come up
with a reasonable justification for delivering in June.
-
We will discuss HST specific requirements next week; everyone should
consider what we need to specify for supporting HST that is not part
of the general Visit Planner requirements.
- Our next meeting will be Monday, August 20th at 3:00pm in N310.
- Information about the APT Visit Planner Project is available at