saveSeismogramToFile
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. 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
<fileType> optional
</fileType>
<prefix>Any text</prefix> optional
<dataDirectory>Any text</dataDirectory> optional
<eventDirLabel>Any text</eventDirLabel> optional
<id>Any text</id> optional
<preserveRequest/> optional
<storeSeismogramsInDB/> optional
<sacHeader> optional
<prefix>Any text</prefix> optional
<dataDirectory>Any text</dataDirectory> optional
<eventDirLabel>Any text</eventDirLabel> optional
<id>Any text</id> optional
<preserveRequest/> optional
<storeSeismogramsInDB/> optional
<sacHeader> optional
<phaseTime> Any number of times
</phaseTime>
</sacHeader>Places this can be found
In seismogramProcess there is a choice between all of the following
- printlineSeismogramProcess
- saveSeismogramToFile
- recordSectionDisplayGenerator
- responseGain
- phaseCut
- rMean
- rTrend
- taper
- externalWaveformProcess
- localSeismogramTemplateGenerator
- filter
- forkProcess
- alwaysSuccess
- phaseSignalToNoise
- seismogramImageProcess
- legacyExecute
- seismogramAND
- seismogramOR
- seismogramNOT
- someDataCoverage
- noDataGaps
- fullDataCoverage
- integrate
- embeddedEventChannelProcessor
- transferResponse