idc users’ guide · 2013. 3. 4. · idc services and training unit idc users’ guide march 2005...

_________________________________________________________________________________________

IDC Users’ Guide

Version 3.0

International Data Centre Division March 2005 Services, Review and Training Section Services and Training Unit

IDC Services and Training Unit

IDC Users’ Guide March 2005 Page ii

IDC Users’ Guide CONTENTS About this Document iii - PURPOSE - SCOPE - AUDIENCE - RELATED INFORMATION - USING THIS DOCUMENT Introduction 1 Who are the IDC Users 2 How to Become a User of the IDC 2 How to Get Access to the IDC 10 Data and Products to be provided by the IDC 11 - DESCRIPTION OF DATA AND PRODUCTS 12 - AVAILABILITY DURING PREPARATION FOR FULL SCALE TESTING 16 Accessing the IDC AutoDRM 18 Establishing IDC Subscriptions 24 Accessing the IDC Secure Web site 32 Accessing the IDC Databases 37 Services to be provided by the IDC 40 - STANDARD SERVICES 41 - REQUESTED SERVICES 42 How to get help 43 Tutorial 44 - ACCESSING THE IDC AUTODRM 44 - ESTABLISHING IDC SUBSCRIPTIONS 50 - ACCESSING THE IDC SECURE WEB SITE 56 - ACCESSING THE IDC DATABASES 60 References 61 Glossary 62 Appendix. External Database Service User's Guide. 64


IDC Users’ Guide March 2005 Page iii

About this Document PURPOSE The IDC Users’ Guide is intended to provide a general overview of how to access data, products and services from the IDC. The aim is to give the essential information on how to interact with the IDC, with references to documents which give more detailed information. This is a dynamic document which will be progressively updated as needed to reflect any changes affecting the users of the IDC. SCOPE This document will give the reader an introduction on how to retrieve IMS data and IDC products, and on what is available during Phase 5a of the IDC Progressive Commissioning Plan, “Preparation for Full Scale Testing of the IDC Hardware/Software”. The four main access methods to IMS data and IDC products will be described, together with examples of how to request the data and products. A brief description of the services of the IDC will also be given. AUDIENCE This document is intended for users of the IDC. These users are expected to follow the spirit of the Treaty and decisions of the PrepCom regarding the use of IMS data and IDC products and services. RELATED INFORMATION Detailed descriptions of the format of all types of messages to be exchanged between the IDC and the NDCs, including subscription and request messages, may be found in “Formats and Protocols for Messages” [IDC3.4.1 Rev5]. Exchange of continuous data is described in “Formats and Protocols for Continuous Data CD-1.0” [IDC3.4.2 Rev0.1] and “Formats and Protocols for Continuous Data CD-1.1” [IDC3.4.3 Rev0.3]. USING THIS DOCUMENT This document consists of two parts. The first part gives an overview of the Products and Services of the IDC and describes: - How to Get Access to the IDC - Data and products available at the IDC during Phase 5a - The four methods by which NDCs may retrieve the data and products - Services to be provided by the IDC - How to get help, with contact information The second part is a tutorial with examples on how to write request and subscription messages to the IDC. It also gives a map of the IDC Secure Web site. The document "External Database Service User's Guide" is attached as an appendix. Questions or comments about this document should be e-mailed to [email protected].


IDC Users’ Guide March 2005 Page 1

Introduction The IDC Users’ Guide is a quick reference provided to any user of the International Data Centre. Its objective is to provide procedures about how to use the IDC. The central themes of the document are data and products and how to retrieve them from the IDC. The IDC is the facility responsible for data collection, processing and storage as well as distribution of data and products under the verification regime. The IDC shall provide the State Signatories with access to all IMS data and all IDC products. In addition, it supports system status monitoring and performance assessment of the IMS and IDC, and provides certain services and technical assistance to States Parties. The functions of the IDC can be organised into three categories: standard products, standard services, and requested services. The IDC started in February 2000 to provide a wide range of products and services to the NDCs. In the sections “How to Become a User” and “How to Get Access to the IDC” the steps to be followed to become a user and establish a connection to the IDC is described. Four methods of access to the IMS data and IDC products are then available: sending requests for data and products of special interest, obtaining data and products on a regular basis through subscriptions, browsing through the Web pages of the IDC and accessing copies of the IDC databases. These items are discussed in more detail in the sections “Accessing the IDC AutoDRM”, “Establishing IDC Subscriptions”, “Accessing the IDC Secure Web site” and “Accessing the IDC Databases”. Many examples on how to use these four access methods are given in the “Tutorial” and the Appendix.



Who are the IDC Users Only persons authorized by a State Signatory can become a user of the IDC. All States Signatories can appoint authorized users. For States Signatories with a Permanent Representative accredited to the CTBTO PrepCom, the Permanent Mission will inform the PTS on the users authorized by the State Signatory. For States Signatories without a Permanent Representative at the CTBTO PrepCom, the Government or the National Authority, if the CTBTO PrepCom has received notification of such an appointment, will inform the PTS directly. How to Become a User of the IDC There are three steps to be taken before being able to use the access methods to the IDC. The first step is to become a user authorized by a State Signatory, because only users with such an authorization can access the IDC products and services. There are currently three classes of user, with different access privileges: principal users, regular users and station operators and station maintenance personnel. Furthermore the IDC has to be informed about the appointment and given sufficient infor-mation about the users to be able to identify them. The total number of users in each class from each State Signatory should not exceed that recommended by Working Group B (WGB) and approved by PrepCom. The Secure Signatory Account Registration Form, as shown on the next six pages, should be sent through the appropriate official channels to the CTBTO PrepCom PTS.



SECURE SIGNATORY ACCOUNT REGISTRATION FORM During the 12th and 13th sessions of WGB of the PrepCom, the rules and procedures for the Secure Signatory Accounts were clarified and further elaborated. Excerpts from CTBT/WGB-12/1 of special relevance in this regard are (on pages 8 and 9): ”WGB noted that in some cases the provisional National Authority and the NDC of State Signatories are located in separate establishments. Furthermore, some NDCs are subdivided, with each subdivision being located in a separate establishment and dealing with one or more of the IMS technologies.” “It was agreed that the following three classes of users, nominated by the principal point of contact and authorized by the State Signatory, could access IMS data and IDC products through the single secure signatory account established for each State Signatory:” “Principal Users” “Regular Users” “Station Operators and Station Maintenance Personnel”. As a result the Registration Form, earlier distributed as an attachment to the Note Verbale of December 6, 1999, has been modified based on the recommendations of WGB. If a State Signatory already has appointed a Principal Point of Contact (see below in section A), the modifications of the Secure Signatory Account will be made based on communication between PTS and the Principal Point of Contact through the Mission, unless the State Signatory requests otherwise. The Provisional Technical Secretariat of the Preparatory Commission kindly requests each State Signatory to complete this form. The completed form will allow the PTS to activate, or modify, a single Secure Signatory Account for each State Signatory. This Account will enable your country, through the users designated on this form, to access IMS data and IDC products as part of initial testing. Initial testing started in February 2000, and will continue in accordance with the Progressive Commissioning Plan for the IDC. Please return the completed form, through the Permanent Mission to the following address:

Preparatory Commission for the CTBTO Provisional Technical Secretariat IDC/SR/ST Vienna International Centre P.O. Box 1200 A-1400 Vienna, Austria Fax: +43-1-26030-5973

In sections B to F templates are given. Copies can be made if more space is needed.

State Signatory: Date of completion of this form: (DD/MM/YYYY)



A. Principal Point of Contact for the Secure Signatory Account

The individual below is designated by the State Signatory to have overall responsibility for its Secure Signatory Account for the purpose of initial testing of the IDC. Any changes to the status of the Account or the Users should be communicated between the Principal Point of Contact and the IDC. Full Name Position Establishment/Organization

Address

City Country Phone Fax E-mail E-mail address from which AutoDRM requests are to be sent (if relevant)



B. Establishments for Accessing the Secure Signatory Accounts

The Establishments below are designated by the State Signatory for accessing the Secure Signatory Account. A maximum of six Establishments can be designated. All Principal Users have to belong to these Establishments. The “CTBT relevant function” refers to the list of functions (provisional National Authority, NDC, subdivision of NDC dealing with specific technologies) as given in CTBT/WGB-12/1, quoted above. The Establishment might be part of a larger Organization.

Name of the Establishment CTBT relevant function Organization

Address

City Country Phone Fax E-mail

Name of the Establishment CTBT relevant function Organization

Address




C. Designated Principal Users for Accessing the IDC Individuals can be designated as Principal Users for the purposes of initial testing. A maximum of eighteen Principal Users can be designated at the Establishments, listed in section B. The PTS will provide each Principal User with the login, password, documentation, policies and procedures necessary to obtain access to IMS data and IDC products. If one of the Principal Users is the same as the Principal Point of Contact, note this below. Full Name Position Establishment

Address

City Country Phone Fax E-mail E-mail address from which AutoDRM requests are to be sent

Full Name Position Establishment

Address

City Country Phone Fax E-mail E-mail address from which AutoDRM requests are to be sent



D. Designated Regular Users for Accessing the IDC Individuals can be designated as Regular Users for the purposes of initial testing. The number of Regular Users should normally be limited to about ten per State Signatory. The Principal Point of Contact must justify requirements considerably greater than this number of ten Regular Users to the PTS. The PTS will provide each Regular User with the login, password, documentation, policies and procedures necessary to obtain access to IMS data and IDC products though the IDC Secure Web site. Full Name Position Organization

Address


Full Name Position Organization

Address




E. Designated IMS Station Operators and IMS Station Maintenance Personnel Individuals can be designated as IMS Station Operators, including station maintenance personnel, for the purposes of initial testing. The PTS will provide each IMS Station Operator with documentation and policies and procedures necessary to obtain access to station status reports and to waveform data from their stations which is already stored at the IDC. Full Name Position Organization

Address

City Country Phone Fax E-mail IMS station/s

Full Name Position Organization

Address

City Country Phone Fax E-mail IMS station/s

F. Please enter any additional comments or questions below:



The second step is to receive information from the IDC regarding user accounts and passwords. This information will be sent by mail or courier service to the principal and the regular users. The receipt of the password has to be acknowledged by the user. The Principal Point of Contact may ask the PTS for modifications of the list of users and the passwords. The password security policy implemented internally at the IDC is described below, in italics. The IDC would appreciate if the users adopted a similar policy. Use of the login or password is intended only for the authorized individual to whom it was issued. The login or password should not be shared with any other person. The individual to whom the login or password has been issued is considered by the IDC as responsible for its use. To assure the confidentiality of the password, it is common to follow guidelines like these: • The password should not be observed by any other person. • The password should be kept safely locked, where no one other than the authorised user

can obtain it. It should be returned to its locked location as soon as it is used. • The login or password should not be stored in a file on any computer. The user accounts and passwords will be needed for getting access to the IDC Secure Web site and to download large data files by the Web browser. The principal users have access also to the subscription and AutoDRM systems at the IDC. For these systems, the e-mail address in the header of an incoming subscription/request message is checked against the list of e-mail addresses of principal users provided in the Registration Form. The check is not case-sensitive. The principal users can also request to be given direct access to the copy of the IDC databases and will then be given SecurID cards for generation of one-time passwords. The users are responsible for the proper use of IMS data and IDC products and services according to the regulations in the Treaty and to the decisions of the PrepCom. A principal user can ask for technical assistance. Procedures will be established for requesting special services. Requests for the services provided in this category should be made through the IDC customer service staff. To avoid overlapping requests, it is the responsibility of the principal users to coordinate requests for data subscriptions, national event screens and expert technical assistance with the Principal Point of Contact. Technical assistance with accessing the IDC, however, will be given to every user and station operator. IMS station operators should send a message to the IDC customer service ([email protected]) with a request for station status information or waveform data from their station/stations. Only waveform data already stored at the IDC are available.



How to Get Access to the IDC The last step to be taken after being recognised as a user is to establish the connection to the IDC. The communication links between the NDCs and the IDC are provided by the Internet or the Global Communications Interface (GCI) which is managed by the IDC. The GCI service is provided by six satellites and terrestrial lines. The State Signatories have a choice between a VSAT link and an Internet link between the NDC and the IDC. Some State Signatories with many IMS stations and corresponding data volumes to the IDC will for this reason be connected directly to the terrestrial backbone of the GCI (Frame Relay link). The standard distribution, or daily volume of data from the IDC to the NDC is defined as: (i) For NDCs using a VSAT connection to the IDC: 150 megabytes, or the volume of IMS data transmitted by the State Signatory to the IDC, whichever is the larger. (ii) For NDCs using a terrestrial link to the IDC: 150 megabytes, or the volume of IMS data transmitted by the State Signatory to the IDC, whichever is the larger. (iii) For NDCs that are part of an independent subnetwork: 150 megabytes, or the volume of IMS data transmitted by the State Signatory to the IDC, whichever is the larger. (iv) For NDCs using an Internet connection to the IDC: 250 megabytes, or the volume of IMS data transmitted by the State Signatory to the IDC, whichever is the larger. NDCs connected in accordance with subparagraphs (i) – (iii) may in addition use the Internet for data distribution from the IDC. If the data volume is larger than the standard distribution, special arrangements have to be made and the additional cost for the extra communication capacity has to be carried by the State Signatory. State Signatories that have chosen a VSAT link may use the Internet before, and in addition to, the establishment of the VSAT link. The paper CTBT/PTS/INF.156/Rev.2, distributed at the 9th session of WGB, contains a GCI questionnaire on contacts and communication options. NDCs, which not already have completed a GCI questionnaire will be asked to complete it. NDCs that have chosen an Internet link will need to procure the services of a local Internet provider and install Internet software.



