From 556369d31b26eb9c80d8f5514197c7303d4793f4 Mon Sep 17 00:00:00 2001
From: Paul McCarthy <pauld.mccarthy@gmail.com>
Date: Fri, 6 Jan 2017 16:13:57 +0000
Subject: [PATCH] I've just discovered that the FEATFSFDesign class does not
 support interaction EVs

---
 fsl/data/featdesign.py | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/fsl/data/featdesign.py b/fsl/data/featdesign.py
index 655719c2d..263ba244a 100644
--- a/fsl/data/featdesign.py
+++ b/fsl/data/featdesign.py
@@ -8,17 +8,20 @@
 a FEAT design matrix.
 
 
-The :class:`FEATFSFDesign`` class is intended to be used to access the design
+The :class:`FEATFSFDesign` class is intended to be used to access the design
 matrix for a FEAT analysis. The main reason for using the ``FEATFSFDesign``
 class, instead of just using the design matrix loaded directly from the
 ``[analysis].feat/design.mat`` file, is because FEAT supports voxelwise EVs,
 where the contents of the design matrix will differ for each voxel in the
 analysis. For all voxelwise EVs (confound or otherwise), the design matrix (in
 ``design.mat``) contains a dummy column which contains the mean across all
-voxels.  The :meth:`FEATFSFDesign.getDesign`` method will return an
+voxels.  The :meth:`FEATFSFDesign.getDesign` method will return an
 appropriate design matrix for a specific voxel.
 
 
+.. note:: Interaction EVs are not currently supported.
+
+
 Explanatory variables in a FEAT design
 --------------------------------------
 
-- 
GitLab