1 / 20

Engineering Data File (EDF) implementation – first results

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

alicia
Download Presentation

Engineering Data File (EDF) implementation – first results

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Engineering Data File (EDF) implementation – first results

  2. 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

  3. How to implement EDF? • Simple ASCII tables • Custom format - named or numbered parameters, etc. • XML

  4. 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>

  5. 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>

  6. 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

  7. XML related technologies • XML • XSL and XSLT – Extensible Stylesheet Language Transformations • W3C XML Schema Definition Language

  8. 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

  9. EDF creation at SLR station

  10. EDF creation Fixed station data Calibration, meteo, etc EDF script EDF XML file

  11. Example usage EDF files Script EDF history Extract data Charting program Simple table Chart

  12. Calibration value temperature dependence

  13. 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>

  14. 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

  15. XML advantages • Flexibility and extensibility • Facilitates data validation and checking (schema declarations, XSLT) • Helps to develop resuable software

  16. Implementation steps • Define EDF schema • Stations implement EDF creation • Define common tasks • Design software

  17. EDF schema

  18. 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>

  19. 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

  20. Conclusions If we want to establish stable, extensible framework for the SLR data exchange , XML is a solution and very likely the best one.

More Related