Data and Products to be provided by the IDC The Initial Plan for the Progressive Commissioning of the IDC (as defined in CTBT/PC/II/1/ Add.2, Appendix V) describes seven Phases. This Plan was revised in CTBT/PC-15/1/Annex II, Appendix IV and Phase 5 divided into 5a and 5b. The IDC is currently in Phase 5a, “Preparation for Full Scale Testing of the IDC Hardware/Software”. The Release 3 of the application software was installed at the IDC in May 2001 and the software is now maintained and further developed and tuned by the IDC. This chapter describes the IMS Data and the IDC Products and comprises the following topics: DESCRIPTION OF DATA AND PRODUCTS

Introduction

Data

Integrated List of Signal Detections

Event Lists and Bulletins

Standard Screened Event Bulletins

AVAILABILITY DURING PREPARATION FOR FULL SCALE TESTING



DESCRIPTION OF DATA AND PRODUCTS The IDC processes the data from IMS stations and generates a number of standard products, the first ones automatically and the later ones after analyst review. Automatic event screening is applied as one of the last steps. The processing steps and the products are shown below in Figure 1.

Figure 1. The IDC processing is depicted as a pipeline with the IMS data flowing into the IDC at the top of the figure and the IDC products flowing out of the IDC at the bottom. Within the large volume of IMS raw data are signals from both natural and man-made events. The IDC applies automatic signal processing methods to raw IMS data to extract parameters from the data. The processing results in signal detections and includes, for each signal detected, a set of standard signal parameters and associated uncertainties. At each stage of the automated processing of the seismoacoustic data, the signal detections are integrated into signal detection lists known as the “Standard List of Signal Detections” (SLSD). For the radionuclide technology the detection list is known as the “Automatic Radionuclide Report” (ARR). Signal parameters from the detected signals are processed in order to estimate when and where the causative events occurred. The products that result from this processing are event lists (which are the result of automated processing) and bulletins (which have been reviewed by expert analysts). The different event lists and bulletins represent different stages of refinement in the processing scheme, with the “Reviewed Event Bulletin” (REB) as the result



of analyst review. For the radionuclide technology, the result of the analyst review is released as a “Reviewed Radionuclide Report” (RRR). Finally event screening is applied and the “Standard Screened Event Bulletin” (SSEB) and its corresponding radionuclide product, the “Standard Screened Radionuclide Event Bulletin” (SSREB) are produced and used as a basis for fusion of all four technologies. The result of the IDC processing of one data day and the status of the IMS stations and the GCI links is summarised in the “Executive Summary”. Data Although IMS data are not products of the IDC, the IDC does make them accessible to States Signatories through the same mechanisms as the IDC products. IMS data are described in the Operational Manuals for the IMS. IMS data offered for selection by the IDC during operation of the current software include: • Continuous waveforms from the primary seismic, hydroacoustic and infrasound stations; • Segmented waveforms from the primary seismic, hydroacoustic and infrasound stations; • Segmented waveforms from the auxiliary seismic stations; • Segmented waveforms from the seismic, hydroacoustic and infrasound stations associated

with events listed in the REB/SEB; and • Sample pulse height data from radionuclide stations (SPHDF and SPHDP) • Other types of pulse height data from radionuclide stations (DETBKPHD, BLANKPHD,

CALIBPHD and QCPHD) Integrated List of Signal Detections Standard Lists of Signal Detections (SLSD) A Standard List of Signal Detections (SLSD) is a collection of signal parameters and their estimated uncertainties for seismic, hydroacoustic or infrasound stations that contain all signals detected at that facility over some time period. The signal detections in the SLSDs are ordered by signal detection time. Automatic Radionuclide Report (ARR) This report results from the application of automated processing of the gamma spectroscopic pulse height data. The report contains information concerning the physical collection of each sample; processing parameters; provisional peak detection information and radionuclide identification; calibration information; and the minimum detectable concentrations of key radionuclides.



Event Lists and Bulletins Standard Event Lists (SELs) These include seismic, hydroacoustic and infrasound signal parameters along with event parameters and their associated uncertainties. Event lists are produced without analyst review and so may contain improperly associated or mislocated events. Improperly associated events will be removed and additional events may be added during analyst review. Standard Event List, SEL1, contains only primary seismic and hydroacoustic information. The SEL2 is produced from signal parameters used to generate SEL1 as well as the signal parameters from some auxiliary seismic stations, additional hydroacoustic information, and some infrasound stations. The third and final event list, SEL3, incorporates any signal parameters from late arriving data. Reviewed Event Bulletin (REB) The Reviewed Event Bulletin (REB) is derived from the SEL3 by confirming, correcting, deleting and adding arrivals and events through expert review of the SEL3 results and raw IMS data by trained analysts. The REB represents the best routine estimate of the seismic, hydroacoustic and infrasound events that meet the IDC event definition criteria at the time that the REB is produced. It includes updated values of all signal and event parameters that appear also in the Standard Event Lists. Standard Event Bulletin (SEB) The SEB contains all information available in the REB, plus additional signal and event parameters. These and the previously calculated parameters are combined to form event characterization parameters. Event screening metrics are computed for each event to indicate numerically the degree to which the event meets, or does not meet, the standard event screening criteria. Reviewed Radionuclide Report (RRR) A Reviewed Radionuclide Report (RRR) is produced for each air filter sample that is exposed to the airflow and from which gamma rays are subsequently counted. A separate RRR is similarly produced for each noble gas sample. The RRR contains the final results of analyst review of the automated radionuclide processing. In addition to sample information included in the ARR, the RRR provides confirmed information on all nuclides detected during the automated and interactive analyses, sample categorization information, and field of regard information indicating air movement relevant to the sample measurement period.



Standard Screened Event Bulletins Standard Screened Event Bulletin (SSEB) Events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena are screened out, using the event screening metrics already computed in the SEB. The SSEB consists of events which have sufficient data but which do not meet the event screening criteria and events that lack sufficient data to apply the event screening criteria. The SSEB contains all information available in the SEB, but only for the subset of events that are not screened out. Standard Screened Radionuclide Event Bulletins (SSREB) Standard Screened Radionuclide Event Bulletins (SSREB) are bulletins based on the analysis of data from the radionuclide stations. They are generated only when man-made fission or activation products are detected and analysed at a radionuclide station above specified normal limits. The SSREB results from the application of screening criteria to the characterization of the radionuclides identified in each RRR. An RRR is not screened out if the RRR indicates the presence of an anomalous measurement in the sample of one or more fission products, or activation products, which is on the standard list of relevant nuclides. An SSREB is released for each RRR that is not screened out. Each SSREB contains information identifying the fission products or activation products; an estimate of the regional source location; and if available, certified laboratory results and isotopic ratio calculations. Executive Summaries The executive summaries contain condensed information on the number of seismic, hydroacoustic, infrasound and radionuclide events; screening information; and statistics on the status of the IMS and IDC systems for a given dataday. The radionuclide network product summary (RNPS) provides a compilation of the status of collection, processing and analysis of data from all radionuclide stations.



AVAILABILITY DURING PREPARATION FOR FULL SCALE TESTING States Signatories are able to select subsets or extracts of the IMS data and IDC products based on specific criteria through IDC Subscription, AutoDRM and Web browser interfaces. Table 1 lists the IMS data and IDC products available at the IDC during the operation of the current software and gives the available selection criteria for each product and access method. In general, IMS data and signal detections may be selected based on the station, the time that they were collected at the station, or their association with an established event. Event lists and bulletins may be selected based on event parameters (location, origin time, depth, magnitude) or on the event metrics. The time when each product is expected to be available by subscription and AutoDRM requests is also given. The Secure Website has a delay of a few hours. The copies of the IDC Databases are updated very frequently.

Table 1: IMS Data and IDC Product Selection Criteria Access Method Product Time when

available Subscription AutoDRM Secure Website IMS Data Continuous Waveforms

near real-time station not available not available

Segmented Waveforms from primary seismic, hydroacoustic and infrasound stations

near real-time not available station, channel, time not available

Segmented Waveforms from auxiliary seismic stations

12 hours after real-time if data was requested by the IDC

station station, channel, time not available

Associated Wave- forms to the REB

2 hours after the REB is released

station, channel, event parameters

station, channel, event parameters, time

displayed, but not possible to download

Sample Pulse Height Data, SPHD

2 - 3 days after end of data collection

station station, time station, station&time

Other Pulse Height Data

4 - 6 hours after real-time

station station, time not available

IDC Products SLSD 2 hours after real

time, updated later station station, time not available

SLSD (associated with events)

2 hours after real- time, updated later

station, event listassociation

station, event list association, time

not available

ARR 2 -3 days from end of data collection

station station, time station, station&time

RRR 3 - 4 days from end of data collection

station station, time station, categorisation level,



time Access Method Product Time when

available Subscription AutoDRM Secure Website SEL1, SEL2, SEL3 2, 6 and 12 hours

post-event event parameters event parameters, time event parameters,

dataday REB Relaxed schedule:

6 -10 days from end of data day

event parameters event parameters, time event parameters, dataday

SEB event parameters event parameters, time event parameters, data day

SSEB event parameters event parameters, time event parameters, data day

SSREB 3 - 4 days from end of data collection; updated later

station station, time station, categorisation level, time

Executive Summary

36 - 64 hours from end of data day

not available dataday dataday

Access Method System monitoring output

Time when available Subscription AutoDRM Secure Website

STA_STATUS 6 hours from end of dataday

station station, dataday station, dataday (in graphical form)

CHAN_STATUS 6 hours from end of dataday

available with no constraints only

dataday not available

For SPHD and ARR on the Web, selection has to start with the station; time alone is not possible.



Accessing the IDC AutoDRM This chapter describes the request message formats and comprises the following topics: Introduction

How to obtain the AutoDRM Help Guide

Request Format Description

Request Environment Lines

Request Lines

Multiple Requests in a single E-mail



INTRODUCTION There are four access methods for retrieving data and products from the IDC: an e-mail based system (AutoDRM), pre-set subscriptions, an interactive system on the Web Server that may be accessed through standard Web Browsers and a copy of the IDC Databases. The subscription system uses the AutoDRM software to carry out most of its functions, so a subscription and a request message look very similar. The AutoDRM, subscription and IDC Databases systems can only be accessed by a principal user. Although there are many types and selections of data that could be retrieved from the IDC, a typical request might use a relatively small subset of the available selection parameters. This subset is described in this Guide. A full description is found in “Formats and Protocols for Messages” [IDC3.4.1 Rev5]. The IDC maintains an Automatic Data Request Manager (AutoDRM) to respond to e-mail requests from principal users in State Signatories for IMS data and IDC products. This service allows custom requests for any tabular data and for non-continuous (segmented) waveform data. If the volume of data requested through the AutoDRM is large (more than 5 Mbytes), the data requested will be placed on a file system at the IDC for downloading using a Web browser. See “Accessing the IDC Secure Web site”. An email message is sent to the user with information on the location of the data. The data will be stored on the file system for at least one week. When a data request is received a check will be made to see that the requestor is a principal user (see the section “Who are the IDC Users”) and that the amount of data returned will not exceed 250 Mbytes per day. Requests that are not sent by a principal user will be rejected. If a request is expected to exceed the limit on data volume, a notification will be sent to the user stating the need for special arrangements, e.g. establishing an enhanced distribution which will have financial implications. HOW TO OBTAIN THE AUTODRM HELP GUIDE To receive an electronic copy of the IDC AutoDRM Help Guide, an user may send a blank e-mail message with the word “HELP” (case-sensitive) in the subject line to [email protected]. The Help Guide will be e-mailed to the source address of the message. It is basically a copy of the AutoDRM and subscription parts of this document, including the tutorial. REQUEST FORMAT DESCRIPTION Requests should be sent to [email protected] and must be formatted according to “For-mats and Protocols for Messages” [IDC3.4.1 Rev5]. Not all of the functionality described in this reference has been implemented yet. The current functionality is summarised below. There is also a template on the IDC Secure Web site that can be used to create requests to the AutoDRM but not all options, available with the current software, are included in the template. The template is basically a message editor, so it is only useful for principal users.



