Point Names

[FrontPage Include Component] Home
Up

NAVIGATOR: Back - Home > Adi > Services > Support > Manuals > Renderer :

Home

Point Names

Up

Categories

Products
Services
Site Map
Search
About us

Search

Contact us

General info

+1 949 858 4216

Sales & support

+1 619 992 3089

E-mail

Information

Sales

Support

CHECK OUT

[FrontPage Include Component]

APAS Sequence Definition - Point Names 

When your file contains human kinematic data, APAS/Renderer will attempt to fit a model with bone geometry to it. This model assumes that at least the following points are present: 

R.FOOT, R.ANKLE, R.KNEE, R.HIP, L.HIP, L.KNEE, L.ANKLE, L.FOOT, R.WRIST, R.ELBOW, R.SHOULDER, L.SHOULDER, L.ELBOW, L.WRIST, CHIN, FOREHEAD.

You can check which points are present by choosing "Options - Properties" in APAS/Renderer, and selecting "Tracing Options" (like displayed below for the demo file RUNNER1.3D)

 

If any of the expected points are missing, APAS/Renderer cannot build a model, and your data will instead be shown as cylinders. Please pay special attention to the CHIN and FOREHEAD points, since these names were not standard supported in older versions of the APAS Software.

If you believe this to be in error, please verify your sequence definition. With the APAS software joint names / sequence definition can be modified easily to include all of the above point names. One way of doing this is:
bulletStart the APAS Digitize Module
bulletOpen the CF File and choose "View - Sequence".
bulletIn the Enter Sequence Parameters dialog box, choose "Segments".
bulletModify the "Joint Name" for each of the points that do not correspond to the above convention.

Once this CF file has been saved, it can be played in APAS/ Renderer with full body bone geometry.

 

Up

This page was last modified on 12/07/2008 at 22:47 PST. Copyright � 1994 - 2002, all rights reserved, Ariel Dynamics Inc. Please send your comments or feedback to webmaster@arielnet.com or proceed to our feedback form. This page has been accessed many times since Dec 12, 2002. Our privacy policy is here.