Closed ghost closed 8 years ago
I've investigated this issue to find a workaround since this a blocker for us. I think I have found the cause for the crash. The crash only seems to happen when, in the actual result, is two result points from the same time, e.g. there was an event at that time point. Additionally one of the points must be within the bound and the other isn't, i.e. the line segment startes within the bound and ends outside.
The following illustrates the problem: actual.csv:
time;a 0;0 1;2 1;1 2;2
expected.csv
time;a 0;0 1;1 2;2
Command:
Compare.exe -o -m csvFileCompare -r . -t 0.001 --inline actual.csv expected.csv
The workaround that I've found is to add a small epsilon to the second point so that the points aren't located on exactly the same time point. E.g.:
time;a 0;0 1;2 1.00000000001;1 2;2
Still, this is a workaround and should really addressed and fixed in CSV-Compare
We're getting "Exception during run: Index was outside the bounds of the array." Command used is:
And the files can be found here
Exact error message is:
The two warnings are rather strange, the two result files has different resolution during different time (due to events). It would also be rather interesting to know why "a" is invalid...
Version of CSV Compare: