Welcome to the home of ALMASW.Usertests. This is a web-based collaboration area for Subsystem Test Schedules, Plans, Reports, and Requirements Tracking

Table of Contents

ALMA Computing IPT

---

Testing and Requirements Clarification Status

• EXEC:
  • R1.0 - Test skipped
  • R1.1 - Partial functionality (UserAdmin) tested. Report done.
  • R2.0 - Post-R2.0 test complete. Results available on the TWiki Here
  • R2.1 - Executive internal pre-test complete. Report available Here. No Post-R2.1 User test is expected to happen.
  • R3.0 - Executive internal pre-test complete (report here). User test identified by Preben as being needed to test new features.
  • R3.1 - Executive internal pre-test complete (report here). User test identified by Preben as being needed to test new features.
  • R4.0 - Test has concluded, and report is written. It is available here.
  • R4.1 - Test has concluded, and report is written. It is available here. Details: Steve Scott completed user testing May 22-23 on the Standard Test Environment (using ALMA software, with simulated hardware) at ESO in Garching, Germany. This test looked at usability issues for the OMC. In general, this test was a success, with Steve exercising the software, and providing feedback on improvements for the OMC, as well as uncovering some bugs. Testing continues related to the GUI2 Function Based Team. Progress can be reviewed at the GUI2 twiki page: http://almasw.hq.eso.org/almasw/bin/view/EXEC/GUI2FBT. Steve has submitted quite a few JIRA tickets addressing usability issues in the GUI2 version of the software. This will continue formal improvement of the Executive.
  • R5.1 - Test has been completed and the results are available here.
  • Requirements: Available on the SSR TWiki. With operations requirements continuing to improve, Preben has started tracking ops requirements with his current development plan

• SCH:
  • R1.0 - Test complete. Report done.
  • R1.1 - Partial functionality tested. No Report yet.
  • R2.0 - No test planned. No user test required for this release.
  • R2.1 - No test planned. No user test required for this release.
  • R3.0 - Testing of the Planning Mode Simulator Completed in March 2006. This report is available: SchedSimUserTestSummary-1.pdf. Follow up testing on the GUI usability has also been completed. The appended report should be available by May 12.
  • R3.1 - Optical pointing test completed in March 2006 was able to exercise both interactive and queued scheduling. Final user test is now available: UserTestReport.mar06.pdf.
  • R4.0 - Progress continues after another iteration between Mel and Sohaila. After further testing using weather data to check the software's selection of Band 6 or Band 7 SBs, a schedule was produced which looks correct upon review by Mel. Specific modifiable criteria were used in order to test one feature at a time of the dynamic scheduling process. For example, 345 GHz was scheduled in preference over 240 GHZ SBs (see attached graph jan_graph.pdf below) by the software (as it should have been).
  • R4.1 - Andy completed Scheduling Simulator GUI testing (looking at usability and bug finding) on April 17th. A brief test report is available: http://almasw.hq.eso.org/almasw/pub/Usertests/WebHome/SchedGUIFinalTestNotes070416.txt. The report has been sent to Mel and Sohaila. This test uncovered several bugs, but otherwise the GUI is in good shape. One item that requires more development is incorporating the ACA into the simulator. Scheduling simulator testing has concluded, and the test report can be found below in the Test Reports section. This tested real world historic weather data from the ALMA site to see how the scheduler would schedule typical ALMA projects. This test confirmed the scheduling simulator software is working as expected (as in properly). With the lead developer on extended leave, it's not clear when user testing will continue.
  • R5.0 - With lead developer position vacant, minimal activity in terms of user testing is expected. There can be some user testing of the Scheduling GUI during testing at the ATF. Until a replacement is selected, little activity will be seen in development.
  • R5.1
  • Requirements: Available on the SSR TWiki. The ACA requirements discussed will be incorporated into the detailed requirements, not in the high level science requirements, as suggested. Andy will be putting them into the detailed requirements as time permits.

