Rank: 1536 based on 75 downloads (last 30 days) and 1 file submitted
photo

Etienne Coetzee

E-mail
Company/University
University of Bristol

Personal Profile:
Professional Interests:

 

Watch this Author's files

 

Files Posted by Etienne
Updated   File Tags Downloads
(last 30 days)
Comments Rating
13 Jul 2011 Screenshot Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee bifurcation, coninuation, coninuation, dynamical systems, fold, hopf 75 24
  • 5.0
5.0 | 5 ratings
Comments and Ratings by Etienne View all
Updated File Comments Rating
28 Feb 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee

Hi Arne

I have not tried this before, although we have done something similar with ADAMS. In ADAMS there is a setting where you can either use ADAMS for the derivative calculation or Simulink. The option needs to be set to Simulink. Maybe VLM has something similar. I cannot even offer to try and debug this because we do not have a VLM license.

You may also want to check the size of your model, compared to the size defined in Ndim. We had problems before when Ndim becomes larger than 100, and we still do not really know why.

Another option may be to construct a reduced order model from the VLM model. You can for instance see if you can use Eureqa or similar tools on a time history of your model, and see if you can get some ODE's from this. You will need to provide enough information though.

Another option may be to try and generate C-code from VLM, and see if you can link this in to vanilla AUTO.

Unfortunately the new version is not available yet. We are currently trying to generate a TLC script that will generate c-code from a Simulink model and link this in to AUTO. This is tricky and I have not had a lot of time to work on this.

Regards

Etienne

20 Dec 2013 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee

Hi Arne

I am on holiday until the new year. I will try to look at it then. We are also working on a newer version of the toolbox, so we may update the toolbox as well in the new year. We are trying to add some new features where you can run Simulink Coder code to make the runs faster.

Regards

Etienne

14 Nov 2013 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee

Hi Olle

I have not tested this with gfortran, which is what I assume you are using. You can get the Intel compiler for Linux for free, so maybe give that a go first.

R2012b has a new help interface. Check at the bottom of the help screen for "Supplemental Software" or type "doc -classic" on the command line. This should bring up the menu with the toolbox. docroot is only valid if you install to the actual docroot directory. Check to see if strcmp(dynasyshelproot,fullfile(docroot,'toolbox','dynasys')) is true. If not, place the whole name from fullfile(docroot,'toolbox','dynasys') into the info.xml file. If it is the same, make sure you have a $ sign and not a % in the file.

Regards

Etienne

03 May 2013 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee

HI Sudharsana

Comment out the lines where "setstatusbar" is called. There seems to be some Java incompatability. You can also look at the getting started documentation to see where the files need to be installed. You can then bypass the GUI.

Regards

Etienne

03 May 2013 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee

HI Rajesh

I had a problem recently where the mex file was not detected, even though it was on the path. Make sure no other mex files are on the path, even if it is mexw32 etc. This seems to make a difference.

I think the INTEGER*4 was removed and changed to INTEGER. The type was automatically set.

You should maybe check to see if you can get the INTEL FORTRAN compiler for Linux. They give it out for free as far as I know. Maybe only for personal use. Your code is obviously compiling so it must be a path error in some way.

Regards

Etienne

Comments and Ratings on Etienne 's Files View all
Updated File Comment by Comments Rating
26 Aug 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee Alexander

Hi there,

I just tried to install the Dynamical Systems Toolbox, and I encountered the following problem:

installdynasys
Warning: Single line Edit Controls can not have multi-line text
> In openfig at 135
In gui_mainfcn>local_openfig at 286
In gui_mainfcn at 159
In installdynasys at 63
Attempt to reference field of non-structure array.

Error in installdynasys>installdynasys_OpeningFcn (line 87)
if Message.UserWrite == 1

Error in gui_mainfcn (line 221)
feval(gui_State.gui_OpeningFcn, gui_hFigure, [], guidata(gui_hFigure), varargin{:});

Error in installdynasys (line 63)
gui_mainfcn(gui_State, varargin{:});

I am using Matlab 8.0.0.783 (R2012b)

12 Aug 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee Jack

28 Feb 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee Defraye, Arne

28 Feb 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee Coetzee, Etienne

Hi Arne

I have not tried this before, although we have done something similar with ADAMS. In ADAMS there is a setting where you can either use ADAMS for the derivative calculation or Simulink. The option needs to be set to Simulink. Maybe VLM has something similar. I cannot even offer to try and debug this because we do not have a VLM license.

You may also want to check the size of your model, compared to the size defined in Ndim. We had problems before when Ndim becomes larger than 100, and we still do not really know why.

Another option may be to construct a reduced order model from the VLM model. You can for instance see if you can use Eureqa or similar tools on a time history of your model, and see if you can get some ODE's from this. You will need to provide enough information though.

Another option may be to try and generate C-code from VLM, and see if you can link this in to vanilla AUTO.

Unfortunately the new version is not available yet. We are currently trying to generate a TLC script that will generate c-code from a Simulink model and link this in to AUTO. This is tricky and I have not had a lot of time to work on this.

Regards

Etienne

28 Feb 2014 Dynamical Systems Toolbox Bifurcation analysis of dynamical systems. Integration of AUTO bifurcation software into MATLAB. Author: Etienne Coetzee Defraye, Arne


Dear Mr. Coetzee,

With regard to my last post, I’ve already solved some problems myself. But now I’m encountering a particular problem, that have brought my entire master thesis to a complete standstill because I can’t find the fault I made myself. Could you please help me with following:

My master thesis deals with the research of using bifurcation theory for analysis of landing gear shimmy. I am using multi-body software, called LMS Virtual.Lab Motion. My goal is to research if there is a possibility to use the bifurcation toolbox in a coupled simulation with the multi-body software Virtual.Lab Motion. The coupled simulation connects Virtual.Lab Motion with Simulink using an S-function in Simulink, that brings all the equations to Simulink.

So now my problem is that I can’t run a Simulink bifurcation, wherein such an S-function is contained.
· The standalone (not using the bifurcation toolbox) coupled simulations work between Matlab and Virtual.Lab Motion.
· And I’ve also run some simple bifurcations with Simulink.
So the combination of those two doesn’t seem so farfetched to me.

However, following error keeps on popping up:
“Error using AUTO07gateway
Numerical instability, NaN or Inf detected in subroutine func, adjust the tolerances of the bifurcation
parameters

Error in auto/runautodst (line 161)
[obj.f7,obj.f8]=AUTO07gateway(obj.s,obj.c,obj.f7,obj.f8);

Error in auto/runauto (line 39)
obj=runautodst(obj);

Error in massaveersyst (line 36)
a{1}=runauto(a{1});”

I’ve already tried changing a lot of parameters, such as the tolerances, but it seems I’m stuck. Does this error rings a bell to you? Is it a common error with a specific origin?

There is one piece of code that I’m still wandering if the problem might lurk there. The piece of code is programmed in the ‘func’ file and calls the Simulink model. Could you tell me what the different function arguments are and what they mean?
o=nameofsimulinkproject(0,u,par(1:1),'outputs');
f=nameofsimulinkproject(0,u,par(1:1),'derivs');

Finally; is there already a release date for the new DST bifurcation toolbox? And will the toolbox have some features that could benefit this application?
I really hope that you could help me,

My most sincerest regards,
Arne

Contact us