[x3d-public] HAnim Schematron warnings and X3DUOM incorrect?

[John Carlson]

On Sun, Jan 15, 2023 at 4:27 PM Joseph D Williams <joedwil at earthlink.net>
wrote:

>
>
> John, and Don,
>
> Thanks for the example johnJoint2 skeleton. Nice work on those ‘custom’
> values you used. Am wishing the Hierarchy diagram included would reflect
> what is actually in the subject user code, for names and hierarchy of Joint
> and Segment and Site nodes, maybe even along with the measurements.
>

Segments and Sites will come soon, but we’re still trying to fix
schematron/X3DUOM, waiting for Don to accomplish updates, then we will
revisit schematron diagnostics.

> I can look at this in more detail, but
>
>   <meta name='modified' content="14 Jan 2023/>
>

Ah, good fix, missing quote.  I’m unsure why validation didn’t catch this.
Weird.

> Fix this one, please.
>
> The rest seems to run but since no viz of skeleton, hard to tell. That is
> why the Hierarchy.txt diagram for this example is so important as an author
> aid. People will add joints and then displacers to get special effects.
>
I’d like to complete the skeleton so it’s visible, but let’s fix schematron
diagnostics with current examples so we don’t get confused with
measurements.

> Finally, as an author, I would like to start with simple access to either
> changing or using all measurements in table a10 and a11 and then push the
> button to generate xml user code for the skeleton.
>

A.10.txt and A.11.txt are available for modification in the zip.   They are
higher than the other A… files because of string comparison is used.

Push button will require an app.  Meanwhile, try:

$ perl h6.pl

You can direct output to a file with:

> myhuman.x3d

Let’s find a place on sourceforge for teamwork.


The hierarchy diagram is simple HAnim GUI that shows all joints, segments
> sites, dimensions and input/outputs. No need now for lines to show segment
> and site connections let’s just add the Segment, put on the Joint center
> marker and add a marker for Site(s) on that segment. Then, hook it up with
> an existing walk or run or animation to see how it works. Now it becomes
> possible to make a simple skin and hook it up.
>

Joe, for me, it’s more of a priority to get the schematron/X3DUOM right, or
improve my understanding of the hierarchy.  I might have additional parts
of the hierarchy in files I haven’t sent yet.   The primary thing to do is
read schematron diagnostics and confirm whether the diagnostics are valid
or not.

I’m sorry I’m being so dramatic.  We can discuss in private if necessary.
We can walk through diagnostics and compare to hierarchy. I plan on focused
work to identify all issues.

I’ll txt you now.

John

> Thanks again,
>
> Joe
>
> *From: *John Carlson <yottzumm at gmail.com>
> *Sent: *Sunday, January 15, 2023 2:17 AM
> *To: *Don Brutzman <brutzman at nps.edu>; Joe D Williams
> <joedwil at earthlink.net>; X3D Graphics public mailing list
> <x3d-public at web3d.org>
> *Subject: *Fwd: HAnim Schematron warnings and X3DUOM incorrect?
>
>
>
> Don, this is my highest priority/stopper now, but me resting even higher!
>
>
>
> Rather than patches right now, confirming the readings of the HAnim
> standard hierarchy, schematron diagnostics and X3DUOM is welcome.  I
> hesitate moving from the parsing the hierarchy to X3DUOM.
>
>
>
> I don’t want to patch my .x3d generator if schematron diagnostics are
> wrong.
>
>
>
> If necessary, i can apply patches to my Hierarchy.txt file or parser.
>
>
>
> Thanks!
>
>
>
> John
>
> ---------- Forwarded message ---------
> From: *John Carlson* <yottzumm at gmail.com>
> Date: Sun, Jan 15, 2023 at 12:36 AM
> Subject: Fwd: HAnim Schematron warnings and X3DUOM incorrect?
> To: Don Brutzman <brutzman at nps.edu>, Joe D Williams <joedwil at earthlink.net>,
> X3D Graphics public mailing list <x3d-public at web3d.org>
>
>
>
> Repeat email.  Need to sync my HAnim Hierarchy.txt (attached, i hope,
> otherwise check HAnim standard) with X3DUOM and maybe XML Schema.
>
>
>
> Very important for building LOA4 HAnim models and checking them with
> Schematron.
>
>
>
> Schematron messages included.   Please check against hierarchy in standard
> or my derivative.
>
>
>
> I do understand that i may need a better introduction to the Hierarchy.
>
>
>
> I’m trying to reduce the pain of recorrecting models that don’t match the
> standard.
>
>
>
> Thanks!
>
>
>
> John
>
>
>
> ---------- Forwarded message ---------
> From: *John Carlson* <yottzumm at gmail.com>
> Date: Sat, Jan 14, 2023 at 3:20 AM
> Subject: Re: HAnim Schematron output sampled
> To: Joe D Williams <joedwil at earthlink.net>, Don Brutzman <brutzman at nps.edu>,
> X3D Graphics public mailing list <x3d-public at web3d.org>
>
>
>
> Whoops, I didn't provide zip.   Attached.
>
>
>
> On Sat, Jan 14, 2023 at 2:58 AM John Carlson <yottzumm at gmail.com> wrote:
>
> Attached source for your perusal!  Please run JohnJoint2.x3d through
> schematron and check messages in last message as reported by Schematron.
>
>
>
> See JohnJoint2.x3d and Hierarchy.txt
>
>
>
> Thanks!
>
>
>
> John
>
> ---------- Forwarded message ---------
> From: *John Carlson* <yottzumm at gmail.com>
> Date: Sat, Jan 14, 2023 at 2:48 AM
> Subject: HAnim Schematron output sampled
> To: Joe D Williams <joedwil at earthlink.net>, Don Brutzman <brutzman at nps.edu>,
> X3D Graphics public mailing list <x3d-public at web3d.org>
>
>
>
> Misreading Hierarchy?
>
>
>
> Please check the Schematron hierarchy against these complaints.   I think
> the schematron may be wrong.  I will send along the model when I get a zip.
>
>
>
> <HAnimJoint DEF='hanim_vl5' name='vl5'/> has parent HAnimJoint
> name='humanoid_root' rather than expected parent name='sacroiliac',
> recommend checking model
> [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2], warning]
>
> <HAnimJoint DEF='hanim_l_sternoclavicular' name='l_sternoclavicular'/> has
> parent HAnimJoint name='vt1' rather than expected parent name='vc7',
> recommend checking model
> [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[2],
> warning]
>
> <HAnimJoint DEF='hanim_r_sternoclavicular' name='r_sternoclavicular'/> has
> parent HAnimJoint name='vt1' rather than expected parent name='vc7',
> recommend checking model
> [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[3],
> warning]
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230115/bbb5d494/attachment.html>