- Source codes and Linux executables for Populate_RdSEED & SimpleResp can respectively be found in: https://ncedc.org/ftp/outgoing/stephane/metadata/IR/Populate_RdSEED/ https://ncedc.org/ftp/outgoing/stephane/metadata/IR/SimpleResp/ - Syntax: % ./Populate_RdSEED -h Populate_RdSEED version 4.2 -- Populates instrument response from a rdseed output file (rdseed -s). Populate_RdSEED [-h] [-v] [-p] where: -h Help - prints syntax message. -v Verbose mode. -p Population mode. Environment variable DB_CONNECT --> Overwrites default database connection string. % ./SimpleResp -h SimpleResp version 2.0 -- Generates Simplified Response From IR Schema. SimpleResp [-h] [[[-v] [-p]] | [-t]] [] where: -h Help - prints syntax message. -v Debugging Mode. -p Population Mode (Replace simple_response table contents). -t Outputs contents of simple_response table to file. Environment variable DB_CONNECT --> Overwrites default database connection string. - For both applications, you can specify the database credentials via an environment variable DB_CONNECT="user/password@dbname" - Ideally, you want to have a dataless SEED volume containing the whole historic information about the stations that you are interested in. For example if you have a dataless SEED volume with all the US stations: 1.- Run 'rdseed -s -f US.dataless > US.rdseed' [Creates rdseed output file] 2.- set env var 'DB_CONNECT' 3.- Run 'Populate_RdSEED -v -p US.rdseed' [Deletes IR rows for all US stations specified in rdseed file & import IR information from rdseed file] 4.- Run 'SimpleResp -v -p output US' [Deletes SimpleResp rows for all US stations and recompute simplified response parameters for all US stations based on IR information] Note that if you do not specify the network code (US) in SimpleResp, it will recompute the simple response information for all networks and stations (based on the Channel_Data table). But if you know that you have just updated instrument responses for the US network, you don't want to have SimpleResp regenerate those parameters for all networks, just the US one. - Populate_RdSEED makes use of the Oracle sequences defined in the IR schema: dcseq, abbseq, dmseq, forseq, poseq, pzseq, uniseq, comseq, forseq. If you have been populating the different IR tables and did not use those sequences to generate the primary keys, you will run into conflicts. One workaround is for you to find out the maximum values for each of those primary keys and recreate the sequences with the maximum value as the start. Here are the sequences and their corresponding fields in the database: abbseq --> D_Abbreviation.id comseq --> D_Comment.id dmseq --> DM.key forseq --> D_Format.id poseq --> PN.key pzseq --> PZ.key uniseq --> D_Unit.id dcseq --> DC_Data.key