Project goal of vue-to-cftc

This repository enables the field biologist maintaining a CFTC core array receiver to submit data in a format acceptable to our database.
This is achieved by providing the scientist with a series of useful, small programs, a corresponding Microsoft Access Database and instruction for use.

System requirements

Windows PC
VEMCO VUE
Perl or R
Microsoft Access (or potentially LibreOffice Base, but I have not recently tested LO Base)

Please read the ImportToAccess.txt file for more details

File requirements

Acoustic telemetry __VRL__ (or __.000__) files.
Corresponding deployments entries in a __CSV__ or __XLS__/__XLSX__.
The __.bat__ and __.pl__ scripts from this lovely online repository that you are currently viewing. You can obtain these compressed in __.zip__ format by [clicking here![Download Icon](/octicons/gif/cloud-download.gif)](../../archive/master.zip).

Basic workflow

This documentation assumes that you've already used VEMCO's VUE to download your data from a receiver.

Create a vdb with time drift-corrected data. You may use the included AutoHotkey (ahk) script to use a larger window within VUE if you have multiple receivers to import at once.
Optional: You may choose to delete tester or beacon tags so only data on fish tags are included.
Export all (remaining) detections in .csv format.
Convert csv files using .bat and perl (pl)script files into CFTC format (PST time).
Import detections into MS Access.
Import or manually enter deployment records into Access.
Check for orphaned detections (detections outside the given deployment windows) using provided Visual Basic for Applications (VBA) macros.
E-mail us the resulting MS Access .mdb file.

Basic script file usage instructions

In windows drag desired .csv files generated by VUE output on top of one of the three vue-to-cftc.bats.

vue-to-cftc-plusMS.bat - will include milliseconds in output for all detections, including those with no specified milliseconds value (0ms).
vue-to-cftc-noMS.bat - will never include milliseconds, even if present in VUE output. This version is the most compatible with earlier versions of Microsoft Access.
vue-to-cftc.bat - will include milliseconds on entries that have milliseconds available from the VUE export. On entries without specified milliseconds (or with exactly 0ms) the output will not include milliseconds. This version is untested with regard to Microsoft Access, but should be roughly as compatible as the plusMS version.

Again, please read the ImportToAccess.txt file for more details.

Bug reports

Please first check if your bug has already been reported here.
Then either create an "issue" here Bug Icon or simply e-mail me.

If you have any technical problems with Git or GitHub, rather than this project specifically, ask GitHub Support directly.

Make modifications to my source

On Github
1. Make modifications by creating your own GitHub account and then "forking" this project by clicking that funky looking icon over there or maybe up there.
2. You can let me know about updates and fixes you've created by doing what GitHub calls a pull request.
3. You can check if anyone has requested to update your fork with THEIR modifications here.
4. For your fork of the project, you can just edit the link that says "send me the modifications via e-mail" with <your@address.com>, remembering to include the less than (<) and greater than (>) symbols around your actual address.
5. Remember if you fork this project, you'll have to go to your settings dialogue and enable issue tracking by checking the box:white_small_square: next to "Issues" under "Features".
Offline/via e-mail
1. You can choose to "go old school" and Download
2. Modify and then
3. Send me the modifications via e-mail, which you can do by telling me your e-mail address. The GitHub system will send me an e-mail, then I'll reply to the address you provide, so you'll know where to send the files.