{"id":364189,"date":"2024-04-25T12:33:27","date_gmt":"2024-04-25T12:33:27","guid":{"rendered":"\/forum\/forums\/reply\/364189\/"},"modified":"2024-04-25T12:33:27","modified_gmt":"2024-04-25T12:33:27","slug":"364189","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/364189\/","title":{"rendered":"Reply To: Run IronScript from slurm"},"content":{"rendered":"

<p>Hi Keniel,<br><br>Please try the following:<\/p><p>$  export ANSYSEM_FEATURE_SF6694_NON_GRAPHICAL_COMMAND_EXECUTION_ENABLE=1<br><\/em><\/strong>$  ansysedt.exe -features=beta -ng -runscriptandexit <scriptName> [<projectName>]<\/em><\/strong><\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”><br>Please search AEDT help for “<\/span>Running Ansys Electronics Desktop from a Command Line”<br><br><\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>Note – ‘-ng’ and ‘-runscriptandexit’ have been available since 2019R1<br><br><\/span><\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Desktop automation is in terms of COM calls to the various COM objects exposed by desktop. This has always been unconditionally supported in a general-purpose graphical mode (<span style=”font-style: italic;”>Desktop with a GUI or in Iconic mode without specialized -batchextract etc modes<\/span>). When desktop is run in non-graphical mode (<span style=”font-style: italic;”>-ng in the command line)<\/span>, recorded scripts cannot be played back: instead, a select few commands are available via the <span style=”font-style: italic;”>-batchextract<\/span> script.<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>To ensure general command execution ability, AnsysET enforced the need for a GUI system: the user’s compute environment required a graphics subsystem (<span style=”font-style: italic;”>X Servers on Linux in particular<\/span>) to be configured.<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Some commands when run graphically would be somewhat expensive because of the needed User Interface updates and sometimes a user composes a script with hundreds of such expensive calls slowing the execution down noticeably. Forcing the user to run desktop in GUI mode forced the performance penalties as well.<\/p><p style=”margin-top: 18pt; margin-bottom: 6pt; font-family: Arial; font-size: 16.0pt; color: black;”>Non Graphical Command Limitations<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>2019 R1 release starts making progress toward allowing all commands to be run non-graphically. commands will be transitioned in phases and some graphical commands like Plot Export will be unavailable initially. If such commands are used, script execution will be terminated with a suitable error message.<\/p><p style=”margin-top: 18pt; margin-bottom: 6pt; font-family: Arial; font-size: 16.0pt; color: black;”>Enabling from the GUI<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Bring up the Options and enable “beta” features. If enabling all beta features is not desired, then the command line will have to be used with the “<span style=”font-style: italic;”>-features<\/span>=<span style=”font-style: italic;”>SF6694_Non_Graphical_Command_execution” <\/span>parameter.<\/p><p style=”margin-top: 18pt; margin-bottom: 6pt; font-family: Arial; font-size: 16.0pt; color: black;”>Enabling from the Command Line<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Invoke desktop in ng mode for script execution by specifying the beta flag: this allows the existing <span style=”font-style: italic;”>-runscriptandexit <\/span>command-line parameter to work in non-graphical mode as well.<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”><span style=”font-weight: bold; font-style: italic;”>ansysedt.exe -features=beta -ng -runscriptandexit <scriptName> [<projectName>]<\/span><\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Note: -features=”beta” turns on all beta features. If there is a need to disable all beta features except <span style=”font-style: italic;”>“non-graphical command execution”, <\/span>the more specific “<span style=”font-style: italic;”>-features<\/span>=<span style=”font-style: italic;”>SF6694_Non_Graphical_Command_execution” <\/span>can be used instead.<\/p><p style=”margin-top: 18pt; margin-bottom: 6pt; font-family: Arial; font-size: 16.0pt; color: black;”>Enabling For Workbench Scenarios<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Prior to 19R1, when workbench was run in batch mode <span style=”font-style: italic;”>(-B command line parameter)<\/span>, several methods of the Electromagnetics Addin are disabled. This saga-feature enables them back and allows all Workebench<->AnsysEDT interaction to occur fully non-graphically. To enable this, you must set the following environment variable.<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>ANSYSEM_FEATURE_SF6694_NON_GRAPHICAL_COMMAND_EXECUTION_ENABLE=1<\/span><\/p><p style=”margin-top: 18pt; margin-bottom: 6pt; font-family: Arial; font-size: 16.0pt; color: black;”>Enabling for stand-alone scripting scenarios<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>For stand-alone scripting scenarios (<span style=”font-style: italic;”>where the ipy64.exe interpreter is used instead of ansysem.exe to run the script)<\/span>. Refer to online help and search for “<span style=”font-style: italic;”>Standalone IronPython<\/span>” for additional details.<\/p><p style=”margin: 0in; font-family: Arial; font-size: 11.0pt; color: black;”>Standalone graphical scripts, have the following preamble.<\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>import sys<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>sys.path.append(“<application path>”)<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>sys.path.append(“<application path>\/PythonFiles\/DesktopPlugin”)<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>import ScriptEnv<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>ScriptEnv.Initialize(“Ansoft.ElectronicsDesktop”)<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”>This is used for the typical graphical AnsysEDT COM server. For, non-graphical com servers, the final <span style=”font-style: italic;”>ScriptEnv.Initialize<\/span> is replaced by ScriptEnv.InitializeNew.<\/p><ul style=”direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;” type=”disc”><li style=”margin-top: 0; margin-bottom: 0; vertical-align: middle; color: black;”><span style=”font-weight: bold; font-family: Verdana; font-size: 11.0pt;”>Note: <\/span><span style=”font-weight: bold; font-style: italic; font-family: Verdana; font-size: 11.0pt;”>InitializeNew<\/span><span style=”font-weight: bold; font-family: Verdana; font-size: 11.0pt;”> does not take the COM ProgID since it launches the Exe directly by computing a path relative to the ScriptEnv.py module.<\/span><\/li>\n

<li style=”margin-top: 0; margin-bottom: 0; vertical-align: middle; color: black;”><span style=”font-weight: bold; font-family: Verdana; font-size: 11.0pt;”>Note: <\/span><span style=”font-weight: bold; font-style: italic; font-family: Verdana; font-size: 11.0pt;”>InitializeNew<\/span><span style=”font-weight: bold; font-family: Verdana; font-size: 11.0pt;”> specifies that a new instance is to be launched everytime. This helps by not connecting to existing COM server.<\/span><\/li>\n<\/ul>\n

<p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>import sys<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>sys.path.append(“<application path>”)<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>sys.path.append(“<application path>\/PythonFiles\/DesktopPlugin”)<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>import ScriptEnv<\/span><\/p><p style=”margin: 0in; font-family: Verdana; font-size: 11.0pt; color: black;”><span style=”font-style: italic;”>ScriptEnv.<\/span><span style=”font-weight: bold; font-style: italic;”>InitializeNew<\/span><span style=”font-style: italic;”>( <\/span><span style=”font-weight: bold; font-style: italic;”>NonGraphical <\/span><span style=”font-style: italic;”>= True)<\/span><\/p><\/p>\n","protected":false},"template":"","class_list":["post-364189","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"acf":[],"_links":{"self":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/364189","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies"}],"about":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/types\/reply"}],"version-history":[{"count":0,"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/364189\/revisions"}],"wp:attachment":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/media?parent=364189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}