HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » file_commands » File Commands Overview
visual3d:documentation:pipeline:file_commands:file_commands_overview

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
visual3d:documentation:pipeline:file_commands:file_commands_overview [2024/06/19 12:50] – sgrangervisual3d:documentation:pipeline:file_commands:file_commands_overview [2024/11/16 22:35] (current) – wikisysop
Line 1: Line 1:
-==== file open/import ====+====== File Commands Overview ======
  
-file commands are separated into three categories:\\ +=== File Open/Import === 
-1) [[visual3d:documentation:pipeline:file_commands:file_management_overview|file_management]]\\ + 
-2) [[visual3d:documentation:pipeline:file_commands:file_open_and_import_commands|file_open/import]]\\ +File Commands are separated into three categories:\\ 
-3) [[visual3d:documentation:pipeline:file_commands:file_save_and_export_commands|file_save/export]]\\+1) [[Visual3D:Documentation:Pipeline:File_Commands:File_Management_Overview|File_Management]]\\ 
 +2) [[Visual3D:Documentation:Pipeline:File_Commands:File_Open_and_Import_Commands|File_Open/Import]]\\ 
 +3) [[Visual3D:Documentation:Pipeline:File_Commands:File_Save_and_Export_Commands|File_Save/Export]]\\
  
  
 \\ \\
-for more pipeline commands, please see the [[visual3d:documentation:pipeline:general_information:pipeline_commands_reference|pipeline commands reference]] page.+For more pipeline commands, please see the [[Visual3D:Documentation:Pipeline:General_Information:Pipeline_Commands_Reference|Pipeline Commands Reference]] page.
  
  
Line 16: Line 18:
 ---- ----
  
-==== file_management ====+=== File_Management === 
 + 
 +[[visual3d:documentation:pipeline:file_commands:exit_workspace]] 
 + 
 +Exits Visual3D. This is useful when an external program launches Visual3D with a pipeline. When the pipeline is finished executing, Visual3D is closed. 
 + 
 +[[visual3d:documentation:pipeline:file_commands:recalc]] 
 + 
 +Recalculate the link model, event dependencies, and execute the [[Visual3D:Documentation:Pipeline:General_Information:RECALC_Pipeline|RECALC Pipeline]]. 
 + 
 +[[visual3d:documentation:pipeline:file_commands:clear_recalc_pipeline]] 
 + 
 +[[visual3d:documentation:pipeline:file_commands:select_active_file]] 
 + 
 +Many of the pipeline commands in Visual3D act on the active files only, and only active file is animated in the 3D viewer.
  
-== exit_workspace ==+[[visual3d:documentation:pipeline:file_commands:File_Close]]
  
-exits visual3d. this is useful when an external program launches visual3d with a pipeline. when the pipeline is finished executing, visual3d is closed. +[[visual3d:documentation:pipeline:file_commands:File_New]]
-== recalc ==+
  
-recalculate the link model, event dependencies, and execute the [[visual3d:documentation:pipeline:general_information:recalc_pipeline|recalc pipeline]]. +Clears the Workspace. Removes all models, motion trials, and the Global Workspace.
-== clear_recalc_pipeline ==+
  
-== select_active_file ==+[[visual3d:documentation:pipeline:file_commands:File_Rename]]
  
-many of the pipeline commands in visual3d act on the active files only, and only active file is animated in the 3d viewer. +[[visual3d:documentation:pipeline:file_commands:assign_tags_to_file]]
-== file_close ==+
  
-== file_new ==+Files can be associated with other files opened in the Visual3D workspace by assigning a TAG to the file.
  
-clears the workspace. removes all models, motion trials, and the global workspace. +[[visual3d:documentation:pipeline:file_commands:Combine_Tags]]
-== file_rename ==+
  
-== assign_tags_to_file ==+Use boolean logic to combine TAGS into a new TAG.
  
-files can be associated with other files opened in the visual3d workspace by assigning a tag to the file. +[[visual3d:documentation:pipeline:file_commands:Remove_Tags]]
-== combine_tags ==+
  
-use boolean logic to combine tags into a new tag. +Removes the specified files from the TAG. Select ALL_FILES, a TAG, or a movement trial.
-== remove_tags ==+
  
-removes the specified files from the tag. select all_files, a tag, or a movement trial. +[[visual3d:documentation:pipeline:file_commands:Remove_CMO_History]]
-== remove_cmo_history ==+
  
-== load_cmo_library ==+[[visual3d:documentation:pipeline:file_commands:Load_CMO_Library]]
  
-== unload_cmo_library ==+[[visual3d:documentation:pipeline:file_commands:Unload_CMO_Library]]
  
-== copy_point_descriptions_to_analog_labels ==+= Copy_Point_Descriptions_To_Analog_Labels =
  
-== copy_point_descriptions_to_point_labels ==+= Copy_Point_Descriptions_To_Point_Labels =
  
