ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗Open, calibrated predictions of neutron reaction cross sections across the chart of nuclides, with a public blind benchmark and a registry of predictions made before the data.
docs/walkthrough/data/board/ holds the per-nucleus rows behind
every scoreboard cell, and recompute.py recomputes the verdicts from them.predictions/2026-10-23/ holds predictions registered on
2026-10-23 for measurements not yet published, with a fixed scoring rule; 16 of the targets are blind and decide the
headline verdict.engine-2026-10-22.library/v0.2/ is the latest version, built with the scored engine (what changed:
CHANGELOG.md); library/v0.1/ stays available unchanged.CITATION.cff (see Citing).Most nuclei have never had a neutron cross section measured, yet reactors, nucleosynthesis networks, fusion shielding and isotope production all need values for them. Incognita gives each nuclide a value, an uncertainty interval whose coverage has been tested on nuclei held out of the fit, and a regime label (measured, anchored, interpolated or extrapolated). The code, the predictions, the exam they were graded on and timestamped predictions for nuclei not yet measured are all public, so every claim can be checked.
| Coverage | 6,168 nuclides (Z = 8–110), 1 keV – 20 MeV: capture, MACS, stellar rates, (n,p), (n,2n), (n,α) |
| Held-out capture | with measured D0, beats the default TALYS recipe on the sealed vault: 0.1519 vs 0.1712 dex |
| Tested intervals | 95 % interval covers 95.3 % of 674 sealed capture bins published after 2012 |
| Engine | a Python/C port of TALYS-2 physics; matches stock TALYS to four decimals on total, elastic, (n,p), (n,α) scores; 11.7x faster per target (no cache) |
Ties and losses are reported too: see the full benchmark.
Needs Linux or macOS, Python 3.12 and uv.
git clone https://github.com/seth-michael-weaver/incognita.git incognita && cd incognita
uv sync --extra dev
uv run python -m incognita.library show Au-197 # capture curve with 68 / 95 % bands, MACS at 30 keV
bash scripts/reproduce.sh # regenerate the benchmark tables and compare with the shipped ones
Running the engine itself needs the TALYS structure database: see Running the engine.
| path | content |
|---|---|
library/v0.2/, library/v0.1/ | the predictions (CC-BY-4.0): v0.2 latest, v0.1 kept unchanged |
incognita/ | library reader, benchmark scorer and tracks, calibration and curation tools |
physics/ | the Hauser–Feshbach engine |
scripts/ | reproduce.sh, scorers, engine driver, native-kernel builds |
docs/release/, docs/registry/ | frozen exam inputs and expected tables; pre-registered predictions |
predictions/ | dated prediction registries (blind targets, fixed scoring rule) |
emu/ | fast emulators of the engine |
docs/walkthrough/ | the explainer website |
The full layout is in the guide.
This is a v0.1 preview: research output, not an evaluation. Held-out tests are retrospective; the pre-registered predictions have not yet been scored against new measurements. There is no claim of better accuracy than evaluated libraries for measured nuclei; where good data exist, use the data or an evaluation. The library and its benchmark numbers come from the v0.1 engine; the scoreboard uses the current engine (22 October 2026). Details: Status and limitations.
Millisecond emulators of the engine, with Jacobians and sampling: emu/README.md.
Use CITATION.cff, and also cite EXFOR (N. Otuka et al., Nucl. Data Sheets 120 (2014) 272) and
TALYS (A. Koning, S. Hilaire, S. Goriely, Eur. Phys. J. A 59 (2023) 131) when you use the engine or the EXFOR-derived
tables.
Code: Apache-2.0 (LICENSE, NOTICE); predictions and data: CC-BY-4.0
(LICENSE-DATA, including third-party terms); ported TALYS routines keep their MIT notice
(physics/hf/NOTICE-TALYS.md).
See CONTRIBUTING.md and the Code of Conduct. If a number here is wrong,
please open an issue with the measurement.