Minutes from 16 February 2010

2010/02/16 CSEP Meeting

Attendees: Phil M., Danijel S., John Y., Masha L.

1. csep-op:
   1. From 2010/01/26 metting: Performance issue due to new NFS server:
      • John wants to try separating testing regions to different disks
        1. Masha said it's OK since all testing regions are independent from each other
   2. John will respond to new web requests to participate in CSEP, and will add applicants to 'csep-all' mailing list
      • Masha will use the mailing list to announce new CSEP releases
   3. USC Matlab license R2009b got picked up by nightly processing on csep-op (since 2010/01/26)
      • Dispatcher for Global one-year forecasts groups is still running
   4. V10.1.0 is running on csep-op as of 2009/01/08:
      • DONE: Trac #207 Inconsistent number of events for 2009-10-03, 2009-11-03, 2009-12-03 observation catalogs of RELM-Mainshock group
2. From 2010/01/26 meeting: Jeremy had a discussion with Peter Shebalin:
   • Should run alarm-based evaluation tests for EAST (alarm-based) model against EEPAS and PPE David Rhoades models (rate-based)
     • Masha responded that EAST model has a single magnitude bin vs. rate-based models having multiple magnitude bins
     • Jeremy said that alarm-based tests won't work then
     • Jeremy will get back to Masha regarding alarm-based tests for alarm-based model vs. rate-based model
3. From 2009/12/15 meeting: Phil suggested to use iRODS as data management for CSEP:
   • John will look into it some time early January
   • John suggested to use VirtualMachine to distribute CSEP software
     1. Will need to have different images for different testing centers due to the installed forecasts models
4. Software development:
   1. Priorities for V10.4.0 release:
      • Self-discovering web service
        1. Danijel pointed out an importance of unifying presentation of all testing centers results
        2. Phil suggested to provide simple client as an example on how to retrieve data with new service
           • John suggested to use wget (on Linux) or web client (on Windows)
        3. John described new web service as a Python script driven by Apache (to be decided) that will use self-discovering approach on available within Testing Center:
           • Geographical regions
           • Forecasts groups
           • Models within each group
           • Test type
           • Summary reports
           • Data format
      • #209 Add per event and sum of true log-likelihoods to L, S and M RELM evaluation tests results
      • DONE #185 Generate summary tables per each evaluation test
        1. Should add support to the current results viewer web site
      • Get rid of remaining Matlab codes:
        1. #68 Adopt QuakeML format for catalog data
           • Masha contacted Fabian about status of QuakePy
           • QuakePy does not have support for applying catalog uncertainties
        2. #51 Consider rewriting/invoking Fortran declustering code in Python
   2. New models
      1. Max will submit ETAS model for California some time in March-April 2010
      2. Matt promised Java version of STEP to be available for the installation within SCEC Testing Center by March, 2010
         • Matt will get back to Masha if he wants to continue testing of fixed Matlab version
   3. From 2010/02/02 meeting: High resolution Global testing region:
      1. Danijel reported that forecast template and format are being defined
      2. Yan sent out an announcement about "FULL EARTH HIGH-RESOLUTION (0.1x0.1 degree) EARTHQUAKE FORECASTS"
         • Using PDE catalog
         • Will integrate within CSEP when testing region is established
5. From 2009/12/08 meeting: CSEP policies
   1. Should discuss if SCEC Testing Center results should be open to the public
      • Danijel will get back to the group
   2. Danijel will work on more content for the main CSEP web pages
6. From 2010/01/12 meeting: John and Masha discussed necessary changes to support web application to view CSEP results:
   • CSEP will publish already existing configuration file for each forecast group to the web server
   • Web service will use file system discover method to identify:
     1. avalable testing regions
     2. available forecasts groups within each testing region
   • Configuration file for each forecast group should include:
     1. Base name of currently tested forecast file
     2. Flag if forecast start date is part of the forecast filename
   • John asked if CSEP Dispatchers should publish any XML format files to the web server at all:
     1. May run into problem of displaying results for not finished evaluation tests
        • May introduce a "lock" to indicate if evaluation is in progress
     2. Makes sense not to duplicate results - especially the ones that nobody is going to look at
7. Hardware:
   1. csep-cert
      • CSEPWebTest.py is not part of nightly build - some issues connecting to the web server
        1. John is looking at the problem