pde2path - a Matlab package for continuation and bifurcation in systems of PDEs

Home | Tutorials | Applications| Backlog


March 2020: pde2path 2.8 (tar.gz, zip), mostly bug-fixes

December 2019: pde2path 2.7 (tar.gz, zip), linking with trullekrul for mesh--adaptation in 3D (and improved mesh--adaptation in 2D); algorithms for canonical paths to canonical periodic states in OC problems

June 2019: pde2path 2.6 (tar.gz, zip) bug-fixes

April 2019: pde2path 2.5 (tar.gz, zip), with demos of pattern formation on curved surfaces

October 2018: pde2path 2.4 (tar.gz, zip) contains a number of bug-fixes, and algorithms to deal with branch points of higher multiplicity

April/August 2017: pde2path 2.3 (tar.gz, zip) comes with new demos and tutorials, for instance the acsuite intended as a soft introduction to pde2path and in particular the OOPDE setting, and demos and tutorials for continuous symmetries and freezing. Besides bug fixes, the main new feature of the successor v2.4 is the handling of multiple steady bifurcation points. The user interfaces and most demo directories did not change from v2.3 to v2.4, and thus besides the pattern formation tutorial, the tutorials contain only minor updates and corrections.

April 2016: pde2path 2.2 can now deal with Hopf bifurcations and time periodic orbits; see here. OOPDE has been linked with pde2path more extensively, which is very useful for 1(space)+1(time) dimensional problems. Problems in 3D and 3+1D can also be treated. The OC functionality is now included in the main branch.

July 2015: pde2path 2.1, add-on library and demo files p2poclib for solving spatially distributed optimal control problems.

June 2014: pde2path 2.0, interface to additional equations, fold continuation, demos with preassembled FEM matrices, reorganization of data-structures.

March 2013: pde2path 1.0.

The old versions can be found here ( pde2path1.0 ) and here ( pde2path2.0 ), but we strongly recommend to now use version 2.6, which is fully downwards compatible with 2.*. Upgrading your pde2path codes from 1.0 to 2.* is easy, but there is no immediate compatibility between 1.0 and 2.*.