All of the examples that I have found in the TestSystems folder leave v0 undefined and let matcont cycle through the unit vectors to determine v0. Is there an example of an ODE definition file that defines the v0 vector rather than leaving it to be determined automatically? I don't know where or how it would be specified.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Knowing the tangent vector at the start of the continuation is only feasible if
(1) you have a correct solution in the first place, so that the tangent vector can be computed. The design of matcont though is that the continuation corrects the first point. This allows you to start with an approximate solution possibly resulting in corrections in the parameter values too, which may be necessary.
(2) you already started the continuation, i.e. from an existing branch and you extend it
(3) you have some asymptotic/algebraic information about the tangent vector, i.e. branch points, Limit cycles from a Hopf point, or codim 2 bifurcation points.
Hope this philosophy helps a bit.
Best, Hil
From: Evelyn Sander esander@users.sourceforge.net
Sent: Sunday, August 12, 2018 10:33 PM
To: [matcont:discussion]
Subject: [matcont:discussion] Setting v0 within the ode definition file
All of the examples that I have found in the TestSystems folder leave v0 undefined and let matcont cycle through the unit vectors to determine v0. Is there an example of an ODE definition file that defines the v0 vector rather than leaving it to be determined automatically? I don't know where or how it would be specified.
All of the examples that I have found in the TestSystems folder leave v0 undefined and let matcont cycle through the unit vectors to determine v0. Is there an example of an ODE definition file that defines the v0 vector rather than leaving it to be determined automatically? I don't know where or how it would be specified.
Knowing the tangent vector at the start of the continuation is only feasible if
(1) you have a correct solution in the first place, so that the tangent vector can be computed. The design of matcont though is that the continuation corrects the first point. This allows you to start with an approximate solution possibly resulting in corrections in the parameter values too, which may be necessary.
(2) you already started the continuation, i.e. from an existing branch and you extend it
(3) you have some asymptotic/algebraic information about the tangent vector, i.e. branch points, Limit cycles from a Hopf point, or codim 2 bifurcation points.
Hope this philosophy helps a bit.
Best, Hil
From: Evelyn Sander esander@users.sourceforge.net
Sent: Sunday, August 12, 2018 10:33 PM
To: [matcont:discussion]
Subject: [matcont:discussion] Setting v0 within the ode definition file
All of the examples that I have found in the TestSystems folder leave v0 undefined and let matcont cycle through the unit vectors to determine v0. Is there an example of an ODE definition file that defines the v0 vector rather than leaving it to be determined automatically? I don't know where or how it would be specified.
Setting v0 within the ode definition file
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/matcont/discussion/762214/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/