Alle Klassen und Schnittstellen
Klasse
Beschreibung
Interface protocol to use for a Product Archive
Breakpoint file information
Uses file name types from InputOutput class
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Representation of the Ipf_Conf Job Order element
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Thrown when a request to a unique named processing parameter is executed and
there is more than one parameter with the given name.
For the user as well as for planning and product access purposes it is important to know, whether a processing facility is
operational or not.
Input or Output information
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
File_Name information
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Ipf_Job_Order information
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Variants of Job Order file specifications: Over time the specification for Job Order files evolves, but processors may rely on
older versions of the specification.
Metric type to use for a Production Metrics
MonOrderStates: A class to hold the state definitions for monitoring orders,
and the respective state IDs.
MonServiceStates: A class to hold the state definitions for monitoring
services, and the respective state IDs.
Master time format for orbit times (ISO-formatted UTC-STS timestamps with
microsecond fraction and without time zone)
Possible methods for partitioning the order time period into individual job time periods for product generation.
Possible sources for Processing Orders
Possible states for a processing order; legal state transitions:
INITIAL -> APPROVED: Customer approved order parameters and/or committed budget
APPROVED -> PLANNED: Jobs for the processing order have been generated
PLANNED -> RELEASED: The order is released for running as planned
RELEASED -> RUNNING: The first jobs have started, further jobs can be started
RUNNING -> SUSPENDING: Order execution halted, no further jobs will be started (started jobs will be completed, if they are not halted themselves)
SUSPENDING -> PLANNED: All jobs for the order are either completed or halted (after suspending the order)
RUNNING -> COMPLETED: All jobs have been completed successfully
RUNNING -> FAILED: All jobs have been completed, but at least one of them failed
PLANNED -> FAILED: The order was cancelled by the operator
COMPLETED/FAILED ->; CLOSED: Delivery/failure has been acknowledged by customer and/or order fee has been paid
Enumeration of valid parameter types for mission-specific parameters
Representation of the Ipf_Proc (IPF = Instrument Processing Facility) job order element, i.e., a processing task with name and
version, as well as input/output and breakpoint files
For details see Generic IPF Interface Specification issue 1 revision 8 - 03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Processing level, usually indicating the number of processing steps required to create a product of this class from
unprocessed ("level 0") data.
Processing_Parameter information
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Production context for the generation of a product (from the ESA PRIP API specification, ESA-EOPG-EOPGC-IF-3, issue 1.4, sec. 3.2)
Quality annotation for products (determined by processor configuration)
Visibility of products to external users (internally all products are visible at all times)
Class to hold general utility methods
Sensing_Time information
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
Storage types of prosEO
String Utils
Time interval for input elements (Time_Interval Job Order element) (note that
in contrast to IpfFileName, file names in time intervals do not carry the
FSType attribute)
For details see Generic IPF Interface Specification issue 1 revision 8 -
03/08/2009 MMFI-GSEG-EOPG-TN-07-0003
prosEO User Roles (low-level roles, which can be bundled for user groups).