ansys-systemcoupling-core 0.6__py3-none-any.whl → 0.8.0__py3-none-any.whl

ansys/systemcoupling/core/adaptor/api_25_1/open.py

@@ -0,0 +1,102 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class open(Command):
+    """
+    Reads the state of a coupled analysis. The state consists of settings to
+    populate the datamodel and results to restart the analysis at the end of
+    a specified coupling step.
+
+    Settings are stored in a file named Settings.h5. Results files may
+    correspond either to coupling iterations or coupling steps, depending on
+    the analysis type and the types of participants involved.
+
+    By default (no arguments provided), this command looks for the ``SyC``
+    directory in the current  working directory. By default, if multiple
+    results files exist, the most recent one is opened.
+
+    If given optional arguments, behavior is modified as described below.
+
+    Cannot be run after the participants have been started.
+
+    Parameters
+    ----------
+    file_path : str, optional
+        Working directory containing the ``SyC`` subdirectory (and its .h5
+        file(s)) to be read.
+    coupling_step : int, optional
+        Integer specifying the coupling step at which the coupled analysis is
+        restarted. When used, System Coupling reads the corresponding
+        ``Results_step<#>.h5`` file in the specified directory and restarts the
+        analysis at the end of the specified coupling step. When this argument
+        is used, System Coupling automatically removes the output files related
+        to all later coupling steps. If the files cannot be removed, then
+        System Coupling generates an exception message instructing you to free
+        up the files and reissue the ``open`` command with the ``coupling_step``
+        argument. If the simulation's results files are associated with
+        coupling iterations, then System Coupling prints an error message
+        indicating this.
+    coupling_iteration : int, optional
+        Integer specifying the coupling iteration at which the coupled analysis
+        is restarted. When used, System Coupling reads the corresponding
+        ``Results_iter<#>.h5`` file in the specified directory and restarts the
+        analysis at the end of the specified coupling iteration. When this
+        argument is used, System Coupling automatically removes the output
+        files related to all later coupling iterations. If the files cannot be
+        removed, then System Coupling generates an exception message
+        instructing you to free up the files and reissue the ``open`` command with
+        the ``coupling_iteration`` argument. If the simulation's results files are
+        associated with coupling steps, then System Coupling prints an error
+        message indicating this.
+
+    """
+
+    syc_name = "Open"
+
+    argument_names = ["file_path", "coupling_step", "coupling_iteration"]
+
+    class file_path(String):
+        """
+        Working directory containing the ``SyC`` subdirectory (and its .h5
+        file(s)) to be read.
+        """
+
+        syc_name = "FilePath"
+
+    class coupling_step(Integer):
+        """
+        Integer specifying the coupling step at which the coupled analysis is
+        restarted. When used, System Coupling reads the corresponding
+        ``Results_step<#>.h5`` file in the specified directory and restarts the
+        analysis at the end of the specified coupling step. When this argument
+        is used, System Coupling automatically removes the output files related
+        to all later coupling steps. If the files cannot be removed, then
+        System Coupling generates an exception message instructing you to free
+        up the files and reissue the ``open`` command with the ``coupling_step``
+        argument. If the simulation's results files are associated with
+        coupling iterations, then System Coupling prints an error message
+        indicating this.
+        """
+
+        syc_name = "CouplingStep"
+
+    class coupling_iteration(Integer):
+        """
+        Integer specifying the coupling iteration at which the coupled analysis
+        is restarted. When used, System Coupling reads the corresponding
+        ``Results_iter<#>.h5`` file in the specified directory and restarts the
+        analysis at the end of the specified coupling iteration. When this
+        argument is used, System Coupling automatically removes the output
+        files related to all later coupling iterations. If the files cannot be
+        removed, then System Coupling generates an exception message
+        instructing you to free up the files and reissue the ``open`` command with
+        the ``coupling_iteration`` argument. If the simulation's results files are
+        associated with coupling steps, then System Coupling prints an error
+        message indicating this.
+        """
+
+        syc_name = "CouplingIteration"

ansys/systemcoupling/core/adaptor/api_25_1/open_results_in_ensight.py

