Next Meeting:
Thursday 26 April 2001 at 10AM PST

Open Problem Reports Status Patrick started by reminding people that the list of open bugs should be addressed as soon as possible. We should be looking to have them fixed in the next release.

1. LDAS 625: mpiAPI stdout/stderr logging -- Phil
   Still plans to get to it ... he has an idea for dealing with it.
2. LDAS 806: build_process documentation for wrapperAPI - Kent
   Ed Maros will be assigned to it.
3. LDAS 782: wrapper spec for spectrum::sequence allows ilwd and LAL structures to be internally inconsistent - Kent
   Kent and Sam Finn agreed to keep degeneracy but specify canonical data which prevents this happening.
4. lal 11: Failure to allocate new memory causes SIGSEGV reported by libinspiral.so. - Duncan
   Duncan will have this fixed by next Thursday.
5. lal 2/3: documentation of codes - Patrick and Duncan
   Underway. Inspiral documentation will be done by inspiral MDC. Alan, Jolien, and Patrick will help Duncan if necessary.

Status of the pipeline from frames to the database
Phil reported that there had been some major modifications to insure that the frameAPI can read arbitrarily created frames. Most of his effort has been directed at this during the past week. He just started working on the mpiAPI to deal with the logic of node allocation. He is going to use a scoring method to insure that jobs never run out of nodes. Should have this done next week.

Several frames have been created with ramp channels in them Phil will post location to the mpiteam so that people can get them if needs be.

They have verified that each API (up to the wrapper) gets the data and mangles it correctly by printing it out to file at each stage. This is great. This facility will be available at the next MDC.

Masha reported that her part of the event monitor is complete. She has been waiting for a shared object to check with. Duncan indicated that the inspiral shared object should now work. Masha will try it and see if the output gets into the database. Masha reported that Ed Maros is re-writing his code to use resource files for description of the database tables -- this seems like a good idea.

Status of FCT code
Linqing reported that she has a working skeleton of the FCT code. She is ready to start putting in LAL stuff and will work with Patrick to get the wrapped client into LALwrapper. Documentation does not yet exist. Minimal documentation will exist by the time of the MDC.

Status of inspiral code
Duncan reported on the hierarchical inspiral code. He has updated the buildOutput() function to deal with BLOBs correctly. After discussion with Patrick on Tuesday, he is ready to code the hierarchical part of the code. He expects to have working code next week and will document it after that.

Status of stochastic code
Warren reported that the stochastic code is evolving. He has something ready to go, but has been working on cleaning up the directory structure for inclusion into LALwrapper. He will have a skeleton by the code freeze on May 1.

Other issues
Masha also thinks she has the latest version of LAM working to buiuld shared object libraries. There is still some problems with the C++ code, but she's trying to build a patch for that. Hopefully it will be available by next week.