Releases: adjtomo/seisflows
SeisFlows Version v2.3.1
What's Changed
Full Changelog: v2.3.0...v2.3.1
Contributors
Assets 2
SeisFlows Devel v3.0.0
This is a pre-release development candidate to keep track of dev updates prior to main branch release
What's Changed
- MAJOR code overhaul: ambient noise adjoint tomography and code improvements by @bch0w in #181
- Adds feature SPECFEM3D_GLOBE mask source in kernels by @bch0w in #186
Full Changelog: v2.3.0...dev3.0.0
Contributors
Assets 2
SeisFlows Version 2.3.0
SeisFlows Version 2.3.0 release, see #180 for release notes and detailed changelog
Key Changes:
- Major bug fixes regarding line search and residuals files #168
- New system module for HPC Wisteria (U. Tokyo) #176
- Allow acoustic domain and pressure seismograms from SPECFEM2D #164
- Various bugfixes and code improvements
Major thanks to @evcano for identifying and fixing bugs in #168!
Contributors
Assets 2
SeisFlows Version 2.2.0
SeisFlows Version 2.1.0
This is an official release for SeisFlows version 2.1.0 which constitutes a major package overhaul and code refactor. See PR #139 for more information and links to relevant PRs and issues that make up this version release.
Backwards incompatible changes have been introduced from versions 2.0.0 -> 2.1.0 through the major source code overhaul, but since we are still in a pre-release phase, I am incrementing the minor version instead of the major version (I know this goes against semantic versioning).
This version of SeisFlows is better suited for rapid development and user uptake. It was also used during the SPECFEM Users Workshop (See #136) and containerized with Docker through the SCOPED project (https://github.com/SeisSCOPED/adjtomo).
Although it's hard to predict the future, I see only minor version increments for the near future as we build out features and capabilities for this major release version, including additional workflows, system support, and features. My goal is that once we get new users running full-scale problems on a variety of HPC systems, I will consider this version "stable" and remove it from pre-release.
SeisFlows version 2.0.0
SeisFlows Version 2.0.0
This is an official release documenting the merger of a previous hard fork of SeisFlows (known as SeisFlows3) back into the main repository (#115). Backwards incompatible changes have been introduced to the package (https://seisflows3.readthedocs.io/en/latest/changelog.html) meaning the previous stable version of SeisFlows will not work with the current API.
If you are looking for the previous version, see the SeisFlows Legacy release (v1.1.0; https://github.com/adjtomo/seisflows/releases/tag/v1.1.0)
This is marked as a pre-release as changes made during the merger may have unexpectedly disrupted some of the functionality within the package (e.g., documentation needs to be rebuilt), however ,ain development will be taking place following this version.
SeisFlows Legacy
SeisFlows Legacy (v1.1.0)
This stable version of SeisFlows is written in Python2 and provides an inversion/migration workflow tool that can be deployed on workstation and HPC systems.
In 2020, main development of the SeisFlows package was forked as SeisFlows3 (#111), resulting in backwards-incompatible changes which included: a move to Python3 syntax, a new parameter file format, and general source code overhaul. SeisFlows3 was maintained as a separate repository until 2022, when it was merged back into this main repository (#115). Main development of the SeisFlows package now occurs here (https://github.com/adjtomo/seisflow), and SeisFlows3 was deleted as a separate fork/repository (bch0w#2) to avoid potential confusion over multiple co-existing development forks.
Due to the introduction of backwards-incompatible changes following the merger of SeisFlows3, the original SeisFlows code has now been named SeisFlows Legacy, versioned as v1.1.0. This version of the code will not be updated or maintained but is retained for provenance. All future development of the SeisFlows package will take place starting at v2.0.0.
Stable-2020
Looks like 2019 changes may have broken some aspects?
"Princeton"
With several members moving on from Jeroen's group, now seems like a good time to mark a v1.0 "Princeton" tag. Future development will shift partly to the University of Alaska Fairbanks, but making sure the codes run well on Princeton clusters remains a top priority.