Table 2: General structure of a request message Line # Syntax Example of contents Description 1 begin message_format

message_format could be ims1.0 or ims2.0

begin ims1.0 message version number

2 fixed (for a request message) msg_type request specifies the type of message

3 msg_id id_string [source] id_string is a unique message identification code (up to 20 characters) containing no blanks or \. Sender can place anything here. source (optional) is a 3-letter country code followed by “_ndc”.

msg_id abc23 any_ndc assigns an identification code to the message as an help to the sender in connecting the answer to the request. Useful for internal tracking if the sender has sent many requests.

4 e-mail address e-mail name@domain_name the e-mail address to which the answer should be sent

5 to (N-1)

customisable (described below) (environmental and request lines will be placed here)

N stop stop end of message The first three lines are the same for all types of messages, except that in this case the msg_type is request. This indicates that a discrete amount of data or products has been requested and is to be delivered upon request, not periodically as by subscription. The fourth line (e-mail name@domain_name) is a request control line giving the e-mail address to which the IDC should send the answer. The fourth line could instead have been given as ftp name@domain_name in which case the IDC stores the answer to the request as a local file and sends an e-mail to name@domain_name notifying that the file is ready to be downloaded using a Web browser and giving the name and location of the file. Requests are defined through environment lines that constrain the data to be sent and request lines that specify which data to send. All lines in a request message are free-format lines. Free-format lines are left-justified and case-insensitive. In the examples lower case is used, as the main reference documents use lower case, but upper case is also allowed. Free-format lines must have one or more blank spaces between fields. The answer to a request message will usually be a fixed-format data message.



REQUEST ENVIRONMENT LINES There are many environment lines (used to constrain the data to be sent in answer to the request) described in detail in “Formats and Protocols for Messages” [IDC3.4.1 Rev5]. Most of the environment lines are optional. If the optional lines are omitted the default values are used. The mostly used environmental keywords are: BULL_TYPE - specifies the type of seismoacoustic bulletin to be delivered. The valid bulletins are sel1, sel2, sel3, reb, seb and sseb. idc_sel1, idc_sel2, idc_sel3, idc_reb, idc_seb and idc_sseb can also be used. There is no default and BULL_TYPE has to be defined when relevant (i.e. for requests of bulletins, events, origins or arrivals). TIME - time range; date and time can be set. For example, time 2003/02/01 23:14:19.7 to 2003/02/01 23:29:19.7 selects 15 minutes. Default is current date and time. If only the date is given, the default time is 00:00:00. time 2003/02/01 to 2003/3/1 12 sets the time range from 2003/02/01 00:00:00.0 to 2003/03/01 12:00:00.0 LAT - latitude range in degrees. For example, lat -12 to 17 limits latitudes to a range from 12 degrees south to 17 degrees north. LON - longitude range in degrees. For example, lon -30 to 90 limits longitudes to a range from 30 degrees west to 90 degrees east. DEPTH - event depth range in kilometres. For example, depth 0.0 to 10.0 limits depths to a range from 0 to 10 km. MAG - magnitude range. For example, mag 4.0 to means all magnitudes at 4.0 or above. MAG_TYPE - the type of magnitude to search when MAG is provided. For example, mag_type mb, Ms requires both magnitude types to be in the defined range. Only mb, Ms and ML can be specified, not any of the other magnitude types. STA_LIST - is the list of stations. If an array station is specified, then all elements of the array are implied. Specific array elements may be referenced individually. The stations must be delimited by commas. For example, sta_list STKA, A* gives STKA and all stations beginning with “A”. If omitted from the message, all stations will be provided. The wildcard character, ‘*’, also does this. CHAN_LIST - is the list of channels. The channels must be delimited by commas. If omitted the vertical channels are provided. For example, chan_list shz, shn, she gives three short-period channels. The wildcard character, ‘*’, yields all channels. RELATIVE_TO - allows a user to request waveforms associated with a particular set of events. The arguments are: bulletin, event or origin. The selection of the bulletin or



events has already been done in the lines before relative_to. The waveform request line has to follow as the next line. REQUEST LINES Request lines specify what type of data to be sent in answer to the request. The most common request keywords for seismo-acoustic data or products are: WAVEFORM - requests seismo-acoustic waveforms. ARRIVAL/SLSD - requests the seismo-acoustic product SLSD with arrival information. BULLETIN - requests a seismo-acoustic bulletin product. EXECSUM - requests the executive summary. STA_STATUS - requests the station status reports CHAN_STATUS - requests the channel status reports STATION - requests station information RESPONSE - requests station instrument response Table 3: Environment variables required or optional for each seismo-acoustic request

Environments waveform arrival/

slsd bulletin execsum sta_status chan_

status station response

bull_type r r time r r r r r1 r1 o lat o o lon o o depth o mag o o mag_type o o sta_list o o o o o o o chan_list o o relative_to o r = required, o = optional 1. Minimum precision is days at the IDC.



For radionuclide data or products: DETBKPHD - requests the radionuclide data PHD of an empty detector chamber BLANKPHD - requests the radionuclide data PHD of an unexposed air filter CALIBPHD - requests the radionuclide data PHD of a standard calibration source QCPHD - requests the radionuclide data PHD of a 15 minutes sample acquisition time SPHDP - requests the radionuclide data SPHD (preliminary, shorter acquisition time) SPHDF - requests the radionuclide data SPHD (full acquisition time). ARR - requests the radionuclide product ARR RRR - requests the radionuclide product RRR SSREB - requests the radionuclide product SSREB

Table 4: Environment variables required or optional for each radionuclide request Environment detbkphd blankphd calibphd qcphd sphdp sphdf arr rrr ssreb

time r r r r r r r r r sta_list o o o o o o o o o

r = required, o = optional MULTIPLE REQUESTS IN A SINGLE E-MAIL Separate requests are delimited as separate messages. In other words, each begin/stop sequence describes a single request which will be sent to the user as a single message. To avoid confusion, it is highly recommended that each request be kept simple; e.g., request the SEL2 and REB as separate requests rather than as combined into a single request. Several request messages may be contained in a single email. In the “Tutorial” on page 44 many examples of requests are given.



Establishing IDC Subscriptions This chapter describes the formats for subscription messages and comprises the following topics: Introduction

Subscription Procedures

Subscription Format Description

Subscription Environment Lines

Subscription Request Lines



INTRODUCTION The IDC subscription service allows principal users to arrange for automatic and regular forwarding of IMS data and IDC products to a State Signatory. A principal user may specify the types and amounts of data to receive, and the frequency with which to receive them (for example, immediately, daily etc.). Subscriptions, if established without a specified end date, continue until the requesting party cancels the subscription or changes the parameters of the subscription. IMS data and IDC products are available through subscription (see Table 1 for details). Continuous IMS waveform data are only available through the subscription service. Subscriptions for immediate delivery of continuous IMS waveform data (data forwarding) require that a link with the continuous data transfer protocol be established between the IDC and the receiving NDC. Subscriptions support selection criteria, so that only the information that is of interest to the user is delivered. The total amount of data forwarded to an NDC per day may not exceed the 250 Mbytes limit unless special arrangements have been made. SUBSCRIPTION PROCEDURES Subscriptions are set up by sending a subscription message to the IDC. Upon receipt, the source of a subscription message is validated being from a principal user and the volume of data that will be typically generated by the request is computed. Subscription messages that are not sent by a principal user will be rejected. If a subscription is expected to exceed the 250 Mbytes per day limit, a notification will be sent to the user stating the need for special arrangements, e.g. establishing an enhanced distribution which will have financial implications. After validation, the new subscription is added to the existing subscriptions for that user and assigned a unique identification number at the IDC. The subscriber receives a LOG data message from the IDC as confirmation of the subscription, e.g. after sending a subscription message for the REB: BEGIN IMS1.0 MSG_TYPE DATA MSG_ID 2143803 GSE_IDC DATATYPE LOG IMS1.0 SUBSCRIPTION ID: 499 PRODUCT ID: 4 was added at 2004/07/23 08:59:27 FREQ DAILY BULL_TYPE REB BULLETIN IMS1.0 STOP



The product identification number (PRODUCT ID in the LOG message above) is a unique identifier for a certain IDC product and may be shared by multiple subscribers, while the subscription identification number (SUBSCRIPTION ID) is a unique identifier for a particular subscription. After the subscription begins, data messages sent to the subscriber include, as the fourth line, the PROD_ID line that includes two numbers. The first is the product id (same as above) and the second the delivery id which identifies a specific delivery. The delivery id is a counter which is increased with one for each delivery. As an example: BEGIN IMS1.0 MSG_TYPE DATA MSG_ID 2143906 GSE_IDC PROD_ID 4 112 DATA_TYPE BULLETIN IMS1.0:SHORT Reviewed Event Bulletin of the CTBT_IDC from 2004/07/18 00:00:00 to 2004/07/19 00:00:00, generated 2004/07/23 15:44:38 EVENT 27181 NEAR EAST COAST OF HONSHU, JAPAN (the rest of the REB follows) STOP The product id for this product is 4 and the delivery id for this specific dataday is 112. The next delivery (the REB for July 19) will as the fourth line have: PROD_ID 4 113. The three identifiers are helpful if the user wants to cancel the subscription. They can also be used when requesting a re-delivery of a subscribed product. To achieve this, the identifiers are combined with subscription requests of a more general nature as described below (see e.g. Table 8). SUBSCRIPTION FORMAT DESCRIPTION Subscriptions will eventually be made using the IMS message formats which are described in “Formats and Protocols for Messages” [IDC3.4.1 Rev5]. Some of the commands, described in that extensive reference, have not been implemented at the IDC. All commands described below, however, have been implemented in the current software. To subscribe, e-mail to [email protected] a formatted subscription message based on the template described below (subscription and AutoDRM messages are in principle case-insensitive, but has to be left-justified i.e. blanks are not allowed at the start of the lines). There is also a template on the IDC Secure Web site that can be used to create subscription requests but not all options, available with the current software, are included in that template.



Table 5: General structure of a subscription message Line # Syntax Example of contents Description 1 begin message_format

message_format could be ims1.0 or ims2.0

begin ims1.0 message version number

2 fixed (for a subscription message)

msg_type subscription specifies the type of message

3 msg_id id_string [source] id_string is a unique message identification code (up to 20 characters) containing no blanks or \. Sender can place anything here source (optional) is a 3-letter country code followed by “_ndc”.

msg_id abc23 any_ndc assigns an identification code to the message as an help to the sender in connecting the answer to the request. Useful for internal tracking if the sender has sent many requests.

4 e-mail address e-mail name@domain_name the e-mail address to which the answer should be sent

5 to (N-1)

customisable (described below)

(environmental and request lines will be placed here)

N stop stop end of message The fourth line is the e-mail address to which the IDC should send the data. The fourth line could also be ftp name@domain_name in which case the IDC stores the subscribed data as a local file and sends an e-mail to name@domain_name notifying that the file is ready to be downloaded with a Web browser and giving the name and location of the file. The final line of any message is the stop line. The message can be customised by inserting environment and request lines after the fourth line and before the stop. These lines contain information that describes how often the IDC will send the responses and what data or products will be sent.



SUBSCRIPTION ENVIRONMENT LINES There are many environment lines (used to constrain the data to be sent and also how often to send the data in answer to a subscription request) discussed in detail in “Formats and Protocols for Messages” [IDC3.4.1 Rev5]. Most of the environment lines are optional. If the optional lines are omitted the default values are used. The structure of a subscription message is very similar to that of a request message and most of the description of the request environment lines above is valid also for the subscription environment. A summary of the most common keywords is given below. However, for subscription the frequency environment could be defined while the time environment in a request message is not applicable for a subscription. BULL_TYPE - specifies the type of seismoacoustic bulletin to be delivered. The valid bulletins are sel1, sel2, sel3, reb, seb and sseb. There is no default and BULL_TYPE has to be defined when relevant (i.e. for requests of bulletins, events, origins or arrivals). FREQ - specifies how often the IDC should send the data or product. The parameter may be daily for delivery each day; continuous when requesting continuous data or immediate when the product is to be delivered as soon as it is formed. The FREQ line may appear only once in each subscription message. LAT - latitude range in degrees. LON - longitude range in degrees. DEPTH - event depth range in kilometres. MAG - magnitude range. MAG_TYPE - the type of magnitude to search when MAG is provided. STA_LIST - is the list of stations. CHAN_LIST - is the list of channels. In addition there are four environment keywords of a more general nature: PRODID_LIST, DELIVID_LIST, SUBSCR_LIST - identification number of the subscribed products, as described above in the section “Subscription Procedures”. SUBSCR_NAME - name of a standard IDC product.



