Hi Micheal, I tried to work out how to switch off the optimization of the ankles
in the y Direction
// “MARKER " + .MarkerTopology.M10.Name + .MarkerTopology.M10.SegNr +
strval(.MarkerTopology.M10.NodePos[0]) +” "+
strval(.MarkerTopology.M10.NodePos[1])+ " "+
strval(.MarkerTopology.M10.NodePos[2])+ " weightdummy.txt " +
.MarkerTopology.M10.Name+ ".txt dummy.txt dummy.txt " + OptSetting,
“MARKER " + .MarkerTopology.M10.Name + .MarkerTopology.M10.SegNr +
strval(.MarkerTopology.M10.NodePos[0]) +” "+
strval(.MarkerTopology.M10.NodePos[1])+ " "+
strval(.MarkerTopology.M10.NodePos[2])+ " weightdummy.txt " +
.MarkerTopology.M10.Name+ “.txt dummy.txt dummy.txt " + " On off On”,
Is that right ?
i have the similar patter for the M7 for i can have for left and right ankles.
Initial conditions are set normally now without any problem, but running
kinematics is giving a certain warming
WARNING(OBJ.MCH.KIN6) : C:\Documents and
Settings\marakilo\Desktop\MyRepository7\Application\Examples\GaitUniMiami\Joints
AndDriversOptimized.any(161) : ‘RightAnkle’ : Close to singular position :
Orientation close to Gimbal Lock, i.e., first and third axis of rotation being
parallel
WARNING(OBJ.MCH.KIN6) : C:\Documents and
Settings\marakilo\Desktop\MyRepository7\Body\AAUHuman\Leg\Interface.any(19) :
‘Ankle’ : Close to singular position : Orientation close to Gimbal Lock,
i.e., first and third axis of rotation being parallel
followed by errors
Failed to resolve kinematic constraints (final kin. error = 7.180717E+000)
Constraint no. 0 above error tolerance 0.000001, error = 0.000004. - constr. #0
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.C0C1Jnt.Constraints’
Constraint no. 1 above error tolerance 0.000001, error = 0.000003. - constr. #1
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.C0C1Jnt.Constraints’
Constraint no. 2 above error tolerance 0.000001, error = 0.000006. - constr. #2
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.C0C1Jnt.Constraints’
Constraint no. 4 above error tolerance 0.000001, error = 0.000001. - constr. #4
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.C0C1Jnt.Constraints’
Constraint no. 18 above error tolerance 0.000001, error = 0.000001. - constr. #1
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.L2L3Jnt.Constraints’
Constraint no. 20 above error tolerance 0.000001, error = 0.000001. - constr. #0
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.L1L2Jnt.Constraints’
Constraint no. 23 above error tolerance 0.000001, error = 0.000002. - constr. #0
in ‘Main.HumanModel.BodyModel.Trunk.JointsLumbar.T12L1Jnt.Constraints’
Constraint no. 44 above error tolerance 0.000001, error = 0.039710. - constr. #0
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Ankle.Constraints’
Constraint no. 45 above error tolerance 0.000001, error = 0.029499. - constr. #1
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Ankle.Constraints’
Constraint no. 46 above error tolerance 0.000001, error = 0.030394. - constr. #2
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Ankle.Constraints’
Constraint no. 47 above error tolerance 0.000001, error = 0.000137. - constr. #3
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Ankle.Constraints’
Constraint no. 49 above error tolerance 0.000001, error = 0.000012. - constr. #1
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Knee.Constraints’
Constraint no. 50 above error tolerance 0.000001, error = 0.000001. - constr. #2
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Knee.Constraints’
Constraint no. 52 above error tolerance 0.000001, error = 0.000004. - constr. #4
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Knee.Constraints’
Constraint no. 53 above error tolerance 0.000001, error = 0.000002. - constr. #0
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Hip.Constraints’
Constraint no. 54 above error tolerance 0.000001, error = 0.000013. - constr. #1
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Hip.Constraints’
Constraint no. 55 above error tolerance 0.000001, error = 0.000004. - constr. #2
in ‘Main.HumanModel.BodyModel.Right.Leg.Jnt.Hip.Constraints’
Constraint no. 56 above error tolerance 0.000001, error = 0.047725. - constr. #0
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Ankle.Constraints’
Constraint no. 57 above error tolerance 0.000001, error = 0.011653. - constr. #1
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Ankle.Constraints’
Constraint no. 58 above error tolerance 0.000001, error = 0.029965. - constr. #2
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Ankle.Constraints’
Constraint no. 59 above error tolerance 0.000001, error = 0.002272. - constr. #3
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Ankle.Constraints’
Constraint no. 60 above error tolerance 0.000001, error = 0.000001. - constr. #0
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Knee.Constraints’
Constraint no. 61 above error tolerance 0.000001, error = 0.000012. - constr. #1
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Knee.Constraints’
Constraint no. 62 above error tolerance 0.000001, error = 0.000005. - constr. #2
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Knee.Constraints’
Constraint no. 63 above error tolerance 0.000001, error = 0.000004. - constr. #3
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Knee.Constraints’
Constraint no. 64 above error tolerance 0.000001, error = 0.000006. - constr. #4
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Knee.Constraints’
Constraint no. 65 above error tolerance 0.000001, error = 0.000005. - constr. #0
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Hip.Constraints’
Constraint no. 66 above error tolerance 0.000001, error = 0.000013. - constr. #1
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Hip.Constraints’
Constraint no. 67 above error tolerance 0.000001, error = 0.000010. - constr. #2
in ‘Main.HumanModel.BodyModel.Left.Leg.Jnt.Hip.Constraints’
Constraint no. 71 above error tolerance 0.000001, error = 0.002598. - constr. #0
in ‘Main.OptStudy.OptModel.Markers.LASI.LinDrv’
Constraint no. 72 above error tolerance 0.000001, error = 0.000180. - constr. #1
in ‘Main.OptStudy.OptModel.Markers.LASI.LinDrv’
Constraint no. 73 above error tolerance 0.000001, error = 0.000703. - constr. #2
in ‘Main.OptStudy.OptModel.Markers.LASI.LinDrv’
Constraint no. 77 above error tolerance 0.000001, error = 0.002501. - constr. #0
in ‘Main.OptStudy.OptModel.Markers.RASI.LinDrv’
Constraint no. 78 above error tolerance 0.000001, error = 0.000233. - constr. #1
in ‘Main.OptStudy.OptModel.Markers.RASI.LinDrv’
Constraint no. 79 above error tolerance 0.000001, error = 0.000291. - constr. #2
in ‘Main.OptStudy.OptModel.Markers.RASI.LinDrv’
Constraint no. 83 above error tolerance 0.000001, error = 0.002570. - constr. #0
in ‘Main.OptStudy.OptModel.Markers.LPSI.LinDrv’
Constraint no. 84 above error tolerance 0.000001, error = 0.000161. - constr. #1
in ‘Main.OptStudy.OptModel.Markers.LPSI.LinDrv’
Constraint no. 85 above error tolerance 0.000001, error = 0.000484. - constr. #2
in ‘Main.OptStudy.OptModel.Markers.LPSI.LinDrv’
Constraint no. 89 above error tolerance 0.000001, error = 0.002531. - constr. #0
in ‘Main.OptStudy.OptModel.Markers.RPSI.LinDrv’
Constraint no. 90 above error tolerance 0.000001, error = 0.000172. - constr. #1
in ‘Main.OptStudy.OptModel.Markers.RPSI.LinDrv’
Constraint no. 91 above error tolerance 0.000001, error = 0.000464. - constr. #2
in ‘Main.OptStudy.OptModel.Markers.RPSI.LinDrv’
Constraint no. 95 above error tolerance 0.000001, error = 0.003992. - constr. #0
in ‘Main.OptStudy.OptModel.Markers.LTHI.LinDrv’
Constraint no. 96 above error tolerance 0.000001, error = 0.000147. - constr. #1
in ‘Main.OptStudy.OptModel.Markers.LTHI.LinDrv’
Constraint no. 97 above error tolerance 0.000001, error = 0.000609. - constr. #2
in ‘Main.OptStudy.OptModel.Markers.LTHI.LinDrv’
Constraint no. 101 above error tolerance 0.000001, error = 0.004968. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.LKNE.LinDrv’
Constraint no. 102 above error tolerance 0.000001, error = 0.000042. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.LKNE.LinDrv’
Constraint no. 103 above error tolerance 0.000001, error = 0.000800. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.LKNE.LinDrv’
Constraint no. 107 above error tolerance 0.000001, error = 0.005437. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.LTIB.LinDrv’
Constraint no. 108 above error tolerance 0.000001, error = 0.000131. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.LTIB.LinDrv’
Constraint no. 109 above error tolerance 0.000001, error = 0.000474. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.LTIB.LinDrv’
Constraint no. 113 above error tolerance 0.000001, error = 0.005532. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.LANK.LinDrv’
Constraint no. 114 above error tolerance 0.000001, error = 0.000089. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.LANK.LinDrv’
Constraint no. 115 above error tolerance 0.000001, error = 0.000250. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.LANK.LinDrv’
Constraint no. 119 above error tolerance 0.000001, error = 0.005267. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.LHEE.LinDrv’
Constraint no. 120 above error tolerance 0.000001, error = 0.000102. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.LHEE.LinDrv’
Constraint no. 121 above error tolerance 0.000001, error = 0.000222. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.LHEE.LinDrv’
Constraint no. 125 above error tolerance 0.000001, error = 0.006178. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.LTOE.LinDrv’
Constraint no. 126 above error tolerance 0.000001, error = 0.000019. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.LTOE.LinDrv’
Constraint no. 127 above error tolerance 0.000001, error = 0.000605. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.LTOE.LinDrv’
Constraint no. 131 above error tolerance 0.000001, error = 0.001744. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RTHI.LinDrv’
Constraint no. 132 above error tolerance 0.000001, error = 0.000114. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RTHI.LinDrv’
Constraint no. 133 above error tolerance 0.000001, error = 0.000021. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RTHI.LinDrv’
Constraint no. 137 above error tolerance 0.000001, error = 0.001402. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RKNE.LinDrv’
Constraint no. 138 above error tolerance 0.000001, error = 0.000092. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RKNE.LinDrv’
Constraint no. 139 above error tolerance 0.000001, error = 0.000166. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RKNE.LinDrv’
Constraint no. 143 above error tolerance 0.000001, error = 0.000329. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RTIB.LinDrv’
Constraint no. 144 above error tolerance 0.000001, error = 0.000119. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RTIB.LinDrv’
Constraint no. 145 above error tolerance 0.000001, error = 0.000008. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RTIB.LinDrv’
Constraint no. 149 above error tolerance 0.000001, error = 0.000139. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RANK.LinDrv’
Constraint no. 150 above error tolerance 0.000001, error = 0.000116. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RANK.LinDrv’
Constraint no. 151 above error tolerance 0.000001, error = 0.000041. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RANK.LinDrv’
Constraint no. 155 above error tolerance 0.000001, error = 0.000085. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RHEE.LinDrv’
Constraint no. 156 above error tolerance 0.000001, error = 0.000100. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RHEE.LinDrv’
Constraint no. 157 above error tolerance 0.000001, error = 0.000072. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RHEE.LinDrv’
Constraint no. 161 above error tolerance 0.000001, error = 0.000096. - constr.
#0 in ‘Main.OptStudy.OptModel.Markers.RTOE.LinDrv’
Constraint no. 162 above error tolerance 0.000001, error = 0.000168. - constr.
#1 in ‘Main.OptStudy.OptModel.Markers.RTOE.LinDrv’
Constraint no. 163 above error tolerance 0.000001, error = 0.000044. - constr.
#2 in ‘Main.OptStudy.OptModel.Markers.RTOE.LinDrv’
Constraint no. 164 above error tolerance 0.000001, error = 0.000040. - constr.
#0 in ‘Main.OptStudy.OptModel.ModelEnvironmentConnection.PelvisThoraxDriver’
Constraint no. 165 above error tolerance 0.000001, error = 0.000016. - constr.
#1 in ‘Main.OptStudy.OptModel.ModelEnvironmentConnection.PelvisThoraxDriver’
Constraint no. 168 above error tolerance 0.000001, error = 0.002753. - constr.
#0 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 169 above error tolerance 0.000001, error = 0.000203. - constr.
#1 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 170 above error tolerance 0.000001, error = 0.000655. - constr.
#2 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 171 above error tolerance 0.000001, error = 0.004062. - constr.
#3 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 172 above error tolerance 0.000001, error = 0.001429. - constr.
#4 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 173 above error tolerance 0.000001, error = 0.005785. - constr.
#5 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 174 above error tolerance 0.000001, error = 0.000972. - constr.
#6 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 175 above error tolerance 0.000001, error = 0.002182. - constr.
#7 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 176 above error tolerance 0.000001, error = 0.006154. - constr.
#8 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 177 above error tolerance 0.000001, error = 0.001939. - constr.
#9 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 178 above error tolerance 0.000001, error = 0.036753. - constr.
#10 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 179 above error tolerance 0.000001, error = 0.890504. - constr.
#11 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 180 above error tolerance 0.000001, error = 0.003911. - constr.
#12 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 181 above error tolerance 0.000001, error = 0.002103. - constr.
#13 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 182 above error tolerance 0.000001, error = 0.004982. - constr.
#14 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 183 above error tolerance 0.000001, error = 0.001912. - constr.
#15 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 184 above error tolerance 0.000001, error = 0.001315. - constr.
#16 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
Constraint no. 185 above error tolerance 0.000001, error = 7.180717. - constr.
#17 in
‘Main.OptStudy.OptModel.ModelEnvironmentConnection.JointsAndDrivers.Jntdriver’
and finally giving the following error
ERROR(OBJ.MCH.KIN3) : C:\Documents and
Settings\marakilo\Desktop\MyRepository7\Application\Examples\GaitUniMiami\GaitUn
iMiami.main.any(212) : ‘OptStudy’ : Kinematic analysis failed in time step
16
i can oviously see that there is still something wrong with the ankle when
running this model, and not only the ankle but i can see that the knee joint is
on the ankle also
I have attached a picture for you can see and comment on it.
I also will attach the last version of my model
Could you please check it and let me know about it ?
Regarding the markers, i have posted a new questions about the problem i am
getting and why it is written that way.
Obviously I still have the problem in Gait3D, the problem is coming i think
having the grey markers different that tne blue ones and also have put a new
post on it .
Sorry for taking much time
Regards
----- Original Message ----
From: Michael Skipper Andersen <msandersen60@hotmail.com>
To: anyscript@yahoogroups.com
Sent: Monday, May 12, 2008 4:13:54 PM
Subject: Re: [AnyScript] Re: Markers in Gait3D
Hey Mike,
I will try to answer your questions for this and the other email you sent.
First, the more markers you have on the model the better. In the setup in
GaitUniMiami, the inversion/eversion degree of freedom is very poorly given
by the markers on the toe and heel and I would highly suggest that you add
more markers. When you add a new marker, you have to make changes in three
files: LocalMarkerCoordina teAndSize. any, MarkerTopology. any and
DataForConfigFile. any. The first file is where you specify the local
coordinate of the marker, the second is where you give the marker a name,
link it to the data and specify which segment it attaches to. The third file
is where you make the new marker get written to the model file given to
GaitApplication2. I would suggest you consult page 8 in the manual for
GaitApplication2 for more details.
When you have added more markers to the feet, you do not need to change the
optimization setting for the ankle markers - your optimization problem will
not be ill-posed anymore.
The length of the thigh and shank that you specify is only used as the start
guess and they will be changed during the optimization. If you want to leave
them out of your optimization problem, you can do that in the
DataForConfigFile. any. This is given by the SCALEMAN keyword. This is also
found on page 8 in the manual.
Regarding the two solutions in the ankle that are written out, it is simply
help information in situations where the ankle does not move as you expect.
It is most like due to the markers on the feet not being placed on the model
correctly. For both solutions that are written out, the first number is the
calculated flexion/extension and the second is invesion/eversion at the
first analysis step. In the top of your model file, there is a keyword
called EULERANGLE and the solution you get written out in the
output-euler. txt file is the solution that is closest (in a two-norm sense)
to this specified value at the first time step. For the samples after, it
picks the solution that is closest to the value found in the previous time
step. This is of course done for all the 16 degrees of freedom in the model
that has to do with relative orientations between segments.
Finally, the extrapolation error seen below is because you have specified
your tStart to be after the last time step in your marker data.
I hope this answered your questions else please ask again.
Best regards
Michael
----- Original Message -----
From: “Mike Arakilo” <marakilo@yahoo. com>
To: <anyscript@yahoogrou ps.com>
Sent: Monday, May 12, 2008 3:49 PM
Subject: Re: [AnyScript] Re: Markers in Gait3D
Hi
I am working on data i got myself.
I will have about 60 patients and i need to runi gait3d for each one
depending oh his data
I have made changes to the folder and everything was fine running the old
data presented in the beginning.
Running the model is giving me the following error
Loading Settings Script from : ‘C:\Documents and Settings\marakilo\ Local
Settings\Applicatio n Data\AnyBody Technology\AnyBody. 3.x.x\Settings. anyst
Settings loaded
Loading Main : "C:\Documents and Settings\marakilo\ Desktop\Mike’ s Model
Anybody V3.1\ARep\Aalborg\ Gait3D\AnyGait. main.any"
Scanning…
Parsing…
Constructing model tree…
Linking identifiers. …
Evaluating constants…
Configuring model…
Evaluating model…
ERROR(OBJ1) : C:\Documents and Settings\marakilo\ Desktop\Mike’ s Model
Anybody V3.1\ARep\Aalborg\ Gait3D\MarkerMov er.any(4) : ‘MarkerData’ :
Parameter has an invalid value for this interpolation; extrapolations are
not allowed.
Deleting last loaded model…Done.
Model loading skipped
What is this error and how can i solve it ?
I have attached the model i am using with the new markers data under Gait3d
File in File section of Mike Arakilos Files
Waiting for your reply as soon as possible
Sorry for any inconvenience
Regards
----- Original Message ----
From: AnyBody Support <support@anybodytech .com>
To: anyscript@yahoogrou ps.com
Sent: Friday, May 9, 2008 8:56:33 AM
Subject: [AnyScript] Re: Markers in Gait3D
Hi Mike,
Are you working with new MoCap Data? Or do you just want to modify
the existing one in Gait3D?
I think you saw the model is driven with the text files P1, P2, . You
can’t modify those files to have a higher frequency or longer time,
because you would have to add data in the files (marker coordinates
for the time steps you would have to add) and you don’t have this
data.
But if you have your own MoCap data with the frequency and time
duration you want, you just have to replace the existing data by
yours in the text files (for the markers and the plates). And you can
keep the rest of the application, model, drivers and so on.
Introducing ligaments does not affect the kinematic, so you can
introduce the same files in the body of GaitUniMiami. It should work
without problems. The interface in GaitUniMiami is different because
it uses the GaitApplication2. You might have heard this new
application create automatically drivers for the lower body using the
Marker’s trajectories data. Then the outputs are quite different
because the MoCap data are from different persons.
Best regards,
Sylvain, AnyBody Support.
— In anyscript@yahoogrou ps.com, Mike Arakilo <marakilo@… .> wrote:
>
> Hi again,
>
>
> i got the answer for the last question from you and i understood
what is happening.
>
> Can i change the frequency in gait3d to 100Hz ?
>
> Still have one last question:
> how do I solve the time issue? the time file in gait3d is from 0 to
1.68 with a step of 0.2
> If I have other set of time for example from 0 to 4 sec, will it
fit in gait3d ? Can I change the file ? if yes, what do i need to
change more ?
>
> I have seen in the new repository the GaitUniMiami … In gait3d i
have introduced some changes regarding ligaments around the ankle and
made modification in Seg file and Leg3d.root and introduced Lig file
and LigPar file. Is that feasible in GaitUniMiami ? Shall I introduce
the same files ? and how differnentthe output data is is Gait3d from
GaitUniMiami ? (becuase i saw the interface and it is much different)
>
> Sorry for the so many questions but i really got confused having 2
files working differently
>
> Waiting for your reply
>
> Regards
>
>
>
>
> ----- Original Message ----
> From: AnyBody Support <support@… >
> To: anyscript@yahoogrou ps.com
> Sent: Thursday, May 8, 2008 8:53:12 AM
> Subject: [AnyScript] Re: Markers in Gait3D
>
>
> Hi Mike,
>
> We usually import the data from Vicon System without introducing
any
> offset in the coordinate of the markers. So the origin point in the
> model is the same as the one from Vicon.
>
> The files Force Plate 1, Force Plate 2, Moment Plate 1 and Moment
> Plate 2 refer to the forces and moments measured by the plates.
These
> forces represent the ground reaction and moment.
> The Center of Pressure is the point of application of the ground
> reaction forces and moments, the location of this point is measured
> by the plate.
>
> The sample frequency for this model is 50Hz.
>
> I’m not sure to understand well your last question. The markers
don’t
> give the joint angles, not directly at least. When we use markers
we
> drive the model by linear measure between the markers and the point
> corresponding on the body. That mean we force those points on the
> body to follow the same trajectory as the markers. I think this is
> what you call driving by trajectory. But we don’t drive directly
the
> joint angles when we use markers.
> We use drivers directly for the joint angles for the simple
> movements, when there is no MoCap data.
>
> Best regards,
> Sylvain, AnyBody Support.
>
> — In anyscript@yahoogrou ps.com, Mike Arakilo <marakilo@ .> wrote:
> >
> > Hi
> >
> > I am working on your advice and it is going well but i got some
few
> questions:
> >
> > - What is the Point of Origin of the sample data present in the
> GAIT3D ? Is it same as the point of Origin of the data we get from
> Vicon System ?
> > - In the data present in GAIT3D we have the following files.
Force
> Plate 1 , Force Plate 2 , Moment Plate 1 and Moment Plate 2. What
is
> the meaning of the data present inside these files ? Are they the
> General forces and Moments ? or the Ground Reaction Forces on F1
and
> F2 with Ground Reaction Moments ?
> > -Same question for the Center of Pressure …
> > - What is the sampling frequency of the data ? 100 Hz ?
> >
> > - What is the difference of driving the model by trajectory data
of
> the markers and the angles of the joints given by each markers ?
> >
> > Thanks for your reply
> >
> > Regards
> >
> >
> > ----- Original Message ----
> > From: AnyBody Support <support@ >
> > To: anyscript@yahoogrou ps.com
> > Sent: Monday, May 5, 2008 2:55:49 PM
> > Subject: [AnyScript] Re: Markers in Gait3D
> >
> >
> > Hi,
> >
> > There are 4 markers that are not used: the 4, 6, 11 and 13, (the
12
> is
> > used). This is because there are more markers than needed to
drive
> the
> > model, if we use all the markers the model will be over
constrained
> and
> > the kinematic impossible to solve.
> >
> > There is a line in the main file:
> > #include "…\BRep\ Aalborg\ToolBox\ Markersets
> KitVaughanMarker s.any
> > "
> > This includes the set of markers in the model. There are more set
> of
> > markers available in BRep\Aalborg\ ToolBox\Markerse ts. You can
> include
> > the one you want, and if the existing ones do not correspond to
> your
> > wish you can modify it, add or remove markers or modify the
> position of
> > the existing ones.
> >
> > For example in the KitVaughanMarkers. any file you find those
lines:
> > AnyFolder &Sacrum = .Trunk.SegmentsLumb ar.PelvisSeg;
> > Sacrum={
> > AnyRefNode SacrumMarker = {
> > sRel= .Scale({-0.036250, 0.000000, 0.000000});
> > AnyDrawNode drw={
> > ScaleXYZ={0. 01,.01,.01} ;
> > RGB={0,0,1};
> > };
> > };
> > };
> > This creates a marker on the Pelvis at the given coordinates. You
> cam
> > create similar markers on the segments you want.
> >
> > Best regards,
> > Sylvain, AnyBody Support.
> >
> > — In anyscript@yahoogrou ps.com, “marakilo” <marakilo@ .> wrote:
> > >
> > > Hi,
> > >
> > > I was having a look in folder jointsanddrivers in gait3d folder
> and i
> > > noticed that there is some markers missing in driving the
models
> i.e
> > > markers 4 6 11 12 13.
> > > Is there particular reason why there are not included here ?
> > > If they are included some other place else can i get the link
for
> it ?
> > >
> > > I am looking for a plugingait model so i noticed that there is 1
> > > marker on the back P15, and i need to have one for left and one
> for
> > > right. How can I change them ? More Properly how can i can add a
> > > marker on the body ?
> > >
> > > Thanks for your reply
> > >
> > > Regards
> > >
> >
> >
> >
> >
> >
> ____________ _________ _________ _________ _________ _________ _
> ____________ __
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile… Try it now.
http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
>
> [Non-text portions of this message have been removed]
>
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
[Non-text portions of this message have been removed]
Users of the AnyBody Modeling System help each other create biomechanical
models in the AnyScript language.Yahoo! Groups Links
[Non-text portions of this message have been removed]