search

ModellingWebLab / project_issues

An issues-only repository for issues that cut across multiple repositories
1 stars 0 forks source link

Split project into multiple repositories #1

Closed jonc125 closed 5 years ago

jonc125 commented 7 years ago

In due course we will need separate repositories for:

Others may be added in the future.

MichaelClerx commented 7 years ago

How are we naming the individual python modules? weblab.x, weblab.y, etc.? Or standalone names like web_lab_related_x, web_lab_related_y ?

jonc125 commented 7 years ago

Standalone names, so each can be pip-installable separately. They may or may not have web_lab in the name; the task queue & Django site probably should, the backend experiment running & fitting code probably not, since they could be used independently.

jonc125 commented 7 years ago

Trac ticket on comparing the C++ & Python backends: https://chaste.cs.ox.ac.uk/trac/ticket/2643

jonc125 commented 7 years ago

What should we call the new pycml? (Which will be used for the repo & Python package name.) Stick with pycml? Or come up with something new?

MichaelClerx commented 7 years ago

No idea!

On the one hand, we want our new modules (functional-curation-with-solver, cellml-reader-with-exports, generic-web-lab-front-end and cardiac-web-lab-front-end*) to be independent, so you can download, use and develop them separately.

But on the other hand, we want short names with some kind of common theme so that it's obvious the projects are linked...

(*We also don't want them to be this awful)

MichaelClerx commented 7 years ago

...but maybe if the libCellML wrappers were really good, the amount of CellML code for the Web Lab would be minimal (call libCellML to parse the file, work with libCellML to get annotated equations).

Then Chaste code could be a separate (Python?) program that uses libCellML to read CellML, maybe do some manipulations of the equation objects for rush-larsen etc., and then write Chaste-specific C++ ?

jonc125 commented 7 years ago

Yes, I think the WebLab-specific CellML handling would be quite different from the Chaste CellML handling if the basic CellML library is actually useful. So hopefully generic stuff would go into a community-wide Python wrapper for libcellml, or into libcellml itself, rather than just being in our code.

jonc125 commented 6 years ago

For the experiment runner task-queue, we need a name :) I'm hoping to a large degree it can be flexible as to what it runs; for the main Web Lab it's the glue between the Django and weblab-fc components, but there could be electrochemistry & neuroscience backends, ideally without having to change more than config settings.

Ideas...

MichaelClerx commented 6 years ago

I like weblab-runner, as it will probably be weblab-specific!

MichaelClerx commented 5 years ago

How's this going?

MichaelClerx commented 5 years ago

@jonc125 is the missing checkbox https://github.com/ModellingWebLab/fc-runner ? Cause if so we can close this :-)