Add TENDL-2023 and TENDL-2025 releases to chain generation URL registry#31
Merged
Conversation
Adds release entries for TENDL-2023 and TENDL-2025 to urls_chain.py and the corresponding release choices to generate_tendl_chain, bringing the chain registry to parity with urls.py. The 2023 tarball is named TENDL-n.2024new.tgz; the 2025 tarball is TENDL-n.tgz. Both URLs were verified live on the Imperial mirror.
The install steps called 'apt-get install libhdf5-serial-dev' against a stale package index, causing intermittent 404s when a cached dependency version (e.g. libcurl4-openssl-dev) was superseded and removed from the mirror pool. Running 'apt-get update' first refreshes the index.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #30.
TENDL-2023 and TENDL-2025 are available on the Imperial mirror already used for earlier releases. This adds their release entries to
urls_chain.pyand the corresponding release choices togenerate_tendl_chain.Issue #30 was scoped to 2025 only, but
urls.py(used by the cross section conversion scripts) already carried bothtendl 2023andtendl 2025entries whileurls_chain.py(chain scripts) had neither. This PR adds both so the chain registry reaches parity withurls.py.Details
https://tendl.imperial.ac.uk/tendl_2025/tar_files/TENDL-n.tgz(verified live, Last-Modified July 2025, ~3.5 GB)https://tendl.imperial.ac.uk/tendl_2023/tar_files/TENDL-n.2024new.tgz(verified live, Last-Modified Aug 2024, ~3.1 GB) — note the different filename vs the other releases, matching the entry inurls.pyOne quirk worth knowing: the TENDL-2025 evaluation headers self-identify as TENDL-2023.1 (NVER=2023, LREL=1), so header-derived library labels will say 2023.1 even for files from the 2025 release.
Changes
src/openmc_data/urls_chain.py: add2023and2025entries undertendlsrc/openmc_data/depletion/generate_tendl_chain.py: add2023and2025to--releasechoices and update help textREADME.md: update thegenerate_tendl_chainrelease column