You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,8 @@ Sympy or any other python package may need to be updated, especially as python v
18
18
- ``git add``, ``git commit`` and ``git push`` the changes
19
19
- Make a pull request. The tests may throw up some errors that may need fixing. The tests are in the tests folder and the reference data in data/tests.
20
20
- Sympy occasionally changes the exact (but mathematically equivalent) form of the generated code between versions.
21
-
To cope with this, a reference file may have per-sympy-version variants named ``<name>--sympy_X_Y.<ext>`` (e.g. ``<model>--sympy_1_13.cpp``) alongside the base file.
22
-
To regenerate the reference data for a new sympy version, run the tests with the ``CHASTE_CODEGEN_REGENERATE_REFERENCES`` environment variable set (this writes the generated output to ``<reference>.regen.<X>.<Y>`` files).
21
+
To cope with this, a reference file may have per-sympy-version variants named ``<name>--sympy_X_Y.<ext>`` (e.g. ``<model>--sympy_1_13.cpp``) alongside the base file.
22
+
To regenerate the reference data for a new sympy version, run the tests with the ``CHASTE_CODEGEN_REGENERATE_REFERENCES`` environment variable set (this writes the generated output to ``<reference>.regen.<X>.<Y>`` files).
23
23
- Mention the changes made in the release notes ``release.txt``
24
24
- To use the changes with chaste, do a new release of chaste_codegen.
25
25
@@ -31,7 +31,7 @@ Updating the ontology and including it in chaste_codegen
31
31
- *Please note* this same way can be used to update the ``cellml`` in ``chaste_codegen/data/tests/cellml`` submodule if required.
32
32
- Create a new branch ``git checkout -b <name_of_new_branch>``
33
33
- ``git add``, ``git commit`` and ``git push`` the changes
34
-
- Make a pull run the tests and fix any issues that arise
34
+
- Make a pull request, run the tests and fix any issues that arise
35
35
- Update the release notes ``release.txt`` with information about the updated ontology.
36
36
- To use the changes with chaste, do a new release of chaste_codegen.
0 commit comments