Back to the main page.

Bug 1001 - ft_plot_headshape redundant?

Reported 2011-10-03 18:58:00 +0200
Modified 2019-08-10 12:33:24 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P1 normal
Assigned to: Stephen Whitmarsh
Depends on:
See also:

Stephen Whitmarsh - 2011-10-03 18:58:36 +0200

Stephen Whitmarsh - 2011-10-03 19:01:11 +0200

ambiguous with other plotting functions, i.e. plot_mesh

Stephen Whitmarsh - 2011-10-03 19:04:05 +0200

In any case it does not plot meshes correctly (only points, no mesh) derived from prepare_headmodel. So make it or break it?

Robert Oostenveld - 2011-10-05 09:09:18 +0200

Just to ensure that the following is clear: ft_plot_headshape has to do with ft_read_headshape, not with the private/headsurface or private/head_surf functions. The ft_read_headshape function has been getting more responsibilities over time, initially it just returned a set of points, then also the fiducials (in some cases) where the fiducials can be in MRI coords as opposed to head coords (hence the warp_apply). Then we also started using it for cortical sheets (for Lilla's MNE/FreeSurfer pipeline) It is indeed not clear whether the "headshape" should be considered a principal building block. Is the function being called from somewhere? @Vladimir: are you using the ft_plot_xxx functions in SPM?

Vladimir Litvak - 2011-10-05 09:12:58 +0200

Not directly. Just via other FT functions (headmodelplot)

Jan-Mathijs Schoffelen - 2013-10-10 10:38:36 +0200

Reviving some old bugs. @Stephen: please think about whether this one is still 'actueel'/relevant, and assign it to yourself in order to fix it at some point. If not relevant anymore, please close.

Jan-Mathijs Schoffelen - 2016-02-21 14:27:45 +0100

Does not seem to be relevant anymore (as per my previous comment), since Stephen has not followed up on this one for a few years. Changing status for this reason.

Robert Oostenveld - 2019-08-10 12:33:24 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue on