Minutes from SSS Mtg 2009-Feb-17
Attendees: B.Butler, M.Claussen, D.Harland, E.Momjian, G.v.Moorsel,
J.Ott, J.Rochford, L.Sjouwerman, B.Truitt, S.Witz
Proceedings
The first thing we did was review the status of the items we discussed in last week's meeting. The status summary is given in the next section, below. After that people brought up issues one by one as follows.
Bryan noted that once we have single sign-on, when the user elects to quit the OPT / RCT / SCT, the user should be brought back to the my.nrao.edu portal.
Lorant suggested what the Submit button should trigger in the event that 1. the scheduling block (SB) is perfectly formed, 2. the SB has warnings but no errors, 3. the SB has errors. For case 3, the Submit button should refuse to submit. For case 2 it should submit, but reiterate to the user that the SB has some minor problems.
Lorant noted that in the RCT if one types in a unitless value for a frequency "Hz" is assumed. "GHz" is a better default. He also noted that the warning that a frequency is out of the receiver's range does not appear until some other field is accessed or the catalog is saved.
Lorant noted that Edo, one of the two outside testers, longed for and "Undo" button.
Bryan noted that once we update webtest, which will be done tomorrow morning, we should encourage our two testers to use the Submit button. Once their observations have run on Friday we can update the OPT et al with single sign-on logic.
There was a discussion about what to do when a pointing scan or tipping scan does not use all the time alloted to it. Right now a pointing scan will repeat until the next scan is scheduled to start, while a single tip will be performed, even if time allows for multiple tips. No action for the OPT crew came from this discussion.
There was another discussion about tipping scans, this time focused on the azimuth to use. Lorant suggested it might be nice to be able to tell the tipping scan to start on the azimuth at which the telescope is currently pointing -- ie, from the previous scan. Bryan pointed out that in A & B configuration not all azimuths are ideal, due to shadowing of one antenna by another. Lorant also suggested an order-of-elevation option of "I don't care" in add'n to down-to-up and up-to-down. The third option would be a signal to use the closer elevation, min or max, to the current telescope elevation.
Bryan noted that there will be a PST post mortem on Thursday at 9:00am.
Updated Status for Last Week's Items
Numbers below are from last week's Preparation for SSS Meeting of 10 Feb 2009 document.
1. Printing of scheduling block summary. Done.
2. Dragging of scans. Still an issue. We've sought help from the Icefaces group (third-party software in charge of this feature).
3. Fly-over help. Removed fly-over from tree component on left of screen. Remaining: dealing w/ help extending beyon right edge of browser.
4. Starting position in sched block for scheduling scans. User interface work done; model support not started. JIRA issue EVL-796.
5. Cal codes in SCT and exec script. Not yet started.
6. Hard-copy user manual. Status?
7. Displaying and editing differences in OPT vs catalog tools. Nothing done here.
8. Add frequency columns to resource summary table. Done.
9. Speed of application. Nothing done here.
10. Max separation of IF pairs. Done.
11. Display of extended receiver band ranges. Done.
12. Use conversion path if either IF < 32GHz. Done.
13. Prog block validator and sum of SB times. Nothing done here.
14. Disable assumed sched start for fixed date SBs. Done.
15. LST & UT precision in SB details. Begun, but on hold.
16. Duplicate names in VLA catalog. Nothing to do.
17. Update script logic for new tipping style. Done.
18. Scan to use hardware config of previous scan (FIN card) User interface work done; model support not started. JIRA issue EVL-797.
19. New icon for new, blank, scans. Not yet started.
20. Users to suggest tips & tricks to Lorant.