TGrabs seems to work fine for me, judging by the red boxes constantly drawn around the ants in the video (see screenshot below). However, the .csv TRex is exporting always lack a portion of the detected blobs. I have tried finding the optimal parameter set through a systematic testing pipeline, but ended up realizing that some parameter sets 'lose' detections in some tracks/parts of the video and other sets lose detections in other parts (see plots below). I cannot identify any clear patterns of which parameters lead to which accuracy.
Is there a way of exporting all the detection stored in the .pv file to .csv, without caring about identity? This would give me a ground truth and basis for testing other algorithms.
I would greatly appreciate any help you could provide!
![tGrabSnap](https://user-images.githubusercontent.com/38962260/118370211-92887580-b55b-11eb-9e8a-9ecf63544001.png)
Snapshot of TGrabs
![paramsTracksLum](https://user-images.githubusercontent.com/38962260/118370771-1ba0ac00-b55e-11eb-88bd-92e37acf5f94.png)
Plots of some of the best performing parameter sets. GrThr: threshold
, match: matching_probability_threshold
, reass: track_max_reassign_time
, split: blob_split_global_shrink_limit
& blob_split_max_shrink
, lumin: correct_luminance true
Other TGrabs parameters;
approximate_length_minutes = 28 averaging_method = max average_samples = 10 image_invert = true threshold = 78 blob_size_range = [0.0001,0.002] reset_average = false framerate = 25
Other TRex parameters:
auto_minmax_size = true auto_number_individuals = true calculate_posture = false output_min_frames = 4 track_include = [[[3840,14],[2920,18],[2920,2160],[3840,2160]],[[2920,38],[2300,50],[2300,2160],[2920,2160]],[[2300,50],[1850,52],[1850,2160],[2300,2160]],[[1850,58],[1210,68],[1210,2160],[1850,2160]],[[1210,42],[950,62],[718,2160],[1210,2160]],[[950,86],[124,94],[160,2160],[1390,2160]]] track_max_speed = 45 track_speed_decay = 0.7