Home Contact Help user undefined project ALL Tables EAS page Preferences

PipelineProcessingOrder Overview

Query Form

Attribute nameAttribute typeDocstringUnit
AlertingAlertingSee the related dataType for further information.
DataSetReleasestrThis release element is inherited from the Plan definition and could be (depending on the context of the processing Plan): - SIM datarelease for a SIM pipeline - Specific run of an IT or SC challenge or a cycle during pre integration or pre production - Specific set of plans built for some specific scientific analysis: calibration campaign, scientific analysis - ... Enable to define a consistent set of data products (used to select a unique instance of a given data product at COORS level) this data product belongs to (not to be confused with the specified DataRelease or intermediateDataRealease by ESA that could be defined a posteriori
EndDatedatetimeEndDate : Set by IAL when the PPO is finished (arrived at a terminal state COMPLETED or ERROR).
EuclidPipelineSoftwareReleasestrConfiguration of the overall Euclid pipeline, representing the aggregation of elementary PFs plus MDB release, ...; This version should be the output of the SGS CCB.
GroupstrGroup: This is the value of the GroupedBy node which yielded this PPO from the parent Plan.
GroupedBystrForwarded from the parent Plan.
IdstrId : This Id is generated by the EAS service that creates the PPOs from the PP. By design this Id should unique. [PIPELINE]-[PURPOSE]-[USER]-PLAN-[NUMBER]-PPO-[NUMBER] is the naming pattern of the PPO that is inherited from the plan Id. [NUMBER] is a running number. e.g : EUC_SIR-PIPELINE-SC2_V0.1-PRODUCTION-RCOLLINS-PLAN-1-PPO-5
InputProductsPortProductsRefSetInputProducts : This is the list of input products per data product type assigned to this PPO. This is a subset of the PlanInputProducts derived from the dataproducts and processing distribution strategy .
InterruptedPipelineRunnerStatestrInterrupted : Last state before ERROR/COMPLETED of PipelineRunner, helps to spot problems faster.
InterruptedStatestrProcessing state from where the PPO was exiting or interrupted by a control action.
LineageFileDataContainerFile containing lineage information added as data file to DSS.
OutputProductsPortProductsRefSetOutputProducts : This is the list of output products per data product type created by running the pipeline defined for this PPO and added by IAL to the PPO.
ParentPlanIdstrParentPlanId : This references the Id of the parent plan from which this PPO is generated.
ParentPPOParentPPOParentPPO : This references the Id of the parent PPO in case of one or multiple retries (due to some failures requiring some retry) from which this PPO is generated. This parentPPO is completed with the creation date of this parent PPO and the number of retries to get the PPO successful.
PfLogFilesDataContainerLogFiles : A data container that references a tarball in the DSS with the log files generated by the science tasks while running the pipeline defined for this PPO.
PipelineExecEnvPipelineExecEnvExecution environment for the pipeline. If not set the PPO is used for data transfer.
PipelineRunnerMessagestrPipelineRunnerMessage : Error message of PipelineRunner, forwarded by ppo-scheduler into here.
PipelineRunnerStatestrPipelineRunnerState : This is to provide some useful feedback to the user about the status of the PPO, when it is running inside the PipelineRunner.
PPOMessagestrPPOMessage : Error message of ppo-scheduler.
ProcessingInfostrProcessingInfo : Additional information with hints on failures or possible problems (warnings). Added by IAL.
ProcessingStatestrProcessingState : This is to provide some useful feedback to the user about the status of the PPO.
PurposestrPurpose : This replicates the purpose from the parent plan.
SdcConfigurationstrSdcConfiguration : Contains the contents of the bootstrap file used by IAL to load the versions of the software and configuration. Set by IAL.
StartDatedatetimeStartDate: Set by IAL when pulled from EAS and ingested into IAL.
TargetSdcstrTargetSdc : This is the SDC xx on which the jobs of the PPO will run. This SDC is assigned to this PPO according to some static rules : observations storage from the EAS allocation table, ,stand alone pipelines such as calibration (for this specific case the targetSDC will be inherited from the PipelineDefinition. This targetSdc could be overwritten by COORS user. This target SDC type should be consistent with the instanceName of ialInstanceNames type stored into the EAS.

Click on a project name to select the project

Select a table listing:

empowered by

EUCLID logo OmegaCEN logo