hilmeijer

Your message contains no details showing or pointing at the problem you face. Please provide more details.

Sorry, but this depends so much on the model equations. You cannot expect others to guess this without providing details; you haven't mentioned either what came out of inspecting the numerical data in the Data Browser. In general, you can experiment with the MaxStepSize. Standard values for Tolerances are fine, and should only be changed after careful inspection.

Thank you for your prompt reply! I’d like to ask further: when plotting the limit cycle starting from the Hopf branching point, Matcont runs very slowly. What adjustments should I make to speed up the calculation? In the “Continuer” section, what do the settings under “Corrector Data” mean? Thank you very much for your time!

Thank you for your prompt reply! I’d like to ask further: when plotting the limit cycle starting from the Hopf branching point, Matcont runs very slowly. What adjustments should I make to speed up the calculation? In the “Continuer” section, what do the settings under “Corrector Data” mean? Thank you very much for your time!

Before I start guessing, have a look at the data browser and specifically at the values of the test functions. Do you see that they change sign? Small(er) stepsizes may sometimes be needed.

This is not necessarily a well-posed question; you can use MatCont for "standard" dynamical systems analysis, so why would the methods differ from any other tool? So it is the Real Part of Eigenvalues for equilibria, or the modulus of Floquet Multipliers for limit cycles. You can inspect the stability looking at a Numeric Window, The Data Browser, or change plot properties (EQ/LC if unstable 'Color','red').

Sorry, but we cannot check just any equations. But suppose these are correct. What you also need is a good initial point. If you start too far away from an equilibrium it will not be able to find it, that is the newton iterations will not converge. So you may first do a simulation (like in the first tutorial) to observe the behaviour and get an idea of what the system is doing.

While I understand how you want to enter your system, the GUI does not work this way. The problem is that we chose to work with scalar state variables. Not with vector-valued ones. In our recent work to work with delays we sort of have an option for vector-valued variables but it is far from automated. Work in progress, if anyone has time. For now, what you can do, is to create a simple system with the correct number of state variables and parameters but no irrelevant ODEs. After creating the file,...