This project has been archived by its maintainers, and is no longer receiving any updates.
⚠️ Warning
This library is deprecated; it will no longer be maintained and will not receive further updates.
A pythonic remotable interface to RedHawkSC and TotemSC that allows integration with other PyAnsys and Python libraries.
How to install
Install from PyPI
User installation can be performed by running:
pip install ansys-seascape
OR
python -m pip install ansys-seascape
Install from latest Github source
Fetch latest source from github:
cd <your-library-directory>
git clone https://github.com/ansys/pyseascape.git
(Optional) Create and enable virtual environment. Please refer to official venv documentation for more help regarding virtual environment setup.
# Create a virtual environment
python -m venv .venv
# Activate it in a POSIX system
source .venv/bin/activate
# Activate it in Windows CMD environment
.venv\Scripts\activate.bat
# Activate it in Windows Powershell
.venv\Scripts\Activate.ps1
Install the project
cd pyseascape
pip install .
Install additional requirements (if needed):
python -m pip install .[tests]
python -m pip install .[doc]
Usage
Note: Either a local installation or remote connection to licensed RedHawk-SC is required to use the pyseascape library. This only offers a remotable frontend interface that can run directly in native Python on any machine.
Launching local RedHawk-SC in backend
from ansys.seascape import RedHawkSC
gp = RedHawkSC(executable=path_to_executable)
OR
from ansys import seascape
gp = seascape.RedHawkSC(executable=path_to_executable)
Connecting to remote RedHawk-SC session
from ansys.seascape import RedHawkSC
url_and_port = url_or_ip_to_redhawksc_server + ":" + port
gp = RedHawkSC(url=url_and_port)
All RedHawk-SC global functions can be called using prefix of RedHawkSC object name. Object methods can be called as normal.
Running RedHawk-SC commands
For example:
# If gp = RedHawkSC(...)
db = gp.open_db(db_name) # Returns a SeascapeDB remotable object
db.create_design_view(...)
# Creating RedHawk-SC objects
inst = gp.Instance("Inst_Name")
# RedHawk-SC modules must also be prefixed by gp
# E.g. using voltage_impact module
gp.voltage_impact.helpers.get_pgimpact_histograms(...)
Accessing RedHawk-SC help
RedHawk-SC native help function supports command based as well as keyword based help. This help can be accessed remotely as well.
# If gp = RedHawkSC(...)
# command based help
gp.help(command="gp.Scatter")
# keyword based help
gp.help(keyword="scatter")
Known issues and limitations
GUI features have not yet been implemented. Hence, commands like open_console_window, open_scheduler_window etc. do not work yet. Commands like gp.scatter_plot also does not work as it requires drawing gui plots
Documentation
Please refer to RedHawk-SC Documentation.
Metadata
Release files for ansys-seascape 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ansys_seascape-0.2.1.tar.gz | 10.6 kB | With provenance | Details for ansys_seascape-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ansys_seascape-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for ansys_seascape-0.2.1-py3-none-any.whl |
Total release size: 22.8 kB
Release files / ansys_seascape-0.2.1.tar.gz
| Download URL | ansys_seascape-0.2.1.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4c25feeb527bad8d5c0e83fe1a0e43c4d51a618ad875a1fb66a83acb9ed67d1
|
|
BLAKE2b-256 checksum How to use checksums |
80c8c504a07431878405ce6635ad651adee31a1e6522a678fddd3b9c46d49686
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / ansys_seascape-0.2.1-py3-none-any.whl
| Download URL | ansys_seascape-0.2.1-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28d116aaf916811e59b73649ecbf9f838a6d6aa2b23bcdeaabb1299b94539f4e
|
|
BLAKE2b-256 checksum How to use checksums |
f16735bee6e9685e8bed6b01bcca38e2a2f70b18ed535125a2b3806eb90acd39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logSecurity for ansys-seascape 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ansys_seascape-0.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.