@@ -0,0 +1,56 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class open_results_in_ensight(Command):
+    """
+    Allows for System Coupling results to be postprocessed in EnSight.
+
+    When this command is issued, System Coupling looks for the ``results.enc``
+    file in the ``SyC/results`` subdirectory of the current working directory.
+
+    When System Coupling finds the file, it loads the file into EnSight and
+    generates a confirmation message indicating that results are being opened.
+
+    If System Coupling is unable to find the ``results.enc`` file and/or the
+    EnSight executable, then it raises an error.
+
+    The ``open_results_in_ensight`` command may be issued multiple times from the same
+    instance of System Coupling. Each time the command is issued, a new
+    instance of the EnSight application is opened. Any existing instances of
+    EnSight remain open, both when additional instances are created and when
+    System Coupling exits.
+
+    Parameters
+    ----------
+    file_name : str, optional
+        The basename of the EnSight case file if using a non-standard file
+        name. Overrides the default file name ``results.enc``.
+    file_path : str, optional
+        The path to the EnSight case if using a non-standard location.
+        Overrides the default path of ``SyC/results``.
+
+    """
+
+    syc_name = "OpenResultsInEnSight"
+
+    argument_names = ["file_name", "file_path"]
+
+    class file_name(String):
+        """
+        The basename of the EnSight case file if using a non-standard file
+        name. Overrides the default file name ``results.enc``.
+        """
+
+        syc_name = "FileName"
+
+    class file_path(String):
+        """
+        The path to the EnSight case if using a non-standard location.
+        Overrides the default path of ``SyC/results``.
+        """
+
+        syc_name = "FilePath"

ansys/systemcoupling/core/adaptor/api_25_1/open_snapshot.py

@@ -0,0 +1,37 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class open_snapshot(Command):
+    """
+    Opens a snapshot containing a previously saved state of the simulation.
+    All state (files and directories) stored in the snapshot will be restored.
+    If other state exists in the working directory, then it will not be
+    modified by this command.
+
+    Note: Snapshot cannot be opened if participants have been started.
+
+    Parameters
+    ----------
+    snapshot_name : str, optional
+        The name of the snapshot to be opened. This is optional if and only if
+        there is only one snapshot available to be loaded. If multiple
+        snapshots exist, then the snapshot name must be specified.
+
+    """
+
+    syc_name = "OpenSnapshot"
+
+    argument_names = ["snapshot_name"]
+
+    class snapshot_name(String):
+        """
+        The name of the snapshot to be opened. This is optional if and only if
+        there is only one snapshot available to be loaded. If multiple
+        snapshots exist, then the snapshot name must be specified.
+        """
+
+        syc_name = "SnapshotName"

ansys/systemcoupling/core/adaptor/api_25_1/output_control.py

