ansys-api-systemcoupling 0.1.0__tar.gz → 0.3.1__tar.gz

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2022 ANSYS, Inc. All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2022 ANSYS, Inc. All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

{ansys-api-systemcoupling-0.1.0/src/ansys_api_systemcoupling.egg-info → ansys_api_systemcoupling-0.3.1}/PKG-INFO

@@ -1,72 +1,84 @@
-Metadata-Version: 2.1
-Name: ansys-api-systemcoupling
-Version: 0.1.0
-Summary: Autogenerated python gRPC interface package for ansys-api-systemcoupling, built on 13:54:04 on 21 February 2023
-Home-page: https://github.com/ansys/ansys-api-systemcoupling
-Author: ANSYS, Inc.
-Author-email: support@ansys.com
-License: MIT
-Requires-Python: >=3.7
-Description-Content-Type: text/markdown
-License-File: LICENSE
-
-### ansys-api-systemcoupling gRPC Interface Package
-
-This Python package contains the auto-generated gRPC Python interface files for
-System Coupling.
-
-
-#### Installation
-
-Provided that these wheels have been published to public PyPI, they can be
-installed with:
-
-```
-pip install ansys-api-systemcoupling
-```
-
-#### Build
-
-To build the gRPC packages, run:
-
-```
-pip install build
-python -m build
-```
-
-This will create both the source distribution containing just the protofiles
-along with the wheel containing the protofiles and build Python interface
-files.
-
-Note that the interface files are identical regardless of the version of Python
-used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
-Python 3.7, so to improve your build time, use Python 3.7 when building the
-wheel.
-
-
-#### Manual Deployment
-
-After building the packages, manually deploy them with:
-
-```
-pip install twine
-twine upload dist/*
-```
-
-Note that this is automatically done through CI/CD.
-
-
-#### Automatic Deployment
-
-This repository contains GitHub CI/CD that enables the automatic building of
-source and wheel packages for these gRPC Python interface files. By default,
-these are built on PRs, the main branch, and on tags when pushing. Artifacts
-are uploaded for each PR.
-
-To publicly release wheels to PyPI, ensure your branch is up-to-date and then
-push tags. For example, for the version ``v0.5.0``.
-
-```bash
-git tag v0.5.0
-git push --tags
-```
+Metadata-Version: 2.4
+Name: ansys-api-systemcoupling
+Version: 0.3.1
+Summary: Autogenerated python gRPC interface package for ansys-api-systemcoupling, built on 11:30:16 on 06 February 2026
+Home-page: https://github.com/ansys/ansys-api-systemcoupling
+Author: ANSYS, Inc.
+Author-email: support@ansys.com
+License: MIT
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: grpcio~=1.30
+Requires-Dist: protobuf<7,>=3.19
+Dynamic: author
+Dynamic: author-email
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+### ansys-api-systemcoupling gRPC Interface Package
+
+This Python package contains the auto-generated gRPC Python interface files for
+System Coupling.
+
+
+#### Installation
+
+Provided that these wheels have been published to public PyPI, they can be
+installed with:
+
+```
+pip install ansys-api-systemcoupling
+```
+
+#### Build
+
+To build the gRPC packages, run:
+
+```
+pip install build
+python -m build
+```
+
+This will create both the source distribution containing just the protofiles
+along with the wheel containing the protofiles and build Python interface
+files.
+
+Note that the interface files are identical regardless of the version of Python
+used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
+Python 3.7, so to improve your build time, use Python 3.7 when building the
+wheel.
+
+
+#### Manual Deployment
+
+After building the packages, manually deploy them with:
+
+```
+pip install twine
+twine upload dist/*
+```
+
+Note that this is automatically done through CI/CD.
+
+
+#### Automatic Deployment
+
+This repository contains GitHub CI/CD that enables the automatic building of
+source and wheel packages for these gRPC Python interface files. By default,
+these are built on PRs, the main branch, and on tags when pushing. Artifacts
+are uploaded for each PR.
+
+To publicly release wheels to PyPI, ensure your branch is up-to-date and then
+push tags. For example, for the version ``v0.5.0``.
+
+```bash
+git tag v0.5.0
+git push --tags
+```

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/README.md

