QuakeSim servers updated to port 80

The gw11.quarry.iu.teragrid.org portal server and gf13.ucs.indiana.edu http server have been updated to use port 80 instead of 8080, so that access to the portal is not blocked by any firewalls. This update is completed by running httpd on the same servers and having httpd redirect requests to URL patterns corresponding to QuakeSim portal and resources to the QuakeSim tomcat servers. Therefore, the tomcat servers are still running on port 8080, and services which used to access the web services through 8080 can still work.

The realtime RDAHMM service configurations are modified so that the service now stores all results to directories under tomcat's "webapps" on gf13. The realtime RDAHMM portlet is also modified so that the results are now accessed from gf13 instead of gf14.

XYZ changed to NEU in daily and realtime RDAHMM

The daily and realtime RDAHMM portlets have been updated so that the "Current X", "Current Y", "Current Z" tags are changed to "North", "East" and "Up".

Modifications to the evaluation process of daily RDAHMM

Previously, the evaluation process of daily RDAHMM only takes a station's GPS data from 2006-10-01 to "today" as input.

We now extend the evaluation input to include all of a station's GPS data since 1994-01-01; i.e., including input data in the modeling process. For any specific station, the state change sequence in the evaluation process for the modeling time section is expected to be the same as the sequence in its modeling result. Further, if any input data is missing between the last "data-available date" of the modeling time section and the first "data-available date" in the evaluation time section, data duplicated from the last "data-available date" of the modeling time section is used to fill the "data-missing" section.

Tooltips Added to Simplex, Disloc, and GeoFEST

GeoFEST, Disloc, and Simplex fault parameter forms now have tool tips to explain the parameters. GeoFEST layer parameters also have tool tips.

Modifications to daily RDAHMM service for supporting JPL data source

We have modified the daily RDAHMM service in the following way so that other data sources can be supported in a flexible way:

1. We run one service process for each data source;

2. Corresponding to different data sources, different directories will be used to save the daily RDAHMM analysis results. Besides, different arguments should be used for querying the input GPS data for different data sources;

3. On start up, a service process will receive the path to a property file as an argument. This file contains information such as the data source, pre-processing treatment, directory for saving the results, and GRWS query arguments for this process. The process will analyze the property file, and thus do analysis to the specified data source, using the right corresponding query arguments, pre-processing treatment, and output directory.

Support for JPL data source added to Daily RDAHMM portlet

Support for JPL data source has been added to daily RDAHMM portlet. We added a separate jsp page, DailyRdahmm_jpl.jsp, to show the results of JPL data source, and added a navigation rule in the portal configuration file, faces-conf.xml, to navigate betweent the pages for SOPAC data source and JPL data source. Now there is a link on each page pointing to the other page, so the user can click this link to view results for the other data source. Updates have been applied to the server at gw11.quarry.iu.teragrid.org:

http://gw11.quarry.iu.teragrid.org:8080/gridsphere/gridsphere

Daily RDAHMM portlet modified corresponding to the video service

We have modified the daily RDAHMM portlet so that it now links to a video file made by the daily RDAHMM video service, which will always be in mp4 format.