saveSeismogramToFile
As of sod-2.2 this processor is deprecated. Unless you specifically want DSML files, use sacWriter or mseedWriter instead. When sod-2.3 is released, this processor will no longer be allowed. The seismograms are written to data files in the given directory. Also writes out a dsml file for use in GEE and other fissures tools that support datasets. If fileType isn't set, seismograms will be saved as mseed. Always returns true unless there is an error.
Example
<saveSeismogramToFile> <fileType>sac</fileType> <dataDirectory>POND_II</dataDirectory> <eventDirLabel>Event_$event.getTime('yyyy_DDD_HH_mm_ss')</eventDirLabel> </saveSeismogramToFile>
This consists of
Places this can be found
In seismogramProcess there is a choice between all of the following
- printlineSeismogramProcess
- sacWriter
- mseedWriter
- recordSectionDisplayGenerator
- responseGain
- phaseCut
- merge
- rMean
- rTrend
- taper
- externalWaveformProcess
- localSeismogramTemplateGenerator
- filter
- forkProcess
- alwaysSuccess
- phaseSignalToNoise
- seismogramImageProcess
- legacyExecute
- seismogramAND
- seismogramOR
- seismogramNOT
- someDataCoverage
- noDataGaps
- fullDataCoverage
- integrate
- differentiate
- embeddedEventChannelProcessor
- transferResponse
- collapseOverlaps
- div
- mul
- invertFlippedChannels
- saveSeismogramToFile
- seismogramSampling
- decimate
- compressionType
- SNEPProblem