<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1695300725;
mso-list-type:hybrid;
mso-list-template-ids:821705852 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>I call this “recognition”.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yes John, recognition can refer to the idea that if you have a set of data points, then you can construct a virtual model of the thing that you can recognize.</p><p class=MsoNormal>That idea is followed by hanim with the simple concept of mapping joint centers in a Humanoid space. Thus, if you can accumulate a data model for a realistic individual by measuring the location of actual Joint centers of the individual in human space, then you can create a realistic articulated virtual skeleton in x3d hanim Humanoid space. Further, this model can be animated by creating parametric data that directly relates movements in human space to representative animations in Humanoid space. Further, x3d hanim provides the same style of data acquisition to establish a Humanoid skin space directly obtained by actual measurements of personal surface features. Overall, connecting the skeleton and provide a world-class platform for developing standardized internal features such as bones, skin, other organs, and teeth, hair and eyeballs.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, recognition ranges from parametrizing certain feature sets and deriving recognizable patterns to providing the immersive virtuality that fully represents the target simulation. The x3d hanim Humanoid, and its animation and interactivity capabilities and possibilities, along with the fact that every other area of x3d is pertinent to the Humanoid, makes it feasible to produce high fidelity models from very detailed measurements and experimental observations.</p><p class=MsoNormal>That is the ultimate hanim idea, realistic Humanoid stimulus/response in realistic stimulus/response environments. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for all thoughts to advance x3d hanim fun. </p><p class=MsoNormal>Joe</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Friday, June 26, 2020 8:08 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Cc: </b><a href="mailto:h-anim@web3d.org">Humanoid Animation (HAnim) Working Group</a>; <a href="mailto:joedwil@earthlink.net">Joe D Williams</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: HAnim diagnostics autogenerated from X3DUOM</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>I call this “recognition”. Is there any chance we can use the same information for HAnim generation?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John</p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Fri, Jun 26, 2020 at 9:41 AM Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:</p></div></div></div><p class=MsoNormal style='margin-left:4.8pt'>I wrote some diagnostic generators for HAnim using information in X3DUOM that list every name for Joint Segment Site along with alias, loa and parent information.<br><br>About 640 rules have been created and added to X3D Schematron for checking correct names, warning about about aliases, and checking for correct parents.<br><br>Autogeneration assets:<br><br>* <a href="https://www.web3d.org/x3d/stylesheets/X3duomToX3dDiagnostics.xslt" target="_blank">https://www.web3d.org/x3d/stylesheets/X3duomToX3dDiagnostics.xslt</a><br><br>* <a href="https://www.web3d.org/x3d/stylesheets/X3dDiagnostics4.0.xml" target="_blank">https://www.web3d.org/x3d/stylesheets/X3dDiagnostics4.0.xml</a><br> (XML fragments get copied into other QA tools)<br><br>Further future feature checks are planned for X3D-Tidy, whenever the extensive information in X3DUOM exceeds that already available in X3D schema validation.<br><br>Next, performed these comprehensive checks against the new HAnim archive. It picked up a large number of additional issues for us to address and fix, one at a time. Results follow.<br><br>* <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation" target="_blank">https://www.web3d.org/x3d/content/examples/HumanoidAnimation</a><br><br>* <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation/build.X3dSchematronX3dTidy.log.txt" target="_blank">https://www.web3d.org/x3d/content/examples/HumanoidAnimation/build.X3dSchematronX3dTidy.log.txt</a><br><br>So, at long last, we are approaching really thorough and rigorous testing of all aspects of HAnim.<br><br>Relevant motto: "you get what you inspect, not what you expect."<br><br>Looking forward to further bug-squashing and progress together. Have fun with X3D4 HAnim2! 8)<br><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" target="_blank">http://faculty.nps.edu/brutzman</a></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>