Skip to content

amp2response: Fix non-standard directions access - #3425

Open
Lestropie wants to merge 1 commit into
masterfrom
amp2response_directions
Open

amp2response: Fix non-standard directions access#3425
Lestropie wants to merge 1 commit into
masterfrom
amp2response_directions

Conversation

@Lestropie

Copy link
Copy Markdown
Member

Bug not previously caught due to absent test coverage.

Probably when I first started implementing amp2response, I commenced with a single-shell implementation, then when I expanded it to handle multi-shell in a single run I failed to update the non-standard code paths accordingly.

Current code erroneously initialises the set of volumes to use during response function estimation to be "all volumes up to index 0", as it erroneously selects the number of unique shells as the number of volumes. There is one direction matrix per shell, so where one of these code paths applies, there is both definitionally and obviously from the preceding code only one shell, and so what is actually required is the number of rows (= # volumes) in the direction matrix of the solitary shell.

@Lestropie
Lestropie requested a review from a team August 3, 2026 10:34
@Lestropie Lestropie self-assigned this Aug 3, 2026
@Lestropie Lestropie added the bug label Aug 3, 2026
@Lestropie Lestropie mentioned this pull request Aug 3, 2026
27 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant