There are some difficulties in the code, and in your file, and also in how you call the code.
First, your call: you have
[time,vapPen,tan2,JB,maxV] = aviVSD('C:\Users\User\Documents\MATLAB\Final Images\test\test.cine',2:10,[0 0],[0 2500],[0.45 0.55],[3 0 0 0 0 500 0 0 0 0.101 0 2 80 1 1 -1 1 2.58309])
The third parameter, which you have as [0 0], needs to be the x and y coordinates of the muzzle origin. The values must be positive integers.
Secondly, the last parameter, which you provided as a numeric vector, needs to be a cell array instead. Use {} instead of [] . Yes, this does disagree with the examples, and No, there does not appear to be any good reason for it, but it is less work to call it with {} than to fix up the code to use () indexing instead of {} indexing.
Thirdly: your test file does not contain any timestamp information in it.
Fourthly: while reading the file, the code properly tests to see whether timestamp information is present, but when it is not present then it fails to assign anything to the TimeStamps variable and then later it crashes when it tries to use the variable. This happens both in readcin and in readcin90 . Both routines need to be slightly repaired for that case.
Fifthly: the aviVSD code assumes that time information is available. Perhaps readcin and readcin90 should be made responsible for figuring out appropriate information for all of the fields in this case, but it was easier to change aviVSD to guess at times. In this case, I decided that frame #1 should correspond to time 0 and that the frames should be considered to be 1/FrameRate seconds apart.
Sixthly: there is a routine in aviVSD dealing with muzzle spray that uses the x and y origin information (that you supplied as 0). It tries to detect something in the image, but in your image it does not find it. It notices that it is not present and scribbles some small data into the image so the algorithm will have something to work with, but when it does so it confuses x and y and it subtracts 1 from the origin coordinates when it should not. The line needed to be changed.
Seventhly: after all of the above fixes, you are going to get a bunch of warnings
Warning: Polynomial is badly conditioned. Add points with distinct X values, reduce the degree of the polynomial, or try centering and scaling as
described in HELP POLYFIT.
It appears those could be triggered by having provided nozzle origin coordinates that are not where the nozzle actually is, leading the code to be unable to detect the center of mass properly. I did not make any changes having to do with this, as it looks to be a matter of you needing to provide better coordinates.
I have attached the repaired files.
