A definitive collection of calibration and ingestion parameter data for all platforms.
The repository is organized by platform. Each platform directory contains two types of data files.
- Calibration sheets in Excel format.
- Ingestion parameter sheets in CSV format.
Filenames adhere to the following conventions:
- Calibration sheets are named
PLATFORMis the platform name (e.g.
XXXXXis the five digit deployment number (e.g.
- Ingestion parameter sheets are named
PLATFORMis the platform name.
Sis the source of data (e.g.
XXXXXis the five-digit deployment number (e.g.
A Platform Parameters Checklist Excel spreadsheet is also included in the repository to help keep track of the sheets that are available and the sheets that still need to be created.
Ingestion Parameter Sheets (CSV Files)
The ingestion parameter sheets require 4 columns of data:
||The name of the ingestion queue that the EDEX application will pull the files from.|
||A filename mask that points to the files to be ingested. Can include UNIX style wildcards (*, ?).|
||The reference designator associated with the files to be ingested.|
||An indication of whether the data is telemetered or recovered.|
Lines can be commented out in the CSV file by placing a pound sign # at the beginning of the line, or at the beginning
of any cell in the line. It's recommended to place the pound sign # in the
uframe_route column. When a line in the
CSV file is commented out, the ingestion script will ignore that line completely.
Extra columns, such as "notes" or "status," can be included in the CSV files. The ingestion script will ignore these columns completely. Feel free to annotate CSV files with extra columns of data as necessary, but entries in the "status" column should use a standard set of codes, using the definitions below:
||Instrument was not integrated onto the platform for this deployment.|
||Data are not available for a known reason (e.g. instrument failed, files were corrupted, instrument was lost).|
||No data in raw data archive, although the instrument was deployed and operational.|
||Data are scheduled for upload to the raw data archive.|
||Data are on the raw data archive but not yet able to be ingested (e.g. parser needs to be developed or modified).|
||Data are on the raw data archive and ready for ingestion.|
Ingest all files described in one or more ingestion csv files.
This allows a simple way to ingest a large amount of uncabled data by simply providing the list of ingestion CSV files.
For example, to ingest all the uncabled data from the CE02SHSP mooring:
ingest_file.py to process each file glob as defined in the ingestion csv file.
Ingest a set of files for a given reference designator.
This tool is designed to test ingestion for a particular uncabled instrument stream. It can also be used to patch ingestion on production, however Large or continual ingestion should be managed by the ingestion tool currently under design by Mark Steiner.
./ingest_file.py Ingest.flort-dj-cspp_recovered CE02SHSP-SP002-07-FLORTJ000 telemetered 2 /omc_data/whoi/OMC/CE02SHSP/R00002/extract/*TRIP.txt
Ingest set of cabled files that have been missed during a previous ingestions. It will scrape all missing dates and then it will perform the playback command.
written by Phil Tran
python ingest_missing.py qpid://guest/guest@uframe-test?queue=Ingest.instrument_events qpid://guest/guest@uframe-test?queue=Ingest.instrument_particles uframe-test
Find files associated with the specified cabled reference designator.
written by Phil Tran
-l option will provide the list of files associated with
the provided reference designator.
python find_raw_cabled_files.py CE04OSPS-SF01B-4B-VELPTD106
python find_raw_cabled_files.py -l CE04OSPS-SF01B-4B-VELPTD106
The file ingest queue can be monitored using the
qpid_stat.py utility in the ooi-tools repository: