ViPRE-PE UnknownDistanceException

[Douglas]

Hi,

I hope that you can help me out with a problem. I'm investigating
ViPRE-PE on Windows XP 5.1.

When I run the command

> java -jar viper-pe.jar -epf object-Person.epf -g test-truth.xml -r test-candidate.xml -o output.txt

[I borrowed the configuration and xml files from a previous post.
Thank you Michael]

I get this in responce I get:

****** NOTE: All output directed to: output.txt ******
04:30:08 Parsing Target Config information.
04:30:08 Parsing Candidate Config information.
04:30:08 Parsing Evaluation Parameter information.
viper.comparison.distances.UnknownDistanceException: Attribute type
not found: http://lamp.cfar.umd.edu/viperdata#bbox
at viper.comparison.distances.Distances.getDistanceFunctor
(Unknown Source)
at viper.comparison.distances.AttrMeasure.<init>(Unknown
Source)
at viper.comparison.TrackingEvaluation$TrackingMeasure.<init>
(Unknown Source)
at viper.comparison.TrackingEvaluation.helpParseAttribMap
(Unknown Source)
at viper.comparison.TrackingEvaluation.parseEvaluation(Unknown
Source)
at viper.comparison.EvaluationParameters.parse(Unknown Source)
at viper.comparison.ViperPE.run(Unknown Source)
at viper.comparison.ViperPE.main(Unknown Source)

Don't know what to do next so hope you can help.

Kind regards,

Douglas

[David Mihalcik]

Hmm... There seems to be a bug in OBJECT-style evaluation. Try
removing the OBJECT_EVALUATION section of the epf file, which seems to
have suffered from some bit rot.

[David Mihalcik]

Added a bug here:

http://github.com/dmihalcik/viper-toolkit/issues#issue/3

On Sep 7, 11:46 am, Douglas <dug.armad...@googlemail.com> wrote:

[Douglas]

Dear David,

Thank you for your quick response. Unfortunately, your suggestion has
not worked, however, using this as inspiration, I deleted the
TRACKING_EVALUATION and it now runs. Thank you.

The TRACKING_EVALUATION section I deleted was:

#BEGIN_TRACKING_EVALUATION

OBJECT Person [dice 1]
*Location : dice matchedpixels arearecall missedpixels falsepixels
fragmentation arearecall areaprecision [dice .5] [maxdev -]


#END_TRACKING_EVALUATION

Does anyone know what is wrong with this?

Kind regards,

Douglas

[David Mihalcik]

I put a modified version of viper that should fix this issue, and a
couple of others, here:

http://github.com/dmihalcik/viper-toolkit/downloads