MichaelClerx
commented
5 years ago I've been thinking about the Myokit version a bit more. It would be quite easy to add an fc option to setup.py, which then requires fc and codegen and cellmlmanip by extension. I want to add support for CellML editing anyway, so there could be several ways forward, e.g. adding fc-model generation to Myokit and using fc directly (without cellml in between), or by only using the IDE in some CellML mode, that then uses cellmlmanip etc.
It'd be really cool if users could work out their protocols etc. offline, then just upload them!
Future stuff, but does require that we start thinking of our modules as user libraries a bit more, implying e.g. some support for multiple versions of the dependencies
Because fitting is hard, and setting up fitting means lots of experimentation, users needs to be able to set up their fitting experiments offline. This means they need to be able to have at least partial WL functionality on their systems, without the Web stuff (front-end, task runners etc.)
One option is to somehow adapt Myokit: It can do CellML, we can improve/add bits where needed. It already has multiple simulation classes so we could add one that uses the web lab solver (provided this is packaged appropriately that should be relatively easy).
Another option is to have some sort of "superpackage": A pypi package that doesn't do much but has dependencies on all the required web lab packages (all nicely in pypi too), so that users can install it and get going. The main content of this package could then be a bunch of examples showing how to use the other packages.