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

[Don Brutzman]

Thanks for feedback Joe.

On 3/1/2021 3:09 PM, Joseph D Williams wrote:
> 
> https://www.web3d.org/x3d/content/examples/HumanoidAnimation/HandFootJointNameAliasFiguresHAnim2and1.pdf

Have also automated production of plain-text table to simplify use and review.  This was very helpful again today, cleaning up ROUTE destinations in JoeKick that were beyond the diagnostic power of the converter.

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation/HAnim2NameHAnim1AliasTables.txt

Will be discussing with Dick, it would be easy enough to automate creation of HTML tables as well for HAnim2 spec addition.

* Mantis 1351 Consider correspondence tables for HAnim2 names and HAnim1 aliases
   https://www.web3d.org/member-only/mantis/view.php?id=1351

Also food for thought: shouldn't HAnimMotion have a name field?  This was probably discussed long ago and rejected due to lack of directly defined functionality.  However the entire rest of an HAnim engine depends on name fields, so I think we should be consistent (or will eventually regret that).

* Mantis 1350 HAnimMotion lacks a name field and is inconsistently defined
   https://www.web3d.org/member-only/mantis/view.php?id=1350

Scrutiny and feedback always welcome.

> Real Fine for the Joint v2 names and v1 ‘alias’ names.
> 
> Another v1 and v2 reference are the part 1 v1 and v2 annex a tables.

yes for a list of feature points (Site) but not for Joint and Segment

> Now all we need is example
> 
> Maybe the Segment v2 names and v1 aliases are not so easy to find but they appear in the v1 hierarchy diagrams and the target v2 code we have, with only the aliases for the new v2 segments missing.
> 
> With great fortune, the joints lists we have from your markup will help with the connections.

yes helping

> I will read the xml validation documentation with reference to spec v1 and v2 hierarchy diagrams to check.
> 
> With documentation of v2 and v1 names I hope I can predict the outcome when we update the target ‘v2 invizable’ we are working on. Then, the stone will stop skidding and begin to roll.

please check all our examples, we now have a much cleaner build.  everything is committed in sourceforge and also pushed to web3d.org

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation/build.X3dTidy.log.txt


> I think the only still missing data will be:
> 
> * example coordinates for the v2 new joints and
> 
> * example coordinates for the v2 new sites
> 
> based on the hanim part 1 annex A default pose and existing coordinates of v1 joints and sites as listed in the annex a tables.

OK

Am also hoping to look at on or more of the Korea chacters with you, interesting errors that appear fixable.  for example:

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA1Index.html

> C:\x3d-code\www.web3d.org\x3d\content\examples\HumanoidAnimation/Characters//JinLOA1.x3d processing with X3dTidy.xslt stylesheet for tidied-up .x3d
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_tarsal_proximal_phalanx'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_tarsal_proximal_phalanx'

and

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA2Index.html

> C:\x3d-code\www.web3d.org\x3d\content\examples\HumanoidAnimation/Characters//JinLOA2.x3d processing with X3dTidy.xslt stylesheet for tidied-up .x3d
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_tarsometatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_metatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_tarsal_proximal_phalanx'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_tarsal_interphalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_tarsal_distal_phalanx'

> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_tarsometatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_metatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_tarsal_proximal_phalanx'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_tarsal_interphalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_tarsal_distal_phalanx'

* https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA3Index.html

> C:\x3d-code\www.web3d.org\x3d\content\examples\HumanoidAnimation/Characters//JinLOA3.x3d processing with X3dTidy.xslt stylesheet for tidied-up .x3d
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_tarsometatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_metatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_tarsal_proximal_phalanx'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='l_tarsal_interphalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='l_tarsal_distal_phalanx'

> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_tarsometatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_metatarsal'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_metatarsophalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_tarsal_proximal_phalanx'
> *** warning, look for missing underscore and digit number as suffix of HAnimJoint name='r_tarsal_interphalangeal'
> *** warning, look for missing underscore and digit number as suffix of HAnimSegment name='r_tarsal_distal_phalanx'

Myeong Won Lee:  I think that you and Team Suwon might have completed these examples before the final naming convention, which was to use consistent names throughout all LOAs rather than change joint names.

Please see

* HAnim2 4.9.7 Site and Segment relationships
   https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#SiteSegmentRelationships

I believe if we append "_2" for index (i.e. longest) toe, that matches the column for LOA3 LOA2 and LOA1.

Joe, wondering if we should further add these as another set of alias values - that would automate appending "_2" whenever no specific toe is defined.  Seems useful and reasonable.

Please look these over when convenient.  Let's discuss in our next meeting please.

> Thanks for all and Spring is getting closer,
> 
> Joe

you betcha, stay safe and careful 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