Add GUI

[MaCuinea]

• Create two tabs: planning and executing.
• Ensure the GUI remains open during operation.

Planning:

• Add more branching - The current GUI allows for branching: a few fields will be adapted based on chosen equipment such as power input (power input: amplitude for IGT and global power for SC).
• Add a "Generate" button to create Python code based on the provided US protocol, which can be embedded into the experimental script.
• Add a ‘Save Protocol’ button to save a protocol in, for example, an ini file.
• Add a ‘Load Protocol’ button to load a protocol from, for example, an ini file. If the protocol is created based on equipment from another manufacturer, it must be automatically converted and fields that cannot be converted like power has to be flagged and left empty.
• Implement additional value checks for both GUI and code structure. Example: pulse duration <= pulse repetition interval.
• Change ‘Focal depth [mm]’ to ‘Focal depth at FWHM [mm]’. Check if the focal depth is defined as focal depth at FWHM for each manufacturer.
• Disable pulse ramp duration and pulse ramp step duration when pulse ramp shape is rectangular.
• Add the possibility to define a pulse train repetition using SC. Discuss with Ben how he is doing it right now.
• GUI should be empty by default to prevent forgetting to fill in one of the values.
• Explore for SC the possibility of setting the transducer via code. Talk to Ben about the advanced mode. SC phase tables are already known to the US driving system software for IGT purposes, but it can also be used for SC.

Executing:

• Provide a summary of the planned protocol.
• Introduce buttons for connecting, disconnecting, sending, executing, and aborting.
• Include a timer during execution and display equipment status.

Add value checks