Notification, communication and procedures for the coordinated CTBTO-WMO experiments on source location estimation 2003 and 2005 (!)

International Data Centre (IDC)/Radionuclide Section (RS)

Last modification: Dec 13, 2004

Authors: G. Wotawa & A. Becker


Preface

This document describes notification, communication, file formats, file naming conventions and other procedures for the March 2003 experiment on source location estimation and the experiment dry run (February 2003). In late 2004 most of the content has been mirrored from the secured to the public ftp/web interface. However download and upload of original data (SRS fields) is still processed via the secured ftp server. Hence there are no differences between the 2003 and the 2005 experiment with regard to data exchange procedures


Reporting: Public web interface

For reporting on the 2003 Experiment and approved contents of the upcoming 2005 Experiment the IDC has set up a public web interface accessible without authentication procedures

http://fts.ctbto.org/atm/

Communication: Secured web interface

For for data exchange purposes the IDC still keeps the secure web interface accessible to the participants

For data upload during the experiment server name, user and password will be provided within each notification mail message (see: notification mail).

To provide technical reference, a user manual for the server can be downloaded here.

Data can be uploaded to the server as follows:

https://fts.ctbto.org/cgi-bin/put-atm/

The current user name and password are different (!) as for the download system.

For the dry run as well as the experiment, it will be included into the notification mail message.

Automated upload of data to our server is possible. There are several ways to achieve this. A sample perl script for automated data upload is provided in the user manual (see appendix) or can be downloaded here. Roland Draxler (RSMC Washington) kindly provided an update capable to pass the required arguments through the command line. For using perl, it is crucial to have LWP (SSL-enabled) and HTTP perl modules available, which can be obtained in source code form from:

http://cpan.perl.org/

We can offer only very limited support for automated data upload from your organization towards the secure web interface and recommend, especially if you are not familiar with perl, to contact your own System Administrator on this issue, providing him with our documentation. Besides perl, Windows-based clients do exist that can achieve the same result.


Procedures: Notification mail

CTBTO requests for support are sent out via e-mail message and are simultaneously put on the secure web interface, for authentication purposes (mails can be manipulated, but nobody except us has write access to the download area of the secure web interface). The notification mail message is intended to allow for automated processing of the request within the participating organization. The IDC is ready to offer - limited - support to allow for automated processing. The issue of automated data upload is addressed in this document.

The e-mail message provides information on

  • Date and time of the request
  • Responsible officer, IDC point of contact
  • Information on the server (location, user name, password)
  • Cross-reference to the request document put on the web (allows for authentication)
  • All required information on the computations
    • Number of stations for which source-receptor matrix computations shall be provided
    • Coordinates of the receptor locations
    • Measurement start/stop
    • Date/time (backward from measurement stop) until which computations are requested
  • Expected response time of the participant (usually 24 hours for each request)
  • Response form (to be modified only in case of non-operational participation or non-participation)

Each participant is kindly requested to send back the WHOLE notification mail message to the IDC as soon as possible to confirm operational participation. In case of delayed participation or non-participation, the respective changes in the response form should be done before sending back the notification mail message to the IDC.

A sample notification mail message can be downloaded here

As soon as the computations are finished, each participant is requested to upload the requested source-receptor matrices in the requested form (see formats and naming conventions) to the server specified in the e-mail notification message. There is no further message necessary from the participant, since the server incoming area is continuously monitored by software that notifies IDC atmospheric transport operations as soon as new data are arriving.

In case of problems that prevent the participant from the submission of results within the time limits, he is asked to notify the IDC point of contact via e-mail (or, if necessary, via other means of communication).


What do we need - source receptor relationship

The IDC requests from the participants information on the so-called "source-receptor relationship" for a number of stations with specific measurement times. This information is needed, for example, to get information on possible sources. For one single measurement at one station, the source-receptor relationship is nothing else than the sensitivity of the measurement to a source at a certain position and time. We need this sensitivity for each point on the globe (1 degree resolution) and for each time increment starting from the end of measurements (collection stop) and going backward to a certain time (e.g. 144 hours; calculation end date/time is specified in the notification mail). The time increment will be 3 hours.

The following shall be (implicitly) assumed:

Source-grid: 1 degree globally

Source duration (for backward modellers: adjoint concentration output sampling interval): 3 hours

Source strength: 1.3 1015 Bq

Backward simulations (recommended):

In a backward (adjoint) simulation using an Atmospheric transport model, the required source-receptor sensitivity can be easily obtained as follows

  • Simulate an adjoint release of 1.3 1015 Bq of a tracer (no deposition, no decay) at a constant rate at the point of the station location backward from collection stop to collection start (usually 24 hours duration)
  • Calculate the respective adjoint tracer concentrations [Bq/m3] at a global 1x1 degree grid, output frequency 3 hours, time average of output 3 hours
  • Simulate backwards in time to the requested ending date/time (usually 6-10 days from sample collection stop)

