Editing
Vicon:Data format documentation
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Raw data == ''//The page is under development'' The existing installation of Vicon mo-cap system consists of three software: * Nexus: Skeleton tracking and motion capture + Video * Tracker: 6:DOF Object tracking (patterns with 4 or more points) * Undistortion tool β Video undistortion tool ( Command line) With the three software, the Vicon system records the coordinate information of each tracking nodes over time. It uses infrared cameras and RGB video cameras to obtain its input, and then generate raw outputs with the software. According to the setup of RGB cameras, there can also be video outputs for assisting annotation of the nodes. ''//TODO: quick description of what the input/output of the different Vicon software modules is. For example, do you need to run any software to obtain the unlabeled trajectories, or is that part of the raw output of the system?'' Each of the software has its own focus in application. However, they have shared file formats for recording data as well. Here is a table of what those different file formats contain and from which component of the Vicon system they are generated. {| class="wikitable" |- ! Format !! Description !! generated by |- | .mp || The coordinate of four markers from an object. They are represented in object space. || shared |- | .x2d, .x3d || A session for offline processing with the positions of all markers. || shared |- | .csv || Stores the positions of each object per frame. With header for detailed information. || Tracker |- | .vvid, .avi || Videos from RGB cameras || Nexus |- | .vsk || Skeleton information from Nexus || ''TODO'' |- | .xcp || Detailed camera information, resulted from calibration. || Undistortion tool |- | .system || Parameters stored in the system || ''TODO'' |} ''TODO: 3D coordinates of backpack points for each backpack (in Backpack coordinates). Is this really an output of the system, i.e. does it find rigid patterns itself? It sounds like it's more of a configuration one has to supply in order to extract backpack positions from unlabeled trajectories.'' A Python script can extract information (which?), however data packet can be lost if too many objects are saved. Need optimization. Resources: * [[File:Vicon_Intro_Hemal.pdf|Hemal's presentation on the Vicon system from 13.6.19]] * [https://owncloud.gwdg.de/index.php/s/XouWYdyD11FnEle Hemal's Vicon toolbox code] * [http://merkur229.inf.uni-konstanz.de:5678/Vicon_no_videos.tar.bz2 Sample data without videos]
Summary:
Please note that all contributions to Collective Computational Unit may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
CCU:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Collective Computational Unit
Main page
Projects
Tutorials
GPU Cluster
Core Facilitys
Mediawiki
Recent changes
Random page
Help
Tools
What links here
Related changes
Page information