burst with one line give an error in the analysis (object 'new_x' not found)

[Grace-Houser]

When analyzing a group of files, occasionally I get an error message that reads "object 'new_x' not found ". If I delete that file causing the error, from the list, then I can proceed with the analysis. However, I do not understand how these "problem files" are different than the others generated in the Buridan Tracker. Could there be a reason behind this or something to check when I receive this error message?

Thank You!!!!

[jcolomb]

thanks for opening an issue!
I haven't used CETRAN for quite a long time, but I remember that sometimes the last line of a file is corrupted with only time and not the position, deleting the last line does the trick.

(new_x values are created when deleting small movements, I think...)

[Grace-Houser]

Thank you for your quick reply!
I took a look at the last line in the file, and nothing was missing (position, time, frame etc.). However, I deleted the last line, just to be sure, and I am unfortunately still getting the same error message:
loading fly CS_M181211_CS_M_02.dat
Warning: Error in : object 'new_x' not found

[Grace-Houser]

I seemed to have solved the issue, taking into consideration what you told me: that the last line of the file may be corrupted. It actually seemed to be the first line of the file which was corrupted, nothing was missing, but it seems that if the first burst is 0 and the rest of the bursts are another number (such as 1), then I get the error message. When I delete the first row, it resolves the problem, some how.
Example Below:
frame time x y burst
2229968 10175 310 23 0
2230969 10736 232 432 1
2230970 10767 233 434 1
2230971 10800 236 435 1
2230972 10831 240 436 1
2230973 10880 243 436 1
2230974 10911 247 436 1

[jcolomb]

ok. I remember now, if there is a burst with only one data (line) then the error occur, it can be the last, the first, or even in the middle (very rare).

Someone should write a small extension to the script to deal with this problem.