Graphical User Interface

[BenWinchester]

Issue

Users who come to CLOVER, in general, do not have an extensive coding background: they are either academics, or field practitioners, for whom using a command-line interface (CLI) can be off-putting.

Proposal

Develop a new graphical user interface (GUI) within CLOVER.

Discussed in #200

^{Originally posted by hamishbeath June 6, 2023}
This would be part of the 'expanding user base' section of the IAA grant and would allow wider use from a non-technical background. The aim would be to implement a very simple GUI that wraps around existing code and facilitates easier input/output management.

[BenWinchester]

🐛 Erorr handling

The errors which CLOVER raises will all need to be caught and displayed nicely with pop-up windows or something similar in the GUI. Errors which are currently not handled correctly by CLOVER in its current form, i.e., which exist as bugs within the code, will need to be fixed before implementing the GUI as well. These include:

• Zero storage scenario #70 and Zero storage scenario #183 - the zero-storage scenario bug, which is currently raised as an error when the user would not expect it,
• Duplicate inverter information #126 and Duplicate inverter information #191 - the duplicate-inverter information bug, which currently would result in the GUI needing to edit multiple files to update the same information.