[x3d-public] HAnim LOA4 Templates. Choices. Preference?

Tue Aug 29 18:14:02 PDT 2023

I renamed the second r_clavicle to r_clavicale to match the left.  The
second l_metacarpal_phalanx_3 should be r_, not l_

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!

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!
[image: image.png]

On Tue, Aug 29, 2023 at 7:56 PM John Carlson <yottzumm at gmail.com> wrote:

> 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?
>
> 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?
>
> $ egrep -n "_metacarpal_phalanx_3|_clavicle"
> HAnimV2JointSegmentSiteHierarchy\[20200708\].txt
> 405:                                    |   l_clavicle
>                                                              #B91
> 471:                                    |         |
>  (l_metacarpal_phalanx_3)  x y z
>  #S76
> 515:                                      r_clavicle
>                                                            #B119
> 517:                                          (r_clavicle  -0.0115 1.4943
> 0.0400)                                                     #S19
> 581:                                              |
>  (l_metacarpal_phalanx_3)  x y z
>  #S79
>
> I can't bring up pictures if there's bugs in input...
>
> John
>
>
>
> On Tue, Aug 29, 2023 at 4:03 PM Joe D Williams <joedwil at earthlink.net>
> wrote:
>
>> For hanimall.txt, might as well add that [notation] that describes the
>> segment from-to.
>>
>> Yes, we've seen close to this as an export form, but no structure.
>>
>> so, again shows that there is No Better form to store this kind of info
>> than in x3d HAnim User Code for skeleton.
>>
>> 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.
>>
>> 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.
>>
>> Joe
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: John Carlson <yottzumm at gmail.com>
>> Sent: Aug 29, 2023 12:11 PM
>> To: Joe D Williams <joedwil at earthlink.net>
>> Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
>> Subject: Re: HAnim LOA4 Templates. Choices. Preference?
>>
>>
>> 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.
>>
>> I won't override the ones you have.
>>
>> 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:
>>
>>
>> https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/HAnimAll.txt (Katy's
>> format extended).
>>
>> X3DJSONLD/src/main/python/HAnim.py at master · coderextreme/X3DJSONLD
>> (github.com)
>> <https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/python/HAnim.py>
>>
>> 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.
>>
>> I do need to carry over id's from X3DUOM, I think!
>>
>> Again, I haven't spot checked any comparison between your hierarchy and
>> X3DUOM, but I will generate a report.
>>
>> JSON is attached.
>>
>> John
>>
>> On Tue, Aug 29, 2023 at 12:05 PM Joe D Williams <joedwil at earthlink.net>
>> wrote:
>>
>>> How about using that joint centers from that page of hierarchy I sent?
>>>
>>> Please try that.
>>>
>>>
>>>
>>> Those are close to what is in Part 1 Annex A standard.
>>>
>>> All loa3 are there but some v2 loa4 joint locations are missing.
>>>
>>> Might try estimating some missing ones.
>>>
>>> Joe
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: John Carlson <yottzumm at gmail.com>
>>> Sent: Aug 29, 2023 9:26 AM
>>> To: Joe D Williams <joedwil at earthlink.net>, X3D Graphics public mailing
>>> list <x3d-public at web3d.org>
>>> Subject: HAnim LOA4 Templates. Choices. Preference?
>>>
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> Is there a another source besides Joe’s hierarchy for Joint and Segment
>>> id?  I’ll probably carry them forward as comments.
>>>
>>> I have nascent JavaScript code for “approving” joints, segments and
>>> sites.  More on that later.
>>>
>>> John
>>>
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230829/e48e87eb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 79716 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230829/e48e87eb/attachment-0001.png>