### printlineSeismogramProcess

This simply prints a line to standard out or a file for each seismogram to be processed. It can be used as a simple status monitor. Both filename and template are Velocity templates. They contain a list of seismogram named seismograms containing all the retrieved seismograms, a list of request named originalRequests that are the requests generated by your request generator, another list of request named availableRequests that are the requests the server said were available for retrieval, site, station, net and event variables. If no template element is given, it defaults to "Got $seismograms.size() seismograms for $channel.codes for eq on $event.time". If no filename is given, the output goes to standard out.

### Example

    <printlineSeismogramProcess/>

### This consists of

<printlineSeismogramProcess>

interleave
<template>Any Text</template> optional
<filename>Any Text</filename> optional
</printlineSeismogramProcess>

### 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