4.12.0 Released

[markcmiller86]

Key changes

• CMake/CTest is fully functional now. It is the supported way of configuring Silo going forward. See documentation for CMake instructions. Autotools still works but is deprecated and will be wholly removed after 4.12.0 release.
• Both LLNL legacy licensed and BSD licensed code are released in a single artifact now. In previous releases, LLNL legacy and BSD licensed artifacts were separated. Now, this is handled during CMake configuration time with the -DSILO_BUILD_FOR_BSD_LICENSE:BOOL option.
• HDF5-2.0 is fully tested and recommended but any version of HDF5 after 1.8.4 should still work. Avoid HDF5 version 1.10.
• All Silo tests now pass with GNU Address Sanitizer enabled.
• All Silo tests are now part of GitHub CI.
• Qt6 is now required for silex tool.
• Usage of master/slave terminology has been removed.
• Quadratic elements are now supported.
• Most differences in the same python object read from PDB and HDF5 drivers have been resolved.
• A new property, DBSetEvalNameschemes() was added to support consumers who don't want to explicitly manage nameschemes.
• Constant nameschemes work with or without delimiter characters.
• Python now correctly closes files when the associated python object is de-allocated.
• An update for Spack is ready and will be finalized shortly after this release
• A number of memory errors, leaks and other bugs found with GNU Address Sanitizer, valgrind and fuzz testing were fixed.
• Documentation was improved
• A missing matname member for DBmultimatspec was added.
• Fixes for compiling with OMP-enabled compiler were added.

Thank you to @biagas, @junghans and @cessenat as well as all our new contributors, below 💪

• @andrewcorrigan made their first contribution in defines SIZEOF_OFF64_T as CMAKE_SIZEOF_VOID_P when off64_t is not defined to fix Mac/AppleClang compilation #239
• @cessenat made their first contribution in silo_f.c: add an interface to free an option set with dbaddcaopt #244
• @chuckatkins made their first contribution in hdf5: Support the API changes in 1.13 #260
• @henryleberre made their first contribution in Miscellaneous CMake improvements #262
• @markstock made their first contribution in Added parens to isnan conditional to satisfy standard #277
• @brtnfld made their first contribution in Include only zfp files when needed, re-ran automake #263
• @kwryankrattiger made their first contribution in HDF5 add new fields for H5FD_class_t #307
• @pkestene made their first contribution in Fix building tests with cmake. #323
• @mathstuf made their first contribution in cmake: fix the name of the version file #357
• @dependabot[bot] made their first contribution in Bump certifi from 2023.7.22 to 2024.7.4 in /docs #381
• @thesamesam made their first contribution in tests: add missing header for difftime #371
• @willzywiec made their first contribution in Update README.md #423
• @junghans made their first contribution in cmake: make install locations configurable #424
• @Malmahrouqi3 made their first contribution in Improved SiloFindHDF5.cmake Search #489

Full Changelog: 4.11.1...4.12.0

---

This discussion was created from the release 4.12.0.

[markcmiller86]

Thanks to @eschnett,, it has been brought to our attention that when the ghpages branch was merged to main in prep for 4.12.0 release, that included all the previous release tarballs which GitHub's git archive command then folded into the auto-generated release assets...making for very large release assets! 😨.

Clearly, we need to adjust some .gitattributes somewhere and re-generate the tarballs. We are working up a fix but it may not be available until next week.

[markcmiller86]

New release assets have been manually created and uploaded. Use those instead of the GitHub autogenerated ones...which we have yet to figure out how to remove.

[mathstuf]

Sorry, I should have been clearer; I was suggesting solutions, not requesting anything specific be done.

[markcmiller86]

Okay well I think the problem is "solved" at this point as long as people download the manually generated release assets instead of the GitHub auto generated ones. In addition I've added a .gitattributes file that will ensure the GitHub auto generated ones in the future will not have all of the unnecessary junk in them.

[markcmiller86]

And it turns out there is no way to actually remove the assets that GitHub auto generates.

[Friedrih]

Will there be a version 4.12 for pypion? Since the link so far gives 4.11
https://git.dias.ie/massive-stars-software/pypion/

[markcmiller86]

@Friedrih we were not aware of Silo's use in the project you mention. That said, we are fairly certain 4.12 will work with pypion if pypion developer's decide to move to it. But, that is a choice up to the pypion development team. There is not really any influence we can have their other to offer rationale(s) for why moving to 4.12.0 might provide some benefits.