Next Meeting:
Thursday 11 January 2001 at 11AM

Status of wrapperAPI
Masha has run wrapperAPI on Beowulf (development system with 16 nodes). Specific user accounts have been added to the system for running multiple jobs. These are being configured today. Will run several users this afternoon. Documentation is almost complete; the PERCEPS problem still is unresolved. WrapperAPI is in very good shape for the MDC. Excellent.

Status of wrapperPI
Phil has checked that it works with 2 simulataneous user commands. The pipeline has been checked including shipping of results to a stub representing the EventMonitor API. Discussion of data ingestion also occured; pessimism that the DC API will be capable of ingesting from an file and writing to the wrapperAPI.

Status of inspiral dso
Duncan reported that he has been working towards the LAL 0.6 release by documenting and inserting the binary inspiral search functions into the latest release. Jolien gets back on 8 January and we will have a release on 10 January. Modifications discussed last week have not yet been done, but he will have them finished by the time he leaves for Caltech on 9 January 2000.

Status of excess power dso
No progress to report. There was some discussion about the possibility of Warren going to Caltech, but he did not think he would have the time.

Any other business
The plan for the MDC is now available on the web page. There are 13 major tests each with subtests explained via a checklist. The entire MDC will be documented and logged into a CVS archive. The test checklists for each stage of the MDC should be updated by the responsible individuals once the document is available from CVS. Moreover tests should be scripted as much as possible; where appropriate, LDAS user commands should be used to test the functionality each component the MPI MDC.

Kent asked about the status of the user commends for running jobs. Phil explained that there is a fully functioning user command which meets the baseline requirements. It can handle input data, template file, shared objects options, ouput options, etc.

Kent commented that there should be a subsection at the end of each test which will contain recommendations upon execution of that test. This will probably include things like: reasoning behind proceeding to the next test of some failure is encountered in a given test, reasoning for spending effort on development during the MDC even tho it slows progress with the test, and recommendations for future development/work.

There was extended discussion of the LDASMDC CVS repository. In particular there were questions about its location in the short and long term. There will be a need to coordinate TAGS between the LDAS, LAL, LDASMDC and LALWRAPPER. This needs to be ironed out. Corrdinate with Isaac Salzman to develop the test scripts, etc.

The MDC will be executed via an LDAS user account called mpimdc. Two systems should be available:

• ldas: for development work. This is the 16 node Beowulf that was purchased recently. The gateway is ldas-dev - the manager API will run on this machine. It can receive LDAS user commands from anywhere.
• ldas-test: for the actual tests. Currently under reconstruction in SRL. Should be available for the MDC.

Finally, the next meeting will be Monday 8 January at 11:00am PST. The standard meeting will also proceed on Thursday 11 January at 11:00am PST.