stepss 3.59__tar.gz → 3.70__tar.gz

{stepss-3.59/stepss.egg-info → stepss-3.70}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stepss
-Version: 3.59
+Version: 3.70
 Summary: Python interface to the STEPSS power-system simulation platform.
 Home-page: https://stepss.sps-lab.org
 Author: Petros Aristidou
@@ -55,7 +55,7 @@ STEPSS is delivered in two editions, which drive the same simulation engines and
 - **STEPSS for Python**, this package. ``pip install stepss``, then script simulations from Python or a Jupyter notebook.
 - **STEPSS for Java**, a desktop application. A single ``stepss.jar`` with a graphical interface, published on the `releases page <https://github.com/SPS-L/stepss-java-ui/releases>`_.
 
-Neither is a wrapper around the other: they are two front ends onto the same Fortran engines, and a case built in one runs unchanged in the other. Pick this one to automate, sweep parameters, or work inside the scientific Python stack; pick the Java edition for interactive work, or for the model-building and curve-viewing tools it carries that this edition does not (see `Choosing an edition`_).
+Neither is a wrapper around the other: they are two front ends onto the same Fortran engines, and a case built in one runs unchanged in the other. Pick this one to automate, sweep parameters, or work inside the scientific Python stack; pick the Java edition for interactive point-and-click work, or to build your own models with CODEGEN (see `Choosing an edition`_).
 
 What this edition bundles
 -------------------------
@@ -70,10 +70,11 @@ Pre-compiled shared libraries for Linux, Windows and macOS ship inside the wheel
 Choosing an edition
 -------------------
 
-Two capabilities live only in the Java edition, because they are separate executables rather than libraries:
+One capability lives only in the Java edition:
 
-- **CODEGEN**, which translates user-written model descriptions into Fortran 2003 and compiles them into a custom simulator. Writing your own exciter, governor or injector needs the Java edition or the `CODEGEN toolchain <https://stepss.sps-lab.org/developer/user-models/>`_ directly.
-- **DYNGRAPH**, the interactive trajectory viewer. This edition reads trajectories into NumPy instead, which is usually what you want from Python.
+- **CODEGEN**, which translates user-written model descriptions into Fortran 2003 and compiles them into a custom simulator. Writing your own exciter, governor or injector needs the Java edition, or the `CODEGEN toolchain <https://stepss.sps-lab.org/developer/user-models/>`_ directly.
+
+**Trajectory viewing exists in both editions**, by different means. The Java edition launches DYNGRAPH, a separate viewer executable. This edition carries its own equivalent, written in Python on top of Matplotlib: ``extractor`` reads a ``.trj`` file into NumPy arrays, and ``curplot`` or a curve's own ``.plot()`` draws them. The results stay in the process as ordinary arrays, so they can be sliced, compared across runs, or handed to any other Python library, and plotting is a method call rather than a separate program.
 
 Everything else, running dynamic simulations and power flows against the same engines and data files, is available here.
 
@@ -84,7 +85,7 @@ Key Features
 - **Runtime interaction** - query bus voltages, branch flows, and component observables while paused; inject disturbances on-the-fly
 - **Trajectory post-processing** - extract and plot time-series results from Fortran binary trajectory files
 - **Parameter sweeps** - script multiple simulations with varying parameters or disturbances
-- **Eigenanalysis support** - export system Jacobian matrices for small-signal stability analysis
+- **Small-signal stability analysis** - compute eigenvalues, damping ratios, participation factors and mode shapes in the engine, or export the system Jacobian and drive your own solver. See ``examples/eigenanalysis/`` for an annotated walkthrough
 - **AC power flow** - the ``stepss.helios`` module runs Helios power flows: solve, modify with redispatch, N-1 contingency screening, and file exports
 - **Shared data files** - the same ``.dat``, ``.dst`` and ``.obs`` files run in the Java edition, so a case can move between the two
 - **Scientific Python integration** - works natively with NumPy, SciPy, Matplotlib, and Jupyter
@@ -104,13 +105,6 @@ Minimal installation (no plotting or notebook support)::
 
 **Optional:** Install `Gnuplot <http://www.gnuplot.info/>`_ to enable real-time observable plots during simulation. stepss will still work without it, but runtime plots will be disabled.
 
-Renamed from PyRAMSES
-~~~~~~~~~~~~~~~~~~~~~
-
-This package was published as ``pyramses`` up to version 3.58. Existing code
-keeps working: ``pip install pyramses`` now installs a shim that forwards to
-this package. New code should use ``import stepss``.
-
 Linux System Prerequisites
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 

{stepss-3.59 → stepss-3.70}/stepss/__init__.py

@@ -19,13 +19,10 @@ Module-level flags set at import time:
 
 - ``__runTimeObs__`` - ``True`` when gnuplot is available on the system PATH and runtime
   observable plots are therefore enabled; ``False`` otherwise.
-
-This package was previously distributed as ``pyramses``. The ``pyramses``
-distribution on PyPI is now a forwarding shim onto this one.
 """
 
 __package_name__ = "stepss"
-__version__ = '3.59'
+__version__ = '3.70'
 __author__ = "Petros Aristidou"
 __copyright__ = "Petros Aristidou"
 __license__ = "Apache-2.0"

{stepss-3.59 → stepss-3.70}/stepss/_bundled.py

@@ -9,5 +9,5 @@ RAMSES_VERSION is also what the stepss version number is built from, so the
 leading components of __version__ always name the library bundled here.
 """
 
