Shore Side Data System (600031 and 900823) : M0 Text File Generation Scripts This page last changed on May 30, 2008 by mccann. M0 Text File Generation Scripts - Documentation Created by Seth Bushinsky - May 30, 2008 Purpose: These programs produce text files from available M0 data. Two types of text files are produced: one set of files for each M0 deployment which consists of one text file per instrument and two text files (one for surface data, one for profile data) that include selected data for all M0 deployments that can be read into Loboviz (http://www.mbari.org/lobo/loboviz.htm) All files can be read using ODV or any text reader. Deployment Instrument Files: Location: \\Tornado\ssdsdata\deployments\m0\ [YYYYMM] \ascii_output Example (\\Tornado\ssdsdata\\deployments\m0\200706\ascii_output) Files created by 'nc_loaddap_text.m' called with the appropriate deployment date by a crontab script on Elvis (see table at the end of this document). For mooring turnaround, go to new deployment folder (\\Tornado\ssdsdata\deployments\m0\ [YYYYMM] ) and create sub-directory titled "ascii_output". Then change deployment call in crontab script - "cron_m0_txt_process". This should find all '.nc' files being created by ssds and make text files from these. Loboviz Text Files: This program produces two text files: M0PROF.txt and M0SURF.txt (along with M0PROF.cfg and M0SURF.cfg). Once a day, these files are copied by Loboviz and ingested so that the data can be plotted online. File location: \\Tornado\ssdsdata\deployments\m0\ascii_all_dep. Generated by "nc_loaddap_odv_surf.m" and "nc_loaddap_odv_prof.m". These files read in the netcdf files generated by ssds, as well as nitrate data from \\Tornado\ssdsdata\isuscimt\data\M0.txt . The netcdf file names are hard-coded into the processing. This script is run once a day. It deletes the last 3 hours of data in the file (which are usually NaN's) and appends new data to the end of the files. It also generates the '.cfg' files that contain the number of lines of data in each file. For mooring turnaround, open both"nc_loaddap_odv_surf.m" and "nc_loaddap_odv_prof.m", go down to where the long list of netcdf files is under the heading "%% Load Variables" and add the new deployments' netcdf files to the list. *If there is a change to the mooring data or some other error, keep in mind that because these files are appended instead of re-written, the mistake will stay in the text files. If this happens, simply delete the files and new ones will be created. However, when this happens, open the text files the next day and look in the header for weird characters that sometimes get added next to the "micro" or "degree" symbols. These can trip up Loboviz and prevent data ingestion. | *Program | Machine | Crontab Script | Scripts called (next table has script location) | '.m' file location |
Text file generation | Elvis (user: ssdsadmin, pw: water4u) | /bin/sh /ssdsdata/deployments/m0/ascii_all_dep/cron/cron_m0_txt_process | nc_loaddap_text.m | \\Tornado\ssdsdata\deployments\m0\ascii_all_dep\mfiles
Loboviz file generation | Elvis | /bin/sh /ssdsdata/deployments/m0/ascii_all_dep/cron/cron_m0_loboviz | nc_loaddap_odv_surf.m, nc_loaddap_odv_prof.m | \\Tornado\ssdsdata\deployments\m0\ascii_all_dep\mfiles |

Document generated by Confluence on Feb 04, 2026 08:56