HAS-Motion Software Documentation

This is an old revision of the document!

---

|filename |filename |filename |filename |filename |filename |filename |filename |filename |filename |filename |filename |filename | | |time |origin |origin |origin |rotation |rotation |rotation |rotation |rotation |rotation |rotation |rotation |rotation | | |frame_numbers|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based| | |original |body1 |body1 |body1 |body1 |body1 |body1 |body1 |body1 |body1 |body1 |body1 |body1 | |item|0 |x |y |z |0 |1 |2 |3 |4 |5 |6 |7 |8 | |1 |0.0 |0.564162 |0.002198 |0.086599 |0.648289 |-0.680243 |-0.342039 |0.259806 |-0.224631 |0.939171 |-0.715696 |-0.697719 |0.031104 | |2 |0.032 |0.569361 |0.004844 |0.081942 |0.712005 |-0.652892 |-0.258418 |0.255689 |-0.101686 |0.961396 |-0.653967 |-0.750593 |0.094538 | \\ the origin is at the proximal end of the segment \\ the rotation matrix is represented as | |||0|1|2||| |[r]=|||3|4|5||| | |||6|7|8||| === quaternion based === | |filename |filename |filename |filename |filename |filename |filename |filename | | |time |origin |origin |origin |quaternion |quaternion |quaternion |quaternion | | |frame_numbers|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based|link_model_based| | |original |body1 |body1 |body1 |body1 |body1 |body1 |body1 | |item|0 |x |y |z |0 |1 |2 |3 | |1 |0.0 |0.9782 |0.5654 |-1.0257 |0.298 |-0.6755 |0.2496 |-0.6264 | |2 |0.032 |0.9782 |0.5654 |-1.0257 |0.298 |-0.6755 |0.2496 |-0.6264 | \\ the file format is column based. additional rigid bodies can be added as new columns with the same format. ==== example 1 ==== exporting the position and orientation of segment rft as an origin and quaternion \\ **export_data_to_ascii_file** ! /file_name= /signal_types=frame_numbers+link_model_based+link_model_based /signal_names=time+origin+quaternion /signal_folder=original+rft+rft ! /start_label= ! /end_label= ! /use_point_rate=false ! /normalize_data=false ! /normalize_points=101 ! /export_mean_and_std_dev=false ! /use_p2d_format=false **;** \\ exporting the position and orientation of segment rft as an origin and rotation \\ **export_data_to_ascii_file** ! /file_name= /signal_types=frame_numbers+link_model_based+link_model_based /signal_names=time+origin+rotation /signal_folder=original+rft+rft ! /start_label= ! /end_label= ! /use_point_rate=false ! /normalize_data=false ! /normalize_points=101 ! /export_mean_and_std_dev=false ! /use_p2d_format=false **;** ==== example 2 ==== open the text file that was just created. select file -> open. select the viewer for .txt files. select "aurora.txt". mergeaurorafiles4.gif the file will be loaded into memory. the aurora file contains position and rotation data for a rigid body. it will appear in visual3d as linkmodel_based items containing the origin (3 components) quaternion (4 components). mergeaurorafiles5.gif visual3d typically works with motion capture markers, so to maximize your ability to work with this data, you can create a set of 3 targets per rigid body using the following command. **create_targets_for_linkmodelbased_rotations** /signal_folders=port_01+port_02+port_03+port_04 **;** targets for each rigid body should appear in the data tree. it is possible to save this data to a c3d formatted file, but the link model data (e.g. the original translation and quaternion will be lost, so it is recommended that you save this data to a cmo file. mergeaurorafiles7.gif if you need a static trial for modeling the data, you can save the first frame of data to a c3d file. mergeaurorafiles8.gif }}}}}}