-RAMSES_VERSION = "v3.59"
+RAMSES_VERSION = "v3.70"
 HELIOS_VERSION = "v1.4.1"

{stepss-3.59 → stepss-3.70}/stepss/libs/ramses.h

@@ -39,3 +39,6 @@ int addObserv(char *string);
 int finalObserv(void);
 int get_last_err_log(char *msg);
 int get_Jac(void);
+int run_ssa(char *basename, double real_limit, double pf_threshold);
+int get_state_matrix_size(int *nx);
+int get_state_matrix(int nx, double *a_sys);

{stepss-3.59 → stepss-3.70/stepss.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stepss
-Version: 3.59
+Version: 3.70
 Summary: Python interface to the STEPSS power-system simulation platform.
 Home-page: https://stepss.sps-lab.org
 Author: Petros Aristidou
@@ -55,7 +55,7 @@ STEPSS is delivered in two editions, which drive the same simulation engines and
 - **STEPSS for Python**, this package. ``pip install stepss``, then script simulations from Python or a Jupyter notebook.
 - **STEPSS for Java**, a desktop application. A single ``stepss.jar`` with a graphical interface, published on the `releases page <https://github.com/SPS-L/stepss-java-ui/releases>`_.
 
-Neither is a wrapper around the other: they are two front ends onto the same Fortran engines, and a case built in one runs unchanged in the other. Pick this one to automate, sweep parameters, or work inside the scientific Python stack; pick the Java edition for interactive work, or for the model-building and curve-viewing tools it carries that this edition does not (see `Choosing an edition`_).
+Neither is a wrapper around the other: they are two front ends onto the same Fortran engines, and a case built in one runs unchanged in the other. Pick this one to automate, sweep parameters, or work inside the scientific Python stack; pick the Java edition for interactive point-and-click work, or to build your own models with CODEGEN (see `Choosing an edition`_).
 
 What this edition bundles
 -------------------------
@@ -70,10 +70,11 @@ Pre-compiled shared libraries for Linux, Windows and macOS ship inside the wheel
 Choosing an edition
 -------------------
 
-Two capabilities live only in the Java edition, because they are separate executables rather than libraries:
+One capability lives only in the Java edition:
 
-- **CODEGEN**, which translates user-written model descriptions into Fortran 2003 and compiles them into a custom simulator. Writing your own exciter, governor or injector needs the Java edition or the `CODEGEN toolchain <https://stepss.sps-lab.org/developer/user-models/>`_ directly.
-- **DYNGRAPH**, the interactive trajectory viewer. This edition reads trajectories into NumPy instead, which is usually what you want from Python.
+- **CODEGEN**, which translates user-written model descriptions into Fortran 2003 and compiles them into a custom simulator. Writing your own exciter, governor or injector needs the Java edition, or the `CODEGEN toolchain <https://stepss.sps-lab.org/developer/user-models/>`_ directly.
+
+**Trajectory viewing exists in both editions**, by different means. The Java edition launches DYNGRAPH, a separate viewer executable. This edition carries its own equivalent, written in Python on top of Matplotlib: ``extractor`` reads a ``.trj`` file into NumPy arrays, and ``curplot`` or a curve's own ``.plot()`` draws them. The results stay in the process as ordinary arrays, so they can be sliced, compared across runs, or handed to any other Python library, and plotting is a method call rather than a separate program.
 
 Everything else, running dynamic simulations and power flows against the same engines and data files, is available here.
 
@@ -84,7 +85,7 @@ Key Features
 - **Runtime interaction** - query bus voltages, branch flows, and component observables while paused; inject disturbances on-the-fly
 - **Trajectory post-processing** - extract and plot time-series results from Fortran binary trajectory files
 - **Parameter sweeps** - script multiple simulations with varying parameters or disturbances
-- **Eigenanalysis support** - export system Jacobian matrices for small-signal stability analysis
+- **Small-signal stability analysis** - compute eigenvalues, damping ratios, participation factors and mode shapes in the engine, or export the system Jacobian and drive your own solver. See ``examples/eigenanalysis/`` for an annotated walkthrough
 - **AC power flow** - the ``stepss.helios`` module runs Helios power flows: solve, modify with redispatch, N-1 contingency screening, and file exports
 - **Shared data files** - the same ``.dat``, ``.dst`` and ``.obs`` files run in the Java edition, so a case can move between the two
 - **Scientific Python integration** - works natively with NumPy, SciPy, Matplotlib, and Jupyter
@@ -104,13 +105,6 @@ Minimal installation (no plotting or notebook support)::
 
 **Optional:** Install `Gnuplot <http://www.gnuplot.info/>`_ to enable real-time observable plots during simulation. stepss will still work without it, but runtime plots will be disabled.
 
-Renamed from PyRAMSES
-~~~~~~~~~~~~~~~~~~~~~
-
-This package was published as ``pyramses`` up to version 3.58. Existing code
-keeps working: ``pip install pyramses`` now installs a shim that forwards to
-this package. New code should use ``import stepss``.
-
 Linux System Prerequisites
 ~~~~~~~~~~~~~~~~~~~~~~~~~~