Skip to content

Read pulserver's [Protocol] listing, so its sequences show their parameters and FOV - #13

Merged
mcencini merged 2 commits into
masterfrom
claude/vscanner-params-fov-5v9gdo
Oct 6, 2026
Merged

mcencini merged 2 commits into
masterfrom
claude/vscanner-params-fov-5v9gdo

Conversation

@mcencini

@mcencini mcencini commented Oct 6, 2026

Copy link
Copy Markdown

Requested by Matteo · project thread

Before: selecting a pulserver sequence in the virtual scanner showed no parameters in the Sequence tab, and resizing the FOV box changed nothing in the scan: the field of view was never sent.

After: each sequence's protocol entries appear in the Sequence tab, and the FOV planned on the localizer travels to pulserver as fov, phase_fov and slice_thickness.

pulserver delimits its protocol blocks with [Protocol], while the console read only [NimPulseqGUI Protocol], so every listing parsed to nothing. Both delimiters are now read and [Protocol] is written (pulserver reads both). A boolean edited in a parameter tab comes back as text ("False"), which was sent as true; it now travels as its value.

How: parse_listing accepts either delimiter; format_values reads a textual boolean. Tests cover both delimiters and the boolean. Checked against pulserver main's real list reply for gre2d: nine entries shown, fov and phase_fov among them.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Afq4fxyjbebF7KbvaNC1uh


Generated by Claude Code

…meters and FOV

pulserver delimits its protocol blocks with [Protocol]; the console read only
[NimPulseqGUI Protocol], so every plugin listed no parameters and a scan sent
no field of view. Both delimiters are read and [Protocol] is written. A
boolean edited in a parameter tab travels as its value, not its text's truth.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Afq4fxyjbebF7KbvaNC1uh
@mcencini mcencini self-assigned this Oct 6, 2026
@mcencini
mcencini merged commit 6f6711b into master Oct 6, 2026
3 checks passed
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.

2 participants