Alerting | Alerting | See the related dataType for further information. | |
AllowPartialResolution | str | Forwarded to the Plan if present, see Plan.AllowPartialResolution. | |
ArchiveProcessingFlag | str | ArchiveProcessingFlag | |
AutomaticTriggering | AutomaticTriggeringParameters | If present, this element indicates that this plan should be processed using an automatic triggering strategy. The goal of automatic triggering is to reduce manual operations and maximize the usefulness of pipeline resources by creating PPOs only when a pipeline is at its optimal readiness state. This implies checking PF-specific business rules such as tile/observation coverage and remaining time before next input data. | |
DynamicWorkdirSizeExpression | str | An expression which is evaluated during plan resolution to dynamically overwrite the EstimatedWorkdirSizeGB element of the associated PPO. See ST_PlanSolver documentation for syntax and evaluation failure fallback mechanism. | |
EstimatedWorkdirSizeGB | int | The size (in GB) of the workdir for the given PPO - including all its intermediate datafiles and products (and all inputs and output files). Actually, the maximum size over the execution time of the PPO. It helps to manage the ppos that can be simultaneously in execution to not exceed the SDC limits on the shared file system. | |
Id | str | The naming rule of the Id are mentioned here: https://euclid.roe.ac.uk/projects/ec_sgs_challenges/wiki/PipelineDef_specifications#PipelineDef-ltIdgt-Naming-Rules | |
InputDataSet | InputDataSet | See the related dataType for further information. | |
OptionalPackageDefRootPaths | str | Url (absolute path) to folders containing additional PackageDefs typically on CernVM-FS (something like /cvmfs/euclid.in2p3.fr/CentOS7/EDEN-X.Y_dev/opt/euclid/PackageDefXYZ/[version]). The rules are defined in this wiki page: https://euclid.roe.ac.uk/projects/codeen-users/wiki/Pipeline_Files_location_and_deployment | |
OutputDataSet | OutputDataSet | See the related dataType for further information. | |
PipelineRootPath | str | Url (absolute path) to folder containing PipelineScript and possibly PackageDefs typically on CernVM-FS (something like /cvmfs/euclid.in2p3.fr/CentOS7/EDEN-X.Y_dev/opt/euclid/Pipeline/[version]). The rules are defined in this wiki page: https://euclid.roe.ac.uk/projects/codeen-users/wiki/Pipeline_Files_location_and_deployment | |
PipelineScriptPath | str | Path (relative to PipelineRootPath) to the PipelineScript in CefdateStartrnVM-FS, for example: VIS/PF_VIS.py The rules are defined in this wiki page: https://euclid.roe.ac.uk/projects/codeen-users/wiki/Pipeline_Files_location_and_deployment | |