Package de.dlr.proseo.model
package de.dlr.proseo.model
The de.dlr.proseo.model package contains all classes required for the modelling of the persistent state
of prosEO, the Processing System for Earth Observation Data
- Author:
- Dr. Thomas Bassler
-
ClassDescriptionCollect production metricsA cron-style trigger, which is tied to specific times of day/week/month.A set of parameters to apply to a generated product of a processing orderA specific processor configuration, tied to a specific ConfiguredProcessor object.A processor configuration fileAn additional input file for a processor configuration for inclusion in generated Job Order FilesA specific version of a Processor combined with a specific Configuration object (i. e. a specific set of configuration data for the given processor version).A trigger that fires upon ingestion of a product fulfilling certain criteria (match of product class, file class [if set] and/or processing mode [if set]); trigger events may be sent by the Ingestor or by Monitors for non-prosEO pickup points (local or remote)Trigger to create a processing order for an expected datatake.History of product downloads; while originially bound to a ProductFile, the entry persists even after deletion of the ProductFile to give a full history of the Product downloadsFilter conditions to apply to an order input product of a specific product class in addition to filter conditions contained in the applicable selection ruleIdentification of the input product to use for On-Demand Production; its intention is to be unambiguous (as per ODPRIP ICD), however this is not guaranteed given the limited number of specification options (uniqueness may be guaranteed when specifying a file name, but it is not, when only specifying a sensing time range).A collection of job steps required to fulfil an order for a specific period of time (e. g. one orbit).Enumeration describing possible job states.A single processor execution to produce a defined output product based on a defined set of required input product (modelled as ProductQuery objects).The possible processing states for a job stepThe possible log levels for stdout and stderrAn Earth Observation mission.Base class for triggers which fire upon reaching start time of a mission planning object plus a given deltaTime (may be negative, which means that the event fires before the start time of the object)External service defined by a caption and an IDThe state of an external service at a given point in timeThe percentage of uptime of an external service for a given calendar dayThe percentage of uptime of an external service for a given calendar monthProgress state of a processing order for a given point in timeAn order state identified by its name (used for database-based configuration of order monitoring)Abstract superclass for all entities monitoring product generation performance for a given period of time per production type (systematic/on-demand/reprocessing)Product generation performance per calendar day per production type (systematic/on-demand/reprocessing)Product generation performance per hour per production type (systematic/on-demand/reprocessing)Product generation performance per calendar month per production type (systematic/on-demand/reprocessing)prosEO service defined by a caption and an IDA service state identified by its name (used for database-based configuration of service monitoring)The state of a prosEO service at a given point in timeThe percentage of uptime of a prosEO service for a given calendar dayThe percentage of uptime of a prosEO service for a given calendar monthThe endpoint to send order completion notifications toThe description of an orbit identified by its start and stop times (e. g. the "spacecraft midnight" events of the Sentinel-5P satellite).Trigger for the generation of processing orders per spacecraft orbitThis class aims at simplifying the generation of processing orders, either for automatic generation due to an OrderTrigger firing, or for manual generation, e. g. from the GUI or CLI.Abstract base class for classes serving as template for the generation of processing orders.Base class for all order generation triggersThis class allows to add mission-specific parameters to any persistent object.The payload of a spacecraft, e. g. the TROPOMI instrument of Sentinel-5P.Abstract superclass of all persistent classes Updated for Spring Data 3.5 / Hibernate 6.6 as per https://docs.spring.io/spring-data/jpa/reference/jpa/entity-persistence.htmlA processing facility for running prosEO jobs and storing prosEO product files, e. g. at a cloud service provider.A customer order to process a specific set of ProductClasses for a specific period of time using a specific set of ConfiguredProcessors.A history entry for logging the processing times of a production orderA specific version of a ProcessorClass.A type of processor capable of generating products of a specific set of ProductClasses.Representation of a data productAvailable archive locations for input products or auxiliary files.A class of products pertaining to a specific Mission, e. g. the L2_O3 products of Sentinel-5P.The data file and pertinent auxiliary files for a product at a given processing facility.A ProductQuery models the need of a JobStep to use a Product of a certain ProductClass for a specific time period.A product retrieval policy consisting of a retrieval mode and a time interval with delta times as defined in Annex B of ESA's Generic IPF Interface Specifications (MMFI-GSEG-EOPG-TN-07-0003, issue 1.8).Class representing a single overlapping time periodAvailable policy types as defined in ESA's Generic IPF Interface Specifications and other sources (e. g.A rule defining the required input ProductTypes for a certain output ProductType using an ordered list of SelectionPolicys.The abstraction of a spacecraft used for a specific Mission.A single, separately adressable execution step of a Processor.A trigger that fires in certain time intervals.Base class for triggers which fire upon reaching a certain point in timeA Workflow allows to select a suitable ConfiguredProcessor based on a given input product type (and possibly also an output product type).Description of possible options, which can be set as "Dynamic Processing Parameters" in Job Orders created using the owning WorkflowAllowed types for workflow options