coriolis data center - PowerPoint PPT Presentation

About This Presentation
Title:

coriolis data center

Description:

and the Samos initiative L. Petit de la Vill on. Ifremer-France-petit_at_ifremer.fr http://www.coriolis.eu.org codac_at_ifremer.fr – PowerPoint PPT presentation

Number of Views:72
Avg rating:3.0/5.0
Slides: 21
Provided by: Thierry104
Category:

less

Transcript and Presenter's Notes

Title: coriolis data center


1
Potential collaboration between the Coriolis
project and the Samos initiativeL. Petit de
la Villéon. Ifremer-France-petit_at_ifremer.fr

http//www.coriolis.eu.org
codac_at_ifremer.fr
2
Plan
  • Description of the Coriolis project and its 5
    components
  • Focus on the Data Centre component (The Coriolis
    data centre)
  • Various sources of data
  • Focus on the research vessels components
  • Routine measurements
  • Potential collaboration between the SAMOS
    initiative and the Coriolis project
  • Could the Coriolis project being a partner of the
    SMOS / Aquarius cal-val process ?

3
Coriolis as a part of a global structure for
operational oceanography a french approach in an
international context
4
Products
Validation
Delayed mode
Near real time
Assimilation
Model outputs
Coriolis aims to be a one-stop shopping for
ocean in-situ data - near real-time
(assimilation) - delayed-mode (validation)
5
Products
Validation
Delayed mode
Near real time
Assimilation
Validation Database
Model outputs
There is a strong need of in situ data for
cal-val purposes.
6
How did Coriolis start to work on operational
oceanography?

http//www.coriolis.eu.org
codac_at_ifremer.fr
7
Coriolis data flow

Argo Dacs Argo coriolis, gyroscope, Mersea,33
projectsProvor, Apex, Nemo
12h
GTS (Météo-France)
daily2
dynamic
web
Quality Controls
Research vessels xbt-ctd, tsg Atalante, thalassa,
suroît, Beautemps-Beaupré, Marion-Dufresne,
Meteor,
12h
daily
ftp, opendap, las
daily
Coriolis-Database
argo
Météo-france Gts data Lagrangian buoys
weekly
Mersea, Mercator Godae
12h
1 year
Productsanalyses, graphics, mapscurrent
estimates sensor drifts
Gtspp- Gosud Meds GTS
daily
48h
Other modelssoap (Shom- French Navy)
VOS- merchant ships ORE SSS (IRD)T S surface
data
annual
Clivardelayed mode data sets
annual
Moorings Tao, Triton, Pirata
Gtspp- Gosud
US-nodc historical data
1 year
8
Data sources


Research vessels
Argo floats


Merchant ships

Sea mamals or sea elephants

Gliders

Moorings
Drifting buoys
9
Vertical profiles from 26th April to 3rd May
2006. This is today !!!
About 5-7000 new profiles every week
10
Coriolis project routine measurements on board
the research vessels
  • - Consider the data collected on board the
    research vessels as a full part of a global and
    continuous component of the ocean observing
    system.Ships considered are mainly french
    vessels. Effort is made at an European level
  • - Define and set up the data collection
    transmission protocols, evaluate the sensors
    drifts in relation with the science group, make
    the link between ship operators and data centre

11
Research vessels component
  • Data considered
  • T and S vertical profile data from XBT and CTD
  • surface T S Data
  • Current data from VM-ADCP
  • In the frame of
  • national projects
  • european funded projects
  • In relationship with international projects
  • GOSUD (IODE)

12
Example T S surface data collected on board
research vessels (thermosalinographs)
13
Example XBT, CTD and ADCP data collected on
board french and european research vessels
14
Directions for potential collaboration (1/5)
  • Access to new sources of data (1/2)
  • SAMOS collect data from US Research Vessels
  • Both meteorological and oceanographic data (SST)
  • Main interest on meteorological data
  • CORIOLIS collect data from french research
    vessels (objective is to enlarge to european
    vessels)
  • oceanographic data (SS-SSS) and meteorological
    data
  • Main interest on oceanographic data
  • gt data exchange between the 2 projects
  • gt an pilot experience could be started on a
    SAMOS research vessel and on Atalante
  • gt Coriolis s Interest is on getting new data,
    receiving feedback on meteorological data quality
  • gt Gosud interest is obvioulsly to have access to
    new data

Meteorological are available for about half of
these locations
15
Directions for potential collaboration (2/5)
Parameters recorded on Coriolis research vessels
  • Meteorological data
  • Wet bulb temperature
  • Sea Surface temperature
  • Humidity
  • Atmospheric pressure
  • Dew Point
  • Precipitation rate
  • Solar Radiation
  • True wind Speed and direction
  • Apparent Wind Speed and direction
  • Coriolis has no experience on QC such data and it
    is not our 1st objective to process them but they
    are available.
  • Some of these parameters are transmitted on the
    GTS
  • Oceanographic data
  • Sea Surface temperature
  • Conductivity
  • Water tank temperature

16
Directions for potential collaboration (3/5)
  • Access to new sources of data (2/2)
  • Coriolis is involved in the OceanSites project as
    a GDAC
  • OceanSites relates to Open Ocean moorings and
    long time series and monitoring
  • They are regular ship cruises planned for
    moorings maintenance
  • Access to data collected by the vessels when they
    cruise to the moorings could also be an
    interesting way to investigate for potential
    collaboration
  • Cruises data are full part of the OceanSites
    Project
  • http//www.oceansites.org/

17
Directions for potential collaboration (4/5)
  • Share the data and distribute them (1/2)
  • As the objectives of the 2 projects are quite
    different, it seems reasonable that
  • Meteorological data go to SAMOS
  • Surface ocean data go to GOSUD
  • The issue to ensure that meteorological data and
    ocean data that are transmitted together, then
    splitted can be reconnected unequivocally
  • Proposals
  • We have to define a common agreed unique tag
    based on the data (as it is already done within
    GTSPP) or based on the files transmitted (could
    assign a ship day tag WMO/date)
  • Data could be shared between the 2 projects
    through 2 DODS Servers
  • GOSUD data available on a DODS server as well as
    all the data hosted by Coriolis
  • http//www.ifremer.fr/cgi-bin/nph-dods/data/in-sit
    u
  • In this scheme the GOSUD and SAMOS sites are not
    mirror sites. Is there a need for a final
    archiving centre or at least a common access to
    the data. To be also defined

18
Directions for potential collaboration (5/5)
  • Share the data and distribute them (2/2)
  • Coriolis has an experience on ocean data routine
    insertion on the GTS (Global Transmission
    NetWork).
  • If we plan to receive the ocean data from SAMOS,
    Coriolis propose to do that for SAMOS data (if
    not yet done)

19
Summarizing
  • Share the data between our 2 projects seems to be
    the 1st obvious step Meteorological data
     against  Ocean data
  • Find an easy way to access collocated meteo and
    ocean data
  • Define a data structure for that
  • Which may include a common format or at least a
    compatible format
  • As a conclusion for a SAMOS / CORIOLIS
    collaboration
  • Routinely collecting data on research vessels is
    very valuable because
  • Ships tracks are far from merchant routes
  • Data are of high quality (because of being
    acquired by specialised staff)
  • Sharing those data is important and using them as
    much as it is possible is also important.
    Feedback to the data originators must be done
    each time it is possible
  • Another message Coriolis is open to a
    collaboration for a centralised in situ ocean
    data access for satellite validation purposes

20
  • Contacts
  • http//www.coriolis.eu.org
  • Codac_at_ifremer.fr
  • Petit_at_ifremer.fr
Write a Comment
User Comments (0)
About PowerShow.com