HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » other » AMASS » tutorials » Getting Started
other:amass:tutorials:getting_started

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
other:amass:tutorials:getting_started [2024/06/19 12:45] – sgrangerother:amass:tutorials:getting_started [2024/07/17 15:44] (current) – created sgranger
Line 1: Line 1:
-{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{===== overview =====+====== Getting Started ======
  
-here is how a new user to amass/capture2d would use the system.+==== Overview ====
  
-  - first, amass is installed, and a default data directory for storing motion capture files is created. if an existing l-frame reference file and marker name file exist, then they are copied to that directory. finally a project file is created (or modified). the project file will have blank values for the calibration, tracking, and identification sections initially. this is described on the [[other:amass:tutorials:installation_|installation]] wiki page.+Here is how a new user to AMASS/Capture2D would use the system.
  
-  - once the **amass wand** (pictured below) arrives in the mail, it is unfolded and the calibration process can start. note: make sure the little black dots on each marker are pointing down, towards the handle. to calibrate a volume, you get all the cameras plugged in and start capture2d. you then **connect** to the cameras and set the duration to 20 seconds (or more if lots of cameras are used). finally, click **start recording** and wave the wand all around the capture volume - high, low, spinning, waving, and near the floor.\\ +  - First, AMASS is installed, and a default data directory for storing motion capture files is created. If an existing L-Frame reference file and marker name file exist, then they are copied to that directory. Finally a project file is created (or modified). The project file will have blank values for the calibration, tracking, and identification sections initially. This is described on the [[Other:AMASS:Tutorials:Installation_|Installation]] wiki page.
-wand2.jpg +
-  - save the .cen recording (giving it a meaningful name), and in amass, click the **refresh** button so that the new file shows up. then click the **calibrate** button. if it doesn't work, collect new data and try again until is does. you simply can't proceed until you have a calibrated volume. there are also troubleshooting pages in the wiki if you have problems. amass automatically recognizes the markers on the wand and can linearize the camera lenses, calculates a residual, and calibrates the entire motion capture volume. +
-  - once the calibration works, click the **apply** button in the calibration report screen.+
  
-  - now you can go back to capture2d and collect subject data for analysis. the tutorial illustrates how to process that data using the track and identify buttons in amass.+  - Once the **AMASS Wand** (pictured below) arrives in the mail, it is unfolded and the calibration process can start. NOTE: make sure the little black dots on each marker are pointing down, towards the handle. To calibrate a volume, you get all the cameras plugged in and start Capture2D. You then **Connect** to the cameras and set the duration to 20 seconds (or more if lots of cameras are used). Finally, click **Start Recording** and wave the wand all around the capture volume - high, low, spinning, waving, and near the floor.\\ 
 +{{:Wand2.jpg}} 
 +  - Save the .cen recording (giving it a meaningful name), and in AMASS, click the **Refresh** button so that the new file shows up. Then click the **Calibrate** button. If it doesn't work, collect new data and try again until is does. You simply can't proceed until you have a calibrated volume. There are also troubleshooting pages in the wiki if you have problems. AMASS automatically recognizes the markers on the wand and can linearize the camera lenses, calculates a residual, and calibrates the entire motion capture volume. 
 +  - Once the calibration works, click the **Apply** button in the Calibration report screen.
  
-===== sample data =====+  - Now you can go back to Capture2D and collect subject data for analysis. The tutorial illustrates how to process that data using the track and Identify buttons in AMASS.
  
-get the [[[https://www.has-motion.com/download/amass/amass_sample.zip|amass sample files]]] here.+==== Sample Data ====
  
-===== getting started with amass =====+Get the [[[https://www.has-motion.com/download/AMASS/AMASS_Sample.zip|AMASS Sample Files]]] here.
  
-this section provides a brief tutorial of how to use amass and the steps necessary to generate 3d data from motion capture data files. it presumes that amass is already installed.+==== Getting Started with AMASS ==== 
 + 
 +This section provides a brief tutorial of how to use AMASS and the steps necessary to generate 3D data from motion capture data files. It presumes that AMASS is already installed.
  
 \\ \\
-the tutorial covers the usual steps followed to process data:+The tutorial covers the usual steps followed to process data:
  
-  - set up the project files +  - Set up the Project Files 
-  - calibrate the 3d volume +  - Calibrate the 3D volume 
-  - track the 3d movement of the markers from the multiple camera views +  - Track the 3D movement of the markers from the multiple camera views 
-  - identify the markers (e.g. give them meaningful names) +  - Identify the markers (e.g. give them meaningful names) 
-  - write the results to a c3d file.+  - Write the results to a c3d file.
  
 \\ \\
-the following assumes that all the sample files were installed in the: “c:\amass_sample” directory. note: if the sample files are copied or unzipped elsewhere, then be aware that the project setup file and the main screen folder selection will need to be modified.+The following assumes that all the sample files were installed in the: “C:\AMASS_Sample” directory. Note: If the sample files are copied or unzipped elsewhere, then be aware that the Project setup file and the main screen folder selection will need to be modified.
  
 \\ \\
-click on the amass program icon in the desktop to start the amass shell program.+Click on the AMASS program icon in the desktop to start the AMASS shell program.
  
-//note: amass starts and loads the last project it was working on. if there was no previous project, or it was moved, then the following screen appears.//+//Note: AMASS starts and loads the last project it was working on. If there was no previous project, or it was moved, then the following screen appears.//
  
-a1.png+{{:a1.png}}
  
-click “open an existing project” and select the sample project file (project.prj) from the files you just installed to begin.+Click “Open an Existing Project” and select the sample project file (project.prj) from the files you just installed to begin.
  
-===== step 1: project control =====+==== Step 1: Project Control ====
  
-if the project name is not project, click on **open…** and navigate to the samples folder. this section duplicates much of the [[other:amass:tutorials:installation_|installation]] information, but goes into more detail about the options.+If the Project name is not Project, click on **Open…** and navigate to the samples folder. This section duplicates much of the [[Other:AMASS:Tutorials:Installation_|installation]] information, but goes into more detail about the options.
  
-make sure the folder box in the bottom left of the screen points to the sample data.+Make sure the Folder box in the bottom left of the screen points to the sample data.
  
-a2.png+{{:a2.png}}
  
-in the project section click on the **edit** button and verify that the parameters have the following entries:+In the Project Section click on the **Edit** button and verify that the parameters have the following entries:
  
-==== input tab ====+=== Input Tab ===
  
-this tab set amass input data format options. no need to change anything.+This tab set AMASS input data format options. No need to change anything.
  
-  * input system = capture (multiple input files formats are supported. capture2d is the program used for naturalpoint cameras. other input sources are supported.) +  * Input system = Capture (multiple input files formats are supported. Capture2D is the program used for NaturalPoint cameras. Other input sources are supported.) 
-  * viewcen = checked (to view centroids meaning to actually see the targets/markers)+  * ViewCen = Checked (to view centroids meaning to actually see the targets/markers)
  
-a3.png+{{:a3.png}}
  
-==== calibrate tab ====+=== Calibrate Tab ===
  
-this tab set amass volume calibration options.+This tab set AMASS volume calibration options.
  
-  * cameras to use = all checked (this option allow you to disable input from specific cameras) +  * Cameras to use = All checked (This option allow you to disable input from specific cameras) 
-  * reference marker file = c:\amass_sample\l_frame_1.ref.+  * Reference marker file = C:\AMASS_Sample\L_Frame_1.ref.
  
-assuming the file location changed, click **browse…** and navigate to select the l-frame file. this file identifies your l-frame and where the markers are located on it. the sample is for a naturalpoint frame.+Assuming the file location changed, click **Browse…** and navigate to select the L-Frame file. This file identifies your L-Frame and where the markers are located on it. The sample is for a NaturalPoint frame.
  
-a4.png+{{:a4.png}}
  
-==== track tab ====+=== Track Tab ===
  
-this tab set amass target tracking options.+This tab set AMASS target tracking options.
  
-  * calibration file = **delete this entry** for the tutorial. if not blank, click browse… and then cancel.+  * Calibration file = **Delete this entry** for the tutorial. If not blank, click Browse… and then Cancel.
  
-this is not critical, since when you create a new calibration file (part of the tutorial) you click an "apply" button that will overwrite whatever is here.+This is not critical, since when you create a new calibration file (part of the tutorial) you click an "Apply" button that will overwrite whatever is here.
  
-a5.png+{{:a5.png}}
  
-==== identify tab ====+=== Identify Tab ===
  
-this tab set amass target naming and identification options. no need to change anything unless the file location changed.+This tab set AMASS target naming and identification options. No need to change anything unless the file location changed.
  
-  * marker file = marker.mkr. if it is something else, click browse… and then navigate to select that file. +  * Marker file = marker.mkr. If it is something else, click Browse… and then navigate to select that file. 
-  * link file = can be blank. it is unused now, but will be needed for the automatic tracking feature (coming soon)+  * Link File = can be blank. It is unused now, but will be needed for the automatic tracking feature (coming soon)
  
-a6.png+{{:a6.png}}
  
 \\ \\
-click **ok** to close the amass parameters window.+Click **OK** to close the AMASS Parameters window.
  
-===== step 2: collecting data =====+==== Step 2: Collecting Data ====
  
-this part assumes you already set up your camera system. clicking the “capture” button in amass launches the capture2d program to connect to naturalpoint cameras and perform a data collection. use the advanced button to set non-traditional settings on the cameras. the 3d view tab in newer versions of capture2d are for force plate data.+This part assumes you already set up your camera system. Clicking the “Capture” button in AMASS launches the Capture2D program to connect to NaturalPoint cameras and perform a data collection. Use the Advanced button to set non-traditional settings on the cameras. The 3D View tab in newer versions of Capture2D are for force plate data.
  
 \\ \\
-in capture2d, simplistically, you:+In Capture2D, simplistically, you:
  
-  - click the connect button, +  - Click the Connect button, 
-  - set a duration, and then +  - Set a duration, and then 
-  - click the start recording button.+  - Click the Start Recording button.
  
-the result is a file of target centroid data (.cen format) from each camera.+The result is a file of target centroid data (.cen format) from each camera.
  
 \\ \\
-the sample data set provides 3 data collections that would be typical of any biomechanics oriented motion capture effort:+The sample data set provides 3 data collections that would be typical of any biomechanics oriented motion capture effort:
  
-  * calibration_trial.cen = the calibration trial where the wand is waved around the volume to enable calibration. inadequate wand coverage results in failed calibration, and no further data can be processed. proper volume calibration is essential to amass. +  * Calibration_trial.cen = The calibration trial where the wand is waved around the volume to enable calibration. Inadequate wand coverage results in failed calibration, and no further data can be processed. Proper volume calibration is essential to AMASS. 
-  * static-001.cen = the static trial of the subject, used to build the biomechanical model in visual3d. +  * Static-001.cen = The static trial of the subject, used to build the biomechanical model in Visual3D. 
-  * movement-001.cen = a movement trial of a subject walking around – not useful for much of any kind on analysis though. it was collected just to test cameras.+  * Movement-001.cen = A movement trial of a subject walking around – not useful for much of any kind on analysis though. It was collected just to test cameras.
  
-note: if systems other than naturalpoint are used, a different capture program is needed.+Note: If systems other than NaturalPoint are used, a different capture program is needed.
  
-a7.png+{{:a7.png}}
  
-===== step 3: calibrating the volume =====+==== Step 3: Calibrating the Volume ====
  
-amass requires the motion capture volume be properly calibrated before any processing can be done. if someone bumps a camera or anything moves or changes, your volume must be re-calibrated.+AMASS requires the motion capture volume be properly calibrated before ANY processing can be done. If someone bumps a camera or anything moves or changes, your volume must be re-calibrated.
  
-using the supplied data files we will illustrate how to calibrate a volume.+Using the supplied data files we will illustrate how to calibrate a volume.
  
 \\ \\
-step 1 is to collect data in capture2d of the wand moving all around the volume. the sample file calibration_trial.cen is provided so that you see what your own result should look like.+Step 1 is to collect data in Capture2D of the wand moving all around the volume. The sample file Calibration_trial.cen is provided so that you see what your own result should look like.
  
-//note: when moving the amass wand around, you want to move it alot - spin it, wave it, get a marker captured in every bit of the lab space as possible and by every camera, and don't forget to wave and spin it right next to the floor too.//+//Note: When moving the AMASS Wand around, you want to move it alot - spin it, wave it, get a marker captured in every bit of the lab space as possible and by every camera, and don't forget to wave and spin it right next to the floor too.//
  
 \\ \\
-once the data is available, like our sample calibration file, here is how it is processed:+Once the data is available, like our sample calibration file, here is how it is processed:
  
-a8.png+{{:a8.png}}
  
-  - first, make sure the **cen** radio button at the bottom of the amass window is selected. +  - First, make sure the **CEN** radio button at the bottom of the AMASS window is selected. 
-  - highlight the calibration_trial.cen file at the top of the screen. (the project must be set up properly to see this.) normally you use your own collected data for this. +  - Highlight the calibration_trial.cen file at the top of the screen. (The project must be set up properly to see this.) Normally you use your own collected data for this. 
-  - click the **calibrate** button in amass to create a calibrated volume file. a **progress bar** will indicate that the calibration/linearization process is taking place, and then the **calibration report** screen will pop up. this resulting calibration file has the .cal extension and contains camera linearization data (to compensate for lens spherical distortions) and volume location. +  - Click the **Calibrate** button in AMASS to create a calibrated volume file. A **progress bar** will indicate that the calibration/linearization process is taking place, and then the **Calibration Report** screen will pop up. This resulting calibration file has the .cal extension and contains camera linearization data (to compensate for lens spherical distortions) and volume location. 
-  - click the **apply** button to tell amass to use these results in tracking and identification processes. it will write the file name into the project file.+  - Click the **APPLY** button to tell AMASS to use these results in tracking and identification processes. It will write the file name into the project file.
  
 \\ \\
-it is useful to review the data at the top of the calibration report. the top part of the window presents an overview of the calibration accuracy and consistency. for example, in this sample we find the point residuals to be 0.594mm, which means that the targets were tracked with sub-millimeter accuracy.+It is useful to review the data at the top of the Calibration Report. The top part of the window presents an overview of the calibration accuracy and consistency. For example, in this sample we find the point residuals to be 0.594mm, which means that the targets were tracked with sub-millimeter accuracy.
  
 \\ \\
-the graphics window indicates the image area of each camera calibrated. the grid also indicates the lens distortions (i.e. linearization map) that were corrected by the calibration. clicking on a different camera in the camera list box on the right displays the calibration grid for that camera. the reference point information refers to the static markers that are used by the calibration to translate all output to the user’s preferred coordinate system.+The graphics window indicates the image area of each camera calibrated. The grid also indicates the lens distortions (i.e. linearization map) that were corrected by the calibration. Clicking on a different camera in the camera list box on the right displays the calibration grid for that camera. The reference point information refers to the static markers that are used by the calibration to translate all output to the user’s preferred coordinate system.
  
 \\ \\
-you should be able to get considerably better results in your own lab. this sample data was not collected carefully, and the cameras were simply set up on tripods in a random fashion as a system test.+You should be able to get considerably better results in your own lab. This sample data was not collected carefully, and the cameras were simply set up on tripods in a random fashion as a system test.
  
-a10.png+{{:a10.png}}
  
 \\ \\
  
  
-  * optional step -- to view any centroid file (to validate that it looks ok), click the viewcen button to launch the centroid viewer window. you can click each of the cameras views (right panel) and play the data (bottom controls) from each camera in the viewer.+  * OPTIONAL step -- To view ANY centroid file (to validate that it looks OK), click the ViewCen button to launch the Centroid Viewer window. You can click each of the cameras views (right panel) and play the data (bottom controls) from each camera in the viewer.
  
-a9.png+{{:a9.png}}
  
-if open, close the viewcen window.+If open, CLOSE the ViewCen window.
  
 \\ \\
-//note: since amass automatically recognizes the wand, the l-frame can also be part of the calibration collection process so that an analysis program like visual3d will know where the origin of the lab coordinate system is located, and where the lab axis are.// you can also put markers on a force plate corner, or make you own l-frame - just modify the .ref file to let it know where the markers are.+//Note: Since AMASS automatically recognizes the wand, the L-Frame can also be part of the calibration collection process so that an analysis program like Visual3D will know where the origin of the lab coordinate system is located, and where the lab axis are.// You can also put markers on a force plate corner, or make you own L-Frame - just modify the .ref file to let it know where the markers are.
  
 \\ \\
-extra information:+EXTRA Information:
  
-a11.png+{{:a11.png}}
  
-to view the calibration report screen at any time:+To view the calibration report screen at any time:
  
-  - select the **cal** radio button at the bottom +  - Select the **CAL** radio button at the bottom 
-  - highlight the calibration file name +  - Highlight the calibration file name 
-  - click the **viewlin** button+  - Click the **ViewLin** button
  
-===== step 4: tracking targets =====+==== Step 4: Tracking Targets ====
  
-once the volume has been calibrated, amass will then allow the processing of data collected in that volume. for this example, a static trial and a movement trial were already collected, and now we can process the data.+Once the volume has been calibrated, AMASS will then allow the processing of data collected in that volume. For this example, a Static trial and a Movement trial were already collected, and now we can process the data.
  
 \\ \\
-the next step is to identify the 3d targets as they move from frame to frame by tracking their individual trajectories and assigning correlated trajectories between camera views to 3d marker segments. to create the tracking data of the static trial:+The next step is to identify the 3D targets as they move from frame to frame by tracking their individual trajectories and assigning correlated trajectories between camera views to 3D marker segments. To create the tracking data of the Static trial:
  
-  - click the **cen** radio button at the bottom of the screen +  - Click the **CEN** radio button at the bottom of the screen 
-  - highlight the static-001.cen file +  - Highlight the Static-001.cen file 
-  - click the **track** button (we skip calibrate button since that is done.)+  - Click the **Track** button (We skip calibrate button since that is done.)
  
-a12.png+{{:a12.png}}
  
-the result of the tracking process is a 3d marker segments file. this is documented on the wiki, but as a rule of thumb, the more long lines across the screen, the better. each segment track is given a different color.+The result of the tracking process is a 3D marker segments file. This is documented on the wiki, but as a rule of thumb, the more long lines across the screen, the better. Each segment track is given a different color.
  
 \\ \\
-this graph shows the number and length of the 3d segments of marker trajectories that were reconstructed from the camera data over the entire data capture time. each horizontal line indicates a separate segment which is continuous over a number of frames. the marker data at this point are unidentified, i.e. the program does not know which segment belongs to which marker.+This graph shows the number and length of the 3D segments of marker trajectories that were reconstructed from the camera data over the entire data capture time. Each horizontal line indicates a separate segment which is continuous over a number of frames. The marker data at this point are unidentified, i.e. the program does not know which segment belongs to which marker.
  
-  * click **close** to exit viewseg.+  * Click **Close** to exit ViewSeg.
  
 \\ \\
-after you close the viewseg display the newly created .seg file is saved and automatically selected in the amass window. also, the identify and viewlin functions become enabled. we can now proceed to identify the specific markers in the selected .seg file.+After you close the ViewSeg display the newly created .seg file is saved and automatically selected in the AMASS window. Also, the Identify and ViewLin functions become enabled. We can now proceed to identify the specific markers in the selected .seg file.
  
-a13.png+{{:a13.png}}
  
 \\ \\
-note: this screen can be re-displayed at any time by selecting the **seg** radio button, highlighting the seg file, and clicking the viewseg button.+Note: This screen can be re-displayed at any time by selecting the **SEG** radio button, highlighting the seg file, and clicking the ViewSeg button.
  
 \\ \\
  
  
-===== step 5: identify targets =====+==== Step 5: Identify Targets ====
  
-once segment tracking is complete, amass enables the identify button. amass should now have the seg radio button selected and the static-001.seg file should be highlighted.+Once segment tracking is complete, AMASS enables the Identify button. AMASS should now have the SEG radio button selected and the Static-001.seg file should be highlighted.
  
 \\ \\
  
  
-  * click the **identify** button in amass.+  * Click the **Identify** button in AMASS.
  
-the main area shows the 3d marker locations at the first frame. at this point the markers are not identified. that is our next task.+The main area shows the 3D marker locations at the first frame. At this point the markers are not identified. That is our next task.
  
 \\ \\
-**note: we can manipulate the opengl view by dragging the left mouse button to pan and tilt, right mouse button to translate, and both mouse buttons to zoom. holding the mouse cursor over a marker displays its arbitrarily assigned segment number. you can move to a different frame number by using the slider at the bottom, or auto play by clicking one of the double arrow buttons.**+**Note: We can manipulate the OpenGL view by dragging the left mouse button to pan and tilt, right mouse button to translate, and both mouse buttons to zoom. Holding the mouse cursor over a marker displays its arbitrarily assigned segment number. You can move to a different frame number by using the slider at the bottom, or auto play by clicking one of the double arrow buttons.**
  
 \\ \\
-clicking and holding both mouse buttons, zoom out until all the markers can be seen (as pictured below). the view is from camera1, but the subject was facing a different camera, and only the lower body had markers. the top group of 4 markers is the pelvis, and the groups at the bottom are the subject’s feet. thighs, knees, and shanks were also marked.+Clicking and holding both mouse buttons, zoom out until all the markers can be seen (as pictured below). The view is from Camera1, but the subject was facing a different camera, and only the lower body had markers. The top group of 4 markers is the pelvis, and the groups at the bottom are the subject’s feet. Thighs, knees, and shanks were also marked.
  
 \\ \\
-//double-clicking a marker (or reflection) will "hide" it. click the unhide button to show it again.//+//Double-clicking a marker (or reflection) will "hide" it. Click the UnHide button to show it again.//
  
 \\ \\
-now we will identify the markers. there are two methods for assigning marker identifications to the segments. the simplest approach is a one-to-one marking.+Now we will identify the markers. There are two methods for assigning marker identifications to the segments. The simplest approach is a one-to-one marking.
  
-a14.png+{{:a14.png}}
  
 \\ \\
  
  
-  - using the pan, tilt, and zoom capabilities reposition the subject to be facing us in the viewer, and tilt them down a bit to clearly separate the pelvis markers and feet. +  - Using the pan, tilt, and zoom capabilities reposition the subject to be facing us in the viewer, and tilt them down a bit to clearly separate the pelvis markers and feet. 
-  - move the slider to frame 81 – the right knee marker will suddenly appear. +  - Move the slider to frame 81 – the right knee marker will suddenly appear. 
-  - click the r-asis label in the upper right panel. the markers will also highlight with red circles. red means that they do not have names associated with them yet. +  - Click the R-ASIS label in the upper right panel. The markers will also highlight with red circles. Red means that they do not have names associated with them yet. 
-  - put the mouse over the right asis marker #1. marker numbers appear when the mouse pointer hovers over them. +  - Put the mouse over the right ASIS marker #1. Marker numbers appear when the mouse pointer hovers over them. 
-  - click the marker and it will get assigned. the marker will turn yellow, and the name will appear when the mouse hovers over it. note: double-clicking on the marker will clear an assignment (in case you mislabel one). beware – double-clicking an unassigned marker hides it (for spurious reflections). the unhide button on the left can bring it back.+  - Click the marker and it will get assigned. The marker will turn yellow, and the name will appear when the mouse hovers over it. NOTE: double-clicking on the marker will clear an assignment (in case you mislabel one). Beware – double-clicking an unassigned marker hides it (for spurious reflections). The Unhide button on the left can bring it back.
  
-a15.png+{{:a15.png}}
  
-now, to speed up the process, we can label a group of markers at once.+Now, to speed up the process, we can label a group of markers at once.
  
-  * click on the l_asis label, and holding down the mouse button, drag the mouse down over the next 3 pelvis marker labels. (note: several groups can be created at once this way too.)+  * Click on the L_ASIS label, and holding down the mouse button, drag the mouse down over the next 3 pelvis marker labels. (Note: Several groups can be created at once this way too.)
  
-  * click on the remaining markers of the pelvis, in descending order in the list.+  * Click on the remaining markers of the pelvis, in descending order in the list.
  
-notice the bottom of the window. each marker gets a line across the screen. gaps in the line indicate drop outs, occlusions, or identification problems. once the ignition marker identifications are done, we need to play through the file identifying the gaps and fixing any marker errors.+Notice the bottom of the window. Each marker gets a line across the screen. Gaps in the line indicate drop outs, occlusions, or identification problems. Once the ignition marker identifications are done, we need to play through the file identifying the gaps and fixing any marker errors.
  
 \\ \\
-note: automatic marker identification is possible (and in the next release), but it still requires a setup process and verification step. automatic identification is a tremendous time saving option, but not a replacement for data validation.+NOTE: Automatic marker identification is possible (and in the next release), but it still requires a setup process and verification step. Automatic identification is a tremendous time saving option, but not a replacement for data validation.
  
-a16.png+{{:a16.png}}
  
 \\ \\
-now we will use the more traditional (and faster) approach that amass has for labeling.+Now we will use the more traditional (and faster) approach that AMASS has for labeling.
  
-  * click in the area to the left of the red bar (the frame indicator) – at the bottom pane of the screen. amass will highlight the next unidentified marker like a blue star, and simultaneously highlight the marker names on the right.+  * Click in the area to the left of the red bar (the frame indicator) – at the bottom pane of the screen. AMASS will highlight the next unidentified marker like a blue star, and simultaneously highlight the marker names on the right.
  
-a17.png+{{:a17.png}}
  
-  * click the r_thigh label on the right, and the program will assign the name and automatically move to the next marker. (if it does not move automatically, just click again in to the left of the frame indicator. this happens because when you click there, it moves the frame too, and the “next” markers may already be identified.)+  * Click the R_THIGH label on the right, and the program will assign the name and automatically move to the next marker. (If it does not move automatically, just click again in to the left of the frame indicator. This happens because when you click there, it moves the frame too, and the “next” markers may already be identified.)
  
-  * label all the markers as shown below. if the program chooses a marker that does not get a name (reflections, etc.) then you may bypass it by either right clicking anywhere in the main viewing area or left clicking to the right of the frame indicator again.+  * Label all the markers as shown below. If the program chooses a marker that does not get a name (reflections, etc.) then you may bypass it by either right clicking anywhere in the main viewing area or left clicking to the right of the frame indicator again.
  
-//note: you will only see the label names when the mouse is over the marker - we photoshopped them in here...//+//NOTE: You will only see the label names when the mouse is over the marker - we PhotoShopped them in here...//
  
-a18.png+{{:a18.png}}
  
-finally, we need to enhance and validate the result.+Finally, we need to enhance and validate the result.
  
-using the slider at the bottom, move through the file looking for unidentified markers and label them. you can also click in the bottom window to jump to frames. we are looking to fill in the gaps in the lines in the bottom viewer (i.e. the continuity display). for example – frame 222 has unidentified markers.+Using the slider at the bottom, move through the file looking for unidentified markers and label them. You can also click in the bottom window to jump to frames. We are looking to fill in the gaps in the lines in the bottom viewer (i.e. the continuity display). For example – frame 222 has unidentified markers.
  
 \\ \\
-once you have finished labeling the completed 3d data may now be written to a .c3d file by clicking on the write c3d button in the left margin.+Once you have finished labeling the completed 3D data may now be written to a .c3d file by clicking on the Write C3D button in the left margin.
  
 \\ \\
-save the identifications you have done by writing them back into the seg file by clicking the save id’s button on the right. warning!! all of the label identifications will be lost if you do not save them. however, it is the c3d file that needs them more than the seg file. chances are you will not ever need to relabel a file once written to c3d format.+Save the identifications you have done by writing them back into the seg file by clicking the Save ID’s button on the right. WARNING!! All of the label identifications will be LOST if you do not save them. However, it is the c3d file that needs them more than the seg file. Chances are you will not ever need to relabel a file once written to c3d format.
  
-===== summary =====+==== Summary ====
  
-that finishes the tutorial. once a volume is calibrated, markers can be tracked and identified, and then the result saved in c3d format for later analysis.+That finishes the tutorial. Once a volume is calibrated, markers can be tracked and identified, and then the result saved in c3d format for later analysis.
  
 \\ \\
-the movement-001.seg file has some marker identifications saved already. this file is provided as a sample of any movement data where marker segments are not constant. it is left as an exercise for the user to finish the labeling and write a c3d file.+The Movement-001.seg file has some marker identifications saved already. This file is provided as a sample of any movement data where marker segments are not constant. It is left as an exercise for the user to finish the labeling and write a c3d file.
  
-the next version of amass will have the automatic tracking feature enabled. to use that feature, the markers will need to be linked together in either a mesh or as a string of markers (or combination of both). the marker linkages can be saved and re-used as a template, just like the files with marker names.+The next version of AMASS will have the automatic tracking feature enabled. To use that feature, the markers will need to be linked together in either a mesh or as a string of markers (or combination of both). The marker linkages can be saved and re-used as a template, just like the files with marker names.
  
 \\ \\
-good luck!+Good luck!
  
 \\ \\
-**c-motion, inc.**+**C-Motion, Inc.** 
  
  
-}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}} 
other/amass/tutorials/getting_started.1718801137.txt.gz · Last modified: 2024/06/19 12:45 by sgranger