SUBSCRIPTION REQUEST LINES Request lines specify what type of data is being subscribed to. The most common request keywords for seismo-acoustic data or products are: WAVEFORM - requests seismo-acoustic waveforms. Depending on the environmental variables a request can be for continuous data forwarding (FREQ set to continuous), for waveform segments associated to REB events (RELATIVE_TO included in the request) or for waveform segments from auxiliary stations. Subscriptions on continuous data must be set up manually. ARRIVAL/SLSD - requests the seismo-acoustic product SLSD with arrival information. BULLETIN - requests a seismo-acoustic bulletin product. STA_STATUS - requests the station status reports CHAN_STATUS - requests the channel status reports

Table 6: Environment variables required/optional for seismoacoustic subscriptions Environments waveform arrival/slsd bulletin sta_status chan_statusbull_type r r freq o o o o o lat o lon o depth o mag o mag_type o sta_list o r o o chan_list o relative_to o r = required, o = optional



For radionuclide data or products: DETBKPHD - requests the radionuclide data PHD of an empty detector chamber BLANKPHD - requests the radionuclide data PHD of an unexposed air filter CALIBPHD - requests the radionuclide data PHD of a standard calibration source QCPHD - requests the radionuclide data PHD of a 15 minute sample acquisition time SPHDP - requests the radionuclide data SPHD (preliminary, shorter acquisition time) SPHDF - requests the radionuclide data SPHD (full acquisition time). ARR - requests the radionuclide product ARR RRR - requests the radionuclide product RRR SSREB - requests the radionuclide product SSREB

Table 7: Environment variables, optional, for each radionuclide subscription Environments detbkphd blankphd calibphd qcphd sphdp sphdf arr rrr ssrebfreq o o o o o o o o o sta_list o o o o o o o o o o = optional



The subscription system has also some request lines of a more general nature which can be used both for seismoacoustic and radionuclide data/products: SUBSCR_RESEND - requests retransmission of an already delivered subscribed product. UNSUBSCRIBE - requests removal of the specified subscriptions. SUBSCR_LOG - requests a log of all the user’s changes to the subscriptions

Table 8: Environment variables required/optional for each subscription modifier

Environments subscr_resend unsubscribe subscr_log prodid_list * * o delivid_list r subscr_list * * o subscr_name * * o

r = required, * = one of the three environments has to be chosen, o = optional

Multiple Subscriptions in a Single E-mail Separate subscriptions are delimited as separate messages. In other words, each begin/stop sequence describes a single subscription which will be sent to the user as a single message. To avoid confusion, it is highly recommended that each subscription be kept simple; e.g., subscribe to the SEL2 and REB as separate subscriptions rather than as combined into a single subscription. Several subscription messages may be contained in a single email. In the “Tutorial” on page 50 many examples on how to set up subscriptions are given.



Accessing the IDC Secure Web site This chapter describes the IDC Secure Web site and comprises the following topics: Introduction

Web Functionality

Web Access through the Internet

Web Access through GCI Intranet

Downloading of Large Files



INTRODUCTION Interactive access to IMS data and IDC products is provided through the IDC Secure Web site to all principal and regular users. Most of the IDC products available through AutoDRM are also available through the Web (Table 1). WEB FUNCTIONALITY The IDC supports a web server on which most IDC products reside. Many of the web pages are dynamic and are created by queries to the IDC archival database when accessed. Data and products are migrated from the operational to the archival database within hours. The exact migration time is product specific. Several services are provided through this interactive interface: 1. SHI Event Lists and Bulletins All of the REBs and SELs (since September 1999), and SEBs and SSEBs since 28 March 2001 are kept on the web server. Maps of the event locations are also provided with many display options. Global and regional scale maps are available by a zoom function. Plots of waveform segments associated to REB events are available, although it is not possible to download the waveforms. 2. Radionuclide Spectra and Products SPHDs, ARRs, RRRs and SSREBs are available. 3. Executive Summaries An Executive Summary giving an overview of the events in the seismic bulletins and Level 4 and 5 spectra is available. The status of the IMS primary seismo-acoustic network is also given. The Radionuclide Network Product Summary (RNPS) gives an overview of the status of processing of data from the radionuclide stations. 4. Status The data availability for the IMS stations can be displayed on a daily basis. The detection performance of the primary seismic network is provided through plots of the detection threshold as a function of event location. 5. Documents IDC and NDC Documentation are available. All of the products available for browsing on the IDC Web Site are available for retrieval using the tools provided by a web browser. This includes the bulletins, event lists, postscript maps of event locations, documents, etc. The Expert Communication System (ECS) is available (but with another userid and password) and contains reports and discussions connected to Preparatory Commission for the CTBTO and its subsidiary organs.



WEB ACCESS THROUGH THE INTERNET Interactive access to IMS data and IDC products is provided through the IDC Secure Web site. The Uniform Resource Locator (URL) for the IDC Secure Web Site is: https://www2.ctbto.org Users will need a security-enabled web browser, i.e. supporting Secure Sockets Layer (SSL) and will be requested to go through the certificate exchange process during the first and, periodically, subsequent connections. The steps to be taken are: 1. Start the web browser. The IDC supports e.g. Internet Explorer, Netscape and Mozilla. 2. Put the URL above in the address field 3. The IDC presents its certificate to your browser. If you accept this certificate, you will

click “next” on the four first pages and “finish” on the fifth. 4. A window appears asking for User ID and password. You should have received these

from the IDC. See the section “How to Become a User of the IDC”. 5. A window might appear stating that you are now accessing a secure document. Click

“OK”. 6. You are now at the home page of the IDC Secure Web site and can go to the Products

pages. The IDC products can be downloaded to your local computer by clicking on the “Downloading” buttons, located on the Products pages.

WEB ACCESS THROUGH GCI INTRANET The instructions given in the section “Web Access through the Internet” are valid also if the access is through GCI Intranet, but the URL is different: https://www2.gci.ctbto.org or alternatively https://www-idc.gci.ctbto.org The steps to be followed are: 1 Start the web browser. The IDC supports e.g. Internet Explorer, Netscape and Mozilla. 2 Put the URL above in the address field 3 The IDC presents its certificate to your browser. If you accept this certificate, you will

click “next” on the four first pages and “finish” on the fifth. 4 The certificate at the IDC is for the site “www2.ctbto.org” (which is the Internet address)

but your browser detects that you are really talking to “www2.gci.ctbto.org”. Click “continue” if you still believes that you are in contact with the IDC.

5 A window appears asking for User ID and password. You should have received these from the IDC. See the section “How to Become a User of the IDC”.

6 A window might appear stating that you are now accessing a secure document. Click “OK”

7 You are now at the home page of the IDC and can go to the Products pages. Note that access over a VSAT link can appears a bit slow. The IDC products can be downloaded to your local computer by clicking on the “Downloading” buttons.



DOWNLOADING OF LARGE FILES The answer to a request for data or products will normally be sent as an e-mail message. If a file, created as an answer to an AutoDRM request, is larger than 5 Mbytes, the user instead receives an e-mail message giving the link to the message directory at the IDC and the name of the message file. Large files can then be downloaded to the user’s local computer by a Web browser. The e-mail message from the IDC will be formatted as an ftp log and could look like: BEGIN IMS2.0 MSG_TYPE DATA MSG_ID 11210131 GSE_IDC REF_ID xxx DATA_TYPE ftp_log FTP_FILE niue $GUEST https://www2.ctbto.org/msgfiles 11210128.msg.Z Use a Web browser to download the data. The required URL is the above https address followed by a slash, followed by the above message filename. Uncompress data after downloading. The ftp file will be removed on 2005/03/15 STOP The important information in this log is the name of the message file. This can be found last on the line starting with “FTP_FILE”. In this case the name of the message file is “11210128.msg.Z”. The last line on the date of removal is also important. The message file might be removed from the IDC computer, but not before the specified date. The message file can be accessed by typing into the address field of a Web browser the URL: https://www2.ctbto.org/msgfiles/112101282.msg.Z Then press the enter key. The next steps depend on your Web browser and operating system. a). Netscape on UNIX. Netscape will bring up a file dialog to save the file to your hard disk. However, when downloading Netscape deletes the suffix “.Z” and saves the message file by default as 11210128.msg. The user has to rename it to 11210128.msg.Z and then use uncompress: <local-host> mv 11210128.msg 11210128.msg.Z <local-host> uncompress 11210128.msg.Z The renaming of the file can also be done in the file dialog by appending .Z to the default name (11210128.msg). b). Netscape on a PC. You will be able to choose between saving the message file to your hard disk or opening the file (or picking an application). Choose to save the file to your hard disk. Then you can uncompress the file using Winzip or a similar application.



c) Internet Explorer on a PC. If Winzip is installed, Internet Explorer will open the file. You will have to extract the file to your hard disk by executing the appropriate command (e.g. by clicking on the Extract icon in Winzip). If Winzip is not installed, you will be given the choice to open the file or to save it. Choose to save the file to your hard disk. Then you can uncompress the file using Winzip or a similar application. In the “Tutorial” on page 56 an index of the Web site is given, together with pictures of some of the Web pages, showing the contents in more detail.



Accessing the IDC Databases This chapter describes how to access the IDC Databases and comprises the following topics: Introduction

Architecture

Access to the IDC Databases

Access to the IDC Parameter Files



INTRODUCTION The external database service provides the principal users with timely and direct access to the information contained in the operations database, the archival database and the IDC parameter files. ARCHITECTURE Every 5th minute, the changes made to the IDC operational and archival databases are propagated and applied to replicas of the operational and archival databases. These replicas are referred to as EXTODB and EXTADB, respectively, and they reside on the external database server. The login server is available for external access over the Internet and has a connection to the external database server. ACCESS TO THE IDC DATABASES The principal users can send a request to IDC services ([email protected]) to get access to the external database service. The user authentication consists of the user's IP address and a two-factor authentication scheme based on a PIN code (chosen by the user) and a six-digit number displayed on the user's RSA SecurID token card. The token code is changing every minute. The card is provided by IDC services upon request. In addition each user will be given a personal account, password protected, on each of the two external databases. The user also needs secure shell software installed on the user's computer. There are three different methods to connect to the external databases: • Remote SQL access. The user logs into the PTS login server. On the login server the user

can invoke SQL*Plus and connect to one of the external database. The database tables can then be queried using SQL.

• Direct SQL access. The user establishes an SSH tunnel from the user's computer via the

login server to the external database server. This step requires user authentication as above. As long as the tunnel is open, the user can connect directly to the external databases without having to log in to the login server.

• Oracle database links. A tunnel is created from the user's database server to the external

databases. The user can then create a database link between the user's database and the external databases and e.g. copy tables to the user's database.

The two last methods require the user to have Oracle installed locally and to make appropriate changes to the Oracle parameters. Details are given in the appendix. To access the information in the external databases, the user has to understand how the information is stored. The event lists and bulletins, for example, are not stored in one table



but the event information is in one table, the arrivals in another and a third table gives the associations between the events and the arrivals. In total more than ten tables are involved in the creation of an event list. This is described in detail in the IDC documentation available on the IDC secure web site. The very large archival tables, 31 in total, have been split into two in the EXTADB for efficiency reasons. For example, the most recent entries of the WFDISC table are in the database account IDCX while the older entries are in the account IDCX_ARCH. On a regular basis, a few times per year, entries older than two months are moved from the tables in IDCX to IDCX_ARCH. The database accounts REB_ARCH, LEB_ARCH, SEGMENT_ARCH, SEL!_ARCH, SEL2_ARCH and SEL3_ARCH have been created in the same way. ACCESS TO THE IDC PARAMETER FILES Once every month (on the second day) the IDC processing parameter files are copied and merged into 4 tar files. For March 2005 (i.e. 0503) the filenames are: /home/misc/files/0503/EVSC0503.tgz /home/misc/files/0503/GA0503.tgz /home/misc/files/0503/oth0503.tgz /home/misc/files/0503/spec0503.tgz The files are saved for 2 months and can be downloaded to your computer with scp (secure copy). Beware that the total file size needed for uncompressing and untarring the files is approximately 2 Gigabytes. In the Appendix, a more detailed description of how to access the IDC external databases and parameters is given.



Services to be provided by the IDC This chapter describes the IDC Services and comprises the following topics: STANDARD SERVICES

Data Collection, Authentication, Quality Control and Storage

System Monitoring

Threshold Monitoring

Documentation

REQUESTED SERVICES

Special Data Management

Expert Technical Analysis

National Event Screening

Technical Assistance

Assistance to Develop NDC Capability



STANDARD SERVICES IMS data and IDC standard services are provided to States Parties by the IDC on a routine (and largely automated) basis. These services include data collection, authentication, quality control and storage; system monitoring; product selection; and IMS data and IDC product dissemination. Product selection and dissemination have already been described above. Data Collection, Authentication, Quality Control and Storage • Data collection: The IDC will collect IMS data sent over the established links of the GCI,

which is managed by the IDC. • Authentication: All data will eventually be transmitted with a digital signature. The