Forward simulations (possible):

Forward simulations are totally valid, but usually computationally inefficient to address our problem (as long as the number of measurement stations is small). Anyway, the following approach would be equivalent to our backward simulation:

  • You have to release material forward in time from a (pseudo-) source grid and sample the material from all pseudo-sources at the receptor location during the whole measurement (sampling) period (from collection start to stop; this is usually a 24-hours concentration average)
  • The release rate at each grid point should again be 1.3 1015 Bq
  • The (forward) release duration should be, as implicitely assumed in the backward computations, 3 hours
  • The pseudo source grid calculations have to be repeated every 3 hours and for each grid point the receptor may be sensitive to (changes with time of the assumed release; the longer ago the release was, the larger this source grid area has to be assumed). The first computations have to start 3 hours before collection stop time with duration 3 hours. Then from 6-3 hours before collection stop, and so on, until you reach the requested end time (for example 144-141 hours backward).
  • What we need from you as output (source-receptor relationship) is the resulting (forward!) concentration at the receptor location (please note that this should be an average from collection start to stop) from the release at the respective grid point and time [in Bq/m3]. This is exactly the sensitivity of the sample to a release at the respective point during the respective time (and thus equivalent to the adjoint tracer concentration in the backward runs at this point and this time).
  • Please assure that your capture all points the receptor is sensitive to during the whole time period under consideration


File formats and names

It has been recommended during the CTBTO-WMO Workshop 2002 to follow the WMO file format and naming standards. While going to GRIB/BUFFR formats is still an important target, for the time being we request that the participants submit the source-receptor relationship (source-receptor matrix) information in unix-compressed ASCII files.

File formats:

Example file (click to download)

 

Header line (line 1)

Longitude of station / latitude of station/ measurement (collection) start time/ Measurement stop time [UTC]/ Total mass [Bq] released in backward model / Maximum number of hours backward/ Output frequency [hours] / averaging time [hours] / resolution of output grid in longitude / latitude [degrees] / station identifier [as specified in notification mail message]

[there is no specific number format required]

Data lines (line 2 - line k)

Latitude of grid point / longitude of grid point / backward time step number / value of source-receptor sensitivity [Bq/m3]

 

In our example, timestep number 1 is 3-0 hours before sample collection stop; timestep number 2 is 6-3 hours before sample collection stop; and so on

Please leave away all zero-value grid points

You can write out the data in any order you wish to

(data loop can go across longitude, latitude or time, you can start with collection stop and go backward in time (forward in time step number) or with the start of model simulation and go forward in time (backward in time step number).

Please unix-compress all files before upload

Show source receptor sensitivity plot for current example

 

File naming convention:

You should name your file as follows:

AAAAA.YYYYMMDDhh.num.txt

AAA

Station identifier

YYYYMMDDhh

collection stop date/time

num

your WMO centre identifier

 

In this example:

SEP63.2003010709.<Your-WMO-id>.txt

 

Submission of zip and tar files:

During the full-scale experiment, we will request, in total, on the order of 20-30 computations. You can expect 5-10 stations (measurements) per request. To facilitate data upload, we open the opportunity to submit standard zip (archive) files or unix tar files to the server. The following procedures should be followed:

  • please name these files XXXX.nn.zip [or .tar, if a tar file], with XXXX being your 4-digit centre identifier, and nn being a consecutive number (01 for the first file you submit, and so on)
  • If you use zip, please make sure that we can extract files from the archive with the standard (unix) unzip command (no special WIN-ZIP !!!)
  • The content of the zip/archive files should strictly follow the defined file naming conventions

THIS IS ONLY AN OPTION, FOR YOUR CONVENIENCE. IF YOU WANT, YOU CAN OF COURSE GO ON SUBMITTING SINGLE FILES !!!


Backward Simulation duration during the experiment

At the workshop, we arranged that the source-receptor sensitivity fields (retroplume concentrations) should go 6 days backward in time. This, of course, referred to the first detection of the material at a station. As the scenario evolves (day 2 and day 3 of the experiment), we will request computations that will again go backward 6 days, but relative to the first detection. That means that these computations are 7 and 8 days long, respectively. If you apply a Lagrangian model in 3-d particle mode, that may have consequences concerning the number of particles you need.

IN SIMPLE WORDS: THE SIMULATION DURATION IN DAYS (HOURS) WILL NOT BE A CONSTANT DURING THE EXPERIMENT. THE SIMULATION END DATE (IN BACKWARD SENSE) WILL BE THE CONSTANT !!!

Dont be surprised that we might, in the first request form, ask for computations for the same stations but with two different collection stop days. That means that we may be interested in the source-receptor sensitivity from some stations on the day BEFORE the event was measured. As the 6-day rule from the first detection applies, the requested pre-detection computations will be only 5 days long.