Minutes from SSS Mtg 2008-May-02 Attendees: D.Harland, G.v.Moorsel, F.Owen, J.Rochford, L.Sjouwerman, B.Truitt During the first part of the meeting Dave presented the initial plan for testing the OPT (see attached pdf file). The main points were: 1. Test only the instrument configuration portion of the program for now. 2. Wait until Monday May 5 before testing 3. Program is at this address: http://webtest.aoc.nrao.edu/rct/ 4. Issues will be tracked as subtasks of JIRA issue EVL-544. See the attached document for more details. In the second part of the meeting Lorant displayed the various catalogs he has set up for himself, including a start on a standard NRAO catalog. Scientists who wish to help test the tool, but who have not spent much time with it yet, will get a better education by speaking with Lorant than speaking with the developers. We will probably have the regular Tuesday meeting next week, at which time we can display the newest layout of the tool and perhaps see Lorant's catalogs again. David [Contents of PDF are in-line, below.] 1. Only Instrument Configuration Catalog a. Wait until Monday May 5, after 8:00am b. We'll notify you when Source Cat is ready 2. Try to make realistic setups a. We'll try hard to save your work 3. Experiment with multiple catalogs and multiple groups (if you think you'll use those for your own work) 4. Try creating configurations you know are wrong a. If system let's you get away w/ it, tell us 5. Create configurations for all EVLA receiver bands 6. Give feedback on everything you see a. Defaults, column alignments, fonts, colors, etc i . Want to make this ready for outside users soon 7. Give copy/cut/paste a workout 8. If you get together and agree on std NRAO setups, work through Lorant. Pgmrs will then need to do something special to make a particular catalog the observatory cat 9. You may suggest new features. Easy, high value, features might be added right away, others should go on wish list. 10. Reporting & Tracking a. JIRA issue EVL-544 is an umbrella task for this round of testing. All items revealed during testing will become subtasks under this umbrella task. b. Scientists can send emails to Dave who will then create issues and assign.