Science Completed Shows the total number and percentage of science processes that have completed under this date. Science Failed Shows the total number and percentage of science processes that have failed under this date. Epilogs Completed Shows the total number and percentage of epilog processes that have completed under this date. Epilogs Failed Shows the total number and percentage of epilog processes that have failed under this date. After drilling down to the lowest date granularity (dependent on the PGE), the individual CATALYST jobs can be seen, which have a different set of columns and values. Those columns are detailed below: Figure 2. Epilog Status Instance Shows the datadate for this CATALYST Job. CATALYST Job Status Shows the state of the CATALYST Job in the CATALYST Server. Hovering over this column with the mouse will show a description of the state in the Operator’s Console. Figure 2. Job Status A CATALYST Job goes through several states in its lifetime. State changes are initiated either by the CATALYST Server for normal job flow (checking inputs, running the job, etc.) or by a user performed action (see ). The CATALYST Job state flow is detailed below: Figure 2. CATALYST Job State Flow waiting The CATALYST job is waiting for all of its inputs to be checked off as being – available. CATALYST gleans whether an input is available from the CATALYST log database (See the CATALYST Server Operator’s Manual for more details). A CATALYST job that is waiting can move to the ready_to_launch state or the completed state. When a waiting job moves directly to completed it is because CATALYST has marked its science process and epilog process statuses as CATALYST_WONT_RUN.
Science Completed Shows the total number and percentage of science processes that have completed under this date. Science Failed Shows the total number and percentage of science processes that have failed under this date. Epilogs Completed Shows the total number and percentage of epilog processes that have completed under this date. Epilogs Failed Shows the total number and percentage of epilog processes that have failed under this date. After drilling down to the lowest date granularity (dependent on the PGE), the individual CATALYST jobs can be seen, which have a different set of columns and values. Those columns are detailed below: Figure 2. Epilog Status Instance Shows the datadate for this CATALYST Job. CATALYST Job Status Shows the state of the CATALYST Job in the CATALYST Server. Hovering over this column with the mouse will show a description of the state in the Operator’s Console. Figure 2. Job Status A CATALYST Job goes through several states in its lifetime. State changes are initiated either by the CATALYST Server for normal job flow (checking inputs, running the job, etc.) or by a user performed action (see ). The CATALYST Job state flow is detailed below: Figure 2. CATALYST Job State Flow waiting – The CATALYST job is waiting for all of its inputs to be checked off as being available. CATALYST gleans whether an input is available from the CATALYST log database (See the CATALYST Server Operator’s Manual for more details). A CATALYST job that is waiting can move to the ready_to_launch state or the completed state. When a waiting job moves directly to completed it is because CATALYST has marked its science process and epilog process statuses as CATALYST_WONT_RUN.