From a8eba9b86ea5eda217f7542cefe70ce938224dac Mon Sep 17 00:00:00 2001 From: Xavier Raynaud Date: Tue, 17 Dec 2024 17:50:53 +0100 Subject: [PATCH] minor update --- Documentation/publishedExamples/runProtonicMembrane.rst | 4 ++-- ProtonicMembrane/examples/runProtonicMembrane.m | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/publishedExamples/runProtonicMembrane.rst b/Documentation/publishedExamples/runProtonicMembrane.rst index 4a395083..dab90c11 100644 --- a/Documentation/publishedExamples/runProtonicMembrane.rst +++ b/Documentation/publishedExamples/runProtonicMembrane.rst @@ -60,8 +60,8 @@ We setup the initial state using a default setup included in the model state0 = model.setupInitialState(); -Schedule schedule -================= +Schedule +======== We setup the schedule, which means the timesteps and also the control we want to use. In this case we use current control and the current equal to zero (see here :battmofile:`here`). We compute the steady-state solution so that the time stepping here is more an artifact to reach the steady-state solution. In particular, it governs the pace at which we increase the non-linearity (not detailed here). diff --git a/ProtonicMembrane/examples/runProtonicMembrane.m b/ProtonicMembrane/examples/runProtonicMembrane.m index ae20b430..2c9ba483 100644 --- a/ProtonicMembrane/examples/runProtonicMembrane.m +++ b/ProtonicMembrane/examples/runProtonicMembrane.m @@ -32,7 +32,7 @@ % We setup the initial state using a default setup included in the model state0 = model.setupInitialState(); -%% Schedule schedule +%% Schedule % We setup the schedule, which means the timesteps and also the control we want to use. In this case we use current % control and the current equal to zero (see here :battmofile:`here`). %