-motion analysis corporation exports c3d files that are consistent with an early version of the c3d file format. one of the restrictions in the early format was that point labels (e.g. names of the markers) were allowed to have only 4 characters. this command will cause visual3d to copy the marker description parameter into the marker label parameter thus giving markers their long names. +Motion Analysis Corporation exports C3D files that are consistent with an early version of the C3D file format. One of the restrictions in the early format was that POINT LABELS (e.g. names of the markers) were allowed to have only 4 characters. This command will cause Visual3D to copy the marker DESCRIPTION PARAMETER into the marker LABEL PARAMETER thus giving markers their long names. 
-== create_targets_for_linkmodelbased_rotations ==+= Create_Targets_For_LinkModelBased_Rotations =
  
-== create_targets_for_linkmodelbased_rotations_from_velocity ==+= Create_Targets_For_LinkModelBased_Rotations_From_Velocity =
  
-== joint_rotations_from_psu_imu ==+= Joint_Rotations_From_PSU_IMU =
  
-== fix_mac_eva7_c3dfile ==+= Fix_MAC_Eva7_C3DFile =
  
-visual3d does not act as a general c3d editor. several commands, however, exist to edit specific parameters in the c3d file:+Visual3D does not act as a general C3D editor. Several commands, however, exist to edit specific parameters in the C3D file:
  
-== modify_analog_parameters ==+= Modify_Analog_Parameters =
  
-this command can be used to change a selection of the analog parameters in a c3d file. there must be the same number of values in the labels, scale, and offset entries. the command will modify the parameters in order. +This command can be used to change a selection of the ANALOG parameters in a C3D file. There must be the same number of values in the LABELS, SCALE, and OFFSET entries. The command will modify the parameters in order. 
-== modify_c3d_manufacturer ==+= Modify_C3D_Manufacturer =
  
-== modify_point_parameters ==+= Modify_Point_Parameters =
  
-the command modify_point_parameters will modify the point labels (e.g. marker names) in the c3d file. the labels listed will be applied to the point parameters in the order listed in the c3d file. if fewer labels are specified in the command than exist in the c3d file, then only the number of labels specified will be modified. +The command Modify_Point_Parameters will modify the POINT LABELS (e.g. Marker Names) in the C3D file. The LABELS listed will be applied to the POINT parameters in the order listed in the C3D file. If fewer LABELS are specified in the command than exist in the C3D file, then only the number of LABELS specified will be modified. 
-== modify_c3d_subjects_parameters ==+= Modify_C3D_Subjects_Parameters =
  
-modify the subject parameter group +Modify the SUBJECT parameter group 
-== modify_point_rate ==+= Modify_Point_Rate =
  
-modify the point and/or analog rate in the c3d file +Modify the point and/or analog rate in the c3d file 
-== remove_prefix_from_point_labels ==+= Remove_Prefix_From_Point_Labels =
  
-vicon corporation's workstation software provides an option to add a prefix to all of the marker labels. this causes visual3d a big problem because visual3d assumes that markers are named consistently between files, especially between the standing trial and the movement trials. +Vicon Corporation's Workstation software provides an option to add a prefix to all of the marker labels. This causes Visual3D a big problem because Visual3D assumes that markers are named consistently between files, especially between the standing trial and the movement trials. 
-=== upsample_point_data_to_analog_rate ===+== Upsample_Point_Data_To_Analog_Rate ==
  
-=== downsample_data ===+== Downsample_Data ==
  
-not available in visual3dv5:+Not Available In Visual3Dv5:
  
-[[visual3d:documentation:pipeline:file_commands:modify_c3d_trial_parameters|modify_c3d_trial_parameters]] +[[Visual3D:Documentation:Pipeline:File_Commands:Modify_C3D_Trial_Parameters|Modify_C3D_Trial_Parameters]] 
-modify the trail parameter group+Modify the TRAIL parameter group
  
 ---- ----
Line 97: Line 106:
 ---- ----
  
-==== file_open/import ====+=== File_Open/Import ===
  
-== file_open ==+= File_Open =
  
-adds a file to the visual3d workspace. +Adds a file to the Visual3D Workspace. 
-== file_close ==+= File_Close =
  
-closes the specified file(s). +Closes the specified File(s). 
-== import_data_from_ascii_file ==+= Import_Data_From_ASCII_File =
  
-imports signals from an ascii file formatted using the [[visual3d:documentation:definitions:file_formats:visual3d_ascii_format|visual3d_ascii_format]]. +Imports signals from an ascii file formatted using the [[Visual3D:Documentation:Definitions:File_Formats:Visual3D_ASCII_Format|Visual3D_ASCII_Format]]. 
-== import_analog_signals ==+= Import_Analog_Signals =
  
-== import_analog_anb_signals ==+= Import_Analog_ANB_Signals =
  
-== import_analog_bioware_signals ==+= Import_Analog_Bioware_Signals =
  
