Seismic software, format conversions

        Command line for help text  Man-page?

• mseed to sac    mseed2sac -h             YES
  
• mseed to ascii   mseed2ascii -h           YES
  
• sac to ascii     sac, help ...
  
• gcf to sac      gcf2sac
  
• gcf to ascii     gcf2asc
  
• ascii to ts
• Further processing: gcf to ts for acceleration and SG-like signal: Scripts  gcf2ts + make-zacc-likeg
  

ASCII to tslist's BIN ts

tslist can read SAC- and GCF-ASCII,
    tslist [<file>|-] -A'>SAC]' -gopt ...
    tslist [<file>|-] -A'>GCF]' -gopt ...
The formats are widely different! See tslist and readfuf

MSEED to SAC or ASCII

MSEED files can straddle a whole day. In order to extract a certain time range,
    mseed2sac -l <select-file> ...
Example from the man-page:
       #net sta  loc  chan  qual  start             end
       IU   ANMO *    BH?
       II   *    *    *     Q
       IU   COLA 00   LH[ENZ] R
       IU   COLA 00   LHZ   *     2008,100,10,00,00 2008,100,10,30,00
Date format:                                              YYYY,DOY,HH,MM,SS

Thus, use of scripts our-mseed2[asc|sac] might ease extraction in order to avoid dimension limitations in tslist.
But what do the columns designate, net? sta? SG OSO?  SG SG? OSO SG?

our-mseed2sac runs mseed2sac without selection and moves the resulting SAC-file into the source's directory.
our-sac2asc [-d <duration>] <sac-bin-file> [<begin> [end]] can be used to extract time slices which
can be picked up by tslist.x ... -A'>SAC'

GCF to SAC or ASCII

The problem is that the utilities cannot read nor write from/to disk /data, only from/to /home. It can read via a symlink to a  /data  directory but not write. Therefore, scripts has been coded up: our-gcf2asc our-gcf2sac and gcf2pipe. All document themselves when switch -h is specified.
Example:

gcf2pipe 3u93z2/20220501_1000z.gcf | tslist.x - -AGCF -g'()' -k0 -I -o tsfiles/gcf_z_220501-10:00-10ms.ts