Package: ansys-systemcoupling-core
OverviewPySystemCoupling provides Pythonic access to Ansys System
Coupling. Although this Ansys product exposes its own
Python-based scripting and command line interface, it is embedded
and based on a specific version of Python. In contrast,
PySystemCoupling enables seamless use of System Coupling within the Python
ecosystem, providing additional capabilities, including:Ability to launch System Coupling using a local Ansys installationAccess to APIs to set up and solve coupled analysesFull access to the System Coupling data model via a convenient and Pythonic interfaceInstallationInstall PySystemCoupling with this command:pip install ansys-systemcoupling-coreAlternatively, clone and install PySystemCoupling indevelopment modewith this code:git clone https://github.com/ansys/pysystem-coupling.git
cd pysystem-coupling
python -m pip install --upgrade pip
pip install -e .
pip install .[classesgen]
python scripts\generate_datamodel.pyDocumentation and IssuesFor more information, see theDocumentationpage.Use thePySystemCoupling Issuespage to
post bug reports, questions and feature requests.UsageIt is assumed that an Ansys installation is available and that this installation
includes System Coupling and the participant products needed for the coupled analysis.The System Coupling installation is found by examining the following environment variables
in this order:SYSC_ROOTAWP_ROOTAWP_ROOT241If a variable is set but does not refer to a valid installation, PySystemCoupling
fails at that point, rather than attempting to use the next variable.In a standard user installation, the expectation is that onlyAWP_ROOT241is set.(It is also possible to provide a different version number as an argument to thelaunch()function. This will affect whichAWP_ROOT<version>environment variable is examined.)The System Coupling API is exposed to PySystemCoupling in two forms:A documented interface based on concrete Python classes, following Pythonic conventionsA dynamic interface, undocumented in PySystemCoupling, that replicates the native System Coupling APIBoth forms are strongly related to each other. A key difference in the Pythonic API is that naming
is adjusted, in a generally predictable manner, to follow Python conventions. If you are already
familiar with System Coupling, adjusting to this form, which is the recommended API, should be easy.
However, if you are transitioning existing scripts, the native System Coupling API is made available
as a convenience.NoteWhile most commands should work as expected via the native System Coupling API,
no guarantees can be given because of the nature of how it is exposed.This example shows how to set up and solve an oscillating plate example in the Pythonic API.
It uses Ansys Fluent as the CFD solver.importansys.systemcoupling.coreaspysystemcouplingsyc=pysystemcoupling.launch()setup=syc.setupsetup.add_participant(input_file="mapdl.scp")setup.add_participant(input_file="fluent.scp")## Create interfaces and data transfers by specifying participant regionsinterface_name="interface-1"interface=setup.coupling_interface.create(interface_name)interface.side["One"].coupling_participant="MAPDL-1"interface.side["One"].region_list=["FSIN_1"]interface.side["Two"].coupling_participant="FLUENT-2"interface.side["Two"].region_list=["wall_deforming"]# Use commands to add data transfersforce_transfer_name=setup.add_data_transfer(interface=interface_name,target_side="One",side_one_variable="FORC",side_two_variable="force",)disp_transfer_name=setup.add_data_transfer(interface=interface_name,target_side="Two",side_one_variable="INCD",side_two_variable="displacement",)# Change analysis duration and step sizesetup.solution_control.time_step_size="0.1 [s]"setup.solution_control.end_time="1.0 [s]"# Set output control settingssetup.output_control.option="StepInterval"setup.output_control.output_frequency=2# Start streaming standard output from serversyc.start_output()# Solvesolution=syc.solutionsolution.solve()The Pythonic API partitions commands via three high-levelrootattributes of theSessionclass:setup,solution, andcase. The preceding example
uses both thesetupandsolutionattributes.Thesetupattribute is the largest part of the API. It is where you find all
commands related to populating the settings that define a coupled analysis. This
attribute also provides direct access to the hierarchical data model.Thesolutionattribute is home to commands related to solving an analysis and
examining the solution.Thecaseattribute, which is not used in the preceding example, provides all
commands related to case file management and persistence.While the preceding example uses thepysystemcoupling.launch()method to start the
System Coupling server, alternatively, the server can be started in advance by calling
command line arguments-mcosimgui--grpcport=<host:port>andpysystemcoupling.connect(host, port).This next example shows how to set up the same analysis using the native System Coupling
API. While the code here is less complete than the code shown previously, it should
sufficiently illustrate the differences and connections between the two API forms.importansys.systemcoupling.coreaspysystemcouplingsyc=pysystemcoupling.launch()native_api=syc._native_apinative_api.AddParticipant(InputFile="mapdl.scp")native_api.AddParticipant(InputFile="fluent.scp")interface=native_api.CouplingInterface["interface-1"]interface.Side["One"].CouplingParticipant="MAPDL-1"...native_api.SolutionControl.TimeStepSize="0.1 [s]"...syc.start_output()native_api.Solve()LicensePySystemCoupling is licensed under the MIT license.Theansys-systemcoupling-corepackage makes no commercial claim over Ansys
whatsoever.  It extends the functionality of Ansys System Coupling by
adding a Python interface to the System Coupling service without changing the
core behavior or license of the original software. Interactively controlling
System Coupling via PySystemCoupling requires a local copy of System Coupling
and licenses for all Ansys products involved in your coupled analysis.To get a copy of Ansys, visitAnsys.