ansys-systemcoupling-core 0.5.0__py3-none-any.whl → 0.7.0__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of ansys-systemcoupling-core might be problematic. Click here for more details.
- ansys/systemcoupling/core/__init__.py +11 -5
- ansys/systemcoupling/core/adaptor/api_23_1/add_interface.py +2 -2
- ansys/systemcoupling/core/adaptor/api_23_1/add_interface_by_display_names.py +2 -2
- ansys/systemcoupling/core/adaptor/api_23_1/add_transformation.py +1 -1
- ansys/systemcoupling/core/adaptor/api_23_1/partition_participants.py +3 -3
- ansys/systemcoupling/core/adaptor/api_23_1/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_23_1/solution_root.py +7 -1
- ansys/systemcoupling/core/adaptor/api_23_1/start_participants.py +1 -1
- ansys/systemcoupling/core/adaptor/api_23_2/add_interface.py +2 -2
- ansys/systemcoupling/core/adaptor/api_23_2/add_interface_by_display_names.py +2 -2
- ansys/systemcoupling/core/adaptor/api_23_2/add_transformation.py +1 -1
- ansys/systemcoupling/core/adaptor/api_23_2/partition_participants.py +3 -3
- ansys/systemcoupling/core/adaptor/api_23_2/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_23_2/solution_root.py +7 -1
- ansys/systemcoupling/core/adaptor/api_23_2/start_participants.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_1/add_aerodamping_data_transfers.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_1/add_interface.py +2 -2
- ansys/systemcoupling/core/adaptor/api_24_1/add_interface_by_display_names.py +2 -2
- ansys/systemcoupling/core/adaptor/api_24_1/add_transformation.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_1/partition_participants.py +3 -3
- ansys/systemcoupling/core/adaptor/api_24_1/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_24_1/solution_root.py +7 -1
- ansys/systemcoupling/core/adaptor/api_24_1/start_participants.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_2/add_aerodamping_data_transfers.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_2/add_interface.py +2 -2
- ansys/systemcoupling/core/adaptor/api_24_2/add_interface_by_display_names.py +2 -2
- ansys/systemcoupling/core/adaptor/api_24_2/add_participant.py +4 -4
- ansys/systemcoupling/core/adaptor/api_24_2/add_transformation.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_2/partition_participants.py +3 -3
- ansys/systemcoupling/core/adaptor/api_24_2/setup_root.py +1 -1
- ansys/systemcoupling/core/adaptor/api_24_2/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_24_2/solution_root.py +7 -1
- ansys/systemcoupling/core/adaptor/api_24_2/start_participants.py +1 -1
- ansys/systemcoupling/core/adaptor/api_25_1/_add_participant.py +80 -0
- ansys/systemcoupling/core/adaptor/api_25_1/_clear_state.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_1/_solve.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_1/abort.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_1/activate_hidden.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_aerodamping_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_data_transfer.py +190 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_data_transfer_by_display_names.py +191 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_expression_function.py +61 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_flow_boundary_data_transfers.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_fsi_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_interface.py +77 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_interface_by_display_names.py +78 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_named_expression.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_ordered_data_transfers.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_participant.py +162 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_reference_frame.py +40 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_thermal_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_1/add_transformation.py +102 -0
- ansys/systemcoupling/core/adaptor/api_25_1/analysis_control.py +293 -0
- ansys/systemcoupling/core/adaptor/api_25_1/apip.py +33 -0
- ansys/systemcoupling/core/adaptor/api_25_1/ascii_output.py +44 -0
- ansys/systemcoupling/core/adaptor/api_25_1/attribute.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/attribute_child.py +64 -0
- ansys/systemcoupling/core/adaptor/api_25_1/automatic_alignment_options.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_1/available_ports.py +40 -0
- ansys/systemcoupling/core/adaptor/api_25_1/avoid_data_reconstruction.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_1/case_root.py +62 -0
- ansys/systemcoupling/core/adaptor/api_25_1/clear_state.py +18 -0
- ansys/systemcoupling/core/adaptor/api_25_1/connect_ensight_dvs.py +41 -0
- ansys/systemcoupling/core/adaptor/api_25_1/coupling_interface.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/coupling_interface_child.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_1/coupling_participant.py +23 -0
- ansys/systemcoupling/core/adaptor/api_25_1/coupling_participant_child.py +271 -0
- ansys/systemcoupling/core/adaptor/api_25_1/create_restart_point.py +29 -0
- ansys/systemcoupling/core/adaptor/api_25_1/data_transfer.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/data_transfer_child.py +187 -0
- ansys/systemcoupling/core/adaptor/api_25_1/delete_snapshot.py +28 -0
- ansys/systemcoupling/core/adaptor/api_25_1/delete_transformation.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_1/dimensionality.py +96 -0
- ansys/systemcoupling/core/adaptor/api_25_1/execution_control.py +246 -0
- ansys/systemcoupling/core/adaptor/api_25_1/execution_control_1.py +24 -0
- ansys/systemcoupling/core/adaptor/api_25_1/expression.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/expression_child.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_1/expression_function.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/expression_function_child.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_1/external_data_file.py +24 -0
- ansys/systemcoupling/core/adaptor/api_25_1/fluent_input.py +77 -0
- ansys/systemcoupling/core/adaptor/api_25_1/fmu_parameter.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/fmu_parameter_child.py +164 -0
- ansys/systemcoupling/core/adaptor/api_25_1/generate_input_file.py +41 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_add_data_transfer_group_commands.py +29 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_execution_command.py +30 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_machines.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_mode_shape_variables.py +29 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_region_names_for_participant.py +31 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_setup_summary.py +25 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_status_messages.py +52 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_supported_participant_types.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_thermal_data_transfer_options.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_1/get_transformation.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_1/global_stabilization.py +155 -0
- ansys/systemcoupling/core/adaptor/api_25_1/has_input_file_changed.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_1/import_system_coupling_input_file.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_1/initialize.py +27 -0
- ansys/systemcoupling/core/adaptor/api_25_1/instancing.py +23 -0
- ansys/systemcoupling/core/adaptor/api_25_1/instancing_child.py +62 -0
- ansys/systemcoupling/core/adaptor/api_25_1/interrupt.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_1/library.py +37 -0
- ansys/systemcoupling/core/adaptor/api_25_1/live_visualization.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/live_visualization_child.py +100 -0
- ansys/systemcoupling/core/adaptor/api_25_1/mapping_control.py +239 -0
- ansys/systemcoupling/core/adaptor/api_25_1/open.py +102 -0
- ansys/systemcoupling/core/adaptor/api_25_1/open_results_in_ensight.py +56 -0
- ansys/systemcoupling/core/adaptor/api_25_1/open_snapshot.py +37 -0
- ansys/systemcoupling/core/adaptor/api_25_1/output_control.py +134 -0
- ansys/systemcoupling/core/adaptor/api_25_1/parameter.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/parameter_child.py +60 -0
- ansys/systemcoupling/core/adaptor/api_25_1/partition_participants.py +138 -0
- ansys/systemcoupling/core/adaptor/api_25_1/properties.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_1/record_interactions.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_1/reference_frame.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/reference_frame_child.py +71 -0
- ansys/systemcoupling/core/adaptor/api_25_1/region.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/region_child.py +71 -0
- ansys/systemcoupling/core/adaptor/api_25_1/reload_expression_function_modules.py +14 -0
- ansys/systemcoupling/core/adaptor/api_25_1/results.py +89 -0
- ansys/systemcoupling/core/adaptor/api_25_1/save.py +51 -0
- ansys/systemcoupling/core/adaptor/api_25_1/save_snapshot.py +54 -0
- ansys/systemcoupling/core/adaptor/api_25_1/setup_root.py +259 -0
- ansys/systemcoupling/core/adaptor/api_25_1/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_25_1/shutdown.py +25 -0
- ansys/systemcoupling/core/adaptor/api_25_1/side.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/side_child.py +56 -0
- ansys/systemcoupling/core/adaptor/api_25_1/solution_control.py +115 -0
- ansys/systemcoupling/core/adaptor/api_25_1/solution_root.py +122 -0
- ansys/systemcoupling/core/adaptor/api_25_1/solve.py +30 -0
- ansys/systemcoupling/core/adaptor/api_25_1/stabilization.py +157 -0
- ansys/systemcoupling/core/adaptor/api_25_1/start_participants.py +47 -0
- ansys/systemcoupling/core/adaptor/api_25_1/step.py +57 -0
- ansys/systemcoupling/core/adaptor/api_25_1/transformation.py +21 -0
- ansys/systemcoupling/core/adaptor/api_25_1/transformation_child.py +62 -0
- ansys/systemcoupling/core/adaptor/api_25_1/type.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_1/unmapped_value_options.py +158 -0
- ansys/systemcoupling/core/adaptor/api_25_1/update_control.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_1/update_participant.py +61 -0
- ansys/systemcoupling/core/adaptor/api_25_1/variable.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_1/variable_child.py +231 -0
- ansys/systemcoupling/core/adaptor/api_25_1/write_csv_chart_files.py +21 -0
- ansys/systemcoupling/core/adaptor/api_25_1/write_ensight.py +46 -0
- ansys/systemcoupling/core/adaptor/impl/injected_commands.py +217 -32
- ansys/systemcoupling/core/adaptor/impl/static_info.py +17 -0
- ansys/systemcoupling/core/adaptor/impl/syc_proxy.py +3 -0
- ansys/systemcoupling/core/adaptor/impl/syc_proxy_interface.py +4 -0
- ansys/systemcoupling/core/adaptor/impl/types.py +1 -1
- ansys/systemcoupling/core/charts/chart_datatypes.py +169 -0
- ansys/systemcoupling/core/charts/csv_chartdata.py +299 -0
- ansys/systemcoupling/core/charts/live_csv_datasource.py +87 -0
- ansys/systemcoupling/core/charts/message_dispatcher.py +84 -0
- ansys/systemcoupling/core/charts/plot_functions.py +92 -0
- ansys/systemcoupling/core/charts/plotdefinition_manager.py +303 -0
- ansys/systemcoupling/core/charts/plotter.py +343 -0
- ansys/systemcoupling/core/client/grpc_client.py +6 -1
- ansys/systemcoupling/core/client/syc_container.py +12 -0
- ansys/systemcoupling/core/examples/downloads.py +17 -26
- ansys/systemcoupling/core/participant/manager.py +25 -9
- ansys/systemcoupling/core/participant/protocol.py +1 -0
- ansys/systemcoupling/core/session.py +23 -9
- ansys/systemcoupling/core/syc_version.py +1 -1
- ansys/systemcoupling/core/util/file_transfer.py +14 -0
- {ansys_systemcoupling_core-0.5.0.dist-info → ansys_systemcoupling_core-0.7.0.dist-info}/METADATA +20 -20
- {ansys_systemcoupling_core-0.5.0.dist-info → ansys_systemcoupling_core-0.7.0.dist-info}/RECORD +167 -46
- {ansys_systemcoupling_core-0.5.0.dist-info → ansys_systemcoupling_core-0.7.0.dist-info}/LICENSE +0 -0
- {ansys_systemcoupling_core-0.5.0.dist-info → ansys_systemcoupling_core-0.7.0.dist-info}/WHEEL +0 -0
|
@@ -24,13 +24,13 @@ class add_interface_by_display_names(Command):
|
|
|
24
24
|
side_one_participant : str
|
|
25
25
|
String indicating the name of the participant to be associated with
|
|
26
26
|
side \"One\" of the interface.
|
|
27
|
-
side_one_regions :
|
|
27
|
+
side_one_regions : List
|
|
28
28
|
List specifying the name(s) of region(s) to be added to side \"One\" of
|
|
29
29
|
the interface.
|
|
30
30
|
side_two_participant : str
|
|
31
31
|
String indicating the name of the participant to be associated with
|
|
32
32
|
side \"Two\" of the interface.
|
|
33
|
-
side_two_regions :
|
|
33
|
+
side_two_regions : List
|
|
34
34
|
List specifying the name(s) of region(s) to be added to side \"Two\"
|
|
35
35
|
of the interface.
|
|
36
36
|
|
|
@@ -76,8 +76,8 @@ class add_participant(InjectedCommand):
|
|
|
76
76
|
input_file : str, optional
|
|
77
77
|
Name of the input file for the participant to be added.
|
|
78
78
|
Currently supported formats are SCP files, Forte input (FTSIM)
|
|
79
|
-
files, mechanical server (
|
|
80
|
-
FMU (.fmu) files, and System Coupling data server (
|
|
79
|
+
files, mechanical server (\*.rst) files, cfd server (\*.csv) files,
|
|
80
|
+
FMU (.fmu) files, and System Coupling data server (\*.scdt/axdt/csv) files.
|
|
81
81
|
executable : str, optional
|
|
82
82
|
Path to the executable file for the participant to be added.
|
|
83
83
|
additional_arguments : str, optional
|
|
@@ -125,8 +125,8 @@ class add_participant(InjectedCommand):
|
|
|
125
125
|
"""
|
|
126
126
|
Name of the input file for the participant to be added.
|
|
127
127
|
Currently supported formats are SCP files, Forte input (FTSIM)
|
|
128
|
-
files, mechanical server (
|
|
129
|
-
FMU (.fmu) files, and System Coupling data server (
|
|
128
|
+
files, mechanical server (\*.rst) files, cfd server (\*.csv) files,
|
|
129
|
+
FMU (.fmu) files, and System Coupling data server (\*.scdt/axdt/csv) files.
|
|
130
130
|
"""
|
|
131
131
|
|
|
132
132
|
syc_name = "InputFile"
|
|
@@ -41,7 +41,7 @@ class add_transformation(Command):
|
|
|
41
41
|
Axis about which a rotation is applied. Used with
|
|
42
42
|
Rotation ``transformation_type``. Available options are: \"XAxis\", \"YAxis\",
|
|
43
43
|
\"ZAxis\", and \"UserDefined\".
|
|
44
|
-
vector :
|
|
44
|
+
vector : Tuple, optional
|
|
45
45
|
A vector for use with \"Translation\" ``transformation_type`` or \"Rotation\"
|
|
46
46
|
``transformation_type`` if the ``axis`` is \"UserDefined\".
|
|
47
47
|
|
|
@@ -33,7 +33,7 @@ class partition_participants(Command):
|
|
|
33
33
|
|
|
34
34
|
See the System Coupling documentation for more details of the
|
|
35
35
|
partitioning algorithms.
|
|
36
|
-
names_and_fractions :
|
|
36
|
+
names_and_fractions : List, optional
|
|
37
37
|
List of tuples specifying the fractions of core count applied for
|
|
38
38
|
each participant
|
|
39
39
|
|
|
@@ -41,14 +41,14 @@ class partition_participants(Command):
|
|
|
41
41
|
associated fraction as its second item. If this parameter is omitted,
|
|
42
42
|
then cores will be allocated for all participants set in the
|
|
43
43
|
data model.
|
|
44
|
-
machine_list :
|
|
44
|
+
machine_list : List, optional
|
|
45
45
|
List of dictionaries specifying machines available for distributed run.
|
|
46
46
|
Each dictionary must have a key \"machine-name\" with machine name as its
|
|
47
47
|
value, and key \"core-count\" with number of cores for that machine as
|
|
48
48
|
its value. Providing this argument will override any machine list
|
|
49
49
|
information detected from the scheduler environment and any information
|
|
50
50
|
provided by the ``--cnf`` command-line argument.
|
|
51
|
-
partitioning_info :
|
|
51
|
+
partitioning_info : Dict, optional
|
|
52
52
|
Dictionary specifying machines resources assigned to each participant by user.
|
|
53
53
|
Dictionary must have participant names as keys and machine lists containing
|
|
54
54
|
machine resources as values. The value of a ``partitioning_info`` machine list is
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
# This is an auto-generated file. DO NOT EDIT!
|
|
3
3
|
#
|
|
4
4
|
|
|
5
|
-
SHASH = "
|
|
5
|
+
SHASH = "7e0e773274d2f0764aec24ce6e3fd38325273307e69773b731adcd546ec36d63"
|
|
6
6
|
|
|
7
7
|
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
8
8
|
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class show_plot(InjectedCommand):
|
|
9
|
+
"""
|
|
10
|
+
Shows plots of transfer values and convergence for data transfers
|
|
11
|
+
of a coupling interface.
|
|
12
|
+
|
|
13
|
+
Parameters
|
|
14
|
+
----------
|
|
15
|
+
interface_name : str
|
|
16
|
+
Specification of which interface to plot.
|
|
17
|
+
transfer_names : List, optional
|
|
18
|
+
Specification of which data transfers to plot. Defaults
|
|
19
|
+
to ``None``, which means plot all data transfers.
|
|
20
|
+
working_dir : str, optional
|
|
21
|
+
Working directory (defaults = ".").
|
|
22
|
+
show_convergence : bool, optional
|
|
23
|
+
Whether to show convergence plots (defaults to ``True``).
|
|
24
|
+
show_transfer_values : bool, optional
|
|
25
|
+
Whether to show transfer value plots (defaults to ``True``).
|
|
26
|
+
|
|
27
|
+
"""
|
|
28
|
+
|
|
29
|
+
syc_name = "show_plot"
|
|
30
|
+
|
|
31
|
+
cmd_name = "show_plot"
|
|
32
|
+
|
|
33
|
+
argument_names = [
|
|
34
|
+
"interface_name",
|
|
35
|
+
"transfer_names",
|
|
36
|
+
"working_dir",
|
|
37
|
+
"show_convergence",
|
|
38
|
+
"show_transfer_values",
|
|
39
|
+
]
|
|
40
|
+
|
|
41
|
+
class interface_name(String):
|
|
42
|
+
"""
|
|
43
|
+
Specification of which interface to plot.
|
|
44
|
+
"""
|
|
45
|
+
|
|
46
|
+
syc_name = "interface_name"
|
|
47
|
+
|
|
48
|
+
class transfer_names(StringList):
|
|
49
|
+
"""
|
|
50
|
+
Specification of which data transfers to plot. Defaults
|
|
51
|
+
to ``None``, which means plot all data transfers.
|
|
52
|
+
"""
|
|
53
|
+
|
|
54
|
+
syc_name = "transfer_names"
|
|
55
|
+
|
|
56
|
+
class working_dir(String):
|
|
57
|
+
"""
|
|
58
|
+
Working directory (defaults = ".").
|
|
59
|
+
"""
|
|
60
|
+
|
|
61
|
+
syc_name = "working_dir"
|
|
62
|
+
|
|
63
|
+
class show_convergence(Boolean):
|
|
64
|
+
"""
|
|
65
|
+
Whether to show convergence plots (defaults to ``True``).
|
|
66
|
+
"""
|
|
67
|
+
|
|
68
|
+
syc_name = "show_convergence"
|
|
69
|
+
|
|
70
|
+
class show_transfer_values(Boolean):
|
|
71
|
+
"""
|
|
72
|
+
Whether to show transfer value plots (defaults to ``True``).
|
|
73
|
+
"""
|
|
74
|
+
|
|
75
|
+
syc_name = "show_transfer_values"
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
# This is an auto-generated file. DO NOT EDIT!
|
|
3
3
|
#
|
|
4
4
|
|
|
5
|
-
SHASH = "
|
|
5
|
+
SHASH = "0987c9ed416b22e5d86458a81cba5c65a60eb6e6a32fb2f856bf7464f995ed36"
|
|
6
6
|
|
|
7
7
|
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
8
8
|
|
|
@@ -16,6 +16,7 @@ from .initialize import initialize
|
|
|
16
16
|
from .interrupt import interrupt
|
|
17
17
|
from .open_results_in_ensight import open_results_in_ensight
|
|
18
18
|
from .partition_participants import partition_participants
|
|
19
|
+
from .show_plot import show_plot
|
|
19
20
|
from .shutdown import shutdown
|
|
20
21
|
from .solve import solve
|
|
21
22
|
from .start_participants import start_participants
|
|
@@ -42,6 +43,7 @@ class solution_root(Container):
|
|
|
42
43
|
"interrupt",
|
|
43
44
|
"open_results_in_ensight",
|
|
44
45
|
"partition_participants",
|
|
46
|
+
"show_plot",
|
|
45
47
|
"shutdown",
|
|
46
48
|
"solve",
|
|
47
49
|
"start_participants",
|
|
@@ -90,6 +92,10 @@ class solution_root(Container):
|
|
|
90
92
|
"""
|
|
91
93
|
partition_participants command of solution_root.
|
|
92
94
|
"""
|
|
95
|
+
show_plot: show_plot = show_plot
|
|
96
|
+
"""
|
|
97
|
+
show_plot command of solution_root.
|
|
98
|
+
"""
|
|
93
99
|
shutdown: shutdown = shutdown
|
|
94
100
|
"""
|
|
95
101
|
shutdown command of solution_root.
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class _add_participant(Command):
|
|
9
|
+
"""
|
|
10
|
+
For internal use only.
|
|
11
|
+
|
|
12
|
+
Parameters
|
|
13
|
+
----------
|
|
14
|
+
participant_type : str, optional
|
|
15
|
+
...
|
|
16
|
+
input_file : str, optional
|
|
17
|
+
...
|
|
18
|
+
executable : str, optional
|
|
19
|
+
...
|
|
20
|
+
additional_arguments : str, optional
|
|
21
|
+
...
|
|
22
|
+
working_directory : str, optional
|
|
23
|
+
...
|
|
24
|
+
python_script : str, optional
|
|
25
|
+
...
|
|
26
|
+
|
|
27
|
+
"""
|
|
28
|
+
|
|
29
|
+
syc_name = "AddParticipant"
|
|
30
|
+
|
|
31
|
+
argument_names = [
|
|
32
|
+
"participant_type",
|
|
33
|
+
"input_file",
|
|
34
|
+
"executable",
|
|
35
|
+
"additional_arguments",
|
|
36
|
+
"working_directory",
|
|
37
|
+
"python_script",
|
|
38
|
+
]
|
|
39
|
+
|
|
40
|
+
class participant_type(String):
|
|
41
|
+
"""
|
|
42
|
+
...
|
|
43
|
+
"""
|
|
44
|
+
|
|
45
|
+
syc_name = "ParticipantType"
|
|
46
|
+
|
|
47
|
+
class input_file(String):
|
|
48
|
+
"""
|
|
49
|
+
...
|
|
50
|
+
"""
|
|
51
|
+
|
|
52
|
+
syc_name = "InputFile"
|
|
53
|
+
|
|
54
|
+
class executable(String):
|
|
55
|
+
"""
|
|
56
|
+
...
|
|
57
|
+
"""
|
|
58
|
+
|
|
59
|
+
syc_name = "Executable"
|
|
60
|
+
|
|
61
|
+
class additional_arguments(String):
|
|
62
|
+
"""
|
|
63
|
+
...
|
|
64
|
+
"""
|
|
65
|
+
|
|
66
|
+
syc_name = "AdditionalArguments"
|
|
67
|
+
|
|
68
|
+
class working_directory(String):
|
|
69
|
+
"""
|
|
70
|
+
...
|
|
71
|
+
"""
|
|
72
|
+
|
|
73
|
+
syc_name = "WorkingDirectory"
|
|
74
|
+
|
|
75
|
+
class python_script(String):
|
|
76
|
+
"""
|
|
77
|
+
...
|
|
78
|
+
"""
|
|
79
|
+
|
|
80
|
+
syc_name = "PythonScript"
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class abort(InjectedCommand):
|
|
9
|
+
"""
|
|
10
|
+
Aborts a solve in progress.
|
|
11
|
+
|
|
12
|
+
See also ``interrupt``. In contrast to an interrupted solve,
|
|
13
|
+
an aborted solve cannot be resumed.
|
|
14
|
+
|
|
15
|
+
Parameters
|
|
16
|
+
----------
|
|
17
|
+
reason_msg : str, optional
|
|
18
|
+
Text to describe the reason for the abort.
|
|
19
|
+
|
|
20
|
+
This might be used for such purposes as providing
|
|
21
|
+
additional annotation in transcript output.
|
|
22
|
+
|
|
23
|
+
"""
|
|
24
|
+
|
|
25
|
+
syc_name = "abort"
|
|
26
|
+
|
|
27
|
+
cmd_name = "abort"
|
|
28
|
+
|
|
29
|
+
argument_names = ["reason_msg"]
|
|
30
|
+
|
|
31
|
+
class reason_msg(String):
|
|
32
|
+
"""
|
|
33
|
+
Text to describe the reason for the abort.
|
|
34
|
+
|
|
35
|
+
This might be used for such purposes as providing
|
|
36
|
+
additional annotation in transcript output.
|
|
37
|
+
"""
|
|
38
|
+
|
|
39
|
+
syc_name = "reason_msg"
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class activate_hidden(Container):
|
|
9
|
+
"""
|
|
10
|
+
Contains settings to control exposure of hidden features.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "ActivateHidden"
|
|
14
|
+
|
|
15
|
+
property_names_types = [
|
|
16
|
+
("beta_features", "BetaFeatures", "bool"),
|
|
17
|
+
("alpha_features", "AlphaFeatures", "bool"),
|
|
18
|
+
("lenient_validation", "LenientValidation", "bool"),
|
|
19
|
+
]
|
|
20
|
+
|
|
21
|
+
@property
|
|
22
|
+
def beta_features(self) -> bool:
|
|
23
|
+
"""Turn on exposure of Beta features."""
|
|
24
|
+
return self.get_property_state("beta_features")
|
|
25
|
+
|
|
26
|
+
@beta_features.setter
|
|
27
|
+
def beta_features(self, value: bool):
|
|
28
|
+
self.set_property_state("beta_features", value)
|
|
29
|
+
|
|
30
|
+
@property
|
|
31
|
+
def alpha_features(self) -> bool:
|
|
32
|
+
"""Turn on exposure of Alpha features. (Beta features must be turned on first)"""
|
|
33
|
+
return self.get_property_state("alpha_features")
|
|
34
|
+
|
|
35
|
+
@alpha_features.setter
|
|
36
|
+
def alpha_features(self, value: bool):
|
|
37
|
+
self.set_property_state("alpha_features", value)
|
|
38
|
+
|
|
39
|
+
@property
|
|
40
|
+
def lenient_validation(self) -> bool:
|
|
41
|
+
"""Allow a case with zero participants and zero coupling interfaces to be set up."""
|
|
42
|
+
return self.get_property_state("lenient_validation")
|
|
43
|
+
|
|
44
|
+
@lenient_validation.setter
|
|
45
|
+
def lenient_validation(self, value: bool):
|
|
46
|
+
self.set_property_state("lenient_validation", value)
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class add_aerodamping_data_transfers(Command):
|
|
9
|
+
"""
|
|
10
|
+
Adds data transfer for each specified mode shape.
|
|
11
|
+
|
|
12
|
+
Returns the name of the Data Transfers created.
|
|
13
|
+
|
|
14
|
+
Parameters
|
|
15
|
+
----------
|
|
16
|
+
interface : str
|
|
17
|
+
String indicating the name of the interface on which the data transfer
|
|
18
|
+
is to be created.
|
|
19
|
+
mode_shapes : List, optional
|
|
20
|
+
List of mode shapes to transfer. If not provided, a
|
|
21
|
+
data transfer is created for each available modeshape.
|
|
22
|
+
|
|
23
|
+
"""
|
|
24
|
+
|
|
25
|
+
syc_name = "AddAerodampingDataTransfers"
|
|
26
|
+
|
|
27
|
+
argument_names = ["interface", "mode_shapes"]
|
|
28
|
+
|
|
29
|
+
class interface(String):
|
|
30
|
+
"""
|
|
31
|
+
String indicating the name of the interface on which the data transfer
|
|
32
|
+
is to be created.
|
|
33
|
+
"""
|
|
34
|
+
|
|
35
|
+
syc_name = "Interface"
|
|
36
|
+
|
|
37
|
+
class mode_shapes(StringList):
|
|
38
|
+
"""
|
|
39
|
+
List of mode shapes to transfer. If not provided, a
|
|
40
|
+
data transfer is created for each available modeshape.
|
|
41
|
+
"""
|
|
42
|
+
|
|
43
|
+
syc_name = "ModeShapes"
|
|
@@ -0,0 +1,190 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
class add_data_transfer(Command):
|
|
9
|
+
"""
|
|
10
|
+
Adds data transfer based on arguments that specify the interface, target
|
|
11
|
+
side, and variables to be associated with each side of the interface.
|
|
12
|
+
The command requires that you specify variables using their names (see
|
|
13
|
+
parameter descriptions for details). Either a variable-based or
|
|
14
|
+
expression-based data transfer may be created with this command based on
|
|
15
|
+
the arguments provided. If a variable-based data transfer argument
|
|
16
|
+
is given, then no expression-based data transfer arguments can be used. If
|
|
17
|
+
an expression-based data transfer argument is given, then no variable-based
|
|
18
|
+
data transfer arguments can be used.
|
|
19
|
+
|
|
20
|
+
Cannot be run after participants have been started.
|
|
21
|
+
|
|
22
|
+
Returns the name of the Data Transfer created.
|
|
23
|
+
|
|
24
|
+
Parameters
|
|
25
|
+
----------
|
|
26
|
+
interface : str
|
|
27
|
+
String indicating the name of the interface on which the data transfer
|
|
28
|
+
is to be created.
|
|
29
|
+
target_side : str
|
|
30
|
+
String indicating the side of the interface to receive the data
|
|
31
|
+
transfer variable. Possible values are \"One\" or \"Two\".
|
|
32
|
+
source_variable : str, optional
|
|
33
|
+
String specifying the name of the variable on the source side of
|
|
34
|
+
the data transfer. Used when creating a variable-based data transfer.
|
|
35
|
+
Must be combined with ``target_variable``.
|
|
36
|
+
target_variable : str, optional
|
|
37
|
+
String specifying the name of the variable on the target side of
|
|
38
|
+
the data transfer. Must be combined with either ``source_variable`` (when
|
|
39
|
+
creating a variable-based data transfer) or with ``value`` (or
|
|
40
|
+
``value_{x|y|z}`` (when creating an expression-based data transfer).
|
|
41
|
+
value : str, optional
|
|
42
|
+
String specifying the expression to use on the source side of the data
|
|
43
|
+
transfer. Used when creating an expression-based data transfer. If the
|
|
44
|
+
``target_variable`` is a vector, a vector-valued expression must be provided.
|
|
45
|
+
Alternatively, ``value_x``, ``value_y``, ``value_z`` may be used to specify the
|
|
46
|
+
individual components of the vector expression.
|
|
47
|
+
value_x : str, optional
|
|
48
|
+
String specifying the X component of the expression to use on the
|
|
49
|
+
source side of the data transfer. This may optionally be used when creating
|
|
50
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
51
|
+
alternative to specifying a vector-valued expression in ``value`. ``value_y`` and
|
|
52
|
+
``value_z`` are also required if ``value_x`` is used.
|
|
53
|
+
value_y : str, optional
|
|
54
|
+
String specifying the Y component of the expression to use on the
|
|
55
|
+
source side of the data transfer. This may optionally be used when creating
|
|
56
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
57
|
+
alternative to specifying a vector-valued expression in ``value``. ``value_x`` and
|
|
58
|
+
``value_z`` are also required if ``value_y`` is used.
|
|
59
|
+
value_z : str, optional
|
|
60
|
+
String specifying the Z component of the expression to use on the
|
|
61
|
+
source side of the data transfer. This may optionally be used when creating
|
|
62
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
63
|
+
alternative to specifying a vector-valued expression in ``value``. ``value_x`` and
|
|
64
|
+
``value_y`` are also required if ``value_z`` is used.
|
|
65
|
+
side_one_variable : str, optional
|
|
66
|
+
String specifying the name of the variable associated with side1
|
|
67
|
+
of the interface. Must be combined with ``side_two_variable``. Used only
|
|
68
|
+
when creating variable-based data transfers. Consider using
|
|
69
|
+
``source_variable``/``target_variable`` parameters instead.
|
|
70
|
+
side_two_variable : str, optional
|
|
71
|
+
String specifying the name of the variable associated with side2
|
|
72
|
+
of the interface. Must be combined with ``side_two_variable``. Used only
|
|
73
|
+
when creating variable-based data transfers. Consider using
|
|
74
|
+
``source_variable``/``target_variable`` parameters instead.
|
|
75
|
+
|
|
76
|
+
"""
|
|
77
|
+
|
|
78
|
+
syc_name = "AddDataTransfer"
|
|
79
|
+
|
|
80
|
+
argument_names = [
|
|
81
|
+
"interface",
|
|
82
|
+
"target_side",
|
|
83
|
+
"source_variable",
|
|
84
|
+
"target_variable",
|
|
85
|
+
"value",
|
|
86
|
+
"value_x",
|
|
87
|
+
"value_y",
|
|
88
|
+
"value_z",
|
|
89
|
+
"side_one_variable",
|
|
90
|
+
"side_two_variable",
|
|
91
|
+
]
|
|
92
|
+
|
|
93
|
+
class interface(String):
|
|
94
|
+
"""
|
|
95
|
+
String indicating the name of the interface on which the data transfer
|
|
96
|
+
is to be created.
|
|
97
|
+
"""
|
|
98
|
+
|
|
99
|
+
syc_name = "Interface"
|
|
100
|
+
|
|
101
|
+
class target_side(String):
|
|
102
|
+
"""
|
|
103
|
+
String indicating the side of the interface to receive the data
|
|
104
|
+
transfer variable. Possible values are \"One\" or \"Two\".
|
|
105
|
+
"""
|
|
106
|
+
|
|
107
|
+
syc_name = "TargetSide"
|
|
108
|
+
|
|
109
|
+
class source_variable(String):
|
|
110
|
+
"""
|
|
111
|
+
String specifying the name of the variable on the source side of
|
|
112
|
+
the data transfer. Used when creating a variable-based data transfer.
|
|
113
|
+
Must be combined with ``target_variable``.
|
|
114
|
+
"""
|
|
115
|
+
|
|
116
|
+
syc_name = "SourceVariable"
|
|
117
|
+
|
|
118
|
+
class target_variable(String):
|
|
119
|
+
"""
|
|
120
|
+
String specifying the name of the variable on the target side of
|
|
121
|
+
the data transfer. Must be combined with either ``source_variable`` (when
|
|
122
|
+
creating a variable-based data transfer) or with ``value`` (or
|
|
123
|
+
``value_{x|y|z}`` (when creating an expression-based data transfer).
|
|
124
|
+
"""
|
|
125
|
+
|
|
126
|
+
syc_name = "TargetVariable"
|
|
127
|
+
|
|
128
|
+
class value(String):
|
|
129
|
+
"""
|
|
130
|
+
String specifying the expression to use on the source side of the data
|
|
131
|
+
transfer. Used when creating an expression-based data transfer. If the
|
|
132
|
+
``target_variable`` is a vector, a vector-valued expression must be provided.
|
|
133
|
+
Alternatively, ``value_x``, ``value_y``, ``value_z`` may be used to specify the
|
|
134
|
+
individual components of the vector expression.
|
|
135
|
+
"""
|
|
136
|
+
|
|
137
|
+
syc_name = "Value"
|
|
138
|
+
|
|
139
|
+
class value_x(String):
|
|
140
|
+
"""
|
|
141
|
+
String specifying the X component of the expression to use on the
|
|
142
|
+
source side of the data transfer. This may optionally be used when creating
|
|
143
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
144
|
+
alternative to specifying a vector-valued expression in ``value`. ``value_y`` and
|
|
145
|
+
``value_z`` are also required if ``value_x`` is used.
|
|
146
|
+
"""
|
|
147
|
+
|
|
148
|
+
syc_name = "ValueX"
|
|
149
|
+
|
|
150
|
+
class value_y(String):
|
|
151
|
+
"""
|
|
152
|
+
String specifying the Y component of the expression to use on the
|
|
153
|
+
source side of the data transfer. This may optionally be used when creating
|
|
154
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
155
|
+
alternative to specifying a vector-valued expression in ``value``. ``value_x`` and
|
|
156
|
+
``value_z`` are also required if ``value_y`` is used.
|
|
157
|
+
"""
|
|
158
|
+
|
|
159
|
+
syc_name = "ValueY"
|
|
160
|
+
|
|
161
|
+
class value_z(String):
|
|
162
|
+
"""
|
|
163
|
+
String specifying the Z component of the expression to use on the
|
|
164
|
+
source side of the data transfer. This may optionally be used when creating
|
|
165
|
+
an expression-based data transfer if the ``target_variable`` is a vector as an
|
|
166
|
+
alternative to specifying a vector-valued expression in ``value``. ``value_x`` and
|
|
167
|
+
``value_y`` are also required if ``value_z`` is used.
|
|
168
|
+
"""
|
|
169
|
+
|
|
170
|
+
syc_name = "ValueZ"
|
|
171
|
+
|
|
172
|
+
class side_one_variable(String):
|
|
173
|
+
"""
|
|
174
|
+
String specifying the name of the variable associated with side1
|
|
175
|
+
of the interface. Must be combined with ``side_two_variable``. Used only
|
|
176
|
+
when creating variable-based data transfers. Consider using
|
|
177
|
+
``source_variable``/``target_variable`` parameters instead.
|
|
178
|
+
"""
|
|
179
|
+
|
|
180
|
+
syc_name = "SideOneVariable"
|
|
181
|
+
|
|
182
|
+
class side_two_variable(String):
|
|
183
|
+
"""
|
|
184
|
+
String specifying the name of the variable associated with side2
|
|
185
|
+
of the interface. Must be combined with ``side_two_variable``. Used only
|
|
186
|
+
when creating variable-based data transfers. Consider using
|
|
187
|
+
``source_variable``/``target_variable`` parameters instead.
|
|
188
|
+
"""
|
|
189
|
+
|
|
190
|
+
syc_name = "SideTwoVariable"
|