Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:pipeline:signal_commands:merge_data [2024/06/14 17:30] – created sgranger
+++ visual3d:documentation:pipeline:signal_commands:merge_data [2024/10/15 02:05] (current) – Cleaned up page. Still need to meet Pipeline Command format. wikisysop
@@ Line 1: / Line 1: @@
-|**Language:**|** English**  • [[index.php?title=Merge_Data/fr&action=edit&redlink=1|français]] • [[index.php?title=Merge_Data/it&action=edit&redlink=1|italiano]] • [[Merge_Data/pt|português]] • [[index.php?title=Merge_Data/es&action=edit&redlink=1|español]] ****|
+===== Merge Data =====
-|===== Contents =====\\ \\ \\ \\ * [[#Parameters|1 Parameters]]\\ * [[#Examples|2 Examples]]\\   * [[#Simple_Example|2.1 Simple Example]]\\   * [[#Add_a_column_to_a_metric|2.2 Add a column to a metric]]\\   * [[#Merge_for_ASCII_export|2.3 Merge for ASCII export]]\\   * [[#Create_Global_List_of_all_Instances|2.4 Create Global List of all Instances]]|
+This command merges data from multiple signals into a single signal in one of two ways:
+  - either via **APPEND_TO_END**, appending one signal to the end of another signal, or
+  - via **MERGE_AS_NEW_COMPONENTS**, treating each original signal as a component of the new signal.
-This command merges data from more than one data name into a single one either by **APPEND_TO_END** (appending one signal to the end of another signal) or by **MERGE_AS_NEW_COMPONENTS** (treat each original signal as a component of the new signal).
+<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>
-|<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>  |  [[File:Merge_Data.png|{{/images/thumb/0/04/Merge_Data.png/400px-Merge_Data.png?400x262}}]]|
+{{:Merge_Data.png}}
-\\
+==== Parameters ====
+**COMPONENT_SEQUENCE:** if empty, all components of the signals will be used
-===== Parameters =====
+**MERGE_TYPE:** APPEND_TO_END or MERGE_AS_NEW_COMPONENTS
-**COMPONENT_SEQUENCE:** if empty, all components of the signals will be used\\
+  - 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
-**MERGE_TYPE:** APPEND_TO_END or MERGE_AS_NEW_COMPONENTS\\
+**IGNORE_MISSING_SIGNALS:**
-APPEND_TO_END append one signal to the end of another signal
+**PRE_CLEAR_RESULT_SIGNAL:** Will delete the resulting signal prior to beginning
-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 ====
-===== Examples =====
+Below are some examples for using the Merge_Data command demonstrating both types of merges.
-Below are two examples for the Merge_Data command
+=== Simple Example ===
-==== 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.
@@ Line 43: / Line 56: @@
 </code>
-==== Add a column to a metric ====
+=== Create Global List of all Instances ===
-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>
@@ Line 74: / Line 77: @@
 </code>
+=== Add a column to a metric ===
-Retrieved from ""
+Another [[Metrics Example 3|example]] adds 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|Exporting 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.