[x3d-public] HAnim 1.0, 2.0 joint, segment and featurePoint names implemented inX3DUOM, X3DJSAIL
Joseph D Williams
joedwil at earthlink.net
Thu Mar 14 18:56:56 PDT 2019
➢ Joe, thanks for all the excellent work on aliases. If you want to continue and integrate corresponding values for object centers and site translations, we can update all these assets further. Starting-point example values are found in
➢ * HAnim 1.0 Annex A (informative) Nominal body dimensions and levels of articulation
http://www.web3d.org/documents/specifications/19774/V1.0/HAnim/BodyDimensionsAndLOAs.html
Yes, I am sorting through the Annex A user code (works for v1) and tables along with the Annex B v2 to find agreement in order to use existing ‘nominal’ joint and site locations where appropriate. As you mentioned, yes, let’s include ‘nominal’ joint and site locations in the schema along with other v1 and v2 information. Now Annex A is a ‘nominal’ male and of course we need at least two general categories with example ‘nominal’ dimensions. Looking at it that way there are many missing dimensions in Annex A and maybe leave a space in the schema for ‘nominal’ male and ‘nominal’ female?
So, attached is what I have as the list of all stuff needed for the LOA4 user code. If I can get this complete, then the user code will be easy.
Please take a look at this. I really need to walk through this at least once more to check before committing to code.
Thanks and Best,
Joe
From: Brutzman, Donald (Don) (CIV)
Sent: Sunday, March 3, 2019 11:17 PM
To: Humanoid Animation (HAnim) Working Group; Joe D Williams
Cc: X3D Graphics public mailing list; Medical working group
Subject: HAnim 1.0, 2.0 joint, segment and featurePoint names implemented inX3DUOM, X3DJSAIL
Progress report. Following up on progress with X3Dv4 XML Schema and X3D Unified Object Model (X3DUOM), all of the allowed X3Dv4 / HAnim v2.0 enumerations for jointName, segmentName and featurePointName are now implemented in X3DJSAIL as lists and utility methods. Accessor methods are also provided for index, Level of Articulation (LOA), alias and parent.
===================================================================
X3D Java Scene Access Interface Library (X3DJSAIL)
http://www.web3d.org/specifications/java/X3DJSAIL.html
X3D Java Scene Access Interface Library (X3DJSAIL) supports programmers with standards-based X3D Java interfaces and objects, all as open source.
===================================================================
Example documentation:
http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/HAnim/HAnimJointObject.html
http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/HAnim/HAnimJointObject.html#jointNameValues
http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/HAnim/HAnimJointObject.html#getName--
http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/HAnim/HAnimJointObject.html#setName-java.lang.String-
static boolean hasJointNameAlias(java.lang.String jointName)
Whether a alias exists for this jointName
static boolean hasJointNameIndex(java.lang.String jointName)
Whether an index exists for this jointName
static boolean hasJointNameLoa(java.lang.String jointName)
Whether an loa exists for this jointName
static boolean hasJointNameParent(java.lang.String jointName)
Whether a parent exists for this jointName
static java.lang.String getJointNameAlias(java.lang.String jointName)
Get alias for this jointName
static int getJointNameIndex(java.lang.String jointName)
Get index for this jointName
static int getJointNameLoa(java.lang.String jointName)
Get Level of Articulation (loa) for this jointName
static java.lang.String getJointNameParent(java.lang.String jointName)
Get parent for this jointName
etc. etc. Similar enumeration lists can be found in HAnimSegment and HAnimSite.
Joe, thanks for all the excellent work on aliases. If you want to continue and integrate corresponding values for object centers and site translations, we can update all these assets further. Starting-point example values are found in
* HAnim 1.0 Annex A (informative) Nominal body dimensions and levels of articulation
http://www.web3d.org/documents/specifications/19774/V1.0/HAnim/BodyDimensionsAndLOAs.html
Looking ahead: next round of X3DJSAIL implementation work will add parent-child validation checks for HAnimJoint, HAnimSegment and HAnimSite nodes. Might possibly skeleton-tree serialization output as well. The alias values will allow backwards validation of HAnim 1.0 (X3Dv3) models. Such capabilities will significantly improve our Quality Assurance (QA) of HAnim models.
We will then work on upgrading X3D Schematron rules and HAnim example scenes to X3Dv4 / HAnim2.0 specifications.
X3D Example Archives: Basic, Humanoid Animation
http://www.web3d.org/x3d/content/examples/Basic/HumanoidAnimation
It remains our hope that HAnimsupport v2.0 representations for full anatomical fidelity of skeleton models and BVH-style motion animation will eventually lead to better support for accurate human modeling in medical tools and electronic health records.
Onward we go. Have fun with Humanoid Animation (HAnim)! 8)
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190314/6f759bae/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: HAnimV2JointSegmentSiteHierarchy[20190314].txt
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190314/6f759bae/attachment-0001.txt>
More information about the x3d-public
mailing list