Perfect, thank you!
Or first a follow-up question, still in the file coco/po/examples/hopf/demo.m, where I have added following lines to plot po_run: figure(2); clf; thm = struct('special', {{'EP'}}); coco_plot_bd(thm, 'po_run', 'p1', 'p2', '||x||_{2,MPD}') When po_run has been calculated with 'bifus', 'off', the plotting function gives following error: Error using coco_bd_col>coco_get_col coco_bd_col: column not found: 'po.test.USTAB' Error in coco_bd_col (line 32) col = coco_get_col(bd, name, cat_flag); Error in coco_plot_bd...
Hi Thanks for confirming the syntax. A quick test with coco/po/examples/hopf/demo.m confirmed that order matters. prob = coco_prob(); %prob = coco_set(prob, 'po', 'bifus', 'off'); %test 1: OK prob = ode_HB2po(prob, '', 'ep_run', HBlab); %prob = coco_set(prob, 'po', 'bifus', 'off'); %test 2: too late fprintf(... '\n Run=''%s'': Continue periodic orbits from point %d in run ''%s''.\n', ... 'po_run', HBlab, 'ep_run'); bd3 = coco(prob, 'po_run', [], 1, 'p1', [-1 1]); The error was that I tried to add...
*all po constructors
Disable detection of bifurcations
Perfect! This question can be closed.
Got it! It seems to be function y = marc(data, xbp, ~, ~, p)
Hello Harry Thank you. I now have understood how to use a bddat function during the continuation run to store quantities of interest to be used during the plotting, and am adapting your example above. For this, I also need to access the current parameter values inside the bddat function. I checked the content of data.coll_seg but did not find this, although data.coll_seg.maps has the field pdim (dimension of parameter vector). Related to your comments above, I suppose that the parameter vector p...