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

[John Carlson]

The links did not contain elements with a missing "default" attribute.  I
now default the default to "x y z" in my code (well, not exactly, but
that's what Joe uses).

John

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

> 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/4e90cfb7/attachment.html>