ansys-systemcoupling-core 0.9.0__py3-none-any.whl → 0.10.0__py3-none-any.whl

ansys/systemcoupling/core/__init__.py

@@ -72,7 +72,7 @@ def launch(
         (The forms ``"24.1"`` and ``"24_1"`` are also acceptable.)
         The version will be sought in the standard installation location. The
         default is ``None``, which is equivalent to specifying
-        ``"251"`` ("2025 R1" release), unless either of the environment
+        ``"252"`` ("2025 R2" release), unless either of the environment
         variables ``SYSC_ROOT`` or ``AWP_ROOT`` has been set. It is considered
         to be an error if either these is set *and* ``version`` is provided.
     start_output: bool, optional

ansys/systemcoupling/core/adaptor/api_25_2/add_data_transfer.py

@@ -9,10 +9,10 @@ class add_data_transfer(Command):
     """
     Adds data transfer based on arguments that specify the interface, target
     side, and variables to be associated with each side of the interface.
-    The command requires that you specify variables using their names (see
-    parameter descriptions for details). Either a variable-based or
+    The command requires that you specify variables using their names, as
+    described below in Essential Keyword Arguments. Either a variable-based or
     expression-based data transfer may be created with this command based on
-    the arguments provided. If a variable-based data transfer argument
+    the Optional Keyword Arguments. If a variable-based data transfer argument
     is given, then no expression-based data transfer arguments can be used. If
     an expression-based data transfer argument is given, then no variable-based
     data transfer arguments can be used.
@@ -36,8 +36,8 @@ class add_data_transfer(Command):
     target_variable : str, optional
         String specifying the name of the variable on the target side of
         the data transfer. Must be combined with either ``source_variable`` (when
-        creating a variable-based data transfer) or with ``value`` (or
-        ``value_{x|y|z}`` (when creating an expression-based data transfer).
+        creating a variable-based data transfer) or with ``value_{x|y|z}``
+        (when creating an expression-based data transfer).
     value : str, optional
         String specifying the expression to use on the source side of the data
         transfer. Used when creating an expression-based data transfer. If the
@@ -48,7 +48,7 @@ class add_data_transfer(Command):
         String specifying the X component of the expression to use on the
         source side of the data transfer. This may optionally be used when creating
         an expression-based data transfer if the ``target_variable`` is a vector as an
-        alternative to specifying a vector-valued expression in ``value`. ``value_y`` and
+        alternative to specifying a vector-valued expression in ``value``. ``value_y`` and
         ``value_z`` are also required if ``value_x`` is used.
     value_y : str, optional
         String specifying the Y component of the expression to use on the
@@ -119,8 +119,8 @@ class add_data_transfer(Command):
         """
         String specifying the name of the variable on the target side of
         the data transfer. Must be combined with either ``source_variable`` (when
-        creating a variable-based data transfer) or with ``value`` (or
-        ``value_{x|y|z}`` (when creating an expression-based data transfer).
+        creating a variable-based data transfer) or with ``value_{x|y|z}``
+        (when creating an expression-based data transfer).
         """
 
         syc_name = "TargetVariable"
@@ -141,7 +141,7 @@ class add_data_transfer(Command):
         String specifying the X component of the expression to use on the
         source side of the data transfer. This may optionally be used when creating
         an expression-based data transfer if the ``target_variable`` is a vector as an
-        alternative to specifying a vector-valued expression in ``value`. ``value_y`` and
+        alternative to specifying a vector-valued expression in ``value``. ``value_y`` and
         ``value_z`` are also required if ``value_x`` is used.
         """
 

ansys/systemcoupling/core/adaptor/api_25_2/add_interface.py

@@ -10,7 +10,7 @@ class add_interface(Command):
     Adds an interface based on the participant and region names specified
     as arguments for each side of the interface. This command requires that
     you specify participants using their names as described below in
-    Essential Keyword Arguments. Non-FMU participants must provide a list
+    Essential Keyword Arguments. Non-FMU participants can provide a list
     of regions as described below in Optional Keyword Arguments. For FMU
     interfaces, specifying the regions are not allowed.
 

ansys/systemcoupling/core/adaptor/api_25_2/add_ordered_data_transfers.py

@@ -7,9 +7,18 @@ from ansys.systemcoupling.core.adaptor.impl.types import *
 
 class add_ordered_data_transfers(Command):
     """
-    Adds data transfer for each ordered pair of variables in an FMU-FMU interface.
-
-    Returns the name of the Data Transfers created.
+    Adds data transfer for each ordered pair of variables in an
+    FMU-FMU interface. Requires the FMU-FMU interface. Requires
+    that the target FMU has the same number of input variables
+    as the source FMU has output variables.
+    The transfers are added in order. That is, the n-th output
+    variable for side one will be connected to the n-th input
+    variable for side two. This is only available for interfaces
+    with FMUs on both side one and side two.
+
+    Data transfers will be created in both directions, if possible.
+
+    Returns the name of the data transfers created.
 
     Parameters
     ----------

ansys/systemcoupling/core/adaptor/api_25_2/add_participant.py

@@ -31,13 +31,8 @@ class add_participant(InjectedCommand):
 
     The remainder of the documentation describes the more usual non-session mode.
 
-    Adds a coupling participant to the data model.
-
-    When executed, this command adds the new participant to the analysis
-    without removing any interfaces or data transfers created previously.
-
+    Adds a coupling participant to the setup.
     Cannot be called after participants have been started.
-
     Returns the name of the participant.
 
     There are several options that can be selected to add the
@@ -76,8 +71,8 @@ class add_participant(InjectedCommand):
     input_file : str, optional
         Name of the input file for the participant to be added.
         Currently supported formats are SCP files, Forte input (FTSIM)
-        files, mechanical server (\*.rst) files, cfd server (\*.csv) files,
-        FMU (\*.fmu) files, and System Coupling data server (\*.scdt/axdt/csv) files.
+        files, Mechanical Server (\*.rst) files, CFD Server (\*.csv) files,
+        FMU (\*.fmu) files, and System Coupling Data Server (\*.scdt/axdt/csv) files.
     executable : str, optional
         Path to the executable file for the participant to be added.
     additional_arguments : str, optional
@@ -87,7 +82,17 @@ class add_participant(InjectedCommand):
     python_script : str, optional
         Instead of the executable, use a Python script and wrap it with
         System Coupling-provided .bat/.sh scripts to set up the environment
-        correctly before calling this Python script.
+        correctly before calling this Python script. On Windows, a few
+        lines will need to be included near the top of the Python script to
+        add the required dll directories as follows:
+
+        .. code-block:: python
+
+            import os
+            import sys
+            if sys.platform.startswith("win"):
+                for p in os.environ["PYTHON_DLL_PATH"].split(os.pathsep):
+                    os.add_dll_directory(p)
 
     """
 
@@ -125,8 +130,8 @@ class add_participant(InjectedCommand):
         """
         Name of the input file for the participant to be added.
         Currently supported formats are SCP files, Forte input (FTSIM)
-        files, mechanical server (\*.rst) files, cfd server (\*.csv) files,
-        FMU (\*.fmu) files, and System Coupling data server (\*.scdt/axdt/csv) files.
+        files, Mechanical Server (\*.rst) files, CFD Server (\*.csv) files,
+        FMU (\*.fmu) files, and System Coupling Data Server (\*.scdt/axdt/csv) files.
         """
 
         syc_name = "InputFile"
@@ -156,7 +161,17 @@ class add_participant(InjectedCommand):
         """
         Instead of the executable, use a Python script and wrap it with
         System Coupling-provided .bat/.sh scripts to set up the environment
-        correctly before calling this Python script.
+        correctly before calling this Python script. On Windows, a few
+        lines will need to be included near the top of the Python script to
+        add the required dll directories as follows:
+
+        .. code-block:: python
+
+            import os
+            import sys
+            if sys.platform.startswith("win"):
+                for p in os.environ["PYTHON_DLL_PATH"].split(os.pathsep):
+                    os.add_dll_directory(p)
         """
 
         syc_name = "PythonScript"

ansys/systemcoupling/core/adaptor/api_25_2/add_transformation.py

@@ -28,22 +28,22 @@ class add_transformation(Command):
     reference_frame : str
         Name of the reference frame to which the transformation will be added.
     transformation_type : str
-        Type of transformation to be added. Available options are \"Rotation\" or
-        \"Translation\".
+        Type of transformation to be added. Available options are Rotation or
+        Translation
 
         Required Parameters for Transformation Types:
             Rotation: ``angle``, ``axis``, ``vector`` (if ``axis`` is \"UserDefined\")
             Translation: ``vector``
     angle : real, optional
-        Angle to rotate a reference frame. Used with \"Rotation\"
+        Angle to rotate a reference frame. Used with Rotation
         ``transformation_type``. Default unit is Radians.
     axis : str, optional
         Axis about which a rotation is applied. Used with
-        Rotation ``transformation_type``. Available options are: \"XAxis\", \"YAxis\",
-        \"ZAxis\", and \"UserDefined\".
+        Rotation ``transformation_type``. Available options are: "XAxis", "YAxis",
+        "ZAxis", and "UserDefined".
     vector : Tuple, optional
-        A vector for use with \"Translation\" ``transformation_type`` or \"Rotation\"
-        ``transformation_type`` if the ``axis`` is \"UserDefined\".
+        A vector for use with Translation ``transformation_type`` or Rotation
+        ``transformation_type`` if the ``axis`` is "UserDefined".
 
     """
 
@@ -66,8 +66,8 @@ class add_transformation(Command):
 
     class transformation_type(String):
         """
-        Type of transformation to be added. Available options are \"Rotation\" or
-        \"Translation\".
+        Type of transformation to be added. Available options are Rotation or
+        Translation
 
         Required Parameters for Transformation Types:
             Rotation: ``angle``, ``axis``, ``vector`` (if ``axis`` is \"UserDefined\")
@@ -78,7 +78,7 @@ class add_transformation(Command):
 
     class angle(Real):
         """
-        Angle to rotate a reference frame. Used with \"Rotation\"
+        Angle to rotate a reference frame. Used with Rotation
         ``transformation_type``. Default unit is Radians.
         """
 
@@ -87,16 +87,16 @@ class add_transformation(Command):
     class axis(String):
         """
         Axis about which a rotation is applied. Used with
-        Rotation ``transformation_type``. Available options are: \"XAxis\", \"YAxis\",
-        \"ZAxis\", and \"UserDefined\".
+        Rotation ``transformation_type``. Available options are: "XAxis", "YAxis",
+        "ZAxis", and "UserDefined".
         """
 
         syc_name = "Axis"
 
     class vector(RealVector):
         """
-        A vector for use with \"Translation\" ``transformation_type`` or \"Rotation\"
-        ``transformation_type`` if the ``axis`` is \"UserDefined\".
+        A vector for use with Translation ``transformation_type`` or Rotation
+        ``transformation_type`` if the ``axis`` is "UserDefined".
         """
 
         syc_name = "Vector"

ansys/systemcoupling/core/adaptor/api_25_2/analysis_control.py

@@ -79,6 +79,9 @@ class analysis_control(Container):
         ("check_for_input_files_changes", "CheckForInputFilesChanges", "str"),
         ("is_user_friendly_mapping", "IsUserFriendlyMapping", "bool"),
         ("reduce_informational_output", "ReduceInformationalOutput", "bool"),
+        ("participant_precision", "ParticipantPrecision", "str"),
+        ("avoid_rbf", "AvoidRBF", "str"),
+        ("interactive_initialization", "InteractiveInitialization", "bool"),
     ]
 
     @property
@@ -301,3 +304,30 @@ class analysis_control(Container):
     @reduce_informational_output.setter
     def reduce_informational_output(self, value: bool):
         self.set_property_state("reduce_informational_output", value)
+
+    @property
+    def participant_precision(self) -> str:
+        """Set global option for participant precision"""
+        return self.get_property_state("participant_precision")
+
+    @participant_precision.setter
+    def participant_precision(self, value: str):
+        self.set_property_state("participant_precision", value)
+
+    @property
+    def avoid_rbf(self) -> str:
+        """UNDOCUMENTED"""
+        return self.get_property_state("avoid_rbf")
+
+    @avoid_rbf.setter
+    def avoid_rbf(self, value: str):
+        self.set_property_state("avoid_rbf", value)
+
+    @property
+    def interactive_initialization(self) -> bool:
+        """Controls whether using interactive initialization for cosim"""
+        return self.get_property_state("interactive_initialization")
+
+    @interactive_initialization.setter
+    def interactive_initialization(self, value: bool):
+        self.set_property_state("interactive_initialization", value)

ansys/systemcoupling/core/adaptor/api_25_2/attribute.py

@@ -9,7 +9,7 @@ from .attribute_child import attribute_child
 
 class attribute(NamedContainer[attribute_child]):
     """
-    Configure a variable's attributes.
+    Configure an attribute.
     """
 
     syc_name = "Attribute"

ansys/systemcoupling/core/adaptor/api_25_2/attribute_child.py

@@ -9,7 +9,7 @@ from .dimensionality import dimensionality
 
 class attribute_child(Container):
     """
-    Configure a variable's attributes.
+    Configure an attribute.
     """
 
     syc_name = "child_object_type"
@@ -25,11 +25,12 @@ class attribute_child(Container):
         ("modifiable", "Modifiable", "bool"),
         ("real_value", "RealValue", "RealType"),
         ("integer_value", "IntegerValue", "int"),
+        ("string_value", "StringValue", "str"),
     ]
 
     @property
     def attribute_type(self) -> str:
-        """The type of the attribute (\"Real\" or \"Integer\")."""
+        """The type of the attribute (\"Real\", \"Integer\", or \"String\")."""
         return self.get_property_state("attribute_type")
 
     @attribute_type.setter
@@ -62,3 +63,12 @@ class attribute_child(Container):
     @integer_value.setter
     def integer_value(self, value: int):
         self.set_property_state("integer_value", value)
+
+    @property
+    def string_value(self) -> str:
+        """String attribute value."""
+        return self.get_property_state("string_value")
+
+    @string_value.setter
+    def string_value(self, value: str):
+        self.set_property_state("string_value", value)

ansys/systemcoupling/core/adaptor/api_25_2/case_root.py

@@ -2,7 +2,7 @@
 # This is an auto-generated file.  DO NOT EDIT!
 #
 
-SHASH = "34d232b251e1d4a5a6b88e3deb9591863eac6afb1446228951276f9b1700da9f"
+SHASH = "959d876aeac97f5477abdc73030965f3b5cf57f93648d88535c634374191caa8"
 
 from ansys.systemcoupling.core.adaptor.impl.types import *
 

ansys/systemcoupling/core/adaptor/api_25_2/create_restart_point.py

@@ -13,17 +13,16 @@ class create_restart_point(Command):
     Signals the System Coupling service and all coupling participants that a
     restart point should be created before the next coupling step begins. The
     restart point is created in addition to restart points created by the
-    ``output_control`` setting in the data model.
+    '``output_control`` setting in the data model.
 
     Note that some participants write their restart files only when the
     coupling run resumes, so their files will not be available immediately
     after the command is issued.
 
     Results information for the coupling step is written to a file named
-    according to the convention ``Results_#.h5``, where ``_#`` is the number of
-    the coupling step. By default, the restart files are written to the ``SyC``
-    directory, which is automatically created by the System Coupling service
-    when restart points are created.
+    according to the convention ``Results_step<#>|iter<#>.h5``, where ``#`` is the number of
+    the coupling step or iteration. The restart files are written to the "SyC"
+    directory, which is automatically created by System Coupling.
     """
 
     syc_name = "CreateRestartPoint"

ansys/systemcoupling/core/adaptor/api_25_2/data_transfer_child.py

@@ -170,7 +170,15 @@ class data_transfer_child(Container):
 
     @property
     def unmapped_value_option(self) -> str:
-        """Option to fill target values not mapped by the regular mapping algorithm"""
+        """Option to fill target values not mapped by the regular mapping algorithm.
+
+        Possible values:
+
+        - \"ProgramControlled\" - Program decides the best algorithm depending on the data topologies and locations.
+        - \"Nearest Value\" - Copy the data from the nearest mapped target location.
+        - \"Interpolation\" - Smoothly interpolate the data based on nearby mapped target locations.
+        - \"Extrapolation\" - Smoothly extrapolate the data based on nearby mapped target locations.
+        """
         return self.get_property_state("unmapped_value_option")
 
     @unmapped_value_option.setter

ansys/systemcoupling/core/adaptor/api_25_2/delete_snapshot.py

@@ -7,7 +7,9 @@ from ansys.systemcoupling.core.adaptor.impl.types import *
 
 class delete_snapshot(Command):
     """
-    Deletes a snapshot if it exists.
+    Deletes the specified snapshot.
+    If the snapshot does not exist, an error will
+    be raised.
 
     Parameters
     ----------

ansys/systemcoupling/core/adaptor/api_25_2/execution_control.py

@@ -47,6 +47,7 @@ class execution_control(Container):
         ("mass_normalized", "MassNormalized", "bool"),
         ("write_output", "WriteOutput", "bool"),
         ("environment_variables", "EnvironmentVariables", "StringListType"),
+        ("precision", "Precision", "str"),
     ]
 
     @property
@@ -254,3 +255,12 @@ class execution_control(Container):
     @environment_variables.setter
     def environment_variables(self, value: StringListType):
         self.set_property_state("environment_variables", value)
+
+    @property
+    def precision(self) -> str:
+        """Set precision for this participant"""
+        return self.get_property_state("precision")
+
+    @precision.setter
+    def precision(self, value: str):
+        self.set_property_state("precision", value)

ansys/systemcoupling/core/adaptor/api_25_2/generate_input_file.py

@@ -9,6 +9,18 @@ class generate_input_file(Command):
     """
     Generates the input journal file for a given Fluent participant.
 
+    Available for Fluent participants when ``fluent_input.option`` is not
+    set to ``journal_file``.
+
+    Given the participant's name and a file name, generates a Fluent
+    journal script which may be set as the value for the ``journal_file``
+    setting.
+
+    System Coupling uses the generated scrkpt for the coupled analysis.
+
+    Scripts generated using this method may be edited before the
+    coupled analysis is started.
+
     Parameters
     ----------
     participant_name : str

ansys/systemcoupling/core/adaptor/api_25_2/get_execution_command.py

@@ -7,7 +7,7 @@ from ansys.systemcoupling.core.adaptor.impl.types import *
 
 class get_execution_command(Command):
     """
