### seismogramOR

The output is the logical OR of the outputs of all included seismogram processors. This means that it will evaluate to true as long as one of the included seismogram processors evaluate to true. The processors after the first true outputted are not evaluated. The result of each processor in the OR is passed to the next processor in the OR, and the result of the last evaluated processor in the OR is passed to the next processor outside of the OR. To isolate the processing inside the OR, wrap it inside of a forkProcess.

### Example

    <seismogramOR>
        <noDataGaps />
        <someDataCoverage />
    </seismogramOR>

### This consists of

<seismogramOR>

seismogramPlus At least once choice
availableDataPlus
seismogramProcess
</seismogramOR>

### Places this can be found

In seismogramProcess there is a choice between all of the following

- printlineSeismogramProcess
- sacWriter
- mseedWriter
- asciiWriter
- wavWriter
- recordSectionDisplayGenerator
- responseGain
- phaseCut
- requestCut
- merge
- gapFill
- rMean
- rTrend
- taper
- externalWaveformProcess
- seismogramScript
- localSeismogramTemplateGenerator
- filter
- rms
- oregonDSPFilter
- forkProcess
- alwaysSuccess
- phaseSignalToNoise
- compoundPhaseSignalToNoise
- seismogramImageProcess
- legacyExecute
- seismogramAND
- seismogramOR
- seismogramNOT
- someDataCoverage
- noDataGaps
- fullDataCoverage
- integrate
- differentiate
- transferResponse
- collapseOverlaps
- div
- mul
- invertFlippedChannels
- seismogramSampling
- decimate
- stddev
- rms
- mean
- minMax
- compressionType
- availableDataPlus