New package: BasisSimulator v0.1.0#155306
Conversation
JuliaRegistrator
commented
May 12, 2026
- Registering package: BasisSimulator
- Repository: https://github.com/MolloiLab/BasisSimulator.jl
- Created by: @Dale-Black
- Version: v0.1.0
- Commit: 9d1cf28818a34208b1088321ee3f2fba6b8c0935
- Reviewed by: @Dale-Black
- Reference: MolloiLab/BasisSimulator.jl@9d1cf28#commitcomment-185104846
- Description: Polychromatic CT simulation and reconstruction in Julia. Runs on Metal, CUDA, ROCm, CPU.
UUID: 8f904df-b85e-4ff6-b463-dae2292396b9 Repo: https://github.com/MolloiLab/BasisSimulator.jl.git Tree: b623a11a2ebe20ea38e6ce844655e1b6884fd4bb Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
Version: 0.3.0 → 0.1.0 — AutoMerge accepts 0.0.1 / 0.1.0 / 1.0.0
for first registration; anything else requires manual review.
Author email: daleblack@molloi.lab → djblack@uci.edu
[deps]: unchanged (9 deps, all reachable from src/).
[weakdeps]: CUDA, Metal unchanged (Julia 1.11+ extension targets).
[compat] (alphabetized, full coverage):
* Added stdlib compat entries (required for AutoMerge):
DelimitedFiles = "1", LinearAlgebra = "1", Random = "1",
Statistics = "1".
* Loosened Serialization = "1.11.0" → "1".
* XrayAttenuation: switched from git-tracked main branch to
registered v0.3.0 (now available in General registry).
Compat pinned to "0.3".
* julia: "1.11, 1.12" → "1.11" (idiomatic; covers 1.11+ within 1.x).
[extras] / [targets]: dropped Roots (only used by the archived
test/archived/vmi_brent_parity.jl, not in the live test suite).
Test target stays.
Manifest.toml now resolves cleanly with no git-tracked deps — all
2590 tests still green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human. 1. New package registrationPlease make sure that you have read the package naming guidelines. 2. AutoMerge Guidelines are all met! ✅Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. 3. To pause or stop registrationIf you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text Tip: You can edit blocking comments to add |