@@ -0,0 +1,134 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+from .ascii_output import ascii_output
+from .live_visualization import live_visualization
+from .results import results
+
+
+class output_control(Container):
+    """
+    Configure output controls.
+    """
+
+    syc_name = "OutputControl"
+
+    child_names = ["results", "ascii_output", "live_visualization"]
+
+    results: results = results
+    """
+    results child of output_control.
+    """
+    ascii_output: ascii_output = ascii_output
+    """
+    ascii_output child of output_control.
+    """
+    live_visualization: live_visualization = live_visualization
+    """
+    live_visualization child of output_control.
+    """
+    property_names_types = [
+        ("option", "Option", "str"),
+        ("generate_csv_chart_output", "GenerateCSVChartOutput", "bool"),
+        ("write_initial_snapshot", "WriteInitialSnapshot", "bool"),
+        ("transcript_precision", "TranscriptPrecision", "int"),
+        ("write_diagnostics", "WriteDiagnostics", "bool"),
+        ("write_weights_matrix", "WriteWeightsMatrix", "bool"),
+        ("write_residuals", "WriteResiduals", "bool"),
+        ("output_frequency", "OutputFrequency", "int"),
+    ]
+
+    @property
+    def option(self) -> str:
+        """Specifies when restart points are generated.
+
+        Allowed values (step-based analyses only):
+
+        - \"LastStep\" - Generates a restart point only for the last
+          coupling step completed.
+        - \"EveryStep\" -
+          Generate a restart point at the end of every coupling step.
+        - \"StepInterval\" - Generates a restart point at the end of
+          coupling steps at the interval specified by the output
+          frequency setting.
+
+        Allowed values (iteration-based analyses only):
+
+        - \"LastIteration\" - Generates a restart point only for the
+          last coupling iteration completed.
+        - \"EveryIteration\" - Generate a restart point at the end
+          of every coupling iteration.
+        - \"IterationInterval\" - Generates a restart point at the
+          end of coupling iterations at the interval specified by
+          the output frequency setting."""
+        return self.get_property_state("option")
+
+    @option.setter
+    def option(self, value: str):
+        self.set_property_state("option", value)
+
+    @property
+    def generate_csv_chart_output(self) -> bool:
+        """Write chart data in CSV format during solve."""
+        return self.get_property_state("generate_csv_chart_output")
+
+    @generate_csv_chart_output.setter
+    def generate_csv_chart_output(self, value: bool):
+        self.set_property_state("generate_csv_chart_output", value)
+
+    @property
+    def write_initial_snapshot(self) -> bool:
+        """Write initial snapshot."""
+        return self.get_property_state("write_initial_snapshot")
+
+    @write_initial_snapshot.setter
+    def write_initial_snapshot(self, value: bool):
+        self.set_property_state("write_initial_snapshot", value)
+
+    @property
+    def transcript_precision(self) -> int:
+        """Number of digits after decimal point in transcript."""
+        return self.get_property_state("transcript_precision")
+
+    @transcript_precision.setter
+    def transcript_precision(self, value: int):
+        self.set_property_state("transcript_precision", value)
+
+    @property
+    def write_diagnostics(self) -> bool:
+        """Write transfer diagnostics dictionary to file."""
+        return self.get_property_state("write_diagnostics")
+
+    @write_diagnostics.setter
+    def write_diagnostics(self, value: bool):
+        self.set_property_state("write_diagnostics", value)
+
+    @property
+    def write_weights_matrix(self) -> bool:
+        """Write mapping weights to file after calculation."""
+        return self.get_property_state("write_weights_matrix")
+
+    @write_weights_matrix.setter
+    def write_weights_matrix(self, value: bool):
+        self.set_property_state("write_weights_matrix", value)
+
+    @property
+    def write_residuals(self) -> bool:
+        """Write residuals to results files."""
+        return self.get_property_state("write_residuals")
+
+    @write_residuals.setter
+    def write_residuals(self, value: bool):
+        self.set_property_state("write_residuals", value)
+
+    @property
+    def output_frequency(self) -> int:
+        """Specify output frequency."""
+        return self.get_property_state("output_frequency")
+
+    @output_frequency.setter
+    def output_frequency(self, value: int):
+        self.set_property_state("output_frequency", value)

ansys/systemcoupling/core/adaptor/api_25_1/parameter.py

@@ -0,0 +1,20 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+from .parameter_child import parameter_child
+
+
+class parameter(NamedContainer[parameter_child]):
+    """
+    Configure a parameter for the coupling participant.
+    """
+
+    syc_name = "Parameter"
+
+    child_object_type: parameter_child = parameter_child
+    """
+    child_object_type of parameter.
+    """

ansys/systemcoupling/core/adaptor/api_25_1/parameter_child.py

@@ -0,0 +1,60 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class parameter_child(Container):
+    """
+    Configure a parameter for the coupling participant.
+    """
+
+    syc_name = "child_object_type"
+
+    property_names_types = [
+        ("participant_display_name", "ParticipantDisplayName", "str"),
+        ("display_name", "DisplayName", "str"),
+        ("data_type", "DataType", "str"),
+        ("tensor_type", "TensorType", "str"),
+    ]
+
+    @property
+    def participant_display_name(self) -> str:
+        """Parameter's display name as defined by the participant solver."""
+        return self.get_property_state("participant_display_name")
+
+    @participant_display_name.setter
+    def participant_display_name(self, value: str):
+        self.set_property_state("participant_display_name", value)
+
+    @property
+    def display_name(self) -> str:
+        """Parameter's display name as defined in System Coupling."""
+        return self.get_property_state("display_name")
+
+    @display_name.setter
+    def display_name(self, value: str):
+        self.set_property_state("display_name", value)
+
+    @property
+    def data_type(self) -> str:
+        """Parameter's data type as reported by the participant.
+
+        Allowed values:
+
+        - Real"""
+        return self.get_property_state("data_type")
+
+    @data_type.setter
+    def data_type(self, value: str):
+        self.set_property_state("data_type", value)
+
+    @property
+    def tensor_type(self) -> str:
+        """Indicates the parameter tensor type (\"Scalar\" only)."""
+        return self.get_property_state("tensor_type")
+
+    @tensor_type.setter
+    def tensor_type(self, value: str):
+        self.set_property_state("tensor_type", value)

ansys/systemcoupling/core/adaptor/api_25_1/partition_participants.py

@@ -0,0 +1,138 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class partition_participants(Command):
+    """
+    Provide a utility for setting the parallel algorithm, parallel partitioning
+    fractions for each participant, and machine list information.
+
+    At least one participant must be defined for this command to be used. Use
+    of this command is not recommended if participants are already running.
+
+    Parameters
+    ----------
+    algorithm_name : str, optional
+        Name of the partitioning algorithm. Available algorithms are:
+
+        - \"SharedAllocateMachines\" (default)
+        - \"SharedAllocateCores\"
+        - \"DistributedAllocateMachines\"
+        - \"DistributedAllocateCores\"
+        - \"Custom\" (see ``partitioning_info`` for more details)
+
+        The algorithms allow for both shared and distributed execution and for
+        the allocation of machines or cores. The default value is generally the
+        best choice, as it allows for each participant to take advantage of all
+        the allocated resources. The other partitioning methods are provided to
+        handle situations where not enough resources are available to run the
+        same machines.
+
+        See the System Coupling documentation for more details of the
+        partitioning algorithms.
+    names_and_fractions : List, optional
+        List of tuples specifying the fractions of core count applied for
+        each participant
+
+        Each tuple must have the participant name as its first item and the
+        associated fraction as its second item. If this parameter is omitted,
+        then cores will be allocated for all participants set in the
+        data model.
+    machine_list : List, optional
+        List of dictionaries specifying machines available for distributed run.
+        Each dictionary must have a key \"machine-name\" with machine name as its
+        value, and key \"core-count\" with number of cores for that machine as
+        its value. Providing this argument will override any machine list
+        information detected from the scheduler environment and any information
+        provided by the ``--cnf`` command-line argument.
+    partitioning_info : Dict, optional
+        Dictionary specifying machines resources assigned to each participant by user.
+        Dictionary must have participant names as keys and machine lists containing
+        machine resources as values. The value of a ``partitioning_info`` machine list is
+        a list of dictionaries specifying machines assigned to corresponding participants.
+        Each dictionary of the machine list must have a key \"machine-name\" with the
+        machine name as its value, and key \"core-count\" with number of cores for that
+        machine as its value.
+
+        Providing this argument will disallow other arguments except ``algorithm_name``,
+        which must set as \"Custom\" if provided. Otherwise, ``algorithm_name`` will be
+        set as \"Custom\" internally if ``partitioning_info`` is provided.
+
+    """
+
+    syc_name = "PartitionParticipants"
+
+    argument_names = [
+        "algorithm_name",
+        "names_and_fractions",
+        "machine_list",
+        "partitioning_info",
+    ]
+
+    class algorithm_name(String):
+        """
+        Name of the partitioning algorithm. Available algorithms are:
+
+        - \"SharedAllocateMachines\" (default)
+        - \"SharedAllocateCores\"
+        - \"DistributedAllocateMachines\"
+        - \"DistributedAllocateCores\"
+        - \"Custom\" (see ``partitioning_info`` for more details)
+
+        The algorithms allow for both shared and distributed execution and for
+        the allocation of machines or cores. The default value is generally the
+        best choice, as it allows for each participant to take advantage of all
+        the allocated resources. The other partitioning methods are provided to
+        handle situations where not enough resources are available to run the
+        same machines.
+
+        See the System Coupling documentation for more details of the
+        partitioning algorithms.
+        """
+
+        syc_name = "AlgorithmName"
+
+    class names_and_fractions(StrFloatPairList):
+        """
+        List of tuples specifying the fractions of core count applied for
+        each participant
+
+        Each tuple must have the participant name as its first item and the
+        associated fraction as its second item. If this parameter is omitted,
+        then cores will be allocated for all participants set in the
+        data model.
+        """
+
+        syc_name = "NamesAndFractions"
+
+    class machine_list(StrOrIntDictList):
+        """
+        List of dictionaries specifying machines available for distributed run.
+        Each dictionary must have a key \"machine-name\" with machine name as its
+        value, and key \"core-count\" with number of cores for that machine as
+        its value. Providing this argument will override any machine list
+        information detected from the scheduler environment and any information
+        provided by the ``--cnf`` command-line argument.
+        """
+
+        syc_name = "MachineList"
+
+    class partitioning_info(StrOrIntDictListDict):
+        """
+        Dictionary specifying machines resources assigned to each participant by user.
+        Dictionary must have participant names as keys and machine lists containing
+        machine resources as values. The value of a ``partitioning_info`` machine list is
+        a list of dictionaries specifying machines assigned to corresponding participants.
+        Each dictionary of the machine list must have a key \"machine-name\" with the
+        machine name as its value, and key \"core-count\" with number of cores for that
+        machine as its value.
+
+        Providing this argument will disallow other arguments except ``algorithm_name``,
+        which must set as \"Custom\" if provided. Otherwise, ``algorithm_name`` will be
+        set as \"Custom\" internally if ``partitioning_info`` is provided.
+        """
+
+        syc_name = "PartitioningInfo"

ansys/systemcoupling/core/adaptor/api_25_1/properties.py

@@ -0,0 +1,36 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class properties(Container):
+    """
+    UNDOCUMENTED
+    """
+
+    syc_name = "Properties"
+
+    property_names_types = [
+        ("accepts_new_inputs", "AcceptsNewInputs", "bool"),
+        ("time_integration", "TimeIntegration", "str"),
+    ]
+
+    @property
+    def accepts_new_inputs(self) -> bool:
+        """Controls whether participant accept new input variables or parameters."""
+        return self.get_property_state("accepts_new_inputs")
+
+    @accepts_new_inputs.setter
+    def accepts_new_inputs(self, value: bool):
+        self.set_property_state("accepts_new_inputs", value)
+
+    @property
+    def time_integration(self) -> str:
+        """Coupling participant time integration method (\"Implicit\" or \"Explicit\")"""
+        return self.get_property_state("time_integration")
+
+    @time_integration.setter
+    def time_integration(self, value: str):
+        self.set_property_state("time_integration", value)

ansys/systemcoupling/core/adaptor/api_25_1/record_interactions.py

@@ -0,0 +1,46 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+
+class record_interactions(Container):
+    """
+    "Controls whether the System Coupling Participant library will record the setup and solution data files for testing and debugging.
+    """
+
+    syc_name = "RecordInteractions"
+
+    property_names_types = [
+        ("record_setup", "RecordSetup", "bool"),
+        ("record_solution", "RecordSolution", "bool"),
+        ("record_precision", "RecordPrecision", "int"),
+    ]
+
+    @property
+    def record_setup(self) -> bool:
+        """Flag indicating whether participant record scp file."""
+        return self.get_property_state("record_setup")
+
+    @record_setup.setter
+    def record_setup(self, value: bool):
+        self.set_property_state("record_setup", value)
+
+    @property
+    def record_solution(self) -> bool:
+        """Flag indicating whether participant record solution files."""
+        return self.get_property_state("record_solution")
+
+    @record_solution.setter
+    def record_solution(self, value: bool):
+        self.set_property_state("record_solution", value)
+
+    @property
+    def record_precision(self) -> int:
+        """Set the digital precision of solution variable,1 <= N <= 16.."""
+        return self.get_property_state("record_precision")
+
+    @record_precision.setter
+    def record_precision(self, value: int):
+        self.set_property_state("record_precision", value)

ansys/systemcoupling/core/adaptor/api_25_1/reference_frame.py

@@ -0,0 +1,20 @@
+#
+# This is an auto-generated file.  DO NOT EDIT!
+#
+
+from ansys.systemcoupling.core.adaptor.impl.types import *
+
+from .reference_frame_child import reference_frame_child
+
+
+class reference_frame(NamedContainer[reference_frame_child]):
+    """
+    Provide a transformation relative to a ParentReferenceFrame.
+    """
+
+    syc_name = "ReferenceFrame"
+
+    child_object_type: reference_frame_child = reference_frame_child
+    """
+    child_object_type of reference_frame.
+    """