Attendance: Kent, Masha, Jolien, Patrick, Joe, Warren, John, Greg,
Duncan, ....
Conventions:
-----------
One-sided spectra have been ratified. There are some minor changes to the
meta-data; some of the particular numbers have not changed. They have added
something that indicates the removal of phase or not.
Target dates: mid-November releases and 20 December for LAL and LALWrapper
and LDAS.
Task: After next release will make changes to header files and ect for conventions.
Status of libtool, LAL and LALWrapper:
-------------------------------------
Need to update howto document for these changes. When Duncan commits changes
to LAL, we should go through and check it. In LDAS, only partially
implemented to get rid of LD_LIBRARY_PATH. Duncan will e-mail Ed about how to
build wrapperAPI in standalone.
Status of the data files for ephemeris:
--------------------------------------
Jolien will look into this. FOr next week.
Periodic DSO (greg):
--------------------
After E6 for MDC. Compiling and building versions of LAL and LALWrapper will
be pushed twice a week. What are the rules and etiquet about putting things
into the test database. Which database? Kent said to use LHO_test. Greg is
working on the frac-remaining; going through to get something non-trivial.
Only submits to database once at the end. There is no advantage to returning
too often but must return every 5 minutes........ regular transfer ......
How to drive LDAS:
driver script outside LDAS. They can do this now. Peter wants to write a
slightly more complex driver script which first polls the database, etc, and
then sends a job to the LDAS system.
Further down the road. May be there by upper limits run. Store state
information in datacondAPI to avoid overlap. They do want to make sure that
they can keep persistent information about linear filtering ....
power, inspiral, tfclusters, fct, slope, ..... real-time.
Would like to have scripts written to test them on LDAS systems before the
upper limit. Within months for stochastic. Greg will be trying to run his
code soon after the run.
Assume that we will query the database and do this stuff......... Need this
table implementation. _Table_design_
Task: Will talk about driving programs.......... next week.
|