Andrew Forsberg: New page:

 We migrated the contact area code to Linux, under $G.  Here's how it works. All the executables are under   /map/gfx0/tools/linux/bin/jspBin  (aka $G/bin/jspBin) and /map/gfx0/tools/...

2009-06-02T18:49:54Z

New page: <pre> We migrated the contact area code to Linux, under $G. Here's how it works. All the executables are under /map/gfx0/tools/linux/bin/jspBin (aka $G/bin/jspBin) and /map/gfx0/tools/...

New page

<pre>
We migrated the contact area code to Linux, under $G.

Here's how it works. All the executables are under
/map/gfx0/tools/linux/bin/jspBin
(aka $G/bin/jspBin)
and /map/gfx0/tools/linux/src/jointViewer

(The source code for /map/gfx0/tools/linux/bin/jspBin/ executables is
located in
/map/gfx0/users/gem/closest/)

Steps to visualize and gather statistics on joint contact areas
---------------------------------------------------------------

A.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** make a data directory (wherever, really) where you'll put the patient specific data. For example, see:

/u/gem/wrists/joint_space/joint_space_orig/

The directory should contain:
a. the bone Geomagic meshes in OIv format, labeled <bone_tag>.iv
b. one animation file for each bone, labeled <bone_tag>_anim.RT
c. an anatomical coordinate system for each bone, labeled <bone_tag>_coord.dat

B.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** edit the batch files "joints_one_linux" and "joints_linux" (located in this directory)
as follows:

1. replace the "set data_directory =" line with

set data_directory = <path to the data directory you made>

2. replace ra2 and ul2 with your bone tags

3. ("joints_one" only) replace x_cube, x_coef and the like, if need be
(x_cube controls the resolution of the distance cube; x_coef extends the
cube on each side by x_coef*100% times the diameter of the object)

4. ("joints" only) replace the "-distMapHorizon 5.0" line with
-distMapHorizon <up to how many mm. you want the contact area to be computed>

5. ("joints" only) replace the "-lineSpacing 1.0" line with
-lineSpacing <how many mm. between contour lines>

C.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linux
-----
** run joints_one

** run joints; the stats will be printed in your data directory in files labeled
<bone_tag>.out

and

<bone_tag>.out.anwar_style_stats

If you want Leor's stats instead, wherer in joints_linux it says
echo "Script for running jointViewer"
/map/gfx0/tools/linux/src/jointViewer/obj/jspJointStats \
-frequency 0.05 \
-distMapHorizon 5.0 \
-lineSpacing 1.0 \
-correctNormals 1 \
-showDistMap 1 \
-showContours 1 \
-showAnimation 1 \
-lineColour 0.3 0.3 0.3 \
-distMapColour 1.0 0.0 0.0 \
2 \
$bone_tag_1 \
$bone_tag_2 \
$data_directory

say instead

/map/gfx0/tools/linux/bin/jspJointStats -frequency 0.05 -distMapHorizon 3.0 -lineSpacing 0.5 -showDistMap 1 -showContours 1 -showAnimation 1 -lineRaisedHt 0.1 -lineColour 0.0 0.5 0.5 -distMapColour 1.0 0.0 0.0 -silent 1 -correctNormals 1 -showCurvature 4 2 \
$bone_tag_1 \
$bone_tag_2 \
$data_directory

Voila. That's all.

If you must run Leor's script for lots of subjects and poses, see
leor_hand_off.txt file in this directory.

Old Linux/Solaris
------------------
Old stuff for Trey is in
/map/gfx1/common/hand/Nurbs_pipeline/for_trey/readme_pipeline
However Solaris libraries are weakened so the Solaris code won't run anymore
</pre>

$G/src/jspBin/trail contact areas.txt - Revision history

Andrew Forsberg: New page:
We migrated the contact area code to Linux, under $G. Here's how it works. All the executables are under /map/gfx0/tools/linux/bin/jspBin (aka $G/bin/jspBin) and /map/gfx0/tools/...