software at the IDC has the ability to validate the authentication signatures and to generate new signatures for the IDC products.

• Data Quality Control: The IDC will check all incoming data for quality. All data will be available, but data with quality problems will not be used in the IDC processing.

• Storage: The IDC will store the continuous data, waveform segments/spectra and IDC Products indefinitely and securely using the mass-storage device.

System Monitoring The IDC will monitor the state-of-health of the global verification system and make this information available. Although all of the state-of-health information is kept at the IDC, convenient reports on the status of stations, channels and data outages are available through subscription and the IDC AutoDRM. The information in these reports is described below. Station Status (STA_STATUS) The Station Status reports give a summary of the capability and the data availability for each of the IMS stations during one data day. Channel Status (CHAN_STATUS) Another product of the system monitoring at the IDC is the Channel Status reports, which give a summary of the data availability and the number, and size of the data gaps for each channel of the IMS stations. The second part of these reports gives the timeliness of the data at the IDC. Threshold Monitoring Threshold monitoring provides an estimate of the magnitude detection threshold as a function of location and time. The main product of this monitoring is a global map showing the average and worst-case 3-station network detection thresholds on an hourly basis. Noise levels and data gaps are displayed graphically for the primary seismic stations. Threshold monitoring is available on the IDC Secure Web site. Documentation The documentation of the IDC procedures, methods and software is available to the users as a service at the IDC. Documentation is available on the IDC Secure Web Site for browsing or downloading.



REQUESTED SERVICES A number of IDC services available under the Treaty are provided only at the request of the Treaty Organization or an individual State Signatory. Some of these services cannot be reasonably provided in any automated fashion and require operator attention. The resources for these types of services are limited and if the request exceeds a certain level, it will invoke a cost for the requestor. The contact information is given below in the section “How to get Help”. The detailed procedures to be followed are described in the draft “Operational Manual for the IDC”. Special Data Management Confidence Building Measures Data will be received on an experimental basis from States Signatories interested in supplying information regarding mining and similar activity. Procedures and infrastructure for handling other types of special data will be developed. This will require close cooperation with States Signatories hosting CNFs, certified laboratories and the OSI division. Expert Technical Analysis Principal users can, after co-ordination with the Principal Point of Contact, request an in-depth technical review to be done at the IDC for events of special interest, free of charge for reasonable efforts. During the current Phase of IDC development, this will be done on an experimental basis to gain experience with this type of service. National Event Screening National event screening will be implemented on an experimental basis and can be requested by the principal users. Technical assistance Technical assistance with accessing the IDC and formulating requirements for selection, screening and acquisition of data and products will be given to every user. The procedures are described in more detail below, in the section “How to get Help”. Assistance to Develop NDC Capability The IDC is providing a common software package for NDCs, especially designed to receive, display and process IMS data and IDC products. It is currently based on Geotool, squal and CD receiver.



How to get help Customer Service Help The IDC has a unit devoted to providing services to the National Authorities and National Data Centres: the Services and Training Unit. This Unit is the point of contact for raising questions and concerns regarding the IDC products and services, and to obtain assistance in accessing IMS data and IDC products. The Unit can be contacted preferably by e-mail: [email protected], but also by facsimile: +431-26030-5973. If mail is preferred, the mailing address is: Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO) Provisional Technical Secretariat IDC/SR/ST Vienna International Centre P.O. Box 1200 A-1400 Vienna Austria The Unit will attempt to address expeditiously all questions and requests. If the question is a more complex one, it might be sent to other sections of the PTS or even to scientific institutes or hardware/software providers. The user will be informed on the status of the question and when an answer is expected to be available. The IDC is planning to use HelpDesk software to log all user requests and to monitor their status. Reports on the quality of the customer service could also be generated by this type of software.

NDC Training Courses The IDC is currently giving three kinds of training courses for NDC personnel; an introductory course for NDC managers, a course for the NDC technical staff on a regional basis and an advanced course for NDC technical staff. The first two courses give a technical introduction to the tasks of an NDC, mostly focused on the products and services of the IDC, with some hands-on training in the access methods for data and products and the NDC-in-a-box software package. The third course, new in 2005, is intended for experienced users of the NDC-in-a-box software package.

IDC Tours Tours of the IDC can be arranged through the IDC Directorate by calling +431 26030-6165.



Tutorial Requests should be sent as e-mail messages to [email protected] All lines in a request message are free-format lines. Free-format lines are left-justified, i.e. blanks are not allowed at the start of the lines. They are also case-insensitive. In the examples lower case is used, but upper case is also allowed. Free-format lines must have one or more blank spaces between fields. In the examples below, the e-mail address is written in italics as name@domain_name. This must be replaced by the actual e-mail address to which the IDC should send the answer. If this line is omitted, the answer is sent to the e-mail address from which the request originated. Both addresses, the request originator and the recipient of the answer, have to be authorized, otherwise the request will be rejected. The subject line of the e-mail message is ignored and can be left blank. Only examples that are currently supported by the IDC software are included. The Tutorial will be updated when additional functionality is implemented at the IDC. ACCESSING THE IDC AUTODRM Seismo-acoustic data and products Below is an example request for the Reviewed Event Bulletin, REB on October 25, 2004. No constraints are given, i.e., all REB events will be sent regardless of location, magnitude, depth or other parameters. Then the type of bulletin desired is stated as REB (bull_type reb). Finally the request line bulletin ims1.0 is used to specify that the bulletin is wanted in IMS1.0 format. If ims1.0 is omitted, the default will be applied and that is the format defined in the begin line (also ims1.0 in this case). begin ims1.0 msg_type request msg_id ex009 any_ndc time 2004/10/25 to 2004/10/26 bull_type reb bulletin ims1.0 stop Users might be interested in receiving REBs constrained to certain geographic regions. The following message requests all those events in the REB, within two specified latitude-longitude boxes, for the month of November 2004, whose depths are less than 30 km and whose mb magnitudes lie between 3.5 and 4.0. Note that in this case the request line (bulletin ims1.0) has to be given twice, once for each region. It is also necessary to specify the type of magnitude (with mag_type), otherwise the magnitude limits are ignored. The environmental lines are valid until they are explicitly changed, so the mag and depth ranges have only to be defined once.



begin ims1.0 msg_type request msg_id ex042 any_ndc time 2004/11/01 to 2004/12/01 bull_type reb mag_type mb mag 3.5 to 4.0 depth to 30 lat -30 to -20 lon -180 to -140 bulletin ims1.0 lat 35 to 45 lon 110 to 140 bulletin ims1.0 stop Users might be interested in the automatically produced event lists. The following request message requests the SEL3 automatic event list for November 14, 2004. begin ims1.0 msg_type request msg_id ex041 any_ndc e-mail name@domain_name time 2004/11/14 to 2004/11/15 bull_type idc_sel3 bulletin stop Requests for the SLSD and the SLSD associated can also be submitted. Note that “arrival” is a synonym for “slsd” that also can be used. The following message requests automatically detected arrivals from stations AKASG, GERES and KMBO in the SEL1 account for the month of February 2005. Unassociated arrivals will also be included. Chan_list can not be used; it will return a message with no data. begin ims1.0 msg_type request msg_id ex006 any_ndc time 2005/02/01 to 2005/03/01 bull_type sel1 sta_list AKASG,GERES,KMBO slsd:automatic stop The following message requests the arrivals at stations CTA and HFS which are associated to events in the REB bulletins for the first days of December 2004 (arrival defaults to arrival:associated):



begin ims1.0 msg_type request msg_id ex007 any_ndc time 2004/12/01 to 2004/12/07 bull_type reb sta_list CTA,HFS arrival stop Raw data (waveform data) from the IMS stations are also available. The available format for waveform data is the IMS1.0 format, with the sub-formats INT and CM6. The following message requests the waveform segments associated to events found in the REB between 1:45 and 2:00 on December 6, 2004 and also the REB events themselves. Presently REB is the only bulletin for which requests of associated waveform segments are fully supported. These types of request use a special waveform segment archive which is only built with REB events, so if e.g. an event in the SEL3 was rejected in the interactive analysis, there will be no associated waveforms available. begin ims1.0 msg_type request msg_id ex002 any_ndc e-mail name@domain_name time 2004/12/6 1:45 to 2004/12/6 2:00 bull_type idc_reb bulletin ims1.0 relative_to bulletin waveform ims1.0:cm6 stop If the line bulletin ims1.0 is omitted, the associated waveform segments, but not the bulletin itself, will be obtained. Waveform segments can also be requested by giving a time interval. The following message requests data from all channels of stations CMAR and PDAR from 1:00 to 1:15 on January 9, 2005. Waveform data before August 2001 are also available, but the request has to be sent to another e-mail address [email protected] begin ims1.0 msg_type request msg_id ex030 any_ndc e-mail name@domain_name time 2005/1/9 1:00 to 2005/1/9 1:15 sta_list CMAR,PDAR waveform ims1.0:int stop



Two products are available from the system monitoring. For these status reports it is not possible to select only a few hours; the whole data day will be returned. Status reports for individual stations can however be selected by sta_list. The daily status reports for station ARCES for February 2005 is obtained by a message of the following form: begin ims1.0 msg_type request msg_id ex029 any_ndc time 2005/02/01 0:01 to 2005/02/28 23:59 sta_list ARCES sta_status ims1.0 stop The following message requests the channel status reports for all channels at all seismoacoustic stations for February 12, 2005. The sta_list or chan_list environments cannot be used (if given, they are ignored) for chan_status requests, so all channels at all stations are always obtained (this is the default when sta_list and chan_list is not specified). Note also the way the time is specified; a request for 2005/02/12 to 2005/02/13 would give three days in the answer (non-standard behaviour). begin ims1.0 msg_type request msg_id ex015 any_ndc time 2005/02/12 0:01 to 2005/02/12 23:59 chan_status ims1.0 stop Radionuclide data and products Radionuclide data and products are presently only available in IMS2.0 format. Requesting IMS1.0 or RMS2.0 format will give the error message “database error”. This error message will also be returned if there is no data in the requested time interval. The following message requests CALIBPHD (i.e. PHD of a standard calibration source) from all radionuclide stations for the first two months of 2005. Because the STA_LIST environment is not specified the default (all stations) is obtained. begin ims2.0 msg_type request msg_id ex052 time 2005/01/01 to 2005/03/01 calibphd ims2.0 stop By changing the request line calibphd to blankphd, to detbkphd or to qcphd the other types of PHDs are obtained.



The following request message requests SPHDF (full SPHD) and SPHDP (preliminary SPHD with a short acquisition time) from all Australian radionuclide stations for March 1, 2005 (based on collection time): begin ims1.0 msg_type request msg_id ex050 time 2005/03/01 to 2005/03/02 sta_list AU* sphdf ims2.0 sphdp ims2.0 stop The following message requests the automatic product ARRs from radionuclide stations AUP04 and NZP46 for the month of February 2005: begin ims2.0 msg_type request msg_id ex051 e-mail name@domain_name time 2005/02/01 to 2005/03/01 sta_list AUP04,NZP46 arr ims2.0 stop The following message requests RRRs from stations in New Zealand for the month of July 2004. begin ims1.0 msg_type request msg_id ex053 e-mail name@domain_name time 2004/07/01 to 2004/08/01 sta_list NZ* rrr ims2.0 stop The following message requests all SSREBs during the second quarter of 2004: begin ims2.0 msg_type request msg_id ex054 any_ndc time 2004/04/01 to 2004/07/01 ssreb ims2.0 stop



Executive summaries Executive summaries based on all technologies are also available and the seismo-acoustic part can be constrained to certain geographic regions or magnitude ranges. The following message requests an executive summary for December 1, 2004, within a specified latitude-longitude box. Note that for the seismo-acoustic summary the request should be for only one dataday at a time to obtain a correct answer. begin ims1.0 msg_type request msg_id ex085 any_ndc e-mail name@domain_name time 2004/12/01 to 2004/12/02 lat 20 to 60 lon 30 to 120 execsum ims1.0 stop Older data Waveform data from January 1, 1995 until August 3, 2001 can be retrieved by sending an AutoDRM request to [email protected] Tips on Submitting Successful AutoDRM Requests The following are some important points to consider when formatting AutoDRM requests: 1. AutoDRM is case-insensitive; i.e. no difference is made between upper and lower case letters. 2. Commas must be used to separate each station listed on the STA_LIST line. 3. No blank characters may be present at the beginning of a command line. 4. The formats delineated in this Guide must be strictly adhered to. 5. It is advisable to keep the request short. In general, it is better to break up one large request into several smaller ones. This helps the user obtain data faster. Several weeks amount of bulletins could be requested at one time, but not waveforms. Waveform files are much larger and should be requested in small pieces like twenty minutes at a time per request. The error messages sometimes obtained from the IDC AutoDRM should not be taken too literally, as they often do not report the actual error. Many different kinds of errors get the same error message. It is also possible to get an error message if there is no data available at the IDC for the requested time interval.



