NCSS Wiki

When adding a station with a new network code, there are all the usual issues for adding a station. And there are several more things required to handle the new network code.

• Add a new partition to the Waveform database table.

• Add new directories to the SAM-FS (currently on strike) to contain waveforms for this network.

• The network needs to be added to an existing waveform archiver or a new waveform archiver needs to be set up. Be sure to name the configuration file appropriately, including the network code in the name.

• Consider adding to adhoc and station list scripts on rodgers. See the section on CISN Ad Hoc List in the ShakeMap page. Ideally each network code should be included in only one of the CISN partial ad hoc lists produced by Caltech, CGS and Berkeley. But this may not always be possible.

• Consider adding the network to the amp export system on the post-processing systems, Doing so will allow amps collected on the RT systems to be exported to other CISN partners. This is in ncpp/ampexc/export/conf/export.props on ucbpp and mnlodb1.

• Consider adding the network to the db2nsmp_xml configuration on RT systems. This will allow waveforms being processed by the RT systems to have their ground motion amps contribute to the Global ShakeMap system. Be sure to ask the network operator if they are willing to have their data used in this way.

• Consider adding the network to the amp import system. If the waveforms are NOT being processed by the RT system, then adding them to the amp import system may be appropriate.

• If the amps from the new network are being imported (previous paragraph), consider adding to the GMP to XML converter. Doing so will make these amps available to the Global ShakeMap system. Look in ncpp/ampexc/exportXML/conf/gmp2xml.conf on the post-processing systems ucbpp and mnlodb1.