Changes between Version 7 and Version 8 of HpcInfo

Timestamp:

Jan 25, 2012, 11:51:22 PM (13 years ago)

Author:

dzollars

Comment:

--

HpcInfo

@@ -43 +43 @@
 At the beginning of the program, periodically during execution, and at the end of of processing, MPI_Analysis writes a UDP status datagram to a listener on the host and port specified in the control.xml file.  Each datagram will consist of the analysisRequestGUID and a status (e.g. started, iteration number, finished).  This is not a reliable two-way communication and it is the responsibility of the listener to follow up and manage any missed messages.
 
-== listen ==
+== listen.php ==
 
-This php program runs as daemon receiving udp packets from the MPI_Analysis program. It is responsible for updating the analysis table in the local gfac database table and the HPCAnalysisResult table in the LIMS database with current status. Current status possibilities include:
+This php program runs as daemon receiving udp packets from the MPI_Analysis program. It is responsible for updating the analysis table in the local gfac database and the HPCAnalysisResult table in the LIMS database with current status. Current status possibilities include:
 
 || Current Status           || Meaning                                                               ||
@@ -66 +66 @@
 || SUBMITTED                || If > 10 mins, request status update || 24 hours || SUBMIT_TIMEOUT    ||
 || SUBMIT_TIMEOUT           || Request a status update             || 24 hours || FAILED            ||
-|| RUNNING                  || If < 10 mins, request status update || 24 hours || RUN_TIMEOUT       ||
+|| RUNNING                  || If > 10 mins, request status update || 24 hours || RUN_TIMEOUT       ||
 || RUN_TIMEOUT              || Request a status update             || 48 hours || FAILED            ||
 || DATA                     || Request status; Request data every 5 mins || 1 hour || DATA_TIMEOUT  ||