Motivation: Tools for cross-platform open-source pulse sequence development have recently gained substantial traction within the MRI community. An important ingredient thereof is the set of scanner-specific "driver" or "interpreter" software modules, which currently have to be compiled and tested for every scanner model and software version. Goal(s): Develop an easy to maintain flexible Pulseq interpreter, with a minimal dependency on the scanner software. Approach: A Pulseq interpreter that relies on the prototype Siemens "Remote Sequence Streaming Interface" was implemented in Python. Results: Our proof-of-concept implementation shows identical simulated sequence diagrams compared to the previous Pulseq interpreter and is producing similar images on the scanner. Impact: Interpreter modules are instrumental for executing open pulse sequences on a particular scanner. The presented work paves a way towards reducing the effort associated with their development and maintenance by potentially reducing adaptations and tests for every scanner software version.
Shafiekhani et al. (Tue,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: