<div dir="ltr"><div dir="ltr"><div>I renamed the second r_clavicle to r_clavicale to match the left. The second l_metacarpal_phalanx_3 should be r_, not l_</div><div><br></div><div>I can now go backwards and forwards from hierarchy to JSON to hierarchy, and from JSON to X3DV. Now to see if this skeleton validates with X3D-Edit. Enjoy!</div><div><br></div><div>Hope you like the picture of the default centers with center updates from X3DUOM! I don't particularly! It's not a long step to bringing in centers from another skeleton!</div><img src="cid:ii_llx1g62k0" alt="image.png" width="562" height="339"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 29, 2023 at 7:56 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@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">The hierarchy can be found through parents in hanimall.txt perhaps (grab a new copy, perhaps). I'm creating data from X3DUOM. Maybe you can direct me where from-to is besides parents?<div><br></div><div>I just found some bugs in your almighty hierarchy (Actually tovrmlx3d.exe, thanks Michalis, great tool) ..r_clavicle is both a segment and a site??? And there's two l_metacarpals?</div><div><br></div><div><div>$ egrep -n "_metacarpal_phalanx_3|_clavicle" HAnimV2JointSegmentSiteHierarchy\[20200708\].txt</div><div>405: | l_clavicle #B91</div><div>471: | | (l_metacarpal_phalanx_3) x y z #S76</div><div>515: r_clavicle #B119</div><div>517: (r_clavicle -0.0115 1.4943 0.0400) #S19</div><div>581: | (l_metacarpal_phalanx_3) x y z #S79</div><div><br></div><div>I can't bring up pictures if there's bugs in input...</div><div><br></div><div>John</div><div><br></div><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 29, 2023 at 4:03 PM Joe D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</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 style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:12pt"><p style="margin:0.1rem 0px;line-height:1">For hanimall.txt, might as well add that [notation] that describes the segment from-to. </p>
<p style="margin:0.1rem 0px;line-height:1">Yes, we've seen close to this as an export form, but no structure.</p>
<p style="margin:0.1rem 0px;line-height:1">so, again shows that there is No Better form to store this kind of info than in x3d HAnim User Code for skeleton. </p>
<p style="margin:0.1rem 0px;line-height:1">Well, for some folks the Hierachy sheet I sent might be more appreciated since it matches the form of the Part 1 Concepts Hierarchy graphs and adds dimensions.</p>
<p style="margin:0.1rem 0px;line-height:1">Even so, if you are storing data in a readable, structured, meaningful, and accessible form, then HAnim User Code xml or Classic can't be beat. </p>
<p style="margin:0.1rem 0px;line-height:1">Joe</p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
</div>
<div style="border-left:1px solid rgb(170,170,170);box-sizing:border-box;padding:10px 0px 10px 15px;margin:0px">
<p>-----Original Message-----<br>From: John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>Sent: Aug 29, 2023 12:11 PM<br>To: Joe D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</a>><br>Cc: X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>Subject: Re: HAnim LOA4 Templates. Choices. Preference?</p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Joe, yes, but many of them are "x y z"...not useful! I'm not saying X3DUOM is going to be better, but all LOAs are in X3DUOM, AFAIK, pulling in all of them.
<div> </div>
<div>I won't override the ones you have.</div>
<div><br>I'll send an update to your hierarchy, filling in "x y z" based on what I see in X3DUOM. I've already extracted stuff from X3DUOM, see:</div>
<div> </div>
<div><a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/HAnimAll.txt" target="_blank">https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/HAnimAll.txt</a> (Katy's format extended).</div>
<div> </div>
<div><a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/HAnim.py" target="_blank">X3DJSONLD/src/main/python/HAnim.py at master · coderextreme/X3DJSONLD (github.com)</a></div>
<div> </div>
<div>So now, I will write code to merge this into the JSON that was derived from your page. After that, I will create something to output the JSON in your format.</div>
<div> </div>
<div>I do need to carry over id's from X3DUOM, I think!</div>
<div> </div>
<div>Again, I haven't spot checked any comparison between your hierarchy and X3DUOM, but I will generate a report.</div>
<div> </div>
<div>JSON is attached.</div>
<div> </div>
<div>John</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">On Tue, Aug 29, 2023 at 12:05 PM Joe D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:12pt">
<p style="margin:0.1rem 0px;line-height:1">How about using that joint centers from that page of hierarchy I sent? </p>
<p style="margin:0.1rem 0px;line-height:1">Please try that.</p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
<p style="margin:0.1rem 0px;line-height:1">Those are close to what is in Part 1 Annex A standard.</p>
<p style="margin:0.1rem 0px;line-height:1">All loa3 are there but some v2 loa4 joint locations are missing. </p>
<p style="margin:0.1rem 0px;line-height:1">Might try estimating some missing ones.</p>
<p style="margin:0.1rem 0px;line-height:1">Joe</p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
</div>
<div style="border-left:1px solid rgb(170,170,170);box-sizing:border-box;padding:10px 0px 10px 15px;margin:0px">
<p>-----Original Message-----<br>From: John Carlson <<a href="mailto:yottzumm@gmail.com" rel="noopener" target="_blank">yottzumm@gmail.com</a>><br>Sent: Aug 29, 2023 9:26 AM<br>To: Joe D Williams <<a href="mailto:joedwil@earthlink.net" rel="noopener" target="_blank">joedwil@earthlink.net</a>>, X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org" rel="noopener" target="_blank">x3d-public@web3d.org</a>><br>Subject: HAnim LOA4 Templates. Choices. Preference?</p>
<p style="margin:0.1rem 0px;line-height:1"> </p>
I’m going to pull HAnim centers from somewhere—not Joe’s hierarchy, but that’s the what I’m basing the skeleton on. The choices 1) X3DUOM. 2) the standard. 3) Katy’s file. I don’t have any code for 1. My preference is 3, 2, 1. I think the best long term is 1. I’d rather not do schema at this point.
<div dir="auto"> </div>
<div dir="auto">I will start work on 1 in python and/or JavaScript, working with X3DUOM to extract centers. My target is either JSON directly from Joe’s hierarchy, which contains places for x y z already, or Katy’s format. I already have JavaScript code for generating VRML from JSON. I will use python to dump X3DUOM to Katy’s format, then I’ll use JavaScript to bring that into the JSON.</div>
<div dir="auto"> </div>
<div dir="auto">Hopefully, I’ll be able to regenerate Joe’s hierarchy from the JSON with more x y z filled in. I’m already storing indentation strings.</div>
<div dir="auto"> </div>
<div dir="auto">Is there a another source besides Joe’s hierarchy for Joint and Segment id? I’ll probably carry them forward as comments.</div>
<div dir="auto"> </div>
<div dir="auto">I have nascent JavaScript code for “approving” joints, segments and sites. More on that later.</div>
<div dir="auto"> </div>
<div dir="auto">John</div>
</div>
<p style="margin:0.1rem 0px;line-height:1"> </p>
</blockquote>
</div>
</div>
<p style="margin:0.1rem 0px;line-height:1"> </p></blockquote></div>
</blockquote></div>