Minutes from 1 December 2009

2009/12/01 CSEP Meeting

Attendees: John Y., Masha L.


  1. csep-op:
    1. NFS server:
      • John will consider available options beginning of next year
      • 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. V9.10.1 release:
      • Running since 2009-11-09
      • No problems
  2. Software development:
    1. Code freeze for V10.1.0 release candidate is Monday, December 7, 2009
    2. John suggested to use VirtualMachine to distribute CSEP software
      • Will need to have different images for different testing centers due to the installed forecasts models
    3. Yan sent out an announcement about "FULL EARTH HIGH-RESOLUTION (0.1x0.1 degree) EARTHQUAKE FORECASTS"
      • Using PDE catalog
      • Will discuss integration of the forecast within CSEP
    4. DONE Trac #190 Isolate source code of installed forecasts models to testing region sub-directory
    5. Trac tickets to address for V10.1.0:
    6. Alvaro Gonzalez submitted two one-day alarm-based models for WPacific and Global regions
    7. DONE Trac #177 XML format of forecast should still be passed through master XML template
      • Discovered a problem when validating EAST forecast on csep-cert:
        1. Trac ticket #195: XML format of the EAST forecast provides wrong value for defaultMagBinDimension
        2. Sent email to Peter Shebalin to approve suggested work around
      • Automatically reinterprets XML forecasts to use [-180;180] range for longitude
        1. Generic implementation to affect all testing regions of all testing centers
        2. Jeremy approved re-interpreted SW Pacific one-year Triple_S forecast
  3. From 2009/10/06 meeting: Fabian presented slides for new implementation of CSEP results web viewer
    • Proposed to use Django based on Model-View-Controller paradigm
    • Split results viewer into:
      • web service for CSEP data products (maps, XML results datasets)
        • Use Database to store CSEP results by Dispatcher
          • John pointed out that it might be redundant to split already available XML results for injection to the database, then reconstruct XML from the database
          • John pointed out that would need to inject already existing data into the database
          • Masha is worried about making it error-prone due to the reprocessing
          • Very minimal work on operational CSEP software if only need to change to publish XML results vs. SVG plots
          • Fabian could work on implementation
          • Danijel suggested to create tests summaries by Dispatcher
            1. Masha suggested to implement visualization of the summary on web server site by CSEP Toolkit modules
      • interactive web application to present data products
        • Danijel asked about authentication for Japanese viewer
          • John suggested to use Apache's one
      • Danijel asked if it shold be integrated into Drupal?
        • John suggested to try a simple example to see if it works
      • James asked why not to use Plone
        • John said that we used to use Plone, but migrated away from it, but may be should investigate more
      • John asked how to discover what is available:
        1. Danijel suggested to use URL queries to discover
        2. Masha suggested that Dispatcher could update already existing configuration files for forecasts groups with current forecasts filenames and publish it as well
        3. John suggested to use allmodels.xml that current web viewer has
  4. 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