200 likes | 310 Views
Engineering Data File (EDF) implementation – first results. EDF goals. Continuous system history over a wide variety of parameters Inter-comparison between parameters of different SLR stations Rapid identification of system drifts or degradation effects
E N D
EDF goals • Continuous system history over a wide variety of parameters • Inter-comparison between parameters of different SLR stations • Rapid identification of system drifts or degradation effects • Correlation of system data with bias reports based on orbit analysis • Easy implementation • Flexibility
How to implement EDF? • Simple ASCII tables • Custom format - named or numbered parameters, etc. • XML
Extended Markup Language – XMLExample 1 <Receiver> <DetectorModel="C-SPAD" DeviceID="1" DetectorType="SPAD" TWCompensation="Yes"/> <FilterModel="Andover 003FC10-25" DeviceID="20010705" BandWidth="0.3"/> </Receiver> <math:Vector dim=“3”> 1, 0, 0 </math:Vector>
Extended Markup Language – XMLExample 2 <EDFVersion="1.0" MJD="52642.3579976852" Epoch="2003-01-03T08:35:31"> <StationSOD="78393402" SCH="4" SCI="3" CalibMethod="0" TimeScale="4" Name="Graz"/> <Hardware> <LaserWavelength="532.0" SemitrainConst="8658" MaxNumOfSemiTrainTracks="10" Energy="0.035“ PulseWidth="35" Divergence="0.0" RepRate="10"/> <Receiver> <DetectorModel="C-SPAD" DeviceID="1" DetectorType="SPAD" TWCompensation="Yes"/> <FilterModel="Andover 003FC10-25" DeviceID="20010705" BandWidth="0.3"/> </Receiver> <TimerModel="Graz ET" DeviceID="Module 1+2" CorrectionID="0"/> </Hardware> <MeteoTemperature="7.1" Pressure="942.4" Humidity="52.8"/> <CalibrationTargetDistance="1.742" CalValue=" 157173" PeakMinusMean=" 2" RecordedPoints=" 500" AcceptedPoints=" 157173" SigmaUsed="2.2" RMS=" 22" Skew="-0.006" Kurtosis="2.432"/> <CustomData/> </EDF>
Why XML? • It is a universally accepted standard way of structuring data (syntax) and data exchange. • It’s supported with a lot of free/inexpensive tools. • The alternative to using XML is to define your own proprietary data syntax, and then build your own proprietary tools to support the proprietary syntax. • XML based data can be extended without losing compatibility with already existing software
XML related technologies • XML • XSL and XSLT – Extensible Stylesheet Language Transformations • W3C XML Schema Definition Language
What‘s necessary to use XML? • In a simplest case – just a text editor and a compiler • XML support now is available in many operating systems and programming languages
EDF creation Fixed station data Calibration, meteo, etc EDF script EDF XML file
Example usage EDF files Script EDF history Extract data Charting program Simple table Chart
EDF history file examples <EDFHistory> <EDFRef href="Graz\XML\Graz 2003 003 0835.xml"/> <EDFRef href="Graz\XML\Graz 2003 003 0900.xml"/> <EDFRef href="Graz\XML\Graz 2003 003 0932.xml"/> <EDFRef href="Graz\XML\Graz 2003 003 1009.xml"/> <EDFRef href="Graz\XML\Graz 2003 003 1022.xml"/> <!-- rest deleted --> </EDFHistory> <EDFHistory> <EDFRef href="RGO\XML\Herst 2003 182 1024.xml"/> <EDFRef href="RGO\XML\Herst 2003 182 1028.xml"/> <EDFRef href="RGO\XML\Herst 2003 183 1428.xml"/> <EDFRef href="RGO\XML\Herst 2003 183 1833.xml"/> <!– rest deleted --> </EDFHistory>
EDF requirements • Continuous system history over a wide variety of parameters • Inter-comparison between parameters of different SLR stations • Rapid identification of system drifts or degradation effects • Correlation of system data with bias reports based on orbit analysis • Easy implementation • Flexibility
XML advantages • Flexibility and extensibility • Facilitates data validation and checking (schema declarations, XSLT) • Helps to develop resuable software
Implementation steps • Define EDF schema • Stations implement EDF creation • Define common tasks • Design software
Extended Markup Language – XMLExample 2 <EDFVersion="1.0" MJD="52642.3579976852" Epoch="2003-01-03T08:35:31"> <StationSOD="78393402" SCH="4" SCI="3" CalibMethod="0" TimeScale="4" Name="Graz"/> <Hardware> <LaserWavelength="532.0" SemitrainConst="8658" MaxNumOfSemiTrainTracks="10" Energy="0.035“ PulseWidth="35" Divergence="0.0" RepRate="10"/> <Receiver> <DetectorModel="C-SPAD" DeviceID="1" DetectorType="SPAD" TWCompensation="Yes"/> <FilterModel="Andover 003FC10-25" DeviceID="20010705" BandWidth="0.3"/> </Receiver> <TimerModel="Graz ET" DeviceID="Module 1+2" CorrectionID="0"/> </Hardware> <MeteoTemperature="7.1" Pressure="942.4" Humidity="52.8"/> <CalibrationTargetDistance="1.742" CalValue=" 157173" PeakMinusMean=" 2" RecordedPoints=" 500" AcceptedPoints=" 157173" SigmaUsed="2.2" RMS=" 22" Skew="-0.006" Kurtosis="2.432"/> <CustomData/> </EDF>
Other possible XML applications in the SLR • Normal points • The data can be extended in the future • XML schema can be used as basic data validation tool at the station and analysis centre • Prediction distribution • Prediction data can be extended without disturbing existing users
Conclusions If we want to establish stable, extensible framework for the SLR data exchange , XML is a solution and very likely the best one.