Attpc-spyral

Latest version: v0.18.0

Safety actively analyzes 723400 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 9

0.10.0rc4

Another release candidate attempting to fix our clustering

0.10.0rc3

0.10.0rc2

Improve noise removal in clustering phase

0.10.0rc1

0.10.0rc0

Release candidate for better errors and some small bugfixes

0.9.0

Hi everyone, this release contains a major feature: shared memory! This allows Spyral processes to share resources, and will greatly reduce the memory load when using things like the interpolation mesh. Any phase is allowed to implement shared memory (including user defined phases), but there are some caveats to how it should be used. First is that any shared memory should be treated as read-only. It should not be written to or modified during the main runtime of Spyral. Spyral does not implement any locks for shared memory, and so any modification of the shared memory would result in a race condition. The other is that shared memory is always allocated if the associated phase is to be run, resulting in a constant memory pressure during Spyral's runtime.

The documentation has been updated accordingly. Please let us know what your experience is with this update, and please make a GitHub Issue if you run into any problems!

What's Changed
* Update gwm17_dev by gwm17 in https://github.com/ATTPC/Spyral/pull/142
* Shared Memory for Phases by gwm17 in https://github.com/ATTPC/Spyral/pull/145
* Doc updates, print reduction, better exceptions by gwm17 in https://github.com/ATTPC/Spyral/pull/146
* Finalize Shared Mem, Update docs and README by gwm17 in https://github.com/ATTPC/Spyral/pull/147
* Update to v0.9.0 by gwm17 in https://github.com/ATTPC/Spyral/pull/148


**Full Changelog**: https://github.com/ATTPC/Spyral/compare/v0.8.0...v0.9.0

Page 6 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.