Friday, May 28, 2010
Portal Hosting Issues
We have experienced issues with the portal hosting server that may temporarily corrupt the user database. These are fully recovered from backups, and we have added additional logging and monitoring, but please report any problems.
Tuesday, April 20, 2010
Disloc InSAR Plotting Feature Added
You can now make InSAR-like fringe plots of Disloc output files. This is done automatically for all new disloc runs and can also be applied to older disloc problems.
Monday, April 12, 2010
QuakeSim DB Crash and Rebuild
The user database crashed on April 11, and the entire portal needed to be rebuilt. All user project data has been preserved, but you will need to recreate your account through the automatic account creation process using the same user name as before. Please contact us if you have any problems.
Tuesday, March 30, 2010
KML generating function added to daily RDAHMM result service
We added a new function to the daily RDAHMM result service, which can generate a KML file describing the states of all stations for a specified date. The file can be opened and shown successfully with Google Earth, but Google map has problems when showing the interactive plots.
A "Get KML For This Day" button is added to the daily RDAHMM portlet, which when clicked will call the daily RDAHMM result service to create a KML for the selected date, and show the content in a new window.
A "Get KML For This Day" button is added to the daily RDAHMM portlet, which when clicked will call the daily RDAHMM result service to create a KML for the selected date, and show the content in a new window.
Tuesday, March 2, 2010
Simplex3 Project Copying
You can now copy projects in the Simplex3 portlet (one of the new "revised" collection).
Revised Disloc, Simplex, and GeoFEST portlets
These have been added under the tab "Revised Deformation Analysis". The new portlets use the revised version of the QuakeTables database.
Thursday, February 18, 2010
Major changes to daily RDAHMM service
We spent a lot of time re-writing a major part of the daily RDAHMM service, and here are some important changes:
1. A large amount of dirty codes are cleared up. The DailyRDAHMMService class is replaced with a new DailyRDAHMMStation class, which performs all functions DailyRDAHMMService used to complete, but with better flexibility and extendability. Some old functions of the DailyRDAHMMThread class are also moved to the DailyRDAHMMStation class.
2. The process of modeling and evaluation for each station are changed to the following sequences:
(1) Check if a model already exists. If so, count the non-duplicated data in the model input -- if more than 200, skip the whole modeling process and go to step (5); otherwise delete the model files and continue with step (2).
(2) Choose intial start and end date for modeling input. First read the startDate saved in jplDates.txt or sopacDates.txt.
if startDate < 2006-09-30 and startDate + 1year <= 2006-09-30 then
endDate = 2006-09-30
else
if startDate + 1year <= "today" then
endDate = startDate + 1year
else
set endDate to null
give up the modeling process and return failure
endif
endif
(3) Adjust endDate.
while number of non-duplicated data in the model input of [startDate, endDate] is less than 200 do
If endDate > "today" then
set endDate to null
give up the modeling process and return failure
endif
endDate += 1year
endwhile
(4) Build the model.
Fill the model input with duplicated data, and build the model.
(5) Do evaluation.
Read the lastDate of model input from the model input file;
Query for input for [lastDate+1, "today"];
Append the queried input to the model input, and fill the combined input with duplicated data;
Do evaluation on the filled input.
3. Two sub-elements are added to each "station" element in the XML file of the station list: one "modelStartDate" sub-element and one "modelEndDate" sub-element. Since these dates are different for different context groups, we now have two different station list files for the two context groups (sopacGlobk and jplGipsy) analyzed.
4. The service is now scheduled to run every seven days, since we got informed that the GPS data are updated in a weekly manner. Maybe we should change the service name to "weekly RDAHMM service"?
1. A large amount of dirty codes are cleared up. The DailyRDAHMMService class is replaced with a new DailyRDAHMMStation class, which performs all functions DailyRDAHMMService used to complete, but with better flexibility and extendability. Some old functions of the DailyRDAHMMThread class are also moved to the DailyRDAHMMStation class.
2. The process of modeling and evaluation for each station are changed to the following sequences:
(1) Check if a model already exists. If so, count the non-duplicated data in the model input -- if more than 200, skip the whole modeling process and go to step (5); otherwise delete the model files and continue with step (2).
(2) Choose intial start and end date for modeling input. First read the startDate saved in jplDates.txt or sopacDates.txt.
if startDate < 2006-09-30 and startDate + 1year <= 2006-09-30 then
endDate = 2006-09-30
else
if startDate + 1year <= "today" then
endDate = startDate + 1year
else
set endDate to null
give up the modeling process and return failure
endif
endif
(3) Adjust endDate.
while number of non-duplicated data in the model input of [startDate, endDate] is less than 200 do
If endDate > "today" then
set endDate to null
give up the modeling process and return failure
endif
endDate += 1year
endwhile
(4) Build the model.
Fill the model input with duplicated data, and build the model.
(5) Do evaluation.
Read the lastDate of model input from the model input file;
Query for input for [lastDate+1, "today"];
Append the queried input to the model input, and fill the combined input with duplicated data;
Do evaluation on the filled input.
3. Two sub-elements are added to each "station" element in the XML file of the station list: one "modelStartDate" sub-element and one "modelEndDate" sub-element. Since these dates are different for different context groups, we now have two different station list files for the two context groups (sopacGlobk and jplGipsy) analyzed.
4. The service is now scheduled to run every seven days, since we got informed that the GPS data are updated in a weekly manner. Maybe we should change the service name to "weekly RDAHMM service"?
Subscribe to:
Posts (Atom)