Minutes from 10 November 2009

2009/11/10 CSEP Meeting

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

1. csep-op:
   1. NFS server:
      • John tried direct connection - shows 3x speed up in file IO
      • Still less number of disks with higher capacity compared to previous NFS server
      • Tonight processing will give runtime for one-day models to compare
      • Not critical change in processing runtime since can still process all one-day forecasts within 5 hours
      • Phil suggested to continue with current NFS server for now
   2. V9.10.1 release:
      • John installed generic, CA, Western Pacific and Global packages on Monday, 2009-11-09
      • John upgraded Scipy to V0.7.1 due to some failures  on csep-op to load Matlab format of forecasts files
      • csep installation passed all unit and acceptance tests
2. Software development:
   1. Phil suggested to open Trac ticket: #189 Install download counter for CSEP packages
   2. Alvaro Gonzalez contacted Masha and would like to submit one-day alarm-based models for WPacific and Global regions
      • Masha suggested to install the models in V10.1.0
      • Waiting for Alvaro's response
   3. Working on Trac #177 XML format of forecast should still be passed through master XML template
      • Automatically reinterpret XML forecasts to use [-90;90] for latitude and [-180;180] range for longitude
        • Generic implementation to affect all testing regions of all testing centers
        • Jeremy confirmed that it's a correct generic assumption and should proceed with implementation
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