@@ -1,60 +1,60 @@
-### ansys-api-systemcoupling gRPC Interface Package
-
-This Python package contains the auto-generated gRPC Python interface files for
-System Coupling.
-
-
-#### Installation
-
-Provided that these wheels have been published to public PyPI, they can be
-installed with:
-
-```
-pip install ansys-api-systemcoupling
-```
-
-#### Build
-
-To build the gRPC packages, run:
-
-```
-pip install build
-python -m build
-```
-
-This will create both the source distribution containing just the protofiles
-along with the wheel containing the protofiles and build Python interface
-files.
-
-Note that the interface files are identical regardless of the version of Python
-used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
-Python 3.7, so to improve your build time, use Python 3.7 when building the
-wheel.
-
-
-#### Manual Deployment
-
-After building the packages, manually deploy them with:
-
-```
-pip install twine
-twine upload dist/*
-```
-
-Note that this is automatically done through CI/CD.
-
-
-#### Automatic Deployment
-
-This repository contains GitHub CI/CD that enables the automatic building of
-source and wheel packages for these gRPC Python interface files. By default,
-these are built on PRs, the main branch, and on tags when pushing. Artifacts
-are uploaded for each PR.
-
-To publicly release wheels to PyPI, ensure your branch is up-to-date and then
-push tags. For example, for the version ``v0.5.0``.
-
-```bash
-git tag v0.5.0
-git push --tags
-```
+### ansys-api-systemcoupling gRPC Interface Package
+
+This Python package contains the auto-generated gRPC Python interface files for
+System Coupling.
+
+
+#### Installation
+
+Provided that these wheels have been published to public PyPI, they can be
+installed with:
+
+```
+pip install ansys-api-systemcoupling
+```
+
+#### Build
+
+To build the gRPC packages, run:
+
+```
+pip install build
+python -m build
+```
+
+This will create both the source distribution containing just the protofiles
+along with the wheel containing the protofiles and build Python interface
+files.
+
+Note that the interface files are identical regardless of the version of Python
+used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
+Python 3.7, so to improve your build time, use Python 3.7 when building the
+wheel.
+
+
+#### Manual Deployment
+
+After building the packages, manually deploy them with:
+
+```
+pip install twine
+twine upload dist/*
+```
+
+Note that this is automatically done through CI/CD.
+
+
+#### Automatic Deployment
+
+This repository contains GitHub CI/CD that enables the automatic building of
+source and wheel packages for these gRPC Python interface files. By default,
+these are built on PRs, the main branch, and on tags when pushing. Artifacts
+are uploaded for each PR.
+
+To publicly release wheels to PyPI, ensure your branch is up-to-date and then
+push tags. For example, for the version ``v0.5.0``.
+
+```bash
+git tag v0.5.0
+git push --tags
+```

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/pyproject.toml

@@ -1,3 +1,3 @@
-[build-system]
-requires = ["setuptools >= 42.0.0", "wheel", "ansys_tools_protoc_helper"]
-build-backend = "setuptools.build_meta:__legacy__"
+[build-system]
+requires = ["setuptools >= 42.0.0", "wheel", "ansys_tools_protoc_helper>=0.4.0"]
+build-backend = "setuptools.build_meta:__legacy__"

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/setup.cfg

@@ -1,4 +1,4 @@
-[egg_info]
-tag_build = 
-tag_date = 0
-
+[egg_info]
+tag_build = 
+tag_date = 0
+

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/setup.py

