[x3d-public] HAnim2 names and HAnim1 aliases for Joint, Segment and Site

[Don Brutzman]

I talked through the logic with Dick during the X3D Specification Editors conference this morning.

It looks like we will be able to keep HAnim2 aliases for feature point names (for example index 101 in table B.2 for l_thumb_distal) even though it is a duplicate for the Segment name alias.

I will keep working on the HAnim1 > HAnim2 conversion efforts.

p.s. almost all of the prior errors in the Korean Character models now appear to be fixed, still have a few more checks to do.


On 3/7/2021 10:00 PM, Brutzman, Donald (Don) (CIV) wrote:
> I was able to accomplish most of our prior discussion points from last Wednesday Joe.  Not ready for your new comments yet, this all takes time.
> 
> I added a test for duplicate alias definitions when building X3DUOM.  It now warns of the following problem that we hadn't noticed yet:
> 
> =======================
> X3dUnifiedObjectModel:  process X3D schema version 4.0 using BuildX3dUnifiedObjectModelXmlFile.xslt


> *** error hanimFeaturePointNameValues xs:enumeration value='l_carpal_distal_phalanx_1' has duplicate alias='l_thumb_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='l_thumb_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='l_carpal_distal_phalanx_2' has duplicate alias='l_index_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='l_index_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='l_carpal_distal_phalanx_3' has duplicate alias='l_middle_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='l_middle_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='l_carpal_distal_phalanx_4' has duplicate alias='l_ring_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='l_ring_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='l_carpal_distal_phalanx_5' has duplicate alias='l_pinky_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='l_pinky_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='r_carpal_distal_phalanx_1' has duplicate alias='r_thumb_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='r_thumb_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='r_carpal_distal_phalanx_2' has duplicate alias='r_index_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='r_index_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='r_carpal_distal_phalanx_3' has duplicate alias='r_middle_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='r_middle_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='r_carpal_distal_phalanx_4' has duplicate alias='r_ring_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='r_ring_distal'
> *** error hanimFeaturePointNameValues xs:enumeration value='r_carpal_distal_phalanx_5' has duplicate alias='r_pinky_distal' separately defined in xs:simpleType name='hanimSegmentNameValues' xs:attribute name='alias' fixed='r_pinky_distal'
> =======================
> 
> I think that the origin of this name collision lies in
> 
> Table B.2 — Feature points

> specifically table indexes 101-110, which lists to HAnim1 alias names in the right column for each HAnim2 feature point.
> 
> However when you look at HAnim version 1 specification, those alias names are for Segments and not Feature Points.
> 
> This duplication might be OK, a Site might be named after its parent Segment and as long as the Site name ends in _pt _view or _tip then the name field (and corresponding DEF) are unique.
> 
> Am getting some difficulties fixing LOA3 examples however, and so wanted to get your opinion on this please.

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman