Parametrization: The category of variables called parameter defaults in AEDT is not supported by the integration plugin. These parameters are displayed in the parameter listings, but do not register them with optiSLang as this causes errors at runtime.

Parametrization: The hidden property of AEDT parameters is not available in optiSLang for filtering parameter listings.

Scheduler mode: Hard stopping running processes by clicking the Halt button ( ) in the optiSLang user interface kills entire process trees. Enforcing the generic maximum runtime setting offered by many nodes works in the same way as the hard stop. However, halting process trees does not affect scheduler jobs being active as independent process trees on the same machine or on other machines in the network. The current implementation of the scheduler job mode of the AEDT node has no generally applicable reliable implementation for forwarding job termination signals to scheduler jobs. However, the library of Python code for the IronPython scripting layer in AEDT is open-source, can be extended by users if needed, and the function submit_via_odesktop in AEDT2_scripting.py offers basic support for receiving a user-written scheduler job abort function.

optiSLang in Optimetrics: Output data of the (solved or unsolved) reference project is not known to optiSLang. This has two consequences. The first consequence is that only dummy values (zero values in signals of length one) are displayed in the output detection listing of an AEDT integration node. The second consequence is that the units of output quantities are unknown. The first consequence reduces the convenience of using calculator functions when defining derived quantities. Because of the second consequence, the output names will be different at runtime as compared to the configuration time if the quantity unit is part of the name. In such a case, you must use the name truncation function to define collection rules for registered output quantities which do not break at runtime. optiSLang can only collect output quantities based on matching object names.

Output collection: In the current implementation, the AEDT node has no direct scan routine for output variables defined in the framework of AEDT. The AEDT output variables can only be forwarded to optiSLang indirectly, by plotting the variables in a report for the standard run modes, and by funneling them into an object in the Calculations tab in the property dialog box of optiSLang Setups under Optimetrics).