other:capture2d:documentation
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
other:capture2d:documentation [2024/06/14 17:19] – created sgranger | other:capture2d:documentation [2024/07/17 15:44] (current) – created sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | |**Language: | + | ====== |
- | |===== Contents =====\\ \\ \\ \\ * [[#Overview|1 Overview]]\\ * [[# | + | ===== Overview ===== |
- | + | ||
- | ====== Overview ====== | + | |
Capture2D™ is a desktop application used for recording and saving 2-D motion data from Natural Point Inc. camera systems. The data is stored in the [[Other: | Capture2D™ is a desktop application used for recording and saving 2-D motion data from Natural Point Inc. camera systems. The data is stored in the [[Other: | ||
- | While Capture2D™ can be used independently to collect and store 2-D centroid data, Capture2D™ is designed to integrate seamlessly with the Ad Tech™ motion analysis software system (AMASS™). AMASS™, also developed by Dr. Dainis, takes 2-D centroid input files and provides volume calibration, | + | While Capture2D™ can be used independently to collect and store 2-D centroid data, Capture2D™ is designed to integrate seamlessly with the Ad Tech™ motion analysis software system (AMASS™). AMASS™, also developed by Dr. Dainis, takes 2-D centroid input files and provides volume calibration, |
Capture2D™ provides support for the following [[http:// | Capture2D™ provides support for the following [[http:// | ||
Line 48: | Line 46: | ||
During the initial set up we highly recommend that you toggle the Save Data as CSV file and Save Settings check boxes for all initial captures. Should you require C-Motion' | During the initial set up we highly recommend that you toggle the Save Data as CSV file and Save Settings check boxes for all initial captures. Should you require C-Motion' | ||
- | ====== The Capture2D™ Interface | + | ===== The Capture2D™ Interface ===== |
The user interface to Capture2D™ consists of a main application window and a Settings dialog. | The user interface to Capture2D™ consists of a main application window and a Settings dialog. | ||
Line 54: | Line 52: | ||
The main application window is modeless (i.e., you do not need to press an OK or Apply button for changes to take effect.) Where as the Settings dialog is modal (i.e., you must press the Apply button in order for changes to take effect.) | The main application window is modeless (i.e., you do not need to press an OK or Apply button for changes to take effect.) Where as the Settings dialog is modal (i.e., you must press the Apply button in order for changes to take effect.) | ||
- | [[File: | + | {{:Capture_2D_start_up_screen.png}} |
- | ====== Clients | + | ===== Clients ===== |
The clients button indicates which client programs (such as AMASS) are currently connected to Capture2D. Thus when Capture2D is streaming to AMASS, AMASS will appear as a client in the client window. This function is not currently operational, | The clients button indicates which client programs (such as AMASS) are currently connected to Capture2D. Thus when Capture2D is streaming to AMASS, AMASS will appear as a client in the client window. This function is not currently operational, | ||
- | ====== Settings | + | ===== Settings ===== |
- | [[File: | + | {{:Capture_2D_settings.png}} |
- | === Stream | + | == Stream == |
The Stream portion of the settings dialogue allows you to control the data that is coming in such as Thread Priority and Thread Sleep Time. | The Stream portion of the settings dialogue allows you to control the data that is coming in such as Thread Priority and Thread Sleep Time. | ||
Line 71: | Line 69: | ||
The code that acquires frames operates in a separate thread of execution (much like a separate program). Each thread (or program) on a computer has a priority. In fact, if you start the Windows task manager (right click the Task bar at the bottom of the screen) you'll see, under the processes tab, that you can view and set the " | The code that acquires frames operates in a separate thread of execution (much like a separate program). Each thread (or program) on a computer has a priority. In fact, if you start the Windows task manager (right click the Task bar at the bottom of the screen) you'll see, under the processes tab, that you can view and set the " | ||
- | [[File: | + | {{:thread_priority.png}} |
**Thread Sleep Time Preference**\\ | **Thread Sleep Time Preference**\\ | ||
Line 80: | Line 78: | ||
It is likely that these features will be either hidden or removed at some point as this level of user control is not that useful now that the frame acquisition code has been refined. | It is likely that these features will be either hidden or removed at some point as this level of user control is not that useful now that the frame acquisition code has been refined. | ||
- | [[File: | + | {{:threadsleep.png}} |
- | === Display | + | == Display == |
The display portion of the settings dialogue allows you to control the program outputs by personalizing the graphics. | The display portion of the settings dialogue allows you to control the program outputs by personalizing the graphics. | ||
- | [[File: | + | {{:Display_settings.png}} |
**Text Size**\\ | **Text Size**\\ | ||
Line 97: | Line 95: | ||
The draw empty frames checkbox tells the program that when the box is checked if there are no new frames when it is time for the graphics to redraw to leave the previous graphics on the screen. If the box is not checked then if there is no new data then graphics will not be drawn. Leaving the checkbox checked will result in smoother graphics however, you will have no visual indication that frames may be missing. | The draw empty frames checkbox tells the program that when the box is checked if there are no new frames when it is time for the graphics to redraw to leave the previous graphics on the screen. If the box is not checked then if there is no new data then graphics will not be drawn. Leaving the checkbox checked will result in smoother graphics however, you will have no visual indication that frames may be missing. | ||
- | === Record | + | == Record == |
The record portion of the settings dialogue controls record function which allows for signal when recordings begin and end as well as saving preferences. | The record portion of the settings dialogue controls record function which allows for signal when recordings begin and end as well as saving preferences. | ||
- | [[File: | + | {{:Capture_2D_record_settings.png}} |
**Countdown**\\ | **Countdown**\\ | ||
Line 121: | Line 119: | ||
The beep after save checkbox gives a beep when the file has successfully been saved. This allows a single user who is the capture volume to know that the recording has stopped even though they may not be able to see the computer screen. | The beep after save checkbox gives a beep when the file has successfully been saved. This allows a single user who is the capture volume to know that the recording has stopped even though they may not be able to see the computer screen. | ||
- | === Save Options and Default | + | == Save Options and Default == |
**Save Settings File**\\ | **Save Settings File**\\ | ||
Line 145: | Line 143: | ||
- | ===== Help & About ===== | + | ==== Help & About ==== |
The help button at the bottom of the Capture2D pages will open this wiki page in order to provide information on the layout and functions of Capture2D. The about button will provide the version and release date of your current software. Furthermore, | The help button at the bottom of the Capture2D pages will open this wiki page in order to provide information on the layout and functions of Capture2D. The about button will provide the version and release date of your current software. Furthermore, | ||
- | [[File: | + | {{:AboutCapture_2D_window.png}} |
- | ====== Capture_Comments | + | ===== Capture_Comments ===== |
Comments can be added to .cen files with the 'Edit Comment' | Comments can be added to .cen files with the 'Edit Comment' | ||
- | [[File: | + | {{:Capture_Browse.jpg}} |
- | ====== Recording Data ====== | + | ===== Recording Data ===== |
- | ===== Connecting to Cameras | + | ==== Connecting to Cameras ==== |
Connect to the cameras by selecting the Connect Button. | Connect to the cameras by selecting the Connect Button. | ||
- | [[File: | + | {{:CaptureConnectButton.jpg}} |
When the cameras are connected, the Connect button becomes a Disconnect button. | When the cameras are connected, the Connect button becomes a Disconnect button. | ||
- | [[File: | + | {{:CaptureDisconnectButton.jpg}} |
* Currently Capture2D™ supports OptiTrack FLEX:100 (R1 and R2) cameras from [[[http:// | * Currently Capture2D™ supports OptiTrack FLEX:100 (R1 and R2) cameras from [[[http:// | ||
Line 173: | Line 171: | ||
* Please let us know about other camera systems of interest as this will help guide future development. | * Please let us know about other camera systems of interest as this will help guide future development. | ||
- | ===== Where to Save on Disk ===== | + | ==== Where to Save on Disk ==== |
Use the browse button to select a good location in which to store your cen files. We highly recommend that you use a separate folder for each subject and for each session that the subject completes. The default path is the Capture2D™ application folder, which isn't writable on Windows 7 and isn't a smart place to store data (fix coming soon). The program will remember the previously selected a folder and will use this path the next time that Capture2D is opened from the desktop. If you open Capture2D through AMASS it will use the same file path that is being used by AMASS. Also be sure to give your files good names (i.e., cal.cen for calibration trial, jump.cen for a trial that involves jumping, etc.). | Use the browse button to select a good location in which to store your cen files. We highly recommend that you use a separate folder for each subject and for each session that the subject completes. The default path is the Capture2D™ application folder, which isn't writable on Windows 7 and isn't a smart place to store data (fix coming soon). The program will remember the previously selected a folder and will use this path the next time that Capture2D is opened from the desktop. If you open Capture2D through AMASS it will use the same file path that is being used by AMASS. Also be sure to give your files good names (i.e., cal.cen for calibration trial, jump.cen for a trial that involves jumping, etc.). | ||
- | [[File: | + | {{:browse_button.png}} |
- | ===== Recording_Data | + | ==== Recording_Data ==== |
Recording is initiated by selecting the "Start Recording" | Recording is initiated by selecting the "Start Recording" | ||
- | [[File: | + | {{:recording_buttons.png}} |
Note that this button is not available unless cameras are connected. | Note that this button is not available unless cameras are connected. | ||
- | ===== Playback | + | ==== Playback ==== |
When the trial has been collected Capture2D™ enters playback mode, so that the captured images can be reviewed. | When the trial has been collected Capture2D™ enters playback mode, so that the captured images can be reviewed. | ||
- | [[File: | + | {{:post_recording_buttons.png}} |
In Playback mode there is an option to proceed to the " | In Playback mode there is an option to proceed to the " | ||
- | ===== Calibration | + | ==== Calibration ==== |
Before any data can be processed by AMASS, it is important to calibrate the system. | Before any data can be processed by AMASS, it is important to calibrate the system. | ||
Line 201: | Line 199: | ||
Once your volume is de-cluttered and your IREDs, Thresholds and Exposures are adjusted as needed you should be able to capture a calibration trial (wand movement and L-frame trail). About 30 seconds should be long enough for four cameras. You might need to record for longer if you have more than four cameras or a large volume (maybe 60 or 90 seconds or longer). You want to give yourself enough time for each camera to see the wand throughout the volume. | Once your volume is de-cluttered and your IREDs, Thresholds and Exposures are adjusted as needed you should be able to capture a calibration trial (wand movement and L-frame trail). About 30 seconds should be long enough for four cameras. You might need to record for longer if you have more than four cameras or a large volume (maybe 60 or 90 seconds or longer). You want to give yourself enough time for each camera to see the wand throughout the volume. | ||
- | ==== Motion Trial versus Calibration Trial ==== | + | === Motion Trial versus Calibration Trial === |
There is no real distinction between recording a motion trial and calibrating the motion capture collection volume. | There is no real distinction between recording a motion trial and calibrating the motion capture collection volume. | ||
Line 207: | Line 205: | ||
A calibration file is simply a recorded trial used for [[Other: | A calibration file is simply a recorded trial used for [[Other: | ||
- | ==== Calibration Wand ==== | + | === Calibration Wand === |
The unique feature of the calibration is the use of the [[Other: | The unique feature of the calibration is the use of the [[Other: | ||
- | ==== Reference Markers | + | === Reference Markers === |
The Reference Markers are typically an L-Frame that is used to identify the Laboratory Coordinate System of the data collection volume. | The Reference Markers are typically an L-Frame that is used to identify the Laboratory Coordinate System of the data collection volume. | ||
Line 217: | Line 215: | ||
For most 3D analyses, the principal purpose of the L-Frame is to identify the direction of gravity (e.g. the vertical direction) | For most 3D analyses, the principal purpose of the L-Frame is to identify the direction of gravity (e.g. the vertical direction) | ||
- | ===== Capturing Motion Trials ===== | + | ==== Capturing Motion Trials ==== |
- | + | ||
- | Once the volume has been appropriately calibrated in AMASS then, so long as the cameras are not moved any number of static or motion trials can be collected. We recommend that you develop a naming convention for your motion files prior to beginning your collection in order to facilitate clear naming and organization of the trials. Once all desired trials have been collected they can then be tracked and labeled using [[|AMASS]]. | + | |
+ | Once the volume has been appropriately calibrated in AMASS then, so long as the cameras are not moved any number of static or motion trials can be collected. We recommend that you develop a naming convention for your motion files prior to beginning your collection in order to facilitate clear naming and organization of the trials. Once all desired trials have been collected they can then be tracked and labeled using [[Other: | ||
- | Retrieved from "" | ||
other/capture2d/documentation.1718385598.txt.gz · Last modified: 2024/06/14 17:19 by sgranger