-== import_analog_frappier_signals ==+= Import_Analog_Frappier_Signals =
  
-== import_analog_fsv_signals ==+= Import_Analog_Fsv_Signals =
  
-== import_analog_ndi_signals ==+= Import_Analog_NDI_Signals =
  
-imports analog signals from ndi toolbench into a c3d file. +Imports Analog signals from NDI Toolbench into a C3D file. 
-== import_analog_noraxon_emg_signals ==+= Import_Analog_Noraxon_EMG_Signals =
  
-== import_pedar_data ==+= Import_Pedar_Data =
  
-== import_analog_son_signals ==+= Import_Analog_SON_Signals =
  
-== import_analog_signals_from_amti_ascii_file ==+= Import_Analog_Signals_From_AMTI_Ascii_File =
  
-the ascii file exported by amti is a very simple file with no header, and the data stored in columns. +The ASCII file exported by AMTI is a very simple file with no header, and the data stored in columns. 
-== import_analog_signals_from_arsalis_ascii_file ==+= Import_Analog_Signals_From_Arsalis_Ascii_File =
  
-== import_analog_signals_from_dasylab_ascii_file ==+= Import_Analog_Signals_From_DASYLAB_Ascii_File =
  
-== import_analog_signals_from_delsys_ascii_file ==+= Import_Analog_Signals_From_Delsys_Ascii_File =
  
-== import_analog_signals_from_microstrain_ascii_file ==+= Import_Analog_Signals_From_Microstrain_Ascii_File =
  
-== import_analog_signals_from_winternet_signals ==+= Import_Analog_Signals_From_Winternet_Signals =
  
-== import_analog_signals_from_adinstruments_chart_ascii_file ==+= Import_Analog_Signals_From_ADInstruments_Chart_Ascii_File =
  
-== import_data_from_ascii_file ==+= Import_Data_From_ASCII_File =
  
-== import_analog_signals_from_datapac_files ==+= Import_Analog_Signals_From_DATAPAC_Files =
  
-== import_signals_from_c3d_file ==+= Import_Signals_From_C3D_File =
  
-this command imports signals from a c3d file into the active file. +This command imports signals from a C3D file into the Active File. 
-== import_surrey_force_platform_signals ==+= Import_Surrey_Force_Platform_Signals =
  
-== merge_aurora_files ==+= Merge_Aurora_Files =
  
-not available in visual3dv5:+Not Available in Visual3Dv5:
  
-[[visual3d:documentation:pipeline:file_commands:import_fsv_files|import_fsv_files]] +[[Visual3D:Documentation:Pipeline:File_Commands:Import_FSV_Files|Import_FSV_Files]] 
-the fsv/tsv file formats were originally developed by manfred berger from innovision systems and are currently used by qualisys and innovision +The FSV/TSV file formats were originally developed by Manfred Berger from Innovision Systems and are currently used by Qualisys and Innovision 
-[[visual3d:documentation:pipeline:file_commands:import_analog_signals_from_fsv_file|import_analog_signals_from_fsv_file]] +[[Visual3D:Documentation:Pipeline:File_Commands:Import_Analog_Signals_From_Fsv_File|Import_Analog_Signals_From_Fsv_File]] 
-importing analog signals stored in an fsv file into an existing c3d file.+Importing ANALOG signals stored in an fsv file into an existing c3d file.
  
 ---- ----
Line 165: Line 174:
 ---- ----
  
-==== file_save/export ====+=== File_Save/Export ===
  
-== file_save ==+= File_Save =
  
-save the current workspace to the active cmo file. +Save the current Workspace to the active CMO file. 
-== file_save_as ==+= File_Save_As =
  
-save the current workspace to a new cmo file. +Save the current Workspace to a new CMO file. 
-== export_3d_animation_to_image ==+= Export_3D_Animation_To_Image =
  
-exporting a snapshot of the animation viewer to a file on disk.+Exporting a snapshot of the animation viewer to a file on disk.
  
-== export_3d_animation_to_video ==+= Export_3D_Animation_To_Video =
  
-== export_3dsspp_batch_file ==+= Export_3DSSPP_Batch_File =
  
-== export_c3dfile ==+= Export_C3DFile =
  
-export one or more c3d files from the workspace +Export one or more C3D files from the Workspace 
-== export_data_to_ascii_file ==+= Export_Data_To_ASCII_File =
  
-== export_polygon_c3dfile ==+= Export_Polygon_C3DFile =
  
-export a file from the workspace to a c3d file suitable for vicon's polygon program +Export a file from the Workspace to a C3D file suitable for Vicon's Polygon program 
-=== export_to_rdbms ===+== Export_To_RDBMS ==
  
  
  
visual3d/documentation/pipeline/file_commands/file_commands_overview.1718801413.txt.gz · Last modified: 2024/06/19 12:50 by sgranger