.. _intro_proc_sh_gamit:

:program:`sh_gamit`
===================

Once you have edited appropriately the template files, you can start the processing from within the experiment directory by giving :program:`sh_gamit` simply the 4-character code for the project or subnet (termed "experiment") and a range of days to process:

.. code-block:: console

   $ sh_gamit -expt emed -d 2018 034 035 036 >& sh_gamit.log

The :program:`sh_gamit` command is executed at the project-directory level.
The time span can also be specified using :option:`-s {<start_day>} {<stop_day>}` to indicate a range of consecutive days, or :option:`-r {<days>}` to indicate that you want to process a single day :option:`{<days>}` before the current date.
If you plan to process data from more than GPS, use :option:`-gnss {<sys>}`, where sys is G for GPS, R for Glonass, C for Beidou, E for Galileo, and I for IRNSS.
You may also override some of the parameters specified in :file:`process.defaults`, e.g.:

:option:`-orbit {<type>}`
   Type of orbit (e.g. igsf igsr igsu codm gfzm siof; see :program:`sh_get_orbits`; default igsf)
:option:`-eops {<name>}`
   EOP series to be used (usno [default], usnd)
:option:`-sessinfo`
   Sampling interval, #epochs, start time (HH MM) (e.g. 30 2880 0 0 )
:option:`-copt`
   List of files to compress in the day directory (default x, k, autcln.out, d)
:option:`-dopt`
   List of files to delete from the day directory (default C-files only)
:option:`-pres ELEV`
   Plot phase vs elevation and as skyplots (default no)
:option:`-nopngs`
   Do not create PNG files of sky plots (default is to create from PostScript)
:option:`-yrext`
   Add year prefix to names of day directories
:option:`-netext {<char>}`
   Add suffix (character) to names of day directories
:option:`-noftp`
   Don’t try to ftp any data from outside your system (default is to ftp)

Most of the time the parameters may be omitted in favor of the values you have specified in :file:`process.defaults` for the whole experiment.
The overrides are useful, however, if you wish to test the effect of processing a day with a different orbit, EOP table, or session length, or for different GNSS, in which case you can create a second directory for the same day by appending a character to its name (e.g., :option:`-netext t` to create :file:`034t/`).
When :option:`-gnss` is specified, the day directories will automatically be named with the GNSS code as the extent (e.g. :file:`034E/` for Galileo).
Finally, you may launch sh_gamit from anywhere on the system by specifying the full path name of the processing directory with :option:`-dir {<path>}`.
When the script runs, it will write to the screen a record of each step, which you may choose to redirect to a file (e.g., :console:`>& sh_gamit.log`).
Examining the screen log together with the comments and source code in :file:`~/gg/com/sh_gamit` and the :file:`GAMIT.fatal` file, will allow you to identify the point and reason for failure should that occur.
When processing of each day is completed, :program:`sh_gamit` will send a mail message to you (:content:`mailto` in :file:`process.defaults`) giving the number of stations used, the rms of the one-way phase residuals for the two best and two worst stations from the :program:`autcln` postfit summary file, the nrms values from the Q-file, the number of ambiguities resolved, and a list of any large adjustments to station coordinates.
These statistics will let you know whether you need to examine the GAMIT output further for possible reprocessing.