Project Deliverable D50 Report on Best Practices ... - ESONET NoE
Project Deliverable D50 Report on Best Practices ... - ESONET NoE
Project Deliverable D50 Report on Best Practices ... - ESONET NoE
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Since September 2005:<br />
All the output off all sensors are readout every 3 minutes and stored in the<br />
database in a special “RawData” table.<br />
At the same time, a parser reads this table to fill different tables dedicated to<br />
each sensor, storing the data timestamp, the parameter values and the reference of<br />
the line from where it was extracted from the RawData table.<br />
The typical flow is of 12500 new lines in RawData table per hour (<strong>on</strong>e line per<br />
oceanographic sensor and other slow c<strong>on</strong>trol informati<strong>on</strong>).<br />
All these data are processed in quasi real time.<br />
Current procedure :<br />
− Each sensor was calibrated before deployment.<br />
− The acquisiti<strong>on</strong> of the oceanographical data is synchr<strong>on</strong>ized with the<br />
ANTARES acquisiti<strong>on</strong> data.<br />
− The data readout method depends <strong>on</strong> c<strong>on</strong>necti<strong>on</strong> type of the sensors :<br />
For most of the sensors, the c<strong>on</strong>necti<strong>on</strong> is d<strong>on</strong>e by a serial link RS232.<br />
For them, the data measurement and their recording is d<strong>on</strong>e by slow c<strong>on</strong>trol<br />
request.<br />
The IP camera and the seismometer have an aut<strong>on</strong>omous Ethernet<br />
c<strong>on</strong>necti<strong>on</strong>.<br />
The IODA has its own system of internal data acquisiti<strong>on</strong> and buffering.<br />
Those data are then send to shore by the Slow C<strong>on</strong>trol.<br />
<str<strong>on</strong>g>Deliverable</str<strong>on</strong>g> #50 - update October 2010 158