Performance evaluation problem

[zitmen]

What steps will reproduce the problem?
1.I correctly imported the ground truth .csv file and the result .csv file 
2.I run the 'performance evaluation' function
3.I received an out-of-bounds exception

What is the expected output? What do you see instead?
I expected to see a result table.
Index out of bounds exception (see attached Exception.txt)

What version of the product are you using? On what operating system?
ImageJ 1.48v ,thunderSTORM 1.3

Please provide any additional information below.
I'm attaching the cvs file that I would like to compare (ground-truth(LDGroundTruthGain1)
and result(LDfangSoftResults)) and the exception

Original issue reported on code.google.com by anna.archetti on 2014-12-17 15:56:03

---

• Attachment: LDfangSoftResults.csv
• Attachment: LDGroundTruthGain1.csv
• Attachment: Exception.txt

[zitmen]

Hi, thanks for the report. What the error means is that you are missing `frame` column
in `LDfangSoftResults.csv`. Is there a way for you to include it in the file? The evaluation
is done on frame-by-frame basis. At the moment the simulation engine doesn't support
multiple blinking events by a single emitter.

Original issue reported on code.google.com by zitmen on 2014-12-17 17:31:48

• Labels added: Type-Enhancement
• Labels removed: Type-Defect

[zitmen]

Thanks! Now it is clear why the performance evaluation function can not work. Unfortunately
the specific SM software I want to test returns only the molecule-localizations without
a reference regarding the frame of a particular molecule. In this case, to compere
the x-y localizations, I usually sort by the column of the x positions of the results
table (when this is statistically adequate). Will you implement another "frame free"
evaluation function too?

Original issue reported on code.google.com by anna.archetti on 2014-12-18 08:52:58

[zitmen]

Yes, I'm going to add this option.

Original issue reported on code.google.com by zitmen on 2015-01-15 00:56:23

[zitmen]

The new feature was added in revision 2620055e8240. New daily build is now available.

Original issue reported on code.google.com by zitmen on 2015-01-15 13:37:41

[zitmen]

Thanks!!

Original issue reported on code.google.com by anna.archetti on 2015-01-16 12:07:00