Rémi Delaporte-Mathurin

Perhaps instead of k_r and k_d we can use k_forward and k_backward (since we impose a "direction" with reactants and products).

Hi @humitos I recently bumped into this issue, ideally I'd like to configure everything from the config file and not have to fiddle with the UI, for reproducibility purposes. Has...

Adding the fenicsx flag to this since it's relevant for FESTIM2

Closing as replaced by #939

A workaround for now is to do: ```python import festim as F import sympy as sp import numpy as np my_model = F.Simulation() my_model.mesh = F.MeshFromVertices(np.linspace(0, 1)) my_model.materials = F.Material(1,...

Actually the code does not work: ```python import festim as F import sympy as sp import numpy as np my_model = F.Simulation() my_model.mesh = F.MeshFromVertices(np.linspace(0, 1)) my_model.materials = F.Material(1, 1,...

The only way I found to circumvent this issue is by monkey patching the sympy C printer: ```python import festim as F import sympy as sp import numpy as np...

A fix would be to replace this line: https://github.com/festim-dev/FESTIM/blob/47d7dc4831fe51b7bf2fe197e973d6ba5d4f6987/festim/temperature/temperature.py#L41 by ```python ccode = sp.printing.ccode(self.value).replace("log", "std::log") self.expression = f.Expression(ccode , t=0, degree=2) ``` we'd have to propagate this fix in all...

@KulaginVladimir what do you think about this one? Should we fix it, or just leave it since there is [a workaround](https://github.com/festim-dev/FESTIM/issues/813#issuecomment-2245575103)?

No it's a legacy-fenics issue. I'll close this! 🚀