Hi Søren,Thanks. Yes, it is clear now. However, the Arm3d\Jnt.any file seems to
define humeral rotation wrt the scapula and not wrt the thorax as in the
Interface.any file. Or am I mistaken? I suppose that I could always create my
definitions. Thanks again for the explanation, it is very clear.There is another
question, I’ll post it separately since it is on a different topic.Thanks
again,-VennTo: anyscript@yahoogroups.comFrom: support@anybodytech.comDate: Fri,
16 Feb 2007 08:55:41 +0000Subject: [anyscript] Re: Bug in GH Rotation axis and
possible typo in art_gh_humSurf definition
Hi Venn
It is a good question, and gives me a chance to explain why the
interface rotational measures was created.
The rotational measures in the interface folder is a little different
from the rotational measures in the Arm3d/joints.any file (these
follow ISB). For example is the rotation of gh measured wrt. thorax
not scapula, this may also explain the sequenc change?. The
rotational measures in the interface files should be seen as
alternative ways of driving the model compared to the original one in
the joints. In the interface we have tried to make the model behave
symmetrical for the left and right side, so that a positive abduction
angle in the right side corresponds to a positive angle on the left
side and so on.
So you may define as many rotational measures you like and the they
can co-exist in the model, and you are free to choose which one of
them you drive. If you prefer the ISB rotational measures you should
use the GH rotation in the Arm3d/Joint.any file. If you would like
another one it can also be defined.
About the radius you are right, this looks like a typo. The size of
the ellipsoid is defined using there control points. This is done to
ensure that the ellipsoid is scaled properly.
I hope this answers your question otherwise please write again
Best regards
Søren, AnyBody Support
— In anyscript@yahoogroups.com, “Vengateswaran J. Ravichandran”
<vennjr@…> wrote:
>
> Hello folks,
>
> Bug?
> The bug corresponds to the definition of AnyKinRotational GHMeasure
in
> BRep\Aalborg\Arm3D\Interface.any (50)
>
> AnyKinRotational GHMeasure ={
> AnyRefNode &ref1 = …ShoulderNodeRef.RotNode;
> AnyRefNode &ref2
= …FolderSide.ShoulderArm.Seg.Humerus.gh.RotNode;
> Type=RotAxesAngles;
> };
>
> Noting that the default order of rotations is Z,Y,X for
RotAxesAngles,
> this doesn’t follow the convention defined by ISB. In my humble
opinion,
> I think the definition should read as below, instead:
> AnyKinRotational GHMeasure ={
> AnyRefNode &ref1 = …ShoulderNodeRef.RotNode;
> AnyRefNode &ref2
= …FolderSide.ShoulderArm.Seg.Humerus.gh.RotNode;
> Type=RotAxesAngles;
> Axis1 = y;
> Axis2 = z;
> Axis3 = y;
> };
>
>
>
> Possible Typo:
> In BRep\Aalborg\Arm3D\HumerusMuscleGeometry.any (46), the radius for
> art_gh_humSurf is defined as :
> Radius = (.P1Radius, .P2Radius, .P2Radius)
>
> I’m wondering if this is a typo or if this is intentional. If it is
a
> typo, should it instead read
> Radius = (.P1Radius, .P2Radius, .P3Radius)?
>
>
> I do note that it is actually a sphere and hence the values
of .PxRadius
> are all the same. So, leaving them as they are wouldn’t change the
final
> results.
>
>
> I appreciate your input into these two issues.
> I thank you, in advance.
> -Venn
>
>
>
> [Non-text portions of this message have been removed]
>
Get the most out of tax shelters and other breaks.
<a href=“http://articles.moneycentral.msn.com/Taxes/TaxShelters/TaxShelters.aspx?icid=WLtextFebtagline”>http://articles.moneycentral.msn.com/Taxes/TaxShelters/TaxShelters.aspx?icid=WLt
extFebtagline</a>
[Non-text portions of this message have been removed]
