User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
docs:utils:poincare [2009/02/23 12:56]
docs:utils:poincare [2010/02/02 07:55] (current)
Line 1: Line 1:
 ====== poincare ====== ====== poincare ======
-compute ​crossings of a Poincare section in a pre-computed trajectory+Compute ​crossings of a Poincare section in a pre-computed trajectory. The Poincare condition is %%(u(t) - ueqb, e) == 0%%, i.e. the displacement from a given point %%ueqb%% is orthogonal to a direction %%e%%. The program checks for changes in sign in the inner product in the stored trajectory (with large %%dT%%, and when it finds one, goes back and reintegrates with small %%dt%%, and then does quadratic interpolation when the fine-scale trajectory recrosses the section. 
 ===== usage ===== ===== usage =====
Line 48: Line 49:
    ​poincare -T0 0 -T1 1000 -d data-ueqb_0001ef1 ueqb ef2    ​poincare -T0 0 -T1 1000 -d data-ueqb_0001ef1 ueqb ef2
 </​code>​ </​code>​
 +===== Hiccups =====
 +:-) Hey John, I was wondering if there was any particular reason you put the cfpause() line in your code other than it was helpful in writing the code. --- //​[[|Dustin Spieker]] 2009-03-02 10:24//
docs/utils/poincare.1235422610.txt.gz · Last modified: 2009/02/23 12:56 by gibson