HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » other » AMASS » documentation » View3D
other:amass:documentation:view3d

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:documentation:view3d [2024/06/19 13:53] – created sgrangerother:amass:documentation:view3d [2024/07/17 15:44] (current) – created sgranger
Line 1: Line 1:
 +====== View3D ======
 +
 **The current version of View3D can only stream data from a //.cen// file. A version to display reconstructed and identified marker data from the //Capture2D// program will be available soon.** **The current version of View3D can only stream data from a //.cen// file. A version to display reconstructed and identified marker data from the //Capture2D// program will be available soon.**
  
Line 5: Line 7:
 Before View3D can produce useful results the camera system must be calibrated, and all necessary tracking parameters must be specified correctly. A valid link file must also be specified in the Identify parameters if you want the program to identify markers. Before View3D can produce useful results the camera system must be calibrated, and all necessary tracking parameters must be specified correctly. A valid link file must also be specified in the Identify parameters if you want the program to identify markers.
  
-===== Parameters =====+==== Parameters ====
  
 The //**View3D**// function uses all of the tracking parameters except those in the **Track only** group. In the **View3D only** group are three additional parameters. The //**View3D**// function uses all of the tracking parameters except those in the **Track only** group. In the **View3D only** group are three additional parameters.
  
-{{track_params.jpg}}+{{:track_params.jpg}}
  
-==== Output delay ====+=== Output delay ===
  
 During tracking the //**Track**// program buffers five frames of data and uses these frames to project where the location of each marker is expected to be in the sixth frame. In normal tracking the first frame in the buffer is output only after the fifth frame is read in resulting in a delay of five frames between input and output of frame data. Although this delay is useful for producing cleaner segments, it may not be desirable in real-time applications. The //**Output delay**// provides user control over the number of frames to delay the output. The entered value must be between 0 and 5 frames, with zero providing the least delay at a possible cost of more breaks in the output trajectories. During tracking the //**Track**// program buffers five frames of data and uses these frames to project where the location of each marker is expected to be in the sixth frame. In normal tracking the first frame in the buffer is output only after the fifth frame is read in resulting in a delay of five frames between input and output of frame data. Although this delay is useful for producing cleaner segments, it may not be desirable in real-time applications. The //**Output delay**// provides user control over the number of frames to delay the output. The entered value must be between 0 and 5 frames, with zero providing the least delay at a possible cost of more breaks in the output trajectories.
  
-==== C3D Output ====+=== C3D Output ===
  
 If this box is checked, //**View3D**// will also write the generated 3D data to a .//c3d// file which can later be analyzed for completeness and accuracy of the tracked and identified data. The data will __always__ be written to the file named //View3D.c3d// in the project **c3d** directory. If this box is checked, //**View3D**// will also write the generated 3D data to a .//c3d// file which can later be analyzed for completeness and accuracy of the tracked and identified data. The data will __always__ be written to the file named //View3D.c3d// in the project **c3d** directory.
  
-===== Data input =====+==== Data input ====
  
 Currently a camera data stream is not yet available from //**Capture2D**//, but the user can select a .//cen// file from the **Input file** list and then click **View3D** to simulate streamed capture data. Currently a camera data stream is not yet available from //**Capture2D**//, but the user can select a .//cen// file from the **Input file** list and then click **View3D** to simulate streamed capture data.
  
-===== View3D display =====+==== View3D display ====
  
-{{view3d.jpg}}+{{:view3d.jpg}}
  
 The display shows all identified and unidentified markers, with links. At the bottom left of the main view are two numbers; the frame number that is being displayed, and the accumulated number of frames which have been missed because of processing or other delays. The view may be rotated and zoomed by the standard mouse actions. The display shows all identified and unidentified markers, with links. At the bottom left of the main view are two numbers; the frame number that is being displayed, and the accumulated number of frames which have been missed because of processing or other delays. The view may be rotated and zoomed by the standard mouse actions.
Line 33: Line 35:
 **Left + Right buttons drag;** translates the image. **Left + Right buttons drag;** translates the image.
 **Right button drag vertical;** zooms the image. **Right button drag vertical;** zooms the image.
-===== Control buttons =====+==== Control buttons ====
  
   * ****Pause**** This button pauses the display. The input stream is not paused except for a .cen file input. The button will change to **Continue** to allow the continuation of response to the input stream.   * ****Pause**** This button pauses the display. The input stream is not paused except for a .cen file input. The button will change to **Continue** to allow the continuation of response to the input stream.
other/amass/documentation/view3d.1718805229.txt.gz · Last modified: 2024/06/19 13:53 by sgranger