Skip to content

Conversation

@emitra17
Copy link
Collaborator

@ionif made a lot of progress on developing this GUI for PyBNF.

In its current form, the GUI is launched by running python main.py from the root directory of the repository. The main purpose of the GUI is to load, modify, and save CONF files, where the graphical interface provides text boxes for each available configuration key. The GUI also supports exporting all files for a fitting job into a new folder, and launching a local PyBNF run using the loaded CONF file.

If someone wants to pick this project back up, here are the steps I see as necessary before this is ready to go:

  • Lots of testing - need to create a lot of test cases (at the least, test compatibility with every PyBNF config key) and confirm that this code is bug free. Unfortunately, the previous GitHub branch listing the current known bugs got deleted by overzealous GitHub features.
  • Beta test on other users. Does the current save/load/run functionality have behavior that is expected and useful? I am especially curious about the "Export Project" and "Save and Run" features.
  • Add documentation of the GUI to the PyBNF documentation.
  • Clean up the documentation within the GUI itself. Currently the GUI has text boxes describing each configuration key, but this text could be updated and made more readable (see, for example, the documentation of config keys within the PyBNF documentation).
  • Streamline launching of the GUI. Ideally, it should be launched by something like pybnfgui or pybnf -g filename.conf from the command line rather than calling python from the source folder.
  • Streamline installation. One should figure out the cleanest way to do this; bundling it with the pybnf package may not be ideal because there are additional dependencies that a command-line pybnf user may not want to bother with. Perhaps a new package that has PyBNF as a dependency?
  • Add support for new configuration keys added to PyBNF after August 2018

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.

3 participants