ESTABLISHING IDC SUBSCRIPTIONS Seismo-acoustic data and products Below is an example request for subscription to the daily Reviewed Event Bulletin, REB. No constraints are given, i.e. all REB events will be sent regardless of location, magnitude, depth or other parameters. The frequency of delivery (FREQ) is set to daily, which means that the REB will be delivered immediately, when analysis has been completed for a whole dataday. Then the type of bulletin desired is stated as REB (bull_type reb). Finally the request line bulletin ims1.0 is used to specify that the bulletin is wanted in IMS1.0 format. begin ims1.0 msg_type subscription msg_id 1040 any_ndc e-mail name@domain_name freq daily bull_type reb bulletin ims1.0 stop Users might be interested in receiving REBs constrained to certain geographic regions. The following subscription message requests events in the daily REB, within two specified latitude-longitude boxes, whose depths are less than 30 km and whose magnitudes lie between 3.5 and 4.0. Note that in this case the request line (bulletin ims1.0) has to be given twice, once for each region. begin ims1.0 msg_type subscription msg_id ex042 any_ndc freq daily bull_type reb mag_type mb mag 3.5 to 4.0 depth to 30 lat -30 to -20 lon -180 to -140 bulletin ims1.0 lat 35 to 45 lon 110 to 140 bulletin ims1.0 stop Users might be interested in the automatically produced event lists. The following subscription message requests the immediate SEL3. Messages will be sent to the user as often as once every 20 minutes.



begin ims1.0 msg_type subscription msg_id ex041 any_ndc e-mail name@domain_name freq immediate bull_type sel3 bulletin ims1.0 stop Subscriptions on the SLSD and the SLSD associated could also be set up. When subscribed to, this product is actually called ARRIVAL. The following subscription message requests all automatic arrivals, at all stations begin ims1.0 msg_type subscription msg_id ex140 any_ndc freq daily sta_list * bull_type sel1 arrival:automatic ims1.0 stop The following subscription message requests the arrivals, at all stations, associated to events in the SEL1 bulletin (note that sta_list is required, although arrivals at all stations are obtained if the selected stations appear at least once): begin ims1.0 msg_type subscription msg_id ex040 any_ndc e-mail name@domain_name freq daily sta_list * bull_type sel1 arrival ims1.0 stop Raw data (waveform data) from the IMS stations are also available. The available formats are the continuous data format (CD-1) for continuous data and the IMS1.0 format for waveform data messages. The sub-format available for the IMS1.0 format is CM6. Continuous data are only available by subscription. According to the "Formats and Protocols for Messages" the following subscription message requests continuous data from the ASAR array:



begin ims1.0 msg_type subscription msg_id 1040 any_ndc e-mail name@domain_name freq continuous sta_list ASAR waveform ims1.0 stop Note, however that at the IDC this request must be handled manually. An e-mail message should therefore preferably be sent to [email protected]. The IP address of the NDC should also be included in the message. To avoid overlapping requests, it is the responsibility of the principal users to coordinate with the Principal Point of Contact. Special arrangements may be needed to utilise a subscription to continuous data. On the average, each seismic station yield a daily data volume of around 10 MB, per channel. Given this, the 150-250 MB limit of data and products per day per NDC can be easily exceeded and a high capacity communications link must then be established by the NDC. Furthermore, the data are sent by the continuous data protocol and the NDC has to install software compatible with this protocol. The details are described in “Formats and Protocols for Continuous Data” [IDC3.4.2] for CD-1 format. A subscription on waveform segments from auxiliary seismic stations received at the IDC can also be set up. begin ims1.0 msg_type subscription msg_id ex063 any_ndc e-mail name@domain_name freq immediate sta_list FITZ waveform IMS1.0 stop Two products are available from the system monitoring. The daily station status reports for a selection of seismoacoustic stations are subscribed to by: begin ims1.0 msg_type subscription msg_id ex053 any_ndc e-mail name@domain_name freq daily sta_list ARCES,FINES,KMBO sta_status ims1.0 stop



The following subscription message subscribes to the daily channel status reports for all channels at all seismoacoustic stations. Note that sta_list or chan_list cannot be used to select specific stations or channels (so all channels at all stations have to be requested as this is the default; nothing will be delivered if a specific station is requested). begin ims1.0 msg_type subscription msg_id ex045 any_ndc e-mail name@domain_name freq daily chan_status ims1.0 stop Radionuclide data and products Radionuclide data and products are presently only available in IMS2.0 format. Requesting IMS1.0 format will give the error message “database error”. The following subscription message requests CALIBPHD (i.e. PHD of a standard calibration source) from all radionuclide stations to be sent immediately when available: begin ims1.0 msg_type subscription msg_id ex043 e-mail name@domain_name freq immediate calibphd ims2.0 stop By changing the request line calibphd to blankphd, to detbkphd or to qcphd the other types of PHDs are subscribed to. The following subscription message requests SPHDF (full SPHD) from all Australian radionuclide stations: begin ims2.0 msg_type subscription msg_id ex052 e-mail name@domain_name freq immediate sta_list AU* sphdf ims2.0 stop The following message subscribes to the automatic product ARRs with no constraints, so all will be obtained as soon as they are produced by the IDC.



begin ims2.0 msg_type subscription msg_id ex038 e-mail name@domain_name freq immediate arr ims2.0 stop The following subscription message requests RRRs from four selected radionuclide stations. begin ims2.0 msg_type subscription msg_id ex037 e-mail name@domain_name freq immediate sta_list NZP46,NZP47,AUP04,JPP38 rrr ims2.0 stop The following subscription message requests all SSREBs to be sent immediately: begin ims2.0 msg_type subscription msg_id ex049 e-mail name@domain_name freq immediate ssreb ims2.0 stop Requesting re-delivery of a subscribed product If an user wants re-delivery of a subscribed product, it can be obtained by a re-delivery request to the IDC. The user has to know the identification number of the product (or the subscription) and the delivery number for the specific product that is wanted. As the delivery numbers are in sequential order, the user can look at the delivery number for the preceding dataday and increment it by one. begin ims1.0 msg_type subscription msg_id ex059 any_ndc prodid_list 1006 delivid_list 1394 resend stop



Obtaining the Subscription List The list of subscriptions that are, or have been, in effect for the user is obtained by a message containing the subscr_log request line. begin ims1.0 msg_type subscription msg_id ex057 any_ndc subscr_log stop The response to this message is a LOG data message from the IDC. This LOG contains a list of all subscriptions, both active and cancelled. BEGIN IMS1.0 MSG_TYPE DATA MSG_ID 11224341 GSE_IDC DATATYPE LOG IMS1.0 SUBSCRIPTION ID: 89 PRODUCT ID: 4 PRODUCT NAME: REB was added at 1999/07/23 08:59:27 FREQ DAILY BULL_TYPE REB BULLETIN IMS1.0 SUBSCRIPTION ID: 90 PRODUCT ID: 1038 was deleted at 1999/07/23 08:59:32 FREQ IMMEDIATE BULL_TYPE REB BULLETIN IMS1.0 STOP Cancelling a Subscription To stop the delivery of a subscription, the product ID number must be known. This is the first number on the fourth line of every delivery from the IDC. The IDs of the subscriptions that are to be deleted are listed on the prodid_list environment line. (It is also possible to instead use the subscr_list or the subscr_name environment lines with the corresponding IDs as obtained in the example above.) This is followed by an unsubscribe request line. begin ims1.0 msg_type subscription msg_id ex060 any_ndc e-mail name@domain_name prodid_list 4 unsubscribe stop A confirmation log message will be sent by the IDC to the subscriber verifying that the subscription has been terminated.



ACCESSING THE IDC SECURE WEB SITE The IDC Secure Web site consists of 7 major categories, of which 5 which are directly clickable, in the top and bottom (Figure 2) of the Web pages. The two others can be found using the menu in the left margin.

Figure 2. The Products page. 1. Standard Products (shown in Figure 2 above) which contains links to Executive Summaries and other summary products: • Executive Summary • Seismic-Acoustic Events List • Radionuclide Network Product Summary (RNPS) A summary of the event screening (obtained by clicking on a link in the Executive Summary) is shown in Figure 3. The Seismic-Acoustic Event List gives the best available event solutions for the specified time period, whether these are from the SELs or the SEBs. In the left margin, there are links to Status Reports, Services and Additional Products, described in the following.



2. Status reports which contains: • Network Status (Data availability for each primary seismoacoustic station and dataday)

This is shown in Figure 4. • Threshold Monitoring (estimated detection thresholds for seismic network, noise levels

and data gaps for primary seismic stations). • AutoDRM status (number of received, queued, failed and finished requests for each day). • GCI Traffic Status (GCI Workflow). Response times, traffic and node up/down events for

each GCI link are shown, but only for the current date. 3. Services which contains: • National Screening (offers a possibility to make ad hoc experiments modifying the

parameters used in event screening. These experiments might be helpful to the States Signatories in, at a later time, formulating the requirements for national screening).

• Custom Bulletin Retrieval (makes available the Product Selection Criteria as defined in Table 1 of this document for seismoacoustic products)

• There is also an interface to the AutoDRM and subscription services of the IDC that contains templates for creating requests. Products and restraints can be selected by clicking on menus. Finally, by clicking on the “Send” button a request message is created and sent to the IDC. The Web browser has to be configured for sending e-mail for this to work properly. Not all functionality available with the current software is shown in this interface, but the message can be manually edited. This interface should only be used by principal users. Although also a regular user has access to this Web interface and can create a request message, this message will be automatically rejected by the IDC, as not coming from a principal user authorized for access to the AutoDRM and subscription services.

4. Additional products, divided into seismo-acoustic and radionuclide products, that contain links to all IDC Products as specified in Table 1. As an example, the Reviewed Event Bulletin is shown in Figure 5. In addition to selecting the data day using the date window in the left margin, there is also a link to a calendar showing for which data days the product is available. 5. Networks which contains:

Maps of the IMS network by technology and information on the stations. Note that only stations providing data to IDC operations are included ("current network"). The list of stations is updated regularly.

6. Documents with links to: • IDC documentation, monthly IDC performance reports, weekly Station Status reports

and NDC-in-a-box documentation. • "Frequently asked questions about NDCs" • System-wide performance test (SPT1) • Status and technical point of contacts of the National Data Centres 7. Site Index: Gives a site map.



Figure 3. The result of the event screening at the IDC. The map in Figure 3 is linked to the Executive Summary (worldwide events). Green events are screened out and red events are not screened out. Blue events are events with insufficient data to do an event screening. Grey events are not considered. Below the map are a list of all events with the event characterisation parameters and the event screening metrics.



Figure 4. Station capability. The station capability for the primary seismic stations for the day February 25, 2005. The colours indicate the percentage of station capability. Red is 0 %, orange is < 70 % but not zero, yellow is 70-90 %, and green is more than 90 %. Capabilities for hydroacoustic and infrasound stations can also be displayed by setting the appropriate tickmark in the box under map annotation/station status.



Figure 5. The Reviewed Event Bulletin. It is possible to modify the map options and by clicking the button “Redraw Map” get the map redrawn with the new options. The map options that can be modified are the click functions, the map projection and the map annotation. By clicking on an event, the details of this event will be displayed. The click function can be modified to instead re-centre the map with the position of the pointer as the new map centre. Modifying the map projection and giving the latitude and longitude of the new centre can also do this. Zoom and map size can also be changed. Finally map overlays are available, e.g. historical seismicity. For the overlay options the names, e.g. “Topographic”, “Tectonic” and “Historical Data”, are clickable links. Click on the name, and an explanation of what the overlay consists of is displayed. Below the map options in this figure the user can, by clicking on any of the links, choose to view the full bulletin in IMS1.0 format or to download the bulletin to a hard disk at the user’s own computer ACCESSING THE IDC DATABASES The document "External Database Service User's Guide" is attached as an appendix.



References - Formats and Protocols for Messages [IDC3.4.1 Rev5] - Format and Protocols for Continuous Data [IDC3.4.2] - Format and Protocols for Continuous Data CD-1.1 [IDC3.4.3] - CTBT/WGB/TL-17/2 “Draft working text of the Operational Manual for the

International Data Centre (May 2002 update)” - CTBT/WGB/TL-11/2/Rev.10 “Operational Manual for Seismological Monitoring and

the International Exchange of Seismological Data” - CTBT/WGB/TL-11/3/Rev.10 “Operational Manual for Hydroacoustic Monitoring and

the International Exchange of Hydroacoustic Data” - CTBT/WGB/TL-11/4/Rev.10 “Operational Manual for Infrasound Monitoring and the

International Exchange of Infrasound Data” - CTBT/WGB/TL-11/5/Rev.10 “Operational Manual for Radionuclide Monitoring and

the International Exchange of Radionuclide Data”