@@ -1,50 +1,53 @@
-"""Installation file for the ansys-api-systemcoupling package"""
-
-import os
-from datetime import datetime
-
-import setuptools
-
-from ansys.tools.protoc_helper import CMDCLASS_OVERRIDE
-
-# Get the long description from the README file
-HERE = os.path.abspath(os.path.dirname(__file__))
-with open(os.path.join(HERE, "README.md"), encoding="utf-8") as f:
-    long_description = f.read()
-
-product = "systemcoupling"
-library = ""
-package_info = ["ansys", "api", product, library, "v0"]
-with open(os.path.join(HERE, "src", "ansys", "api", product, library, "VERSION"), encoding="utf-8") as f:
-    version = f.read().strip()
-
-package_name = "ansys-api-systemcoupling"
-dot_package_name = '.'.join(filter(None, package_info))
-
-description = f"Autogenerated python gRPC interface package for {package_name}, built on {datetime.now().strftime('%H:%M:%S on %d %B %Y')}"
-
-if __name__ == "__main__":
-    setuptools.setup(
-        name=package_name,
-        version=version,
-        author="ANSYS, Inc.",
-        author_email='support@ansys.com',
-        description=description,
-        long_description=long_description,
-        long_description_content_type='text/markdown',
-        url=f"https://github.com/ansys/{package_name}",
-        license="MIT",
-        python_requires=">=3.7",
-        install_requires=["grpcio~=1.30", "protobuf~=3.20"],
-        package_dir = {"": "src"},
-        packages=setuptools.find_namespace_packages("src", include=("ansys.*",)),
-        package_data={
-            "": ["*.proto", "*.pyi", "py.typed", "VERSION"],
-        },
-        entry_points={
-            "ansys.tools.protoc_helper.proto_provider": [
-                f"{dot_package_name}={dot_package_name}"
-            ],
-        },
-        cmdclass=CMDCLASS_OVERRIDE
-    )
+"""Installation file for the ansys-api-systemcoupling package"""
+
+import os
+from datetime import datetime
+
+import setuptools
+
+from ansys.tools.protoc_helper import CMDCLASS_OVERRIDE
+
+# Get the long description from the README file
+HERE = os.path.abspath(os.path.dirname(__file__))
+with open(os.path.join(HERE, "README.md"), encoding="utf-8") as f:
+    long_description = f.read()
+
+product = "systemcoupling"
+library = ""
+package_info = ["ansys", "api", product, library, "v0"]
+with open(
+    os.path.join(HERE, "src", "ansys", "api", product, library, "VERSION"),
+    encoding="utf-8",
+) as f:
+    version = f.read().strip()
+
+package_name = "ansys-api-systemcoupling"
+dot_package_name = ".".join(filter(None, package_info))
+
+description = f"Autogenerated python gRPC interface package for {package_name}, built on {datetime.now().strftime('%H:%M:%S on %d %B %Y')}"
+
+if __name__ == "__main__":
+    setuptools.setup(
+        name=package_name,
+        version=version,
+        author="ANSYS, Inc.",
+        author_email="support@ansys.com",
+        description=description,
+        long_description=long_description,
+        long_description_content_type="text/markdown",
+        url=f"https://github.com/ansys/{package_name}",
+        license="MIT",
+        python_requires=">=3.7",
+        install_requires=["grpcio~=1.30", "protobuf>=3.19,<7"],
+        package_dir={"": "src"},
+        packages=setuptools.find_namespace_packages("src", include=("ansys.*",)),
+        package_data={
+            "": ["*.proto", "*.pyi", "py.typed", "VERSION"],
+        },
+        entry_points={
+            "ansys.tools.protoc_helper.proto_provider": [
+                f"{dot_package_name}={dot_package_name}"
+            ],
+        },
+        cmdclass=CMDCLASS_OVERRIDE,
+    )

ansys_api_systemcoupling-0.3.1/src/ansys/api/systemcoupling/VERSION

@@ -0,0 +1 @@
+0.3.1

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/__init__.py

@@ -1,8 +1,8 @@
-"""Autogenerated Python gRPC interface package for ansys-api-systemcoupling."""
-
-import pathlib
-
-__all__ = ["__version__"]
-
-with open(pathlib.Path(__file__).parent / "VERSION", encoding="utf-8") as f:
-    __version__ = f.read().strip()
+"""Autogenerated Python gRPC interface package for ansys-api-systemcoupling."""
+
+import pathlib
+
+__all__ = ["__version__"]
+
+with open(pathlib.Path(__file__).parent / "VERSION", encoding="utf-8") as f:
+    __version__ = f.read().strip()

ansys_api_systemcoupling-0.3.1/src/ansys/api/systemcoupling/v0/chart.proto