• TelCal:
  • R1.0 - Test complete. Report done.
  • R1.1 - Test complete. Report done.
  • R2.0 - Test Report posted. It can be found Here
  • R2.1 - Test complete. Report can be found here.
  • R3.0 - Test and report are complete. Awaiting copy of report from Philippe.
  • R3.1 - Testing and report are complete. A copy of the test can be found below.
  • Features associated with Optical pointing reduction were tested March 2006.
  • R4.0 - Features associated with holography reduction scheduled were tested during the holography integrated user test (18-22Dec06). Test report available under "Test Reports" section.
  • R4.1 - Testing has concluded, and Philippe has posted a test report. The link can be followed under the test reports part of this twiki page. Some follow-up testing is needed, once some limitations are removed (including data format, clic version, and method to display results).
  • R5.0 - As mentioned above, some follow-up testing is needed, and with increased use at the ATF TelCal testing should continue out there, under real world conditions.
  • R5.1
  • Requirements: Available on the SSR TWiki.

• Archive:
  • R1.0 - Technical test by Andreas complete. Report done.
  • R1.1 - Test skipped.
  • R2.0 - Test Skipped.
  • R2.1 - Benchmarking and XML user tests are planned to occur in Socorro. Exact date is TBD.
  • R3.0 - No user tests identified by subsystem lead
  • R3.1 - No user tests identified by subsystem lead. Basic archive operation tested during optical pointing integrated user test in March 2006.
  • R4.0 - Archive queries associated with monitor point extraction, and holography related project queries will be tested during the holography integrated user test scheduled for late March 2007. This was also tested during the light user test (18-22Dec06), whose report can be found below, under the "Test Reports" section.
  • R4.1 - The R5.0 testing includes ASA development done during R4.1, so the entry below counts for both this release and R5.0.
  • R5.0 - ASA testing has concluded, as of 2008-01-07. The scope of the test is to allow people to look at and test the portal, the user repository and self-registration, the spectral line catalogue, search the Tycho catalogue (used for optical pointing) and an image server as a demonstration. Also the user/tester feedback system. The testers are Gary Fuller (subsystem scientist), John Richer at Cambridge, John Hibbard, Paola Andreani and Martin Zwaan at the ESO ARC. Once a test report becomes available, it will be posted on this page.
    • The key points of the test (provided by Gary): ASA UT1 provided the first opportunity for a limited number of people outside the ALMA Archive subsystem to view and interact with the ASA GUI interface and user self-registration. During the tests the system was robust and stable. The component of the ASA which was most extensively tested was the UserRepository which allows user self-registration. This system performed well with no serious bugs reported or deficiencies identified. The other components tested also performed well.
    • Andy also did some limited user testing of the archiveQuery command. Results can be seen in the test report in the Test Reports section below.
  • R5.1
  • Requirements: Version 2 of the ASA requirements (and GUI requirements) have been posted, and can be found on the SSR Twiki (http://almasw.hq.eso.org/almasw/bin/view/SSR/SoftwareSubsystemsDetailedRequirements).

• CORR:
  • R1.0 - Test not needed, no hardware
  • R1.1 - No science user test needed.
  • R2.0 - No science user test needed.
  • R2.1 - Testing completed in Feb and March 2006. This was to test simulated data flow through the correlator software. Test report is available: Correlator_simulations_April11.pdf
  • R3.0 - Ideally, Ed will be able to conclude follow-up software testing by the summer, when feedback to the developer will be most useful.
  • Post-R3.0 testing: The current approach is to have user feedback from ATF testing to check Correlator software development.
  • Requirements: Tunable Filter requirements are complete. They can be found on this page, down below, as well as on the SSRs detailed requirements page.

• Sci PL:
  • R1.0 - Protopipe test complete. Report done.
  • R1.1 - Heuristics test completed. Report finalized.
  • R2.0 - 1 user (Chris Wilson) recursion test has been completed, report complete, available in PDF down below.
  • R2.1 - Technical test results have been reviewed by Lindsey and Dirk. Bandpass flagging calibration is OK.
  • R3.0 - This test is complete. Test report has been written. It is available under the Test Reports section.
  • R3.1 - This test report is complete, available below under the Test Reports section (as User Test 4).
  • R4.0 - User test is complete (User Test 4). Report is available below.
  • R4.1 - User Test 5 is complete, and the report is in rough draft form. Initial feedback from the developers who reviewed the test report is favorable. Chris expects the test report to be in final form by April 11th. This represents the first test of Single Dish heuristics, including these single dish observing modes: raster and pointing. Further information can be found on the pipeline UT5 twiki page: http://almasw.hq.eso.org/almasw/bin/view/PIPELINE/UserTest5
  • R5.0
  • R5.1
  • Requirements: Granular requirements complete and put on the SSR TWiki. ACA pipeline requirements will be incorporated by Chris, as time permits. This will be at a low priority, since the developer will not have the time to address them in the near term, anyway.

• PL-QL:
  • R1.0 - No development, no test needed
  • R1.1 - No development, no test needed
  • R2.0 - No test plan yet (but it is needed)
  • R2.1 - Test planned will consist of ITS verification of connection to the rest of the system.
  • R3.0 - No test
  • R4.0 - No test plan yet
  • R4.1 - No test plan yet
  • R5.0 - As this is being incorporated into the OMC, this should be testable at the ATF.
  • Requirements: Final version of the granular requirements is available on the SSR Twiki Here

• ObsPrep:
  • R1.0 - Test complete. Report done.
  • R1.1 - Test skipped.
  • R2.0 - Test complete. Report done. Posted on this page
  • R2.1 - Light User Test completed. Results available Here
  • R3.0 - Test complete - results are available: ObsPrepUT3Grades20060208.pdf: ObsPrep UT3 test requirement grades and ObsPrepUT3CollQuest20060208.pdf: ObsPrep UT3 collated answers to questionnaire. This test was considered successful. In general it tested the user interface, software defaulting and validation.
  • R3.1 - User test has concluded. Test report is available on this page under "Test Reports"
  • R4.0 - This test has concluded, a final test report is available. It is under the Test Report section of this Twiki page.
  • R4.1 - Testing has concluded, Leonardo is currently putting together the test report. No major issues were seen during testing. Tester reports have been discussed with the developer. A copy of the test report can be found in the Test Reports section below. As can be seen in the report, there was quite a bit of feedback provided by the testers that included bugs uncovered, as well as suggested improvements in the interface.
  • R5.0 - This user test is planned for May, 2008. There is a problem: Java 6 is required for this version of the OT. This requirement will restrict the testers to those that can run Java 6 on their computers.
    • A brief synopsis of this user test: The test will focus on the phase II part of the tool and will test some interface and usability concepts, the correlator setup tool, the exposure time calculator and possibly some other features that we are considering to include in this release. In theory the tool should allow users to set up a complete single field interferometry project. The testing will involve the novice user interface and the expert system setup view.
  • R5.1
  • Requirements: Available on the SSR TWiki.

• Ctrl:
  • R1.0 - ATF functionality tested. Report done.
  • R1.1 - Test skipped.
  • R2.0 - Test skipped.
  • R2.1 - Operator GUI test completed 2 June 05. Test report/proposal available on this page, under Test Reports -> Control
  • R3.0 - No user tests identified by subsystem scientist
  • R3.1 - No user tests identified by subsystem scientist Features associated with optical pointing tested in integrated user test March 2006.
  • R4.0 - Holography features were tested in the light user test (18-22Dec06) for this release. The test report found under "Test Reports" below details testing and results.
  • R4.1 - This version is the antenna verification branch of the software, and is being tested extensively at the ATF by both CIPT internal and external testers.
  • R5.0 - ATF testing will test the control software extensively. This includes testing being done by people outside of the CIPT.
  • R5.1
  • Requirements: The blanking/flagging document created by Jeff Mangum can be found below, under Requirements. It has been reviewed by Allen, and will provide the basis for implementing the rules in the software. There will be an FBT to address blanking/flagging. Also, there are some ACA control requirements that will be incorporated by Andy in the Control granular requirements, as time permits.

• Offline:
  • User Test 1: R1.0 - Single field interferometry - reduction & imaging. Test complete. Report done.
  • User Test 2: R1.1 - Mosaic interferometry - reduction & imaging. Test complete. Report done. Posted on this page
  • User Test 3: R2.0 - Combining synthesis & single dish data/images. Test complete.
  • User Test 4: R2.1 - Single baseline data reduction and analysis - supporting the ATF. Test complete, report is written, and available on this page, under Test Reports.
  • User Focus Group: provided focused input on the python user interface development. Completed May 2006.
  • User Test 5: Tested single dish reduction and imaging. The final test report has been written, and is available below, under the Test Report section.
  • Post- User Test 5: CASA had a beta release (version 0.5) at the end of November, 2007. This follows intensive pre-beta testing being done with the NAASC staff. There may be no more formal user tests, merely user feedback, based on CASA releases.
  • CASA has been released to 19 users, about half of them have downloaded the software. User feedback has been light so far. The next release update is planned for February, 2008. There will also be an assessment on the number of testers that can be supported.
  • CASA February update has been delayed into April. Once this release is made, there will be recruitment of the CASA Advisory Group. This group will be dedicated users/testers to provide feedback to the developers.
  • Requirements: Granular requirements adequate. Additional single-baseline requirements identified. Unclear how single-BL development will be completed in time for commissioning. The draft revision of the additional granular requirements has been completed, comments provided, and another revision is circulating.

• Integrated user tests:
  • Testing by the Science IPT continues at the ATF. As of early April, they are testing the line length corrector, antenna baselines, dynamic interferometry, and skydips.
    • Version 5.0.3 of the ALMA software is in use at the ATF. It has proven to be less robust than in the past, and this is probably due to the new version of ACS included in the software. But the users are still taking and reducing data within the software.
    • Operations improving with skydip scripts run every night, auto tuning using all CIPT software (no more engineering scripts to set up FE and BE hardware), CorrGUI^?? output to monitor scans in a convienent place (operator console), ASDM format data archived automatically, and CASA fill (with some workarounds) and analysis.
  • Other testing going on at the ATF:
    • A. Hale working to develop a prioritized list of requirements for Archive based on testing last month.
    • D. Shepherd evaluated shift-log tool with Maurizio, Emilio and Lars-Ake. Decided on needed improvements for operations and priorities for development and testing at the ATF. Operators should be able to start using the shift-log in mid- to late-April with some minor enhancements. Automatic generation of a log entry when an SB starts and stops should be available in early May. This is a high-priority request from AIV.
  • Science validation test for Single Field Interferometry occurred during the last week of February, 2008. The report is available in the Test Reports section.
    • The software was more robust than in the past, and the learning curve, including improved documentation, was not as steep. Though the ASDM was not in a usable state, and they were unable to submit an SB created by the OT.
  • The next science validation test is planned for the week of 27Jan08. There are monthly reports on ATF activitied available: http://almasw.hq.eso.org/almasw/bin/view/ATF/MonthlyReportsToManagement. These cover all ATF activities, not just computing/software.
  • Optical pointing Integrated User Test # 1: report is complete, and available: UserTestReport.mar06.pdf. Follow up testing report also available. Some final follow up testing occurred May 11th. This was needed due to an error in jlog version being installed in earlier tests.
  • Holography integrated user test # 2: small user mini-test started 2006-12-18 and ended 2006-12-22. This verified software functionality. The details can be found in the test report below (under "Test Reports" section).
  • Debra is now coordinating the schedule of ATF activities. A test schedule will be defined based on CIPT development goals. At this point, large scale (multi-day) user testing is not planned as part of the ATF's activities.
  • Look under the Test Reports section for integrated test activity (typically single day events, with test reports outlining test results).

• Requirements Management Plan:
  • Approved - 29 Nov 2004 version
  • Being drafted based on CDR2 presentation.

---

Test Schedules

Requirements

• BlankingFlagging.pdf: This is a draft document compiled by Jeff Mangum to help define consistent rules on blanking and flagging data. This is particularly geared for Control/Correlator, but can be applied anywhere ALMA data is found (telcal, quicklook, etc.)

• GUI.design.requirements.doc: Draft Exec Operator GUI interface requirements and story board layout, Version A4, 10 January 2006

• CorrTFBGranReqs20060410.pdf: Final correlator tunable filter granular requirements

• PDF files and Zip files containing PDF spreadsheets and documentation for each subsystem for R2.1
  • ExecSubSysReq21Jan05R21.pdf: Exec PDF spreadsheet (posted 21Jan05)
  • ReqSpreadsheetsR2.1.zip: Spreadsheets mapping features to HLA goals and science requirements (all subsysytems except Exec)
  • GranReqs.zip: Reference: granular requirements for all subsystems (including a draft from control, but not the final control requirements)
  • HLATwikiGoals.zip: Reference: HLA goals for R2.0 and 2.1 (taken from HLA Twiki, reproduced here for convenience)

• Excel Template for tracking science software requirements
  • ALMA.rqmts.tracking.template.xls: Excel spread sheet (updated 04 Mar 04)
  • ALMA.rqmts.tracking.template.pdf: PDF of spread sheet (updated 04 Mar 04)

• Compliance Matricies for each test cycle
  • compliance-matrix1.pdf: High-level goals for each subsystem having tests between R1 and R1.1 (updated 04 Mar 04)
  • compliance-matrix2.pdf: DRAFT High-level goals for each subsystem having tests between R1.1 and R2 (updated 04 Mar 04)

Test Reports

• Integrated User Tests
  • UserTestReport.mar06.pdf: Final report from the Integrated User Test, March 31, 2006: Observatory mode for the Optical Pointing use case.
  • test.report.txt: Integrated user test report #2 - April 2006. This is a short report on a 'spot check' of top priority issues identified during the first integrated user test.
  • holo.final.report.txt: Integrated user test for the holography use case. This test occurred at the ATF 18-22Dec06.
  • ATF_Integrated_User_Test_28sep07.pdf: Integrated user test which occurred at the ATF on 2007-Sep-28. This test looked at usability of the software, and it robustness, if the software is shipped to Chile. Debra headed up the testing, with several other testers.
    • ATF_Integrated_User_Test_20071101.pdf: Follow up user testing, done by Andy on 2007-11-01 at the ATF. This stuck to the scope of the previous, to check on software improvements since the previous test.
  • ATFreport_20080303.pdf: This test report is provided by Science IPT testers, doing single field interferomtry. High points: software was robust and learning curve has improved. Low points: incomplete ASDM was not usable and OT could not create a submittable SB for testing.
  • AIV_ATF_Computing_Test.doc: This test report is based on testing done in May 2008 at the ATF by AIV. High points: higher level of stability, and key new functionality for system verification. The CCL interface was particularly flexible, something key to AIV success.

• Archive Subsystem
  • Archive Test Report from Socorro visit 6-14 Jun 05
  • asa_ut1_report.pdf: ALMA Science Archive test report. This test occurred from 30 November 2007 to 7 January 2008. This included a small group of external users, with the final report written by subsystem scientist Gary Fuller.
  • DRSP_ATFArchive_Tests_20080310.pdf: This test occurred at the ATF on 20080310. This is testing the usability of getting project data out of the archive (using the archiveQuery command), with DRSP projects put into the database.

• Control Software Subsystem
  • Control-TestReport1.pdf: 2004 March User Test Report
  • Control.GUI.TestReport.jun05.pdf: PDF version of initial Control operator GUI test, done on 2 June 05. Debra Shepherd, Andy Hale, Alessandro Caproni, and Steve Harrington attended the test.
  • Control.GUI.TestReport.jun05.doc: .doc version of the above document

• Correlator Software Subsystem
  • Archive Test Report from Socorro visit 6-14 Jun 05: During the Archive test, the Correlator software was producing channel average and spectral data, and sending it to the Archive.
  • Correlator_simulations_April11.pdf: Test report for testing which concluded in March, 2006

• Executive Software Subsystem
  • ExecUserAdminR1dot1TestReportDraftB.pdf: User Test for R1.1 25 Aug 2004
  • ExecR2dot1TestReport7jul05DraftA.pdf: Pre-R2.1 Executive developer test. Completed on March 31, 2005
  • Steve Scott was at the ATF testing the OMC on May 10th, 2006. This is not a formal release user test, but merely an introduction on how the software interacts with the hardware. A collection of his notes are at StevesDayWithExecutiveAtTheATF.
  • R40ExecUserTest.txt: R4.0 test concluded in October 2006.
  • http://almasw.hq.eso.org/almasw/pub/EXEC/ExecRelease4_1/ExecR41UserTest.txt: R4.1 user test concluded in May 2007.

• Observing Preparation Subsystem
  • ObsPrep.TestReport1.pdf: 2004 February User Test Report
  • ALMA_ObsPrep_UT2_Report_31Jan05.pdf:
    1. January User Test 2 Report
  • R2.1 Light User Test Report
  • UT3 test reports
    • ObsPrepUT3Grades20060208.pdf: ObsPrep UT3 test requirement grades
    • ObsPrepUT3CollQuest20060208.pdf: ObsPrep UT3 collated answers to questionnaire
  • UT3dot1_Report.pdf: ObsPrep user test 3.1, which started August 3, 2006
  • UT4dot0_Report.pdf: This is the final UT4.0 test report for the OT.
    • dss.test.notes.ObsPrep.UT4.pdf: Debra Shepherd's detailed notes created during OT User Test 4
    • lk.test.notes.ObsPrep.UT4.pdf: Lewis Knee's detailed notes from OT User Test 4
  • UT4dot1_Report.rtf.pdf: User Test 4.1 report.
  • atf.ot.test.notes.29apr08.txt: Debra has done some OT testing at the ATF. These are the detailed test notes from that. She has discussed suggested changes with the developer.

• Offline Subsystem
  • Offline.TestReport1.pdf:
    1. February User Test Report (single field interferometry)
  • UserTestReport.dec04.doc:
    1. December Offline User Test (small, interferometric mosaics)
  • UserTestReport.dec04.pdf: 2004 December Offline User Test
  • Offline.Test3.Report.7july05-final.pdf: 2005 April User Test Report (PDF) (combined single-dish and interferometric mosaic imaging)
    • combined.R2.0.grades.14jun05.pdf: This is Appendix C of the report (test users' requirement audits), separated from the report with easier to read fonts (PDF)
  • test.summary.jul05.pdf: Summary of Offline user tests as of July 2005
  • Offline.Test4.Report.apr06.pdf: Offline User Test Report #4, April 2006 (focus on supporting commissioning)
  • Offline.Test5.Report.mar07.final.pdf: This is the test report for User Test 5, which occurred in Socorro March 5-9 2007
    • rqmts.final.grades.pdf: PDF of Appendix B: Offline Requirements - Grade Spreadsheets from the Test Report. Separated from the report, for readability
    • rqmts.final.grades.xls: Excel format of Appendix B

• Pipeline Subsystem
  • Pipeline.TestReport1.txt: 2004 April User Test Report
  • Test2report17Dec04.ps: PS format Second User test for Science Pipeline 17Dec04
  • Test2report17Dec04.pdf: PDF format Second User test for Science Pipeline 17Dec04
  • Test3reportPipeline.pdf: Test 3 for Pipeline (recursion test) PDF
  • PipelineTest3Report.pdf: User Test 3, report written April 2006
  • http://almasw.hq.eso.org/almasw/pub/PIPELINE/DesignReviews/Test4report.pdf: Test report for User test 4, started Jan 9, 2007, finished April 4, 2007.
    • http://almasw.hq.eso.org/almasw/pub/PIPELINE/DesignReviews/Pipeline_Test4_AppendixAA.pdf: Appendix A of the report: "Summary of Key Questionnaire Responses."
  • PipelineTest5report.pdf: Report from the Fifth Pipeline Heuristics User Test (test started 2007-12-17, ended 2008-02-13)

• Scheduling Subsystem
  • SimulatorUserTestSummary2007.pdf: This was a scheduling simulator user test which occurred over September/October/November 2007. It used historical ALMA weather data to test opacity, RMS, and wind speed to determine which SBs to schedule.
  • SchedGUIFinalTestNotes070416.txt: Brief report by Andy, based on testing the simulator GUI delivered for R4.1. This test concluded April 16th, 2007.
  • SchedSimUserTestSummary-1.pdf: April/May 2006 user test report
  • Scheduling.TestReport1.txt: 2003 December User Test Report

• Telescope Calibration Subsystem
  • http://www.iram.fr/~salome/TELCAL/CLIC/last/index.html: Test report for September 2007 user test report. This is for TelCal 4.1.
  • TelCalreport-3.1.pdf: Test Report written 2006-08-28. This is still under review by John Richer, so there may be changes (2006-12-11).
  • report.pdf: TelCal R2.1 User Test Report
  • telcal_r2.pdf: TelCal R2.0 User Test Report
  • COMP-90.00.00.00-009-A-REP.pdf: TelCal R1.1 User Test Report
  • Telcal.TestReport.feb2004.pdf: 2004 February User Test Report
  • ROnedotOneSciReqAudit

Test Plans

• Integrated User Test Plan
  • integrated.test.plan.doc: Integrated user test plan, Version A6 - MSWord document - updated 13feb06.
  • integrated.test.plan.pdf: Integrated user test plan, version A6, pdf file - updated 13feb06.
  • int.usr.test.optical.pointing.doc: Test procedures for the optical pointing integrated user test - created 15feb06
  • int.usr.test.optical.pointing.pdf: Test procedures - pdf file - created 15feb06
  • int.usr.test.holography.pdf: integrated user test 2: procedures for holography, pdf file. TWiki will not allow .doc file to be uploaded. If you want a copy in MS Word format, please e-mail Debra Shepherd.

• Master User Test Plan for R2.1
  • MasterUsertestplanR2dot116Mar05.pdf: PDF Format Master User test plan for R2.1
  • MasterUsertestplanR2dot116Mar05.xls: Excel Format Master User test plan for R2.1
  • TestCycleCompMatrices9May05.pdf: Matrices reporting tests which have either occurred, or will occur (for test cycle 2 - R1.1, test cycle 3 - R2.0, and test cycle 4 - R2.1).
  • MasterUsertestplanR2dot1_2Sep05.pdf: Status of the current user test cycle (for R2.1 deliverables)

• Integration, Test, & Support

• Archive Subsystem

• Control Software Subsystem

• Correlator Software Subsystem
  • 2.Corr.User.Test.Draft.doc: correlator user test plan draft - 21feb06, first draft created by Debra & Andy based on DOORS features - may be modified by Ed Fomalont and Jim Pisano.

• Executive Software Subsystem
  • 3.Exec.User.Test.Draft.doc: R3.0 Exec user test plan draft - 21feb06, first draft created by Debra & Andy based on DOORS features - may be modified by Steve Scott and Preben Grosbol.

• Observing Preparation Subsystem
  • 1.ObsPrep.User.Test.Draft.doc: R3.0 Obs Prep user test plan draft - used by Leondaro Testi to create the final test report.

• Offline Subsystem

• Pipeline Subsystem
  • 5.PL.User.Test.Draft.doc: R3.0 Pipeline user test plan draft - 22feb06, first draft created by Debra & Andy based on DOORS features - may be modified by Chris Wilson and Lindsey Davis. Test is designed based actual development, this plan can be used as the basis of the final report (it was created after the test plan was defined).

• Scheduling Subsystem
  • 4.Sched.User.TestPlan.pdf: R3.0 final user test plan
  • 4.Sched.User.Test.Draft.doc: R3.0 Scheduling user test plan draft 21feb06, first draft created by Debra & Andy based on DOORS features - may be modified by Mel Wright & Sohaila Lucero.

• Telescope Calibration Subsystem
  • 6.TelCal.User.Test.Draft.doc: R3.0 TelCal user test plan draft - 22feb06, first draft created by Debra & Andy based on DOORS features - may be modified by John Richer & Robert Lucas.

Use Cases

• http://www.aoc.nrao.edu/~dshepher/alma/usecases This link will take you to a collection of Use Cases (including those currently being developed), sorted according to subsystem

Operations Documents

• ALMAOperationsPlan-H2.pdf: ALMA Operations Plan (vers A 2004-06-15) ALMA-00.00.00.00-002-A-PLA
• COMP-70.00.00.00-005-A-SPE.pdf: Operations Requirements and Specification on the Computing IPT (vers A 2004-06-19)

User Test Data and Documentation

• SoftwareOperationalDocumentation: This is documentation based on the Antenna Verification version of the software.
• CurrentSoftwareVersionAtATFDocumentation: This documentation reflects the latest software installed at the ATF.
• HolographyIntegratedUserTest2006
• ArchiveAPDMTestProjects
• Scheduling user tests late 2006: this is an iterative test where Mel is reviewing dynamic scheduling output based on weather data and SBs of 2 different frequencies (band 6 and band 7)
  • jan_graph.pdf: This is the output from the dynamic scheduler using data representative of weather during January at the ALMA site
  • mar_graph.pdf: This is the output from the dynamic scheduler using data representative of weather during March at the ALMA site
  • may_graph.pdf: This is the output from the dynamic scheduler using data representative of weather during May at the ALMA site

November 2005 SSR Meeting Feature Reports

• NovSSRMeetingFeatureReports
• PMCSDoorsReports

Site Tools of the Usertests Web

•      (More options in WebSearch)
• WebChanges: Display recent changes to the Usertests web
• WebIndex: List all Usertests topics in alphabetical order. See also the faster WebTopicList
• WebNotify: Subscribe to an e-mail alert sent when something changes in the Usertests web
• WebStatistics: View access statistics of the Usertests web
• WebPreferences: Preferences of the Usertests web (TWikiPreferences has site-wide preferences)

Notes:

• You are currently in the Usertests web. The color code for this web is this background, so you know where you are.
• If you are not familiar with the ALMASW collaboration platform, please visit WelcomeGuest first.

Web	ALMASW Site Map	Use to...
Main	Welcome to ALMASW... Users, Groups, Offices - tour this expandable virtual workspace.	...get a first-hand feel for TWiki possibilities.
TWiki	Welcome, Registration, and other StartingPoints; TWiki history & Wiki style; All the docs...	...discover TWiki details, and how to start your own site.
ACA	Atacama Compact Array	rehearse your Japanese skills
ACS	ALMA Common Software	...collaborate on ACS design and development.
ATF	ALMA Test Facility	.keep record of ATF procedures, on-going activities, known problems, etc.
Archive	ALMA Archive	...collaborate on
CONTROL	ALMA Control Software	...control
CORR	ALMA Correlator	...correlate on several topics...
EXEC	EXECUTIVE subsystem web	...professionally execute without pain
HLA	High-level analysis and design workspace	Discuss issues, track actions and progress, schedule meetings.
ITS	Integration, Test and Support
JAO	JAO Computing Group
MNGPUB	ALMA Computing Management Public Web
OBOPS	OBservatory OPerations Support (software)
OBSPREP	ALMA Observing Preparation subsystem	...collaborate on the design and implementation of the Observing Preparation Software System.
OFFLINE	ALMA Offline Data Reduction & Analysis	...collaborate on development of the offline system
PIPELINE	Pipeline subsystem	...collaborate on pipeline subsystem development.
SCHEDULING	dynamic scheduler
SE	Members of the Software Engineering group can enter their frustration and voice their discontent here.	Discussion, action items for SE issues
SSR	ALMA Science Software Requirements	... making sure we build the software ALMA needs ...
Sandbox	Sandbox test area with all features enabled.	...experiment in an unrestricted hands-on web.
TELCAL	Telescope Calibration subsystem	...collaborate on developing the Telescope Calibration subsystem
Test	pippo	...collaborate on
Usertests	information, schedule and reports on user tests
You can use color coding by web for identification and reference. This table is updated automatically based on WebPreferences settings of the individual webs. Contact mzampare@eso.org if you need a separate collaboration web for your team. See also AdminToolsCategory.

Legend of icons:

= Go to the home of the web = Search the web

= See recent changes in the web = Subscribe to get notified of changes by e-mail