Differences

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

--- visual3d:documentation:third-party:matlab:matlab [2024/07/12 14:07] – created sgranger
+++ visual3d:documentation:third-party:matlab:matlab [2024/07/17 15:46] (current) – created sgranger
@@ Line 204: / Line 204: @@
 To clarify, the basic algorithm of the above CALL_MFILE command is illustrated below:
-{{integrateMatlab.gif}}\\
+{{:integrateMatlab.gif}}\\
@@ Line 490: / Line 490: @@
 This command is similar to [[#Export_Data_To_Matlab|Export_Data_To_Matlab]] except that the resulting data is placed in an Matlab .mat file rather than being pushed into the Matlab Workspace
-{{export_data_to_matfile.png}}
+{{:export_data_to_matfile.png}}
 It is very important to note that Visual3D expresses an unknown value (e.g. a TARGET with residual of -1) using the value DATA_NOT_FOUND (-99999). Matlab doesn't recognize this Visual3D expression, so you may want to replace DATA_NOT_FOUND with NaN (e.g. /USE_NAN_FOR_DATANOTFOUND=TRUE). If you don't and you list the contents of the variable in Matlab, your data may be scaled to 1.e5, which means that most of your values may end up looking as if they were zero. If you enter DATA_NOT_FOUND, you can have your m-file search for this value, so that you can continue to perform matrix math in Matlab (which won't process NaN in an array). Text version below:
@@ Line 566: / Line 566: @@
 Invoke the Pipeline Edit Dialog
-{{Export_Data_To_Matlab_Dlg1.gif}}\\
+{{:Export_Data_To_Matlab_Dlg1.gif}}\\
@@ Line 574: / Line 574: @@
 Add the name of the Matlab struct array and the first TARGET. Select the Add Data button
-{{Export_Data_To_Matlab_Dlg2.gif}}\\
+{{:Export_Data_To_Matlab_Dlg2.gif}}\\
@@ Line 582: / Line 582: @@
 Add the remaining 2 signals
-{{Export_Data_To_Matlab_Dlg3.gif}}\\
+{{:Export_Data_To_Matlab_Dlg3.gif}}\\
@@ Line 653: / Line 653: @@
-{{Import_Data_From_Matlab_Dlg.gif}}
+{{:Import_Data_From_Matlab_Dlg.gif}}
 ==== Eval_In_Matlab ====