<div dir="ltr">Hypothesis: the hanim motion fields were originally designed to make it easy to copy and paste from freely available motion capture .bvh files.<div>If so, then -as we get further from copy and pasta-ability- there may be some demand for tools to import .bvh and convert to these x3d MF fields.</div><div>Or - have web3d browsers load .bvh directly, via a mapping / lookup node / field./ table which you would likely also need for import tools.</div><div>-Doug</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 20, 2020 at 12:38 PM GPU Group <<a href="mailto:gpugroup@gmail.com">gpugroup@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><a href="https://www.web3d.org/documents/specifications/19774/V2.0/MotionDataAnimation/ExampleMocapAnimationMotionObject.html" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/MotionDataAnimation/ExampleMocapAnimationMotionObject.html</a> <br></div><div>This version of AnnexD is what I used - and it looks like an SFString 0 as does values and jpints</div><div>WARNING - any examples from this AnnexD may need rework for web3d </div><div></div><div>-Doug</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 20, 2020 at 12:21 PM Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">MUFTI you definitely want to be looking at the HAnim2 specifications.<br>
<br>
Web3D Consortium members are the controlling authority for X3D and HAnim specifications, International Standards Organization (ISO) certifies.<br>
<br>
X3D3 is simply implementing HAnim2, typically as tersely as possible so that there is no confusion in prose that HAnim2 is the controlling specification. Please see<br>
<br>
* ISO/IEC 19774-1, HAnim2 Specifications parts 1 and 2<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/</a><br>
<br>
===============================================<br>
* ISO/IEC 19774-1, HAnim2 Specifications part 1<br>
clause 3 Terms and definitions<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/glossary.html" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/glossary.html</a><br>
<br>
3.11<br>
level of articulation<br>
LOA<br>
degree of fidelity based on number of joints in an HAnim figure<br>
===============================================<br>
<br>
also<br>
<br>
* 4.8.5 Levels of articulation<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#LevelsOfArticulation" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#LevelsOfArticulation</a><br>
<br>
"Level of articulation (LOA) represents the complexity and detail of joints for a humanoid skeletal hierarchy, and can be used for generating various motions based on the joints. There are five levels of articulation:<br>
<br>
LOA‑0 represents only the humanoid_root Joint object without an accompanying hierarchy, as shown in (Figure 4.3).<br>
LOA‑1 represents the simplest organization and hierarchy of joints for a humanoid. There are 18 joints and 18 segments. Each segment has a joint in the hierarchy. Figure 4.4 represents LOA‑1 joints.<br>
LOA‑2 consists of 71 joints and 71 segments (Figure 4.5).<br>
LOA‑3 consists of 94 joints and 94 segments (Figure 4.6).<br>
LOA‑4 builds on LOA‑3 by adding anatomical details of hands and feet (Figure 4.7). LOA‑4 consists of 148 joints and 148 segments. Hands and feet joints for LOA‑4 are illustrated in 4.9.3 and 4.9.4 respectively."<br>
<br>
<br>
* 4.9 Structure of a humanoid, 4.9.6 Hierarchy<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#Hierarchy" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#Hierarchy</a><br>
<br>
* 4.9 Structure of a humanoid<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html</a><br>
<br>
* Annex A (informative) Nominal human body dimensions and levels of articulation (LOAs)<br>
Nominal human body dimensions and levels of articulation (LOAs)<br>
<br>
* A.2 Levels of articulation (LOAs)<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/BodyDimensionsAndLOAs.html#LevelsOfArticulation" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/BodyDimensionsAndLOAs.html#LevelsOfArticulation</a><br>
<br>
There is a lot of information in there that deserves careful reading. You will find tables and diagrams that illustrate every joint and (bone) segment in the human body, along with a number of useful feature-point sites. This took years of effort by many members of HAnim working group.<br>
<br>
Current work by Joe Williams, John Carlson and myself is improving past-legacy examples to match HAnim2 capabilities with X3D4. We hope that testing and verification will help.<br>
<br>
* HumanoidAnimation X3D Examples Archive<br>
<a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/content/examples/HumanoidAnimation</a><br>
<br>
* X3D Tooltips, HAnimHumanoid loa<br>
<a href="https://www.web3d.org/x3d/content/X3dTooltips.html#HAnimHumanoid.loa" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html#HAnimHumanoid.loa</a><br>
<br>
HAnim designers hope that by identifying both HAnimHumanoid models and HAnimMotion animations with the LOA supported, it will be easier to mix/match models and animations. Since each LOA is a strict subset of the next LOA, some compatibility is possible across human LOA levels.<br>
<br>
* 4.9.7 Site and Segment relationships<br>
<a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#SiteSegmentRelationships" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#SiteSegmentRelationships</a><br>
<br>
It is not impossible to think that someday this work might even rise to the level of rigor needed for 3D HAnim models becoming part of medical records. HAnim and X3D4 have the potential to help... everyone.<br>
<br>
Thanks for your scrutiny and helpful questions.<br>
<br>
<br>
On 6/18/2020 11:02 PM, John Carlson wrote:<br>
> <br>
> To answer your question, many parts of the government like to create acronyms.<br>
> <br>
> John<br>
<br>
Sorry John, can't blame government for this one. (Wondering, are parts of the government controlling your keyboard?!)<br>
<br>
> On Fri, Jun 19, 2020 at 12:38 AM J. Scheurich <<a href="mailto:mufti11@web.de" target="_blank">mufti11@web.de</a> <mailto:<a href="mailto:mufti11@web.de" target="_blank">mufti11@web.de</a>>> wrote:<br>
> <br>
> hI,<br>
> <br>
> From<br>
> <br>
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD1/Part01/components/hanim.html#HAnimMotion" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD1/Part01/components/hanim.html#HAnimMotion</a><br>
> <br>
> SFInt32 [in,out] loa -1 [-1,4]<br>
> <br>
> What does "loa" mean ? Fieldnames in X3D are often english words,<br>
> but the dictionary <a href="http://leo.org" rel="noreferrer" target="_blank">leo.org</a> <<a href="http://leo.org" rel="noreferrer" target="_blank">http://leo.org</a>> has no results for "loa" 8-(<br>
> <br>
> so long<br>
> MUFTI<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div>
</blockquote></div>