Minutes from 8 December 2009

2009/12/08 CSEP Meeting

Attendees: Danijel S., 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:
  2. Software development:
    1. Code freeze for V10.1.0 release candidate was on Monday, December 7, 2009
    2. John installed CSEP V10.1.0 release candidate packages on csep-cert today using YUM repository
    3. Masha started unit and acceptance tests for the installation
    4. 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
    5. 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
    6. DONE Trac #190 Isolate source code of installed forecasts models to testing region sub-directory
    7. Trac tickets to address for V10.1.0:
    8. Alvaro Gonzalez submitted two one-day alarm-based models for WPacific and Global regions
    9. DONE Trac #177 XML format of forecast should still be passed through master XML template
      • Masha passed Jeremy's one-year SW Pacific forecast through master XML template on csep-cert and re-ran N-test for latest processed test date
        • Number of events in KJSS and TripleS N-test cumulative test results match (34 events)
      • Discovered a problem when validating EAST forecast on csep-cert:
        1. DONE: Trac ticket #195: XML format of the EAST forecast provides wrong value for defaultMagBinDimension
        2. Peter Shebalin submitted fixes to the model:
          • To mentioned above Trac ticket #195
          • Fix to read forecastStartDate from input parameter file
        3. Masha re-generated Peter's forecast on csep-cert, Peter approved results published by csep-cert server to intensity web viewer
  3. CSEP policies:
    1. Danijel suggested to open Trac pages:
      • John and Masha confirmed that models source codes have restricted SVN access
    2. Should discuss if SCEC Testing Center results should be open to the public
      • Danijel will get back to the group
    3. CSEP code distribution should be open to the public:
      • Masha mentioned that main CSEP web page has a link to the distribution under Software
      • Will become public once we open up CSEP Trac to the public
    4. Danijel will work on more content for the main CSEP web pages
  4. 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
  5. 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