Minutes of the LSUG Teleconference
Thursday, 27 February 2003  (10:00PST)
Attendance:  Stuart,  Kent,  Matt,  Jolien,  Patrick,  Igor,  Erik, 
Philip,  Jordan,  Greg,  

LDAS:
        0.2 % failure rate at the sites.  Made headway on MPI -- and
        frameAPI core dumping not sorted.   Still some problems with
        performance.  For now,  we'll stick with what we have for now.
        
        
S2 data distribution:
        First successful staging of data with sanQFS.  They will keep
        testing and hope  to get started with RDS generation soon.  They
        are going to try to get ldas-jobs system up and running at CIT. 
        There is an issue in channel lists being different for the two
        sites generating the RDS tools.  They do not know what lists
        they are using:  philip, Igor, Greg need to change.  
        
        Stuart will move ndas frames over to samQFS also next week and
        we can start moving things that way.  
        
        Long discussion of bug in Igor's RDS generation at LLO.  Igor is
        filling gaps manually.  Once sure things are working,  he'll
        update his running scripts.   
        
        Need a bug report:  Igor is in charge of opening the bug report.
        
        Catch up:  wait until Monday to decide about how to deal with it
        and decide what to do.  
        
        
Updating LALWrapper:
        Changes to waveBurst and blockNormal.  New versions of LAL and
        LALWrapper will be tagged and pushed ldas-test and version
        pushed to the sites Friday (or as as possible afte that).  
        
        
Run Plan:
        Greg will need two (2) nodes at LHO for his known pulsar demod. 
        It was agreed that he should go ahead with that.   He was
        worried about frameAPI seg faulting.   Will wait until the new
        release of LDAS with fix.   
        
S2 playground data:
        somebody needs to send Stuart a set of GPS times.  Sensemon
        frames and segment tables.  
        
        
Pre-run Injection data:
        Action to figure out where the data is for calibration during
        the pre-run.   Send e-mails.   
        
        All injection data from both LHO and LLO.

Patrick Brady