Glossary To help the user in interacting with the IDC and in understanding the documentation, the following abbreviations and words are defined: A ARR Automated Radionuclide Report. AutoDRM Automated Data Request Manager. B BLANKPHD A PHD acquired by counting an unexposed filter paper. C CALIBPHD A PHD acquired by counting a known standard source. CNF Co-operating National Facility CTBTO Comprehensive Nuclear-Test-Ban Treaty Organisation. D DETBKPHD Detector Background PHD F FTP File Transfer Protocol. G GCI Global Communications Infrastructure. I IDC International Data Centre of the CTBTO Preparatory Commission. IMS International Monitoring System of the CTBTO Preparatory Commission. N NDC National Data Centre. P PHD Pulse Height Data PrepCom Preparatory Commission for the CTBTO Product The result of automatic processing of data and/or analyst review. PTS Provisional Technical Secretariat. Q QCPHD Quality Control PHD R REB Reviewed Event Bulletin. RRR Reviewed Radionuclide Report.



S SEB Standard Event Bulletin. SEL1, SEL2, SEL3 Standard Event Lists 1, 2 and 3. SHI or seismo-acoustic Seismic, hydroacoustic and infrasound. SLSD Standard List of Signal Detections SPHDF Sample Pulse Height Data with a full acquisition time. SPHDP Preliminary Sample Pulse Height Data with a shorter acquisition time SSEB Standard Screened Event Bulletin. SSREB Standard Screened Radionuclide Event Bulletin U User A person who is authorized to use IMS data and IDC products and services.

See section “How to become a User” W Web or WWW World Wide Web. Web Server A device which contains the informational site on the Web (e.g., the

IDC). Web Browser A tool for reading information on Web Servers (e.g., Netscape).



APPENDIX

External Database Service User’s Guide

We make IT work.

Computer Infrastructure

Version: Draft 13 February 2003

International Data Centre Computer Infrastructure Section



Table of Contents

1. Introduction............................................................................................................66

1.1 Purpose ...............................................................................................................66

1.2 Audience.............................................................................................................66

1.3 Document history and reference.........................................................................66

1.4 Acknowledgement ..............................................................................................66

2. Background ............................................................................................................67

3. Features of the New Release..................................................................................67

3.1 External Databases .............................................................................................67

3.2 Parameter Files ...................................................................................................68

3.3 Authentication ....................................................................................................68

3.4 Encryption ..........................................................................................................68

3.5 Interactive Shell..................................................................................................68

3.6 TCP Port Forwarding .........................................................................................69

3.7 Data Transfer ......................................................................................................69

4. Service Subscription ..............................................................................................70

5. Configuration and Service Usage .........................................................................70

5.1 Basic Operations with SecurID Cards................................................................70 5.1.1 Initialize SecurID PIN .............................................................................................70 5.1.2 Next PASSCODE Mode..........................................................................................72

5.2 SSH Client Configuration...................................................................................73 5.2.1 Background Information..........................................................................................73 5.2.2 How to get a SSH client...........................................................................................74 5.2.3 Use SSH as a Telnet Terminal .................................................................................74 5.2.4 Use SSH as a Tunnel ...............................................................................................75

5.3 Assess to the External Databases .......................................................................77 5.3.1 Remote SQL Access ................................................................................................77 5.3.2 Direct SQL Access ..................................................................................................78 5.3.3 Oracle Database Links .............................................................................................78

5.3.4 Database Tables …………………………………………………………………. 16

5.4 Access to the Parameter Files.............................................................................17



Introduction

Purpose

The International Data Centre (IDC) has implemented a new release of the external database service to provide the National Data Centres (NDCs) with timely and direct access to the information contained in the operations database, the archive database and the corresponding parameter files. The purpose of this document is to describe the features of the new release and provide guidelines to access the service from the NDCs.

Audience

This guide is for people who access the external database service from the NDCs, referred to as the NDC users. Readers of this guide are assumed to be familiar with relational database concepts and the Structured Query Language (SQL). They are also assumed to be familiar with the UNIX and Windows operating systems.

Document history and reference

REFERENCE: TITLE: External Database Service User’s Guide VERSION CHANGES AUTHOR(S) DATE Version Nr. 1.0 Merged with parameter

access document Peder Johansson Head, Services and Training Unit

February 13, 2003

Version Nr. 1.0 Applied changes to this version

Cong Tang Database Administration Officer

January 17, 2003

Version Nr. 1.0 Applied changes to this version

Giuseppe Maggiore Systems Engineer

January 17, 2003

Acknowledgement

In this document we use information from Jose Guerrero on “One-Time Password system”. We would like to thank the following staff members for their contribution to the success of the external database project: Chee-wai Lai, Christian Korschan, Peter Hindinger, Stefan Radman, Wolfgang Drexler and Zineb Abbali.



Background

The IDC has the requirements to establish a database service to provide the NDCs with read-only access to the information contained in the operations database, the archive database and the corresponding parameter files. This subject was discussed during several evaluation workshops and Working Group B’s sessions. In response to these requirements, the IDC established the first release of the external database service and made it available for testing in September 2001. Because of technical limitations, the first release contained information from the archive database only and was updated once per day. During the eighteenth session, the Working Group B (WGB) recommended that the PrepCom tasked the PTS to improve the service and provide the NDCs with timely (less than five minutes behind real time) and direct access to the information contained in the operations database, the archive database and the corresponding parameter files. In August 2002, the IDC started the development of Release 2 of the external database service. The new release has been successfully implemented in January 2003 and made available to the NDCs in February 2003.

Features of the New Release

The new release of the external database service is expected meet all the requirements from the NDCs as reported during the eighteenth session of the WGB. Some main features of this service are described below.

External Databases

To maintain normal operations of the IDC operations system, the NDCs will be provided with read-only access to replica of the operations and archive databases instead of direct access to these databases. To distinguish from the operations and archive databases, the corresponding replica databases are called External Operations and Archive Databases. The external databases contain approximately 250 millions records from the operations and archive databases. Every day, six millions records in the operations and archive databases are modified, and these changes are propagated to the external databases every five minutes. To access the external databases, the user needs to open a secure shell tunnel from user’s workstation or database server to the login server located at the PTS. Once the connection has been established, the user can access the external databases in one of the following ways:

Remote SQL Access Direct SQL Access Oracle Database Links

Remote SQL Access After having logged into the PTS login server, the user can invoke Oracle SQL*Plus from this machine and execute SQL statements to query the replication tables. The user can also submit his or her scheduled jobs using the crontab or at command. Direct SQL Access It is possible to have direct SQL access from the NDCs. From example, local applications at the NDC sites can be directly connected to the external databases. To enable this feature, the user needs to establish a secure shell tunnel (with TCP port forwarding) from the user’s machine to the PTS login server. Once the secure shell tunnel has been established, direct SQL access is possible through the tunnel.



Oracle Database Links It is also possible to create Oracle database links from the user’s database to the external databases for copying tables from the IDC to the NDCs. Requirements for this type of access is similar to that for direct SQL access. The only difference is that the secure shell tunnel must be initiated from the database server at the NDC site.

Parameter Files

The parameter files used by the IDC monitoring software are organized as several files and stored on the PTS login server. The destination files will be updated monthly to reflect changes to the source parameter files. The NDCs can obtain these files using secure copy (e.g. SCP or WinSCP).

Authentication

Authentication for the external database service is implemented on the following security layers:

User’s IP Address Two-Factor Authentication Scheme Database Authentication

User’s IP Address Any user accessing the service has to provide a static Internet IP address (or range of addresses) from where an initial secure shell connection to the PTS login server will be established. Only users coming from the IP addresses registered with the PTS may connect to the login server. Two-Factor Authentication Scheme User authentication is performed on the login server using a two-factor authentication scheme based on an RSA SecurID token card. In this case, a password (known as PASSCODE) is a combination of a PIN and a token code. A PIN is a secret user-defined alphanumeric string from 4 to 8 characters. A token code is a six-digit number displayed on the user’s RSA SecurID token card. A token code is changing every minute and cannot be reused. The two-factor authentication scheme is compulsory to gain access to the PTS login server.

Database Authentication In addition to the two-factor authentication scheme, each user from the NDCs will be given a personal account on each external database. With these personal accounts, users can query the tables replicated from the operations and archive databases. A personal database account must be authenticated by a password to enable direct SQL access and database links from the NDCs.

Encryption

The external database service provides a security mechanism to encrypt each session from the user’s machine to the login server. This is implemented using built-in features of the SSH protocol.

Interactive Shell



The NDC users may use interactive shells enabled on the login server for the following purposes:

to write user-defined scripts in shell or perl languages to have remote (interactive or automated) SQL access to the external databases

TCP Port Forwarding

SSH TCP Port Forwarding mechanism is implemented on the login server. Essentially, this feature enables the user to create a secure (encrypted) tunnel from the user’s machine to the login server. Insecure TCP services, such as SQL*Net can then be routed through the tunnel. All TCP traffic passing between the hosts, including passwords will be encrypted. The mechanism is described in the following picture.

Secure Encrypted Tunnel

Untrusted NetworkTrusted Network

SSH gatewayserver

Applicationserver

Insecure TCP Service

SSH terminal connection

Insecure TCP Service

With TCP Port Forwarding direct SQL access and database links from the NDCs to the external databases are possible without opening these databases directly to the Internet.

Data Transfer

The data transfer feature is provided via Secure Copy (SCP) command that is bundled with the SSH package. The user can therefore download and/or upload data files between user’s machine and the login server. However, the SCP must be initiated from the user’s machine.



Service Subscription

Access to this service will be given, on request, to all principal users.

A principal user can request access and obtain further assistance by emailing the IDC Services (Email: [email protected]). The user should provide the IDC Services with a list of the IP addresses to be used for accessing the service.

The IDC Services will send a SecurID card to the user by mail. The user should confirm the receipt of the card by sending an email to the IDC Services; otherwise the card

will be deactivated. IDC Services will then provide the username.

Note: All users of the Release 1 can use the existing SecurID cards to access the new service.

Configuration and Service Usage

This section provides details on how to access the external database service from the NDCs. The following topics are covered.

Basic Operations with SecurID Cards SSH Client Configuration Access to the External Databases Access to the Parameter Files

Basic Operations with SecurID Cards

Initialize SecurID PIN

Before you can use your SecurID card to log into the external database service, the PIN must be first initialized. This can be achieved by logging into: https://www2.ctbto.org. At the first time login, you will be prompted to choose a new PIN (please see below). The PIN may contain letters as well as digits of length from 4 through 8 characters. Here are details on how to create your own PIN.

Browse the IDC Secure web site https://www2.ctbto.org. The system prompts you to enter a USERNAME and a PASSWORD.

At the “User Name” prompt, type your USERNAME.



As you have not yet chosen your PIN, at the PASSWORD prompt type the token code that is currently displaying on your SecurID card (6 digits).

Click OK.

If you enter the code incorrectly, the system displays Authorization failed. Wait until your token code has

changed and try again.

Once you have entered a valid code, the system prompts you to perform the New PIN operation.

Wait for the next token code to be displayed on your SecurID card and type it in the Enter SecurID Passcode field.

Type the new PIN you want to use into the Enter a new PIN field. Click on Create New PIN. If you entered a PIN code that contains illegal characters (hyphens, colons, etc.) you will be presented the

message "Illegal new PIN. Please reenter.” Enter a PIN code that contains only alphanumeric characters (upper- or lowercase).

If you entered your token code incorrectly or did not wait for the next token code you will see the message "Passcode not authorized by SecurID. Please reenter.". Please wait for the next token code to be displayed, enter it carefully and try again.

Once your new PIN is accepted, click “Continue”.



Now you can use your SecurID card to log into the IDC Secure web site https://www2.ctbto.org and the PTS login server rlogin.ctbto.org. Your SecurID password (also called PASSCODE) is your PIN followed (without a blank or anything else in between) by the token code currently displaying on your card.

Next PASSCODE Mode

If you repeatedly typed in the incorrect PASSCODE for three times, your SecurID card is automatically set to a so-called “Next PASSCODE” mode. In that case, you need to confirm your possession of the SecurID token with the IDC secure web site https://www2.ctbto.org before you can log into the service again. After ten consecutive failures, your card is locked and you need to contact the IDC Services to have it unlocked. The procedure to confirm your possession of the SecurID card when it is in the “Next PASSCODE” mode is as follows:

Browse the IDC Secure web site https://www2.ctbto.org. After the certificate handshake the system prompts you to enter a USERNAME and a PASSWORD.