@@ -0,0 +1,159 @@
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+// Enum containing the different types of chart series.
+enum TransferSeriesType {
+  SERIES_TYPE_UNKNOWN=0;
+  SERIES_TYPE_CONVERGENCE = 1;
+  SERIES_TYPE_SUM = 2;
+  SERIES_TYPE_WEIGHTED_AVERAGE = 3;
+}
+
+// Information about the chart series data associated with a data transfer.
+message TransferSeriesInfo {
+	// The type of line series.
+	TransferSeriesType series_type = 1;
+	// The unique internal name of the data transfer.
+	string transfer_name = 2;
+	// The unique internal name of the participant. This is required for transfer value series
+	// but is empty for CONVERGENCE series. Used in chart labelling.
+	string participant_name = 3;
+	// The suffix for this component series, if applicable. This is only needed for
+	// transfer value series that have multiple components, such as complex or vector
+	// values. Suffixes for complex components are "real" and "imag", and suffixes for
+	// vector components are "x", "y", and "z". A combination is possible, such as
+	// "y real" and "x imag". (Empty for CONVERGENCE series)
+	string component_suffix = 4;
+}
+
+// Information about the chart series data associated with a single interface.
+message InterfaceInfo {
+	// The name of the coupling interface data model object.
+	string interface_name = 1;
+	// The list of TransferSeriesInfo associated with this interface.
+	repeated TransferSeriesInfo transfer_info = 2;
+}
+
+// Complete metadata for available chart series.
+message ChartMetadata {
+	// Whether the chart is for a transient analysis.
+	bool is_transient = 1;
+	// The metadata for the series associated with each interface.
+	repeated InterfaceInfo interface_info = 2;
+}
+
+// The plot data for a single chart line series and information to allow
+// it to be associated with chart metadata.
+// An instance of this type is assumed to be associated with a single interface.
+// This message supports per-iteration incremental data, batched data for a
+// subset of iterations, or complete data for all iterations.
+message SeriesData {
+	// The name of the interface this series is associated with.
+	string interface_name = 1;
+	// Index of the TransferSeriesInfo metadata for this series within the
+	// InterfaceInfo for the interface this series is associated with.
+	int32 transfer_series_index = 2;
+	// The 0-based start index of the data field. This defaults to 0 and
+	// only needs to be set to a different value if incremental data, such
+	// as might arise during "live" update of plots, has become available.
+	// Data indexes correspond to iterations. Iteration N will have an
+	// index of N-1.
+	int32 start_index = 3;
+	// The series data. This is always indexed by iteration. Extract time
+	// step-based data by using a time step to iteration mapping.
+	repeated double data = 4;
+}
+
+
+// Message providing notification and details of a new timestep in a transient analysis.
+// This message is intended for use in live updates. See TimestepData for
+// cumulative timestep information.
+message TimestepStart {
+	// The timestep count of the new timestep.
+	int32 timestep_count = 1;
+	// The end time of the current timestep.
+	// For the first timestep, this is the timestep size. For subsequent
+	// timesteps, the timestep size can be determined by subtracting the previous
+	// time value from the current time value.
+	double time = 2;
+}
+
+// Message providing notification and details of the end of a timestep in a transient analysis.
+// This message is intended for use in live updates. See TimestepData for
+// cumulative timestep information.
+message TimestepEnd {
+	// The timestep count of the ended timestep.
+	int32 timestep_count = 1;
+	// The ending iteration for the timestep. NB: This is a 1-based iteration count.
+	int32 iteration_count = 2;
+}
+
+// Chart data event that can contain different types of chart data.
+// The first event in a stream will typically contain interface metadata,
+// followed by series data and timestep data as they become available.
+message ChartDataEvent {
+	oneof event_data {
+		// Metadata containing information about the available series.
+		ChartMetadata metadata = 1;
+		// Series data for a specific chart line series.
+		SeriesData series_data = 2;
+		// Timestep start notification for transient analyses.
+		TimestepStart timestep_start = 3;
+		// Timestep end notification for transient analyses.
+		TimestepEnd timestep_end = 4;
+	}
+}
+
+// Message providing all series data for all interfaces.
+// For use in post-solve, non-streaming retrieval of chart data.
+message AllSeriesData {
+	// List of all available series data.
+	repeated SeriesData series_data = 1;
+}
+
+// Message providing all timestep data for transient analyses.
+// For use in post-solve, non-streaming retrieval of chart data.
+message TimestepData {
+	// The mapping of timestep count to iteration count.
+	// NB: these are 1-based step and iteration counts.
+	repeated int32 timestep_to_iteration = 1;
+	// The time values for each timestep.
+	repeated double time_values = 2;
+}
+
+// Service for querying chart data, both as a "live" stream during a solve
+// and as non-streaming requests for data after a solve has been performed.
+service ChartData {
+	// Streams chart data events starting with interface metadata followed by
+	// series data and timestep data as they become available on the server.
+	// For transient cases, timestep data will be included in the stream.
+	rpc StreamChartData(ChartDataRequest) returns (stream ChartDataEvent);
+
+	// The following RPCs provide non-streaming access to chart data.
+	// This should be available as long as a solve has been performed
+	// in the current session.
+
+	// Retrieves the chart metadata for all available series.
+	rpc GetChartMetadata(ChartMetadataRequest) returns (ChartMetadata);
+	// Retrieves all data for all chart series.
+	rpc GetChartSeriesData(ChartSeriesDataRequest) returns (AllSeriesData);
+	// Retrieves all data for all chart timesteps.
+	rpc GetChartTimestepData(ChartTimestepDataRequest) returns (TimestepData);
+}
+
+// Request message for chart data streaming.
+message ChartDataRequest {
+}
+
+// Request message for chart metadata retrieval.
+message ChartMetadataRequest {
+}
+
+// Request message for all chart series data retrieval.
+message ChartSeriesDataRequest {
+}
+
+// Request message for chart timestep data retrieval.
+message ChartTimestepDataRequest {
+}

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/command.proto

