HAS-Motion Software Documentation

This is an old revision of the document!

---

<code>\\ merge_data\\ /signal_types=\\ /signal_folder=\\ /signal_names=\\ ! /component_sequence=\\ ! /result_types=derived\\ ! /result_folders=processed\\ /result_name=\\ ! /merge_type=append_to_end\\ ! /ignore_missing_signals=false\\ ! /pre_clear_result_signal=false\\ ;\\ </code> | merge_data.png| \\ ===== parameters ===== **component_sequence:** if empty, all components of the signals will be used\\ **merge_type:** append_to_end or merge_as_new_components\\ append_to_end append one signal to the end of another signal merge_as_new_components treat each original signal as a component of the new signal **ignore_missing_signals:**\\ **pre_clear_result_signal:** will delete the resulting signal prior to beginning\\ ===== examples ===== below are two examples for the merge_data command ==== simple example ==== the command below will create a vector named **vector** from 3 analog signals. this is an example of merging 3 signals into one signal. <code> merge_data /signal_names=analog1+analog2+analog3 /signal_types=analog+analog+analog /signal_folder=original+original+original /signal_components=0+0+0 /result_name=vector /result_type=derived /result_folder=processed /merge_type=merge_as_new_components ; </code> ==== add a column to a metric ==== another example using the merge_data command can be found on the [[|metrics example 3]] page. in this example, the command is used to add an indexing column to a metric (single values). this will allow the metric to be graphed. ==== merge for ascii export ==== the example found on [[visual3d:documentation:pipeline:file_commands:export_data_to_ascii_file#example_6:_export_concatenated_metric_signals|export_data_to_ascii_file#example_6:_export_concatenated_metric_signals]] will concatenate metrics signals prior to exporting to an ascii file. when exporting, all signals are exported to separate columns in the exported file. for metric signals (e.g. signals with only one or two entries/frames) this can be inconvenient. it is not possible to concatenate the signals in the export command, but it is possible to concatenate the signals explicitly before export. ==== create global list of all instances ==== <code> select_active_file /file_name=all_files ; merge_data /signal_types=metric /signal_folder=processed /signal_names=global::list_of_instances+l_ankle_stiffness /component_sequence=all /result_types=metric ! /result_folders=processed /result_name=global::list_of_instances ! /merge_type=append_to_end /ignore_missing_signals=false /pre_clear_result_signal=true ; </code>