Type your USERNAME and PASSCODE (your PIN followed by the current token code.

Click OK

The following window will be displayed even when the PASSCODE has been correctly entered.

Click OK. If you have entered correct USERNAME and PASSCODE, the “next PASSCODE” window will appear

for you to enter the next PASSCODE.



Wait until the token code changes, then carefully type the new PASSCODE (PIN and token code) and click OK.

If you can see the IDC web page below, your SecurID card has been set back to the normal mode.

SSH Client Configuration

Background Information

SSH stands for Secure SHell. A shell is the Command Line Interface found on UNIX, DOS and other

operating systems. In order to gain interactive access to a UNIX machine you typically use a telnet

terminal client. After telnet makes its initial connection, the remote machine asks for your user name

and password. The responses you type are transmitted over the network in clear text. The security

issue with this scenario is that a hacker somewhere on the Internet can monitor the network and

capture your user name and password as they travel across the network from your local machine to the

remote machine. In addition, any other data transmitted during your session is transmitted in clear text



and can be captured by the hacker. A SSH client replaces your typical telnet client and resolves this

security issue because it encrypts the initial handshake as well as the data transmitted during a session.

How to get a SSH client

In order to use the external database service SSH client software needs to be installed on the user’s workstation and database server. The table below shows current web links where some SSH client freeware can be downloaded:

Platform Product Web Link Description

UNIX Open SSH http://www.openssh.com This product is free and usually comes with SSH server and client

Windows PUTTY http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

PUTTY is a free implementation of Telnet and SSH (SCP included) for Win32 platforms. These are small and fast applications.

Windows Winscp http://winscp.vse.cz/eng/ Winscp, based on PUTTY, provides an easy graphical interface, with drag and drop support

It is recommended to use the latest releases of these tools.

Use SSH as a Telnet Terminal

You can use SSH as a Telnet Terminal to the login server.

Syntax: % ssh [email protected]

When prompted for password, enter your SecurID PASSCODE to log into the login server.

If you use PuTTY, here is the equivalent command:

C:\> putty.exe –ssh [email protected]

To use PuTTY in GUI mode, simply run putty.exe without any argument. The PuTTY Configuration window will be displayed:



On the PuTTY Configuration window, navigate to the “Session” category. At the “Host Name” box, enter rlogin.ctbto.org For protocol, check the radio button SSH Click the “Open” button to open an SSH session to the login server

Use SSH as a Tunnel

For security reasons, the external databases are not directly accessible from the Internet. In order to establish direct SQL*NET connections from your machine to the external databases, your SQL*NET client must be able to communicate to the Oracle service running on the IDC external database server ctbto6.ctbto.org, port 1630. This can be achieved by using the following command: % ssh -L 9000:ctbto6.ctbto.org:1630 [email protected] You will be prompted to enter your passcode. Now all TCP traffic sent to the local port 9000 will be routed through the SSH tunnel to port 1630 on the database server ctbto6.ctbto.org as long as the tunnel is left open. Details about direct SQL access will be discussed in section 5.3.2. If you use PuTTY, here is the equivalent command: C:\> putty -L 9000:ctbto6.ctbto.org:1630 [email protected] With PuTTY you can configure TCP port forwarding in GUI mode, which allows you to save the configuration for subsequent sessions. Here are the details: Step 1: Invoke Putty without any argument. Step 2: On the PuTTY Configuration window, navigate to the “Tunnels” under the Connection/SSH sub category



At the “Source port” box, enter local port 9000 At the “Destination” box, enter ctbto6.ctbto.org:1630 Check the radio button “Local” Click the “Add” button

Step 3: Navigate to the “Session” category:

At the “Host Name” box, enter rlogin.ctbto.org For protocol, check the radio button SSH At the “Save Sessions” box, enter “IDC External databases” Click the “Save” button to save the configuration for future sessions



Click the “Open” button to open the connection to the login server

Assess to the External Databases

Remote SQL Access

If you do not have Oracle client software installed on your machine, you can still query the external database tables by logging into the PTS login server. You can also run your scheduled jobs on the login server. Here are steps to gain access to the external databases. Step 1: Establish an SSH session to the PTS login server Please see section 5.2.3 for details. Step 2: Connect to the External Databases Once the SSH session has been established, you can invoke Oracle SQL*Plus on the login server and connect to one of the external databases. Here are the connect strings for the external databases:

EXTODB - connect string for the external operations database EXTADB - connect string for the external archive database

You are given a personal account on each of these databases. The account names are the same as your UNIX login name. Command to invoke SQL*Plus on the login server: % sqlplus /nolog SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jan 13 10:13:39 2003 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL> Command to connect to the external operations database: SQL> connect account_name@EXTODB Command to connect to the external archive database: SQL> connect account_name@EXTADB The initial database password will be provided by the IDC Services. At the first login, you will be prompted to change your database password. Example: SQL> connect account_name@EXTODB Enter password: ERROR: ORA-28001: the password has expired Changing password for account_name New password: Retype new password: Password changed Connected. SQL>



Occasionally, you may want to change your database password. Here is the SQL command to change your database password. SQL> ALTER USER account_name IDENTIFIED BY "new_password" REPLACE "old_password"; Note that the old and new passwords are surrounded by the double quotation marks. Step 3: Query Database Tables Now you can query the database tables using the Structured Query Language (SQL). The IDC Release 3 tables and synonyms can be viewed by using the following queries: SQL> SELECT * FROM r3_tables; SQL> SELECT * FROM r3_synonyms;

Direct SQL Access

Here are steps to connect your applications (e.g. SQL*Plus, Oracle Forms) directly to the external databases: Step1: Configure tnsnames.ora Add the following entries to the tnsnames.ora on your local machine: # IDC External Operations Database EXTODB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 9000)) (ADDRESS = (PROTOCOL = TCP)(HOST = ctbto6.ctbto.org)(PORT = 1521)) ) (CONNECT_DATA = (SID = extodb) ) (SOURCE_ROUTE = YES) ) # IDC External Archive Database EXTADB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 9000)) (ADDRESS = (PROTOCOL = TCP)(HOST = ctbto6.ctbto.org)(PORT = 1521)) ) (CONNECT_DATA = (SID = extadb) ) (SOURCE_ROUTE = YES) ) Step 2: Establish an SSH tunnel that forwards local port 9000 to the PTS login server Please see section 5.2.4 for details. Step3: Make direct SQL connections to the External Databases Once an SSH tunnel to the login server has been established and is kept open, you should be able to connect your application directly to the external and archive databases. All SQL*NET communication from your local machine to the external databases will be going through the established SSH tunnel.

Oracle Database Links

If you are running an Oracle database at your site, you can also link your database to the external databases at the IDC. This type of access is useful for copying tables from the external databases to your local database.



The setup is similar to that for direct SQL access. The only difference is that the Steps 1 and 2 must be done on your database server. Once an SSH tunnel has been established, you can link your local database to the IDC external databases. Example: Create database links from an NDC database to the external databases. SQL> -- Connect to your local database (NDC database) SQL> SQL> CONNECT account_name@LOCAL Enter password: ***** Connected. SQL> SQL> -- Create a database link to your personal account at the EXTODB SQL> SQL> CREATE DATABASE LINK extodb.ctbto.org 2 CONNECT TO account_name 3 IDENTIFIED BY "password" 4 USING 'EXTODB'; Database link created. SQL> SQL> -- Create a database link to your personal account at the EXTADB SQL> SQL> CREATE DATABASE LINK extadb.ctbto.org 2 CONNECT TO account_name 3 IDENTIFIED BY "password" 4 USING 'EXTADB'; Database link created. SQL> SQL> -- Check whether the database links work SQL> SQL> SELECT * FROM global_name@extodb; GLOBAL_NAME ------------------------------------------------------------------- EXTODB.CTBTO.ORG SQL> SQL> SELECT * FROM global_name@extadb; GLOBAL_NAME ------------------------------------------------------------------- EXTADB.CTBTO.ORG SQL> SQL> -- Copy some small tables from CTBTO to your local database SQL> SQL> CREATE TABLE site 2 AS SELECT * FROM idcx.site@extodb; Table created. SQL> SQL> CREATE TABLE chan_groups 2 AS SELECT * FROM idcx.chan_groups@extodb; Table created. If you want to copy a large volume of data, please contact the IDC Services for further assistance.

Database Tables

To view a list of the IDC tables in the external databases make an SQL query as in 5.3.1: SQL> SELECT * FROM r3_tables; SQL> SELECT * FROM r3_synonyms;



The very large archival tables, 31 in total, have been split into two in the EXTADB for efficiency reasons. For example, the most recent entries of the WFDISC table are in the database account IDCX, while the older entries are in the account IDCX_ARCH. On a regular basis, a few times per year, entries older than two months are moved from the tables in IDCX to IDCX_ARCH. The database accounts REB_ARCH, LEB_ARCH, SEGMENT_ARCH, SEL1_ARCH, SEL2_ARCH and SEL3_ARCH have been created in the same way. Note: No tables in EXTODB are split!



Access to the Parameter Files

Background information As requested by the Working Group B, the IDC has made available the configuration tree for the seismic, hydroacoustic and infrasound (SHI) parameters on the login server. A single file containing the entire SHI configuration tree would be very large,, so four files of more manageable sizes are used. As an example, these IDC ‘Parameter Files‘ for the month October 2002 were named EVSC0210.tgz, GA0210.tgz, spec0210.tgz and oth0210.tgz. EVSC0210.tgz contains the event screening parameters. GA0210.tgz contains the Global Association (GA) Parameter Files. spec0210.tgz contains parameters related to the description of the earth, such as travel time curves. oth0210.tgz contains other configuration files such as parameters for all IDC applications. File Name Convention The IDC Parameter Files have the following name convention: <prefix><date>.<format> where <prefix> has one of the following values:

Prefix Remarks EVSC Event Screening Oth Other Configuration Files GA Global Association spec Earth Specifications

<date> is in the form yymm yy stands for the last two digits of the year mm stands for two digits for the month i.e. 0210 stands for year 2002, month October. <format> is tgz that stands for tar format file compressed with gzip utility. A file coming in this format can be easily managed on UNIX or LINUX platforms using a command as follows: gzip –dc <filename> | tar xvf – The command above will uncompress the file on the fly and pass the output to the tar command that will unpack them under the current directory (all directories and files contained in each of the IDC Parameter Files are stored with a relative path) i.e. $ gzip -dc oth0210.tgz|tar xvf – BEWARE THAT THE TOTAL FILE SIZE NEEDED FOR UNCOMPRESSING AND UNTARRING THE FILES IS APPROXIMATELY 2 GIGABYTES (GB). File sizes will vary month to month but 2 GigaBytes of disk space should be enough for the unpacking. We kindly ask you not to unpack these files at the login server site.



File Location The IDC Parameter Files are located on the rlogin.ctbto.org server under the following directory: /home/misc/files/<date> where <date> follows the convention explained above i.e. /home/misc/files/0210 directory contains the IDC Parameter Files delivered on October 2002 as listed below: EVSC0210.tgz GA0210.tgz oth0210.tgz spec0210.tgz File Frequency Update The IDC Parameter Files are updated on the second day of each month. The IDC Parameter Files of the previous month are removed from the rlogin.ctbto.org server a week later after a successful update. Command Examples The IDC Parameter Files can be transferred using the secure copy protocol: On a Windows platform using pscp bundle with PUTTY: pscp <username>@rlogin.ctbto.org:/home/misc/files/0210/ EVSC0210.tgz EVSC0210.tgz the command above will transfer the parameter file EVSC delivered in October 2002 (directory 0210, filename EVSC0210.tgz) to the current directory on the user local machine. On Unix or LINUX platforms using scp bundle with SSH, the same command will look as follows: scp <username>@rlogin.ctbto.org:/home/misc/files/0210/ EVSC0210.tgz EVSC0210.tgz Please note that, in both cases the absolute path of the file location is given and necessary in order to work

properly.

Description of File Contents The files for the month of October 2002 (0210) are described as follows: EVSC0210.tgz contains the event screening parameters and configuration files, including a large bathymetry file used for hydroacoustic event screening. At the IDC, this file represents /cmss/config/earth_specs/EVSC/*. GA0210.tgz contains the Global Association (GA) parameter files and two large grid database files. GA associates the arrivals and forms events through a process of trial locations at pre-computed grid points around the world. At the IDC, this file represents /cmss/config/earth_specs/GA/*.



spec0210.tgz contains parameters related to the description of the earth, such as travel time curves and corrections, hydroacoustic blockage files, magnitude correction files, slowness-azimuth station correction tables, neural net weights for the StaPro module and long-period phase correction files. At the IDC, this file represents /cmss/config/earth_specs/* minus the GA and EVSC directories. oth0210.tgz contains other configuration files (outside of earth_specs). At the IDC, this file represents the /cmss/config/app_config/* tree with parameter files for all IDC applications, the /cmss/config/host_config/* tree with the host configuration files, the /cmss/config/station_specs/* tree with the station specification parameters and the /cmss/config/system_specs/* tree with the high level parameters, the configuration of the database accounts, the X applications resource files, etc. The filenames will change to reflect the year and month as stated above. If you have any questions, please email [email protected] for online support. We welcome any feedback or comments that you might have.