@@ -1,23 +1,23 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-import "ansys/api/systemcoupling/v0/variant.proto";
-
-service Command {
-  rpc InvokeCommand (CommandRequest) returns (CommandResponse) {}
-}
-
-message CommandRequest {
-  message Argument {
-    string name = 1;
-    Variant val = 2;
-  }
-  string command = 1;
-  repeated Argument args = 2;
-}
-
-message CommandResponse {
-  Variant result = 1;
-}
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+import "ansys/api/systemcoupling/v0/variant.proto";
+
+service Command {
+  rpc InvokeCommand (CommandRequest) returns (CommandResponse) {}
+}
+
+message CommandRequest {
+  message Argument {
+    string name = 1;
+    Variant val = 2;
+  }
+  string command = 1;
+  repeated Argument args = 2;
+}
+
+message CommandResponse {
+  Variant result = 1;
+}

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/error.proto

@@ -1,9 +1,9 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-message ErrorDetails {
-  string exception_classname = 1;
-  string stack_trace = 2;
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+message ErrorDetails {
+  string exception_classname = 1;
+  string stack_trace = 2;
 }

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/output_stream.proto

@@ -1,15 +1,15 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-service OutputStream {
-  rpc BeginStdStreaming(StdStreamRequest) returns (stream StdStreamResponse) {}
-}
-
-message StdStreamRequest {
-}
-
-message StdStreamResponse {
-  string text = 1;
-}
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+service OutputStream {
+  rpc BeginStdStreaming(StdStreamRequest) returns (stream StdStreamResponse) {}
+}
+
+message StdStreamRequest {
+}
+
+message StdStreamResponse {
+  string text = 1;
+}

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/process.proto

@@ -1,15 +1,15 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-service Process {
-  rpc Ping (PingRequest) returns (PingResponse) {}
-  rpc Quit (QuitRequest) returns (QuitResponse) {}
-}
-
-message PingRequest {}
-message PingResponse {}
-
-message QuitRequest {}
-message QuitResponse {}
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+service Process {
+  rpc Ping (PingRequest) returns (PingResponse) {}
+  rpc Quit (QuitRequest) returns (QuitResponse) {}
+}
+
+message PingRequest {}
+message PingResponse {}
+
+message QuitRequest {}
+message QuitResponse {}

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/solution.proto

@@ -1,30 +1,30 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-service Solution {
-  rpc Solve (SolveRequest) returns (SolveResponse) {}
-  rpc Interrupt (InterruptRequest) returns (InterruptResponse) {}
-  rpc Abort (AbortRequest) returns (AbortResponse) {}
-}
-
-// Note that all responses are currently empty messages
-// In particular no status info for solve is returned -
-// failure or early termination of solve will be
-// communicated by an exception as for commands
-// via the Command service.
-
-message SolveRequest {}
-message SolveResponse {}
-
-message InterruptRequest {
-  string reason = 1;
-}
-message InterruptResponse {}
-
-message AbortRequest {
-  string reason = 1;
-}
-message AbortResponse {}
-
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+service Solution {
+  rpc Solve (SolveRequest) returns (SolveResponse) {}
+  rpc Interrupt (InterruptRequest) returns (InterruptResponse) {}
+  rpc Abort (AbortRequest) returns (AbortResponse) {}
+}
+
+// Note that all responses are currently empty messages
+// In particular no status info for solve is returned -
+// failure or early termination of solve will be
+// communicated by an exception as for commands
+// via the Command service.
+
+message SolveRequest {}
+message SolveResponse {}
+
+message InterruptRequest {
+  string reason = 1;
+}
+message InterruptResponse {}
+
+message AbortRequest {
+  string reason = 1;
+}
+message AbortResponse {}
+

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys/api/systemcoupling/v0/variant.proto

@@ -1,51 +1,51 @@
-// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
-syntax = "proto3";
-
-package ansys.api.systemcoupling.v0;
-
-enum NoneValue {
-  NONE_VALUE=0;
-}
-
-message StringVector {
-  repeated string item = 1;
-}
-
-message DoubleVector {
-  repeated double item = 1;
-}
-
-message BoolVector {
-  repeated bool item = 1;
-}
-
-message Int64Vector {
-  repeated sint64 item = 1;
-}
-
-message VariantMap {
-  map<string, Variant> item = 1;
-}
-
-message VariantVector {
-  repeated Variant item = 1;
-}
-
-message Variant {
-  oneof as {
-      NoneValue none_state = 1;
-
-      bool bool_state = 2;
-      sint64 int64_state = 3;
-      double double_state = 5;
-      string string_state = 6;
-
-      BoolVector bool_vector_state = 7;
-      Int64Vector int64_vector_state = 8;
-      DoubleVector double_vector_state = 9;
-      StringVector string_vector_state = 10;
-      VariantVector variant_vector_state = 11;
-      VariantMap variant_map_state = 12;
-  }
-}
-
+// Copyright (C) 2023 ANSYS, Inc. and/or its affiliates.
+syntax = "proto3";
+
+package ansys.api.systemcoupling.v0;
+
+enum NoneValue {
+  NONE_VALUE=0;
+}
+
+message StringVector {
+  repeated string item = 1;
+}
+
+message DoubleVector {
+  repeated double item = 1;
+}
+
+message BoolVector {
+  repeated bool item = 1;
+}
+
+message Int64Vector {
+  repeated sint64 item = 1;
+}
+
+message VariantMap {
+  map<string, Variant> item = 1;
+}
+
+message VariantVector {
+  repeated Variant item = 1;
+}
+
+message Variant {
+  oneof as {
+      NoneValue none_state = 1;
+
+      bool bool_state = 2;
+      sint64 int64_state = 3;
+      double double_state = 5;
+      string string_state = 6;
+
+      BoolVector bool_vector_state = 7;
+      Int64Vector int64_vector_state = 8;
+      DoubleVector double_vector_state = 9;
+      StringVector string_vector_state = 10;
+      VariantVector variant_vector_state = 11;
+      VariantMap variant_map_state = 12;
+  }
+}
+

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1/src/ansys_api_systemcoupling.egg-info}/PKG-INFO

