Gary Mirams

See also https://github.com/Chaste/trac_archive/wiki/Chaste-Guides-_-Running-Acceptance-Tests I had a quick look, 'almost' managed to get it working again, but I think some of my paths need tidying up ``` python -m pip install...

I got a new mac desktop and am experimenting with it...

I would think `GetM()` etc. methods should be replaced by ones that follow the OdeSystemInformation form, e.g. `GetVariable("M")` or `GetParameter("M")` etc. (automatically available when OdeSystemInformation in the hpp is complete.)

Work is in a separate [chaste_codegen_sbml](https://github.com/Chaste/chaste-codegen-sbml) project.

OK, good, in that case it might be good enough to make the tutorials refer to `CHASTE_TEST_OUTPUT` and not need any docker specialisation.

Hmm, if it is after Cardiac Simulation it probably is unrelated, can you run with just one core so you see which one has launched and got stuck?

cough @fcooper8472 !

Should be OK I guess. But it does mean that it becomes impossible to distribute an executable that writes to a settable `CHASTE_TEST_OUTPUT` (e.g. my main use-case worry would be...

closing as no further info provided

I'm happy with those proposals, doing absolute ones makes more sense as relative would presumably be with respect to initial guess or something which would be a bit strange to...