Back to the main page.

Bug 1257 - ft_analysisprotocol should properly support multiple different branching scenarios

Reported 2012-01-13 11:34:00 +0100
Modified 2012-03-14 10:00:44 +0100
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P3 normal
Assigned to: Eelke Spaak
Depends on:
See also:

Eelke Spaak - 2012-01-13 11:34:29 +0100

Robert, comment on bug 1141: branching (when going upward, or merging when going downward) happens in functions that combine multiple inputs. E.g. grandaverage, or statistics. In that case cfg.previous = {varargin{1}.cfg, varargin{2}.cfg, ...} A new application for branching/merging is now also with sideways entry of previous cfgs in volcfg = ... vol = ft_prepare_headmodel(volcfg) sourcecfg = ... sourcecfg.vol = vol; % note that this also contains the volcfg source = ft_sourceanalysis(cfg, data) where the output source.cfg = data.cfg, but where source.cfg.vol.cfg is a "sideways" branch into the headmodel construction tree (which can contain a sequence of volumerealign, volumereslice, and volumesegment prior to ft_prepare_headmodel). The visualisation of the sideways branching would probably best be done with something like fn = fieldnames(cfg) for i=1:length(fn) if isa(cfg.(fn{i}), 'struct') && isfield(cfg.(fn{i}), 'cfg') % sideways branch detected, do something with it end Could you still add this to the ft_analysisprotocol visualisation?

Eelke Spaak - 2012-01-13 12:19:21 +0100

Fixed in revision 5140.

Eelke Spaak - 2012-03-14 10:00:44 +0100

closing several bugs that have been RESOLVED for a long time