-    Gets the execution command needed to start the specified participant
+    Gets the execution command needed to start the specified participant.
 
     Parameters
     ----------

ansys/systemcoupling/core/adaptor/api_25_2/get_machines.py

@@ -7,7 +7,28 @@ from ansys.systemcoupling.core.adaptor.impl.types import *
 
 class get_machines(Command):
     """
-    Get currently available machines.
+    Get a list of dictionaries with machine names and core counts for
+    the machines available for parallel processing.
+
+    Returns information in the following format::
+
+        [
+            {
+            'machine-name' : <machine-name-1 (str)>,
+            'core-count' : <core-count-1 (int)>
+            },
+            {
+            'machine-name' : <machine-name-2 (str)>,
+            'core-count' : <core-count-2 (int)>
+            },
+            ...
+        ]
+
+    Returns an empty list when machines and core counts are not
+    provided to System Coupling. You may specify those
+    by providing --cnf command-line option when starting System
+    Coupling. You can also specify those via the Parallel
+    Partitioning dialog box in the System Coupling GUI.
     """
 
     syc_name = "GetMachines"

ansys/systemcoupling/core/adaptor/api_25_2/get_region_names_for_participant.py

@@ -7,15 +7,16 @@ from ansys.systemcoupling.core.adaptor.impl.types import *
 
 class get_region_names_for_participant(Command):
     """
-    Gets all of the specified participant's regions.
+    This query is deprecated and will be deleted in future releases.
+    To get region names for a participant, you can use ``get_child_names``
+    query, for example:
 
-    Returns a dictionary with the regions as keys and the corresponding
-    display names as values.
+    ``setup.coupling_participant[name].region.get_child_names()```
 
     Parameters
     ----------
     participant_name : str
-        String indicating the participant for which regions are returned.
+        Name of the participant.
 
     """
 
@@ -25,7 +26,7 @@ class get_region_names_for_participant(Command):
 
     class participant_name(String):
         """
-        String indicating the participant for which regions are returned.
+        Name of the participant.
         """
 
         syc_name = "ParticipantName"

ansys/systemcoupling/core/adaptor/api_25_2/mapping_control.py

@@ -44,6 +44,12 @@ class mapping_control(Container):
         ("rbf_clipping_scale", "RBFClippingScale", "RealType"),
         ("rbf_max_extrapolation_factor", "RBFMaxExtrapolationFactor", "RealType"),
         ("clipping", "Clipping", "bool"),
+        ("max_search_radius", "MaxSearchRadius", "RealType"),
+        (
+            "extensive_data_unmapped_value_option",
+            "ExtensiveDataUnmappedValueOption",
+            "str",
+        ),
     ]
 
     @property
@@ -247,3 +253,21 @@ class mapping_control(Container):
     @clipping.setter
     def clipping(self, value: bool):
         self.set_property_state("clipping", value)
+
+    @property
+    def max_search_radius(self) -> RealType:
+        """Maximum search radius to use for point cloud mapping. The value is non-dimensionalized relative to the average spacing between source points."""
+        return self.get_property_state("max_search_radius")
+
+    @max_search_radius.setter
+    def max_search_radius(self, value: RealType):
+        self.set_property_state("max_search_radius", value)
+
+    @property
+    def extensive_data_unmapped_value_option(self) -> str:
+        """Option for handling of unmapped extensive data on target mesh. Allowed values are ProgramControlled, Interpolate, or ZeroFill."""
+        return self.get_property_state("extensive_data_unmapped_value_option")
+
+    @extensive_data_unmapped_value_option.setter
+    def extensive_data_unmapped_value_option(self, value: str):
+        self.set_property_state("extensive_data_unmapped_value_option", value)

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

@@ -15,35 +15,38 @@ class open(Command):
     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.
+    By default, 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.
+    If given optional arguments, behaves as described below in "Optional
+    Keyword Arguments".
 
     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.
+        Directory containing the .h5 file(s) to be read. When used, the
+        System Coupling Service looks for files in the specified directory.
+        Default is 'SyC'. It is recommend to not use anything other than
+        a default directory for the ``file_path``.
     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
+        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
+        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
+        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
@@ -61,8 +64,10 @@ class open(Command):
 
     class file_path(String):
         """
-        Working directory containing the ``SyC`` subdirectory (and its .h5
-        file(s)) to be read.
+        Directory containing the .h5 file(s) to be read. When used, the
+        System Coupling Service looks for files in the specified directory.
+        Default is 'SyC'. It is recommend to not use anything other than
+        a default directory for the ``file_path``.
         """
 
         syc_name = "FilePath"
@@ -71,13 +76,13 @@ class open(Command):
         """
         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
+        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
+        argument. If the simulation's ``results`` files are associated with
         coupling iterations, then System Coupling prints an error message
         indicating this.
         """
@@ -88,7 +93,7 @@ class open(Command):
         """
         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
+        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