| Description | HLCH ingester |
|---|---|
| Docstring | Ingester module for High level control History data, as shown below. ExeProcs: <H>MSG3:Instrument::P4871_7139¬EX=Automatic¬2¬1525219320@853 <H>MSG3:Instrument::P4871_7139¬ST=1525219320@854¬3¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬ID=SN_SV500¬4¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬V=43-180¬5¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬SC=7103.220418¬6¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬T=Seviri Observ File¬7¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬S=2¬8¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬S=6¬9¬1525219320@854 <H>MSG3:Instrument::P4871_7139¬S=14¬68¬1525219325@720 <H>MSG3:Instrument::P4871_7139¬E=1525219325@720¬69¬1525219325@720 ... APEX history consist of 2 types of files: - HLCH files (what this ingester handles) - Procedure Archive (PA) files The ingesters for those 2 types parse the input files, or rather interpret them to extract ENTITY data and execution LOG data. In HLCH files, Procedure initalisation info, end info and Interaction info form procedure ENTITY table entries. Other info (mostly states), go into history LOG table. |
| Wiki page | None |
| Activity file | HL_PROCHIST_INGESTER.xml |
| Executable | alg/hl_prochist_ingester.py |
| Calling convention | filename |
| Table triggers | None |
| Scheduler triggers |
|
| Output tables | |
| Event raised | None |