ansys-systemcoupling-core 0.9.1__py3-none-any.whl → 0.10.1__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 +1 -1
- ansys/systemcoupling/core/adaptor/api_25_2/_add_participant.py +80 -0
- ansys/systemcoupling/core/adaptor/api_25_2/_clear_state.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_2/_solve.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_2/abort.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_2/activate_hidden.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_aerodamping_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_data_transfer.py +190 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_expression_function.py +61 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_flow_boundary_data_transfers.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_fsi_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_interface.py +77 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_named_expression.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_ordered_data_transfers.py +41 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_participant.py +177 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_reference_frame.py +40 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_thermal_data_transfers.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_2/add_transformation.py +102 -0
- ansys/systemcoupling/core/adaptor/api_25_2/analysis_control.py +333 -0
- ansys/systemcoupling/core/adaptor/api_25_2/apip.py +33 -0
- ansys/systemcoupling/core/adaptor/api_25_2/ascii_output.py +44 -0
- ansys/systemcoupling/core/adaptor/api_25_2/attribute.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/attribute_child.py +74 -0
- ansys/systemcoupling/core/adaptor/api_25_2/automatic_alignment_options.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_2/available_ports.py +40 -0
- ansys/systemcoupling/core/adaptor/api_25_2/avoid_data_reconstruction.py +56 -0
- ansys/systemcoupling/core/adaptor/api_25_2/case_root.py +62 -0
- ansys/systemcoupling/core/adaptor/api_25_2/clear_state.py +18 -0
- ansys/systemcoupling/core/adaptor/api_25_2/connect_ensight_dvs.py +41 -0
- ansys/systemcoupling/core/adaptor/api_25_2/coupling_interface.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/coupling_interface_child.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_2/coupling_participant.py +23 -0
- ansys/systemcoupling/core/adaptor/api_25_2/coupling_participant_child.py +272 -0
- ansys/systemcoupling/core/adaptor/api_25_2/create_restart_point.py +28 -0
- ansys/systemcoupling/core/adaptor/api_25_2/data_transfer.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/data_transfer_child.py +195 -0
- ansys/systemcoupling/core/adaptor/api_25_2/delete_snapshot.py +30 -0
- ansys/systemcoupling/core/adaptor/api_25_2/delete_transformation.py +42 -0
- ansys/systemcoupling/core/adaptor/api_25_2/dimensionality.py +96 -0
- ansys/systemcoupling/core/adaptor/api_25_2/execution_control.py +266 -0
- ansys/systemcoupling/core/adaptor/api_25_2/execution_control_1.py +24 -0
- ansys/systemcoupling/core/adaptor/api_25_2/expression.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/expression_child.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_2/expression_function.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/expression_function_child.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_2/external_data_file.py +24 -0
- ansys/systemcoupling/core/adaptor/api_25_2/fluent_input.py +77 -0
- ansys/systemcoupling/core/adaptor/api_25_2/fmu_parameter.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/fmu_parameter_child.py +164 -0
- ansys/systemcoupling/core/adaptor/api_25_2/generate_input_file.py +53 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_add_data_transfer_group_commands.py +29 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_execution_command.py +30 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_machines.py +34 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_mode_shape_variables.py +29 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_region_names_for_participant.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_setup_summary.py +25 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_status_messages.py +52 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_supported_participant_types.py +13 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_thermal_data_transfer_options.py +32 -0
- ansys/systemcoupling/core/adaptor/api_25_2/get_transformation.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_2/global_stabilization.py +155 -0
- ansys/systemcoupling/core/adaptor/api_25_2/has_input_file_changed.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_2/import_system_coupling_input_file.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_2/initialize.py +27 -0
- ansys/systemcoupling/core/adaptor/api_25_2/instancing.py +25 -0
- ansys/systemcoupling/core/adaptor/api_25_2/instancing_child.py +114 -0
- ansys/systemcoupling/core/adaptor/api_25_2/interrupt.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_2/library.py +37 -0
- ansys/systemcoupling/core/adaptor/api_25_2/live_visualization.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/live_visualization_child.py +100 -0
- ansys/systemcoupling/core/adaptor/api_25_2/map.py +19 -0
- ansys/systemcoupling/core/adaptor/api_25_2/mapping_control.py +273 -0
- ansys/systemcoupling/core/adaptor/api_25_2/open.py +107 -0
- ansys/systemcoupling/core/adaptor/api_25_2/open_results_in_ensight.py +56 -0
- ansys/systemcoupling/core/adaptor/api_25_2/open_snapshot.py +37 -0
- ansys/systemcoupling/core/adaptor/api_25_2/output_control.py +134 -0
- ansys/systemcoupling/core/adaptor/api_25_2/parameter.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/parameter_child.py +60 -0
- ansys/systemcoupling/core/adaptor/api_25_2/partition_participants.py +148 -0
- ansys/systemcoupling/core/adaptor/api_25_2/properties.py +36 -0
- ansys/systemcoupling/core/adaptor/api_25_2/record_interactions.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_2/reference_frame.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/reference_frame_child.py +71 -0
- ansys/systemcoupling/core/adaptor/api_25_2/region.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/region_child.py +71 -0
- ansys/systemcoupling/core/adaptor/api_25_2/reload_expression_function_modules.py +14 -0
- ansys/systemcoupling/core/adaptor/api_25_2/results.py +89 -0
- ansys/systemcoupling/core/adaptor/api_25_2/save.py +53 -0
- ansys/systemcoupling/core/adaptor/api_25_2/save_snapshot.py +54 -0
- ansys/systemcoupling/core/adaptor/api_25_2/setup_root.py +243 -0
- ansys/systemcoupling/core/adaptor/api_25_2/show_plot.py +75 -0
- ansys/systemcoupling/core/adaptor/api_25_2/shutdown.py +25 -0
- ansys/systemcoupling/core/adaptor/api_25_2/side.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/side_child.py +56 -0
- ansys/systemcoupling/core/adaptor/api_25_2/solution_control.py +127 -0
- ansys/systemcoupling/core/adaptor/api_25_2/solution_root.py +134 -0
- ansys/systemcoupling/core/adaptor/api_25_2/solve.py +30 -0
- ansys/systemcoupling/core/adaptor/api_25_2/stabilization.py +157 -0
- ansys/systemcoupling/core/adaptor/api_25_2/step.py +57 -0
- ansys/systemcoupling/core/adaptor/api_25_2/transformation.py +21 -0
- ansys/systemcoupling/core/adaptor/api_25_2/transformation_child.py +62 -0
- ansys/systemcoupling/core/adaptor/api_25_2/type.py +39 -0
- ansys/systemcoupling/core/adaptor/api_25_2/unmapped_value_options.py +158 -0
- ansys/systemcoupling/core/adaptor/api_25_2/update_control.py +43 -0
- ansys/systemcoupling/core/adaptor/api_25_2/update_interfaces.py +19 -0
- ansys/systemcoupling/core/adaptor/api_25_2/update_participant.py +61 -0
- ansys/systemcoupling/core/adaptor/api_25_2/variable.py +20 -0
- ansys/systemcoupling/core/adaptor/api_25_2/variable_child.py +231 -0
- ansys/systemcoupling/core/adaptor/api_25_2/write_csv_chart_files.py +21 -0
- ansys/systemcoupling/core/adaptor/api_25_2/write_ensight.py +46 -0
- ansys/systemcoupling/core/adaptor/api_25_2/write_target_data.py +32 -0
- ansys/systemcoupling/core/adaptor/impl/get_syc_version.py +4 -1
- ansys/systemcoupling/core/adaptor/impl/injected_commands.py +3 -1
- ansys/systemcoupling/core/charts/csv_chartdata.py +4 -3
- ansys/systemcoupling/core/charts/plot_functions.py +12 -4
- ansys/systemcoupling/core/charts/plotter.py +3 -2
- ansys/systemcoupling/core/client/grpc_client.py +11 -2
- ansys/systemcoupling/core/client/syc_container.py +40 -35
- ansys/systemcoupling/core/client/syc_process.py +5 -2
- ansys/systemcoupling/core/native_api/datamodel_metadata.py +3 -2
- ansys/systemcoupling/core/native_api/object_path.py +2 -1
- ansys/systemcoupling/core/syc_version.py +1 -1
- ansys/systemcoupling/core/util/assertion.py +38 -0
- ansys/systemcoupling/core/util/file_transfer.py +2 -1
- ansys/systemcoupling/core/util/yaml_helper.py +5 -5
- {ansys_systemcoupling_core-0.9.1.dist-info → ansys_systemcoupling_core-0.10.1.dist-info}/METADATA +16 -10
- {ansys_systemcoupling_core-0.9.1.dist-info → ansys_systemcoupling_core-0.10.1.dist-info}/RECORD +129 -18
- {ansys_systemcoupling_core-0.9.1.dist-info → ansys_systemcoupling_core-0.10.1.dist-info}/WHEEL +0 -0
- {ansys_systemcoupling_core-0.9.1.dist-info → ansys_systemcoupling_core-0.10.1.dist-info}/licenses/LICENSE +0 -0
|
@@ -0,0 +1,36 @@
|
|
|
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 expression_child(Container):
|
|
9
|
+
"""
|
|
10
|
+
Define a named expression that can be referenced in other expressions.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "child_object_type"
|
|
14
|
+
|
|
15
|
+
property_names_types = [
|
|
16
|
+
("expression_name", "ExpressionName", "str"),
|
|
17
|
+
("expression_string", "ExpressionString", "str"),
|
|
18
|
+
]
|
|
19
|
+
|
|
20
|
+
@property
|
|
21
|
+
def expression_name(self) -> str:
|
|
22
|
+
"""Name used to reference this expression from another expression"""
|
|
23
|
+
return self.get_property_state("expression_name")
|
|
24
|
+
|
|
25
|
+
@expression_name.setter
|
|
26
|
+
def expression_name(self, value: str):
|
|
27
|
+
self.set_property_state("expression_name", value)
|
|
28
|
+
|
|
29
|
+
@property
|
|
30
|
+
def expression_string(self) -> str:
|
|
31
|
+
"""String defining the expression."""
|
|
32
|
+
return self.get_property_state("expression_string")
|
|
33
|
+
|
|
34
|
+
@expression_string.setter
|
|
35
|
+
def expression_string(self, value: str):
|
|
36
|
+
self.set_property_state("expression_string", value)
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
from .expression_function_child import expression_function_child
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
class expression_function(NamedContainer[expression_function_child]):
|
|
11
|
+
"""
|
|
12
|
+
Makes an external Python function accessible from expressions.
|
|
13
|
+
"""
|
|
14
|
+
|
|
15
|
+
syc_name = "ExpressionFunction"
|
|
16
|
+
|
|
17
|
+
child_object_type: expression_function_child = expression_function_child
|
|
18
|
+
"""
|
|
19
|
+
child_object_type of expression_function.
|
|
20
|
+
"""
|
|
@@ -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 expression_function_child(Container):
|
|
9
|
+
"""
|
|
10
|
+
Makes an external Python function accessible from expressions.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "child_object_type"
|
|
14
|
+
|
|
15
|
+
property_names_types = [
|
|
16
|
+
("module", "Module", "str"),
|
|
17
|
+
("function", "Function", "str"),
|
|
18
|
+
("function_name", "FunctionName", "str"),
|
|
19
|
+
]
|
|
20
|
+
|
|
21
|
+
@property
|
|
22
|
+
def module(self) -> str:
|
|
23
|
+
"""Name of the Python module that exports the function."""
|
|
24
|
+
return self.get_property_state("module")
|
|
25
|
+
|
|
26
|
+
@module.setter
|
|
27
|
+
def module(self, value: str):
|
|
28
|
+
self.set_property_state("module", value)
|
|
29
|
+
|
|
30
|
+
@property
|
|
31
|
+
def function(self) -> str:
|
|
32
|
+
"""Name of the function in the module."""
|
|
33
|
+
return self.get_property_state("function")
|
|
34
|
+
|
|
35
|
+
@function.setter
|
|
36
|
+
def function(self, value: str):
|
|
37
|
+
self.set_property_state("function", value)
|
|
38
|
+
|
|
39
|
+
@property
|
|
40
|
+
def function_name(self) -> str:
|
|
41
|
+
"""Name to use when referencing the function in an expression."""
|
|
42
|
+
return self.get_property_state("function_name")
|
|
43
|
+
|
|
44
|
+
@function_name.setter
|
|
45
|
+
def function_name(self, value: str):
|
|
46
|
+
self.set_property_state("function_name", value)
|
|
@@ -0,0 +1,24 @@
|
|
|
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 external_data_file(Container):
|
|
9
|
+
"""
|
|
10
|
+
Participant external data file settings.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "ExternalDataFile"
|
|
14
|
+
|
|
15
|
+
property_names_types = [("file_path", "FilePath", "str")]
|
|
16
|
+
|
|
17
|
+
@property
|
|
18
|
+
def file_path(self) -> str:
|
|
19
|
+
"""Path to file for communication with a coupling participant."""
|
|
20
|
+
return self.get_property_state("file_path")
|
|
21
|
+
|
|
22
|
+
@file_path.setter
|
|
23
|
+
def file_path(self, value: str):
|
|
24
|
+
self.set_property_state("file_path", value)
|
|
@@ -0,0 +1,77 @@
|
|
|
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 fluent_input(Container):
|
|
9
|
+
"""
|
|
10
|
+
Fluent input.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "FluentInput"
|
|
14
|
+
|
|
15
|
+
property_names_types = [
|
|
16
|
+
("option", "Option", "str"),
|
|
17
|
+
("case_file", "CaseFile", "str"),
|
|
18
|
+
("data_file", "DataFile", "str"),
|
|
19
|
+
("enable_autosave", "EnableAutosave", "bool"),
|
|
20
|
+
("journal_file", "JournalFile", "str"),
|
|
21
|
+
]
|
|
22
|
+
|
|
23
|
+
@property
|
|
24
|
+
def option(self) -> str:
|
|
25
|
+
"""Type of solver input file(s) to be used for the Fluent run.
|
|
26
|
+
|
|
27
|
+
Allowed values:
|
|
28
|
+
|
|
29
|
+
- \"InitialCaseFile\" - (Default) A case file will be defined as a
|
|
30
|
+
solver input for the coupled analysis run.
|
|
31
|
+
|
|
32
|
+
- \"InitialCaseAndDataFile\" - A Fluent case file and data file
|
|
33
|
+
will be defined as solver inputs for the coupled analysis run.
|
|
34
|
+
|
|
35
|
+
- \"JournalFile\" - A journal file will be defined as the solver
|
|
36
|
+
input for the coupled analysis run."""
|
|
37
|
+
return self.get_property_state("option")
|
|
38
|
+
|
|
39
|
+
@option.setter
|
|
40
|
+
def option(self, value: str):
|
|
41
|
+
self.set_property_state("option", value)
|
|
42
|
+
|
|
43
|
+
@property
|
|
44
|
+
def case_file(self) -> str:
|
|
45
|
+
"""Set Fluent initial case file."""
|
|
46
|
+
return self.get_property_state("case_file")
|
|
47
|
+
|
|
48
|
+
@case_file.setter
|
|
49
|
+
def case_file(self, value: str):
|
|
50
|
+
self.set_property_state("case_file", value)
|
|
51
|
+
|
|
52
|
+
@property
|
|
53
|
+
def data_file(self) -> str:
|
|
54
|
+
"""Set Fluent initial data file."""
|
|
55
|
+
return self.get_property_state("data_file")
|
|
56
|
+
|
|
57
|
+
@data_file.setter
|
|
58
|
+
def data_file(self, value: str):
|
|
59
|
+
self.set_property_state("data_file", value)
|
|
60
|
+
|
|
61
|
+
@property
|
|
62
|
+
def enable_autosave(self) -> bool:
|
|
63
|
+
"""Set Fluent autosave frequency to System Coupling output control frequency to generate .flprj file."""
|
|
64
|
+
return self.get_property_state("enable_autosave")
|
|
65
|
+
|
|
66
|
+
@enable_autosave.setter
|
|
67
|
+
def enable_autosave(self, value: bool):
|
|
68
|
+
self.set_property_state("enable_autosave", value)
|
|
69
|
+
|
|
70
|
+
@property
|
|
71
|
+
def journal_file(self) -> str:
|
|
72
|
+
"""Set Fluent journal file."""
|
|
73
|
+
return self.get_property_state("journal_file")
|
|
74
|
+
|
|
75
|
+
@journal_file.setter
|
|
76
|
+
def journal_file(self, value: str):
|
|
77
|
+
self.set_property_state("journal_file", value)
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
#
|
|
2
|
+
# This is an auto-generated file. DO NOT EDIT!
|
|
3
|
+
#
|
|
4
|
+
|
|
5
|
+
from ansys.systemcoupling.core.adaptor.impl.types import *
|
|
6
|
+
|
|
7
|
+
from .fmu_parameter_child import fmu_parameter_child
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
class fmu_parameter(NamedContainer[fmu_parameter_child]):
|
|
11
|
+
"""
|
|
12
|
+
Configure a parameter for an FMU coupling participant.
|
|
13
|
+
"""
|
|
14
|
+
|
|
15
|
+
syc_name = "FMUParameter"
|
|
16
|
+
|
|
17
|
+
child_object_type: fmu_parameter_child = fmu_parameter_child
|
|
18
|
+
"""
|
|
19
|
+
child_object_type of fmu_parameter.
|
|
20
|
+
"""
|
|
@@ -0,0 +1,164 @@
|
|
|
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 fmu_parameter_child(Container):
|
|
9
|
+
"""
|
|
10
|
+
Configure a parameter for an FMU coupling participant.
|
|
11
|
+
"""
|
|
12
|
+
|
|
13
|
+
syc_name = "child_object_type"
|
|
14
|
+
|
|
15
|
+
property_names_types = [
|
|
16
|
+
("data_type", "DataType", "str"),
|
|
17
|
+
("participant_display_name", "ParticipantDisplayName", "str"),
|
|
18
|
+
("display_name", "DisplayName", "str"),
|
|
19
|
+
("real_value", "RealValue", "RealType"),
|
|
20
|
+
("real_min", "RealMin", "RealType"),
|
|
21
|
+
("real_max", "RealMax", "RealType"),
|
|
22
|
+
("integer_value", "IntegerValue", "int"),
|
|
23
|
+
("integer_min", "IntegerMin", "int"),
|
|
24
|
+
("integer_max", "IntegerMax", "int"),
|
|
25
|
+
("logical_value", "LogicalValue", "bool"),
|
|
26
|
+
("string_value", "StringValue", "str"),
|
|
27
|
+
("enumeration_value", "EnumerationValue", "int"),
|
|
28
|
+
("enumeration_min", "EnumerationMin", "int"),
|
|
29
|
+
("enumeration_max", "EnumerationMax", "int"),
|
|
30
|
+
]
|
|
31
|
+
|
|
32
|
+
@property
|
|
33
|
+
def data_type(self) -> str:
|
|
34
|
+
"""FMUParameter's data type as reported by the participant.
|
|
35
|
+
|
|
36
|
+
Allowed values:
|
|
37
|
+
|
|
38
|
+
- Real
|
|
39
|
+
- Integer
|
|
40
|
+
- Logical
|
|
41
|
+
- String
|
|
42
|
+
- Enumeration"""
|
|
43
|
+
return self.get_property_state("data_type")
|
|
44
|
+
|
|
45
|
+
@data_type.setter
|
|
46
|
+
def data_type(self, value: str):
|
|
47
|
+
self.set_property_state("data_type", value)
|
|
48
|
+
|
|
49
|
+
@property
|
|
50
|
+
def participant_display_name(self) -> str:
|
|
51
|
+
"""Parameter's display name as defined by the participant solver."""
|
|
52
|
+
return self.get_property_state("participant_display_name")
|
|
53
|
+
|
|
54
|
+
@participant_display_name.setter
|
|
55
|
+
def participant_display_name(self, value: str):
|
|
56
|
+
self.set_property_state("participant_display_name", value)
|
|
57
|
+
|
|
58
|
+
@property
|
|
59
|
+
def display_name(self) -> str:
|
|
60
|
+
"""Parameter's display name as defined in System Coupling."""
|
|
61
|
+
return self.get_property_state("display_name")
|
|
62
|
+
|
|
63
|
+
@display_name.setter
|
|
64
|
+
def display_name(self, value: str):
|
|
65
|
+
self.set_property_state("display_name", value)
|
|
66
|
+
|
|
67
|
+
@property
|
|
68
|
+
def real_value(self) -> RealType:
|
|
69
|
+
"""Real data start value."""
|
|
70
|
+
return self.get_property_state("real_value")
|
|
71
|
+
|
|
72
|
+
@real_value.setter
|
|
73
|
+
def real_value(self, value: RealType):
|
|
74
|
+
self.set_property_state("real_value", value)
|
|
75
|
+
|
|
76
|
+
@property
|
|
77
|
+
def real_min(self) -> RealType:
|
|
78
|
+
"""Real data minimum value."""
|
|
79
|
+
return self.get_property_state("real_min")
|
|
80
|
+
|
|
81
|
+
@real_min.setter
|
|
82
|
+
def real_min(self, value: RealType):
|
|
83
|
+
self.set_property_state("real_min", value)
|
|
84
|
+
|
|
85
|
+
@property
|
|
86
|
+
def real_max(self) -> RealType:
|
|
87
|
+
"""Real data maximum value."""
|
|
88
|
+
return self.get_property_state("real_max")
|
|
89
|
+
|
|
90
|
+
@real_max.setter
|
|
91
|
+
def real_max(self, value: RealType):
|
|
92
|
+
self.set_property_state("real_max", value)
|
|
93
|
+
|
|
94
|
+
@property
|
|
95
|
+
def integer_value(self) -> int:
|
|
96
|
+
"""Integer data start value."""
|
|
97
|
+
return self.get_property_state("integer_value")
|
|
98
|
+
|
|
99
|
+
@integer_value.setter
|
|
100
|
+
def integer_value(self, value: int):
|
|
101
|
+
self.set_property_state("integer_value", value)
|
|
102
|
+
|
|
103
|
+
@property
|
|
104
|
+
def integer_min(self) -> int:
|
|
105
|
+
"""Integer data minimum value."""
|
|
106
|
+
return self.get_property_state("integer_min")
|
|
107
|
+
|
|
108
|
+
@integer_min.setter
|
|
109
|
+
def integer_min(self, value: int):
|
|
110
|
+
self.set_property_state("integer_min", value)
|
|
111
|
+
|
|
112
|
+
@property
|
|
113
|
+
def integer_max(self) -> int:
|
|
114
|
+
"""Integer data maximum value."""
|
|
115
|
+
return self.get_property_state("integer_max")
|
|
116
|
+
|
|
117
|
+
@integer_max.setter
|
|
118
|
+
def integer_max(self, value: int):
|
|
119
|
+
self.set_property_state("integer_max", value)
|
|
120
|
+
|
|
121
|
+
@property
|
|
122
|
+
def logical_value(self) -> bool:
|
|
123
|
+
"""Logical data start value."""
|
|
124
|
+
return self.get_property_state("logical_value")
|
|
125
|
+
|
|
126
|
+
@logical_value.setter
|
|
127
|
+
def logical_value(self, value: bool):
|
|
128
|
+
self.set_property_state("logical_value", value)
|
|
129
|
+
|
|
130
|
+
@property
|
|
131
|
+
def string_value(self) -> str:
|
|
132
|
+
"""String data start value."""
|
|
133
|
+
return self.get_property_state("string_value")
|
|
134
|
+
|
|
135
|
+
@string_value.setter
|
|
136
|
+
def string_value(self, value: str):
|
|
137
|
+
self.set_property_state("string_value", value)
|
|
138
|
+
|
|
139
|
+
@property
|
|
140
|
+
def enumeration_value(self) -> int:
|
|
141
|
+
"""Enumeration data start value."""
|
|
142
|
+
return self.get_property_state("enumeration_value")
|
|
143
|
+
|
|
144
|
+
@enumeration_value.setter
|
|
145
|
+
def enumeration_value(self, value: int):
|
|
146
|
+
self.set_property_state("enumeration_value", value)
|
|
147
|
+
|
|
148
|
+
@property
|
|
149
|
+
def enumeration_min(self) -> int:
|
|
150
|
+
"""Enumeration data minimum value."""
|
|
151
|
+
return self.get_property_state("enumeration_min")
|
|
152
|
+
|
|
153
|
+
@enumeration_min.setter
|
|
154
|
+
def enumeration_min(self, value: int):
|
|
155
|
+
self.set_property_state("enumeration_min", value)
|
|
156
|
+
|
|
157
|
+
@property
|
|
158
|
+
def enumeration_max(self) -> int:
|
|
159
|
+
"""Enumeration data maximum value."""
|
|
160
|
+
return self.get_property_state("enumeration_max")
|
|
161
|
+
|
|
162
|
+
@enumeration_max.setter
|
|
163
|
+
def enumeration_max(self, value: int):
|
|
164
|
+
self.set_property_state("enumeration_max", value)
|
|
@@ -0,0 +1,53 @@
|
|
|
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 generate_input_file(Command):
|
|
9
|
+
"""
|
|
10
|
+
Generates the input journal file for a given Fluent participant.
|
|
11
|
+
|
|
12
|
+
Available for Fluent participants when ``fluent_input.option`` is not
|
|
13
|
+
set to ``journal_file``.
|
|
14
|
+
|
|
15
|
+
Given the participant's name and a file name, generates a Fluent
|
|
16
|
+
journal script which may be set as the value for the ``journal_file``
|
|
17
|
+
setting.
|
|
18
|
+
|
|
19
|
+
System Coupling uses the generated scrkpt for the coupled analysis.
|
|
20
|
+
|
|
21
|
+
Scripts generated using this method may be edited before the
|
|
22
|
+
coupled analysis is started.
|
|
23
|
+
|
|
24
|
+
Parameters
|
|
25
|
+
----------
|
|
26
|
+
participant_name : str
|
|
27
|
+
Name of the participant for which the execution command will
|
|
28
|
+
be returned.
|
|
29
|
+
file_name : str
|
|
30
|
+
Name of the journal script to be written. Note that this name is relative
|
|
31
|
+
to the participant's working directory.
|
|
32
|
+
|
|
33
|
+
"""
|
|
34
|
+
|
|
35
|
+
syc_name = "GenerateInputFile"
|
|
36
|
+
|
|
37
|
+
argument_names = ["participant_name", "file_name"]
|
|
38
|
+
|
|
39
|
+
class participant_name(String):
|
|
40
|
+
"""
|
|
41
|
+
Name of the participant for which the execution command will
|
|
42
|
+
be returned.
|
|
43
|
+
"""
|
|
44
|
+
|
|
45
|
+
syc_name = "ParticipantName"
|
|
46
|
+
|
|
47
|
+
class file_name(String):
|
|
48
|
+
"""
|
|
49
|
+
Name of the journal script to be written. Note that this name is relative
|
|
50
|
+
to the participant's working directory.
|
|
51
|
+
"""
|
|
52
|
+
|
|
53
|
+
syc_name = "FileName"
|
|
@@ -0,0 +1,29 @@
|
|
|
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 get_add_data_transfer_group_commands(Command):
|
|
9
|
+
"""
|
|
10
|
+
Given an interface name, returns a list with possible commands
|
|
11
|
+
for adding data transfer groups.
|
|
12
|
+
|
|
13
|
+
Parameters
|
|
14
|
+
----------
|
|
15
|
+
interface : str
|
|
16
|
+
String indicating the name of the interface.
|
|
17
|
+
|
|
18
|
+
"""
|
|
19
|
+
|
|
20
|
+
syc_name = "GetAddDataTransferGroupCommands"
|
|
21
|
+
|
|
22
|
+
argument_names = ["interface"]
|
|
23
|
+
|
|
24
|
+
class interface(String):
|
|
25
|
+
"""
|
|
26
|
+
String indicating the name of the interface.
|
|
27
|
+
"""
|
|
28
|
+
|
|
29
|
+
syc_name = "Interface"
|
|
@@ -0,0 +1,30 @@
|
|
|
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 get_execution_command(Command):
|
|
9
|
+
"""
|
|
10
|
+
Gets the execution command needed to start the specified participant.
|
|
11
|
+
|
|
12
|
+
Parameters
|
|
13
|
+
----------
|
|
14
|
+
participant_name : str
|
|
15
|
+
Name of the participant for which the execution command will
|
|
16
|
+
be returned.
|
|
17
|
+
|
|
18
|
+
"""
|
|
19
|
+
|
|
20
|
+
syc_name = "GetExecutionCommand"
|
|
21
|
+
|
|
22
|
+
argument_names = ["participant_name"]
|
|
23
|
+
|
|
24
|
+
class participant_name(String):
|
|
25
|
+
"""
|
|
26
|
+
Name of the participant for which the execution command will
|
|
27
|
+
be returned.
|
|
28
|
+
"""
|
|
29
|
+
|
|
30
|
+
syc_name = "ParticipantName"
|
|
@@ -0,0 +1,34 @@
|
|
|
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 get_machines(Command):
|
|
9
|
+
"""
|
|
10
|
+
Get a list of dictionaries with machine names and core counts for
|
|
11
|
+
the machines available for parallel processing.
|
|
12
|
+
|
|
13
|
+
Returns information in the following format::
|
|
14
|
+
|
|
15
|
+
[
|
|
16
|
+
{
|
|
17
|
+
'machine-name' : <machine-name-1 (str)>,
|
|
18
|
+
'core-count' : <core-count-1 (int)>
|
|
19
|
+
},
|
|
20
|
+
{
|
|
21
|
+
'machine-name' : <machine-name-2 (str)>,
|
|
22
|
+
'core-count' : <core-count-2 (int)>
|
|
23
|
+
},
|
|
24
|
+
...
|
|
25
|
+
]
|
|
26
|
+
|
|
27
|
+
Returns an empty list when machines and core counts are not
|
|
28
|
+
provided to System Coupling. You may specify those
|
|
29
|
+
by providing --cnf command-line option when starting System
|
|
30
|
+
Coupling. You can also specify those via the Parallel
|
|
31
|
+
Partitioning dialog box in the System Coupling GUI.
|
|
32
|
+
"""
|
|
33
|
+
|
|
34
|
+
syc_name = "GetMachines"
|
|
@@ -0,0 +1,29 @@
|
|
|
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 get_mode_shape_variables(Command):
|
|
9
|
+
"""
|
|
10
|
+
Given an interface name, returns a list of mode shape variables available
|
|
11
|
+
from the MECH-SRV participant.
|
|
12
|
+
|
|
13
|
+
Parameters
|
|
14
|
+
----------
|
|
15
|
+
interface : str
|
|
16
|
+
String indicating the name of the interface.
|
|
17
|
+
|
|
18
|
+
"""
|
|
19
|
+
|
|
20
|
+
syc_name = "GetModeShapeVariables"
|
|
21
|
+
|
|
22
|
+
argument_names = ["interface"]
|
|
23
|
+
|
|
24
|
+
class interface(String):
|
|
25
|
+
"""
|
|
26
|
+
String indicating the name of the interface.
|
|
27
|
+
"""
|
|
28
|
+
|
|
29
|
+
syc_name = "Interface"
|
|
@@ -0,0 +1,32 @@
|
|
|
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 get_region_names_for_participant(Command):
|
|
9
|
+
"""
|
|
10
|
+
This query is deprecated and will be deleted in future releases.
|
|
11
|
+
To get region names for a participant, you can use ``get_child_names``
|
|
12
|
+
query, for example:
|
|
13
|
+
|
|
14
|
+
``setup.coupling_participant[name].region.get_child_names()```
|
|
15
|
+
|
|
16
|
+
Parameters
|
|
17
|
+
----------
|
|
18
|
+
participant_name : str
|
|
19
|
+
Name of the participant.
|
|
20
|
+
|
|
21
|
+
"""
|
|
22
|
+
|
|
23
|
+
syc_name = "GetRegionNamesForParticipant"
|
|
24
|
+
|
|
25
|
+
argument_names = ["participant_name"]
|
|
26
|
+
|
|
27
|
+
class participant_name(String):
|
|
28
|
+
"""
|
|
29
|
+
Name of the participant.
|
|
30
|
+
"""
|
|
31
|
+
|
|
32
|
+
syc_name = "ParticipantName"
|
|
@@ -0,0 +1,25 @@
|
|
|
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 get_setup_summary(InjectedCommand):
|
|
9
|
+
"""
|
|
10
|
+
Returns a string containing a formatted summary of the
|
|
11
|
+
coupled analysis setup.
|
|
12
|
+
|
|
13
|
+
This summary is printed in the System Coupling transcript
|
|
14
|
+
output at the beginning of a solve. However, it is sometimes
|
|
15
|
+
useful to see the summary before starting the solve.
|
|
16
|
+
|
|
17
|
+
The summary output is generated by System Coupling and is not
|
|
18
|
+
modified for PySystemCoupling purposes. Any ``datamodel`` type names
|
|
19
|
+
that are referenced in the summary therefore might not
|
|
20
|
+
be fully consistent with PySystemCoupling conventions.
|
|
21
|
+
"""
|
|
22
|
+
|
|
23
|
+
syc_name = "GetSetupSummary"
|
|
24
|
+
|
|
25
|
+
cmd_name = "get_setup_summary"
|
|
@@ -0,0 +1,52 @@
|
|
|
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 get_status_messages(InjectedCommand):
|
|
9
|
+
"""
|
|
10
|
+
Provides information relating to the current state of the analysis setup.
|
|
11
|
+
|
|
12
|
+
The return value is a list of dictionaries. Each dictionary holds a
|
|
13
|
+
single message about the setup status, along with some associated information.
|
|
14
|
+
The dictionary has string-valued fields: ``"message"``, ``"level"``,
|
|
15
|
+
and ``"path"``.
|
|
16
|
+
|
|
17
|
+
The ``"message"`` field is the actual text of the message.
|
|
18
|
+
|
|
19
|
+
.. note::
|
|
20
|
+
In the current release, generated messages have not been adapted to
|
|
21
|
+
the PySystemCoupling environment and may use naming and terminology that
|
|
22
|
+
is native to the System Coupling application and its own command line
|
|
23
|
+
interface.
|
|
24
|
+
|
|
25
|
+
Because there is generally a straightforward mapping to the PySystemCoupling
|
|
26
|
+
exposure of settings and so on, the messages should not be difficult
|
|
27
|
+
to interpret. Nevertheless, the ``get_status_messages`` method should
|
|
28
|
+
be regarded as *beta* functionality in the current release.
|
|
29
|
+
|
|
30
|
+
The ``"level"`` field provides information about the severity or nature of the
|
|
31
|
+
message. Possible values are ``"Error"``, ``"Warning"``, ``"Information"``,
|
|
32
|
+
``"Alpha"``, and ``"Beta"``. ``"Alpha"`` and ``"Beta"`` indicate settings related
|
|
33
|
+
to activated alpha or beta features.
|
|
34
|
+
|
|
35
|
+
It is not possible to solve an analysis that has any issues at the ``"Error"``
|
|
36
|
+
severity level. An attempt to invoke the ``solve`` command while there are
|
|
37
|
+
any errors results in an immediate failure.
|
|
38
|
+
|
|
39
|
+
If the ``"path"`` field is set, it contains a string representation of the path
|
|
40
|
+
to the setting to which the message pertains. This is given in the form of
|
|
41
|
+
chained Python attribute accesses starting from the ``setup`` attribute.
|
|
42
|
+
|
|
43
|
+
Thus, if an issue were detected that is specific to the ``absolute_gap_tolerance``
|
|
44
|
+
setting in a particular coupling interface, a ``"path"`` such as the following would
|
|
45
|
+
be provided:
|
|
46
|
+
|
|
47
|
+
``'coupling_interface["Interface-1"].mapping_control.absolute_gap_tolerance'``
|
|
48
|
+
"""
|
|
49
|
+
|
|
50
|
+
syc_name = "GetErrors"
|
|
51
|
+
|
|
52
|
+
cmd_name = "get_status_messages"
|