Adding a Telonics Parameter File (TPF) may require reprocessing some collar files

[regan-sarwas]

Current Behavior:
If a collar, with existing parameters without an end date (typical) is redeployed with new parameters, but the new parameters are not added to the database, the database will process the collar file with the older TPF file. This may produce an incorrect CSV file with no locations (and no errors!). For example BBorg's collar 694025 deployed on 2020-11-13 produced on locations until the correct TPF file was loaded 2020-11-24. (the incorrect CSV files were manually deleted and files reprocessed).

Preferred Behavior:
When a new TPF file is loaded, find all collar files that 1) have derived CSV files and 2) would have been processed with the new TPF file had it existed when the file was processed. Then delete all the derived CSV files for those collar files. The files will automatically be reprocessed on the next run of the 'ArgosProcessor.exe'

[regan-sarwas]

In the meantime here is a workaround:
In the animal movements application 1) upload the new TPF file and assign it to the collar. 2) go to the collar details dialog (double click the collar in the PI's list). On the files tab, sort the files with newest on top. Record the fileid of the files that were incorrectly processed. In SSMS or Data Studio, execute the following queries:

-- Check the list of files
-- replace xxx, yyy, zzz with the fileids from the previous step
select * from collarfiles where fileid in (xxx, yyy, zzz) and Format = 'C' and ParentFileID is not null

-- delete the 'broken' files
-- replace xxx, yyy, zzz with the fileids from the previous step
delete from collarfiles where fileid in (xxx, yyy, zzz) and Format = 'C' and ParentFileID is not null

Within 10 minutes the file will be regenerated.

If you do not feel comfortable with the SQL queries, then you can look for and delete the files by name in the files list on the PI dialog.