Configuration files in /home/adcp/config: (0) crontab.txt: - use EDITOR=/bin/vi and run "crontab -e" to create this entry - The last line is all we add to the crontab entry, the rest is added as a comment by "crontab -e" (1) sensor_cfg.py: - serial logging: (baud rates, ports, messages to be logged) - lists all ADCP instruments as a group - lists all serial inputs (with ADCPS as a subset) (see examples) (2) et_email_body: - part of the body of the email that goes to the ET (3) procsetup_onship.py: - contains info for email, post-processing heading correction, and configuring the 5-minute-vector-plot (see examples) (4) cruise_cfg.m__, cruise_proc.m__, cruise_disp.m__: - templates for matlab processing programs - contain data and web path information, instrument configs - tailored for each cruise by DAS.py, named for cruiseid - ONLY change these files if a configuration changes. The changes to these files will be propagated to all cruises started (with Start Cruise) after the change. (The changes will also propagate if you connect to an old cruise) (see examples) (5) cmdfiles/*.cmd: - command files for running ADCP instruments configuration file: read by --------------------- ------------------------------------------- sensor_cfg.py DAS.py procsetup_onship.py DAS.py, quick_adcp.py, plotting scripts, daily.py et_email_body daily.py *.cmd DAS.py cruise_cfg.m__ DAS.py (creates specific version for cruise) cruise_proc.m__ DAS.py cruise_disp.m__ DAS.py Specific version of processing configuration files, eg. for cruiseid "CRUISE" configuration file: read by --------------------- ------------------------------------------- CRUISE_cfg.m quick_adcp.py, plotting scripts CRUISE_proc.m DAS.py, quick_adcp.py, plotting scripts CRUISE_disp.m quick_adcp.py, plotting scripts