@@ -1,72 +1,84 @@
-Metadata-Version: 2.1
-Name: ansys-api-systemcoupling
-Version: 0.1.0
-Summary: Autogenerated python gRPC interface package for ansys-api-systemcoupling, built on 13:54:04 on 21 February 2023
-Home-page: https://github.com/ansys/ansys-api-systemcoupling
-Author: ANSYS, Inc.
-Author-email: support@ansys.com
-License: MIT
-Requires-Python: >=3.7
-Description-Content-Type: text/markdown
-License-File: LICENSE
-
-### ansys-api-systemcoupling gRPC Interface Package
-
-This Python package contains the auto-generated gRPC Python interface files for
-System Coupling.
-
-
-#### Installation
-
-Provided that these wheels have been published to public PyPI, they can be
-installed with:
-
-```
-pip install ansys-api-systemcoupling
-```
-
-#### Build
-
-To build the gRPC packages, run:
-
-```
-pip install build
-python -m build
-```
-
-This will create both the source distribution containing just the protofiles
-along with the wheel containing the protofiles and build Python interface
-files.
-
-Note that the interface files are identical regardless of the version of Python
-used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
-Python 3.7, so to improve your build time, use Python 3.7 when building the
-wheel.
-
-
-#### Manual Deployment
-
-After building the packages, manually deploy them with:
-
-```
-pip install twine
-twine upload dist/*
-```
-
-Note that this is automatically done through CI/CD.
-
-
-#### Automatic Deployment
-
-This repository contains GitHub CI/CD that enables the automatic building of
-source and wheel packages for these gRPC Python interface files. By default,
-these are built on PRs, the main branch, and on tags when pushing. Artifacts
-are uploaded for each PR.
-
-To publicly release wheels to PyPI, ensure your branch is up-to-date and then
-push tags. For example, for the version ``v0.5.0``.
-
-```bash
-git tag v0.5.0
-git push --tags
-```
+Metadata-Version: 2.4
+Name: ansys-api-systemcoupling
+Version: 0.3.1
+Summary: Autogenerated python gRPC interface package for ansys-api-systemcoupling, built on 11:30:16 on 06 February 2026
+Home-page: https://github.com/ansys/ansys-api-systemcoupling
+Author: ANSYS, Inc.
+Author-email: support@ansys.com
+License: MIT
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: grpcio~=1.30
+Requires-Dist: protobuf<7,>=3.19
+Dynamic: author
+Dynamic: author-email
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+### ansys-api-systemcoupling gRPC Interface Package
+
+This Python package contains the auto-generated gRPC Python interface files for
+System Coupling.
+
+
+#### Installation
+
+Provided that these wheels have been published to public PyPI, they can be
+installed with:
+
+```
+pip install ansys-api-systemcoupling
+```
+
+#### Build
+
+To build the gRPC packages, run:
+
+```
+pip install build
+python -m build
+```
+
+This will create both the source distribution containing just the protofiles
+along with the wheel containing the protofiles and build Python interface
+files.
+
+Note that the interface files are identical regardless of the version of Python
+used to generate them, but the last pre-built wheel for ``grpcio~=1.30`` was
+Python 3.7, so to improve your build time, use Python 3.7 when building the
+wheel.
+
+
+#### Manual Deployment
+
+After building the packages, manually deploy them with:
+
+```
+pip install twine
+twine upload dist/*
+```
+
+Note that this is automatically done through CI/CD.
+
+
+#### Automatic Deployment
+
+This repository contains GitHub CI/CD that enables the automatic building of
+source and wheel packages for these gRPC Python interface files. By default,
+these are built on PRs, the main branch, and on tags when pushing. Artifacts
+are uploaded for each PR.
+
+To publicly release wheels to PyPI, ensure your branch is up-to-date and then
+push tags. For example, for the version ``v0.5.0``.
+
+```bash
+git tag v0.5.0
+git push --tags
+```

{ansys-api-systemcoupling-0.1.0 → ansys_api_systemcoupling-0.3.1}/src/ansys_api_systemcoupling.egg-info/SOURCES.txt

@@ -5,6 +5,7 @@ setup.py
 src/ansys/api/systemcoupling/VERSION
 src/ansys/api/systemcoupling/__init__.py
 src/ansys/api/systemcoupling/py.typed
+src/ansys/api/systemcoupling/v0/chart.proto
 src/ansys/api/systemcoupling/v0/command.proto
 src/ansys/api/systemcoupling/v0/error.proto
 src/ansys/api/systemcoupling/v0/output_stream.proto

ansys_api_systemcoupling-0.3.1/src/ansys_api_systemcoupling.egg-info/requires.txt

@@ -0,0 +1,2 @@
+grpcio~=1.30
+protobuf<7,>=3.19

ansys-api-systemcoupling-0.1.0/src/ansys/api/systemcoupling/VERSION

@@ -1 +0,0 @@
-0.1.0

ansys-api-systemcoupling-0.1.0/src/ansys_api_systemcoupling.egg-info/requires.txt

@@ -1,2 +0,0 @@
-grpcio~=1.30
-protobuf~=3.20