Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
problems about viper-pe point distance
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
avastreg  
View profile  
 More options Feb 29 2008, 7:13 am
From: avastreg <isac.new...@gmail.com>
Date: Fri, 29 Feb 2008 04:13:19 -0800 (PST)
Local: Fri, Feb 29 2008 7:13 am
Subject: problems about viper-pe point distance
Hi, i'm new with ViPER-PE and i'm working on it for my graduating
thesis. That's a very good work, but i've got some problems on point
type evaluation.

I get a NullPointerException at
viper.descriptors.attributes.Attribute_point
$EuclideanDistance.helpGetDistance(Unknown Source)
at viper.comparison.distances.Distances.. etc
and then the exception chain until to main.

Here there are my test file:

target GT:

            <object framespan="77:94" id="0" name="Person">
                <attribute name="PositionBar">
                    <data:point framespan="77:77" x="14" y="180"/>
                    <data:point framespan="78:78" x="17" y="187"/>
                    <data:point framespan="79:79" x="18" y="182"/>
                </attribute>
            </object>

candidate:

            <object framespan="77:94" id="0" name="Person">
                <attribute name="PositionBar">
                    <data:point framespan="77:77" x="12" y="176"/>
                    <data:point framespan="78:78" x="17" y="187"/>
                    <data:point framespan="79:79" x="23" y="188"/>
                </attribute>
            </object>

my epf file:

#BEGIN_OBJECT_EVALUATION
OBJECT Person [- -]
   PositionBar : [- 0.1]
#END_OBJECT_EVALUATION

//#BEGIN_FRAMEWISE_EVALUATION
 OBJECT Person
     PositionBar : euclidean
//#END_FRAMEWISE_EVALUATION

i've tried the object evaluation only and i get the NullPointer.

If needed i'll post my pr file.

Is it a bug?? Have i do something wrong?

Thank you in advice for the help!


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
David Mihalcik  
View profile  
 More options Mar 2 2008, 12:32 am
From: David Mihalcik <kraka...@gmail.com>
Date: Sat, 1 Mar 2008 21:32:16 -0800 (PST)
Local: Sun, Mar 2 2008 12:32 am
Subject: Re: problems about viper-pe point distance
There is a bug in the distance measure for points. It isn't
'null safe', meaning it will fail instead of giving a distance if no
point is specified in either the target or candidate data on a frame.

A work around is making sure you have a value on every frame that is
in your object, but that might not be doable. (e.g. a face landmark
point disappears when a person turns their head, but the 'object' is
the person, not the landmark, so you'd still expect to have a
descriptor).

I'd recommend filing a bug with viper-bugs, or you can fix it yourself
if you download the source code. The bug is in the method on the top
of your stack trace, in the EuclideanDistance inner class of
viper.descriptors.attributes.Attribute_point. You'd have to check the
values of the Difference object for nulls, instead of doing what it
does now, which is dereference them directly.

On Feb 29, 7:13 am, avastreg <isac.new...@gmail.com> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
avastreg  
View profile  
 More options Mar 5 2008, 11:52 am
From: avastreg <isac.new...@gmail.com>
Date: Wed, 5 Mar 2008 08:52:33 -0800 (PST)
Local: Wed, Mar 5 2008 11:52 am
Subject: Re: problems about viper-pe point distance
Thank you for your suggestion and your answer, i've fixed it in the
source code, checking values for null.

Greetings

Alessandro

On 2 Mar, 06:32, David Mihalcik <kraka...@gmail.com> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google