-
Notifications
You must be signed in to change notification settings - Fork 15
Introduction to File Structure
The following is a suggested file structure that will ensure most script contingencies are met throughout the PRH creation process. If you are following this structure, the highest level should be a "CATS" folder. Within this, the important folders are "tag_data" (includes any files that are created through the tag data processing steps), "tag_data_raw" (includes the raw, unprocessed deployment data), "location data" (includes locational metadata such as identifying photos or videos of the deployment procedure), "Calibrations" (includes calibration files for each working tag), and the tag guide ".xls" file (described here).
Within the "tag_data_raw" folder, create a folder for each tagging location (e.g. Alaska, Falklands, Hawaii) and within each location folder, create a folder for each year. So the file path for a raw tag deployment might be: "F:\CATS\tag_data_raw\Alaska\2019\mn190720-55". When a tag deployment comes back from the field, download all of the data (".csv" files, video files, and audio files if present) into a folder titled "raw" within your deployment folder (file path example: "F:\CATS\tag_data_raw\Alaska\2019\mn190720-55\raw"). As you import your data with the "importCATSdata" script, a ".mat" file and two "TDR" (time-depth record) files will be created and and placed just outside of the "raw" folder for that deployment (see figure below).
If you are working with an older version CATS tag that outputs audio data as ".raw" files, you must create a "wavfiles" folder within your raw folder (file path example: "F:\CATS\tag_data_raw\Alaska\2019\mn190720-55\raw\wavfiles") and fill this folder with the outputs from ffmpeg (described here) before running the first cell of the "MainCATSprhTool". The figure below shows an example of the raw data folder with the "wavfiles" folder present and raw downloaded data from the deployment. If you are working with a newer CATS tag that outputs your audio as ".wav" files, you may skip this step entirely.
For your processed data, you will want to create a folder for each deployment within the "tag_data" folder that has the location in the file name, so a potential file path looks like: "F:\CATS\tag_data\mn190720-55 (SE Alaska)". As you work your way through the "MainCATSprhTool", place all created files, including the finished prh file, into this folder (see figure below for an example set of files).