Skip to content

Changelog entries for abTEM#563 (PRISM exit planes, ensembles, single positions) - #40

Open
pzeiger wants to merge 1 commit into
mainfrom
changelog/prism-exit-planes
Open

pzeiger wants to merge 1 commit into
mainfrom
changelog/prism-exit-planes

Conversation

@pzeiger

@pzeiger pzeiger commented Oct 9, 2026

Copy link
Copy Markdown
Member

Changelog entries for abTEM#563, which is still open and stacked on abTEM#556. The changelog lists only changes that are merged into dev, so this should merge after abTEM#563 does.

Entries

  • Performance: one bullet, at the end of the section. The automatic PRISM batch sizes now count the exit planes, and the bullet gives the peak-memory figure from the PR (9 exit planes, 128 x 128 grid). The PR description reports 9249 MB before and 1284 MB after, rounded here to 9.2 GB and 1.3 GB.
  • Bugfixes: one bullet with a sub-bullet per fix, as in Changelog entries for abTEM#556 (seven fixes, two changes in results, CPU–GPU arithmetic) #38, at the end of the section. The behaviour change comes first and starts with Behaviour change:. It covers PRISM reduce without a scan, and a single (x, y) position, which return no position axis; this answers point 4 of the abTEM#563 review. The other sub-bullets cover the exit-plane axis, eager WavesDetector over FrozenPhonons(ensemble_mean=True), and transition_potential_scan with upsample=True.

The Bugfixes section ends at the same place in #35, #36, #38 and #39, so whichever merges later needs a trivial rebase of the insertion point.

🤖 Written and posted by Claude Code on Paul's behalf

… positions)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant