Print

Print


I've only seen this occur once before for one subject andI don't know why it occurred. 

It turns out the the contrast vector SPM.xCon.c does not get changed (please double check this in your case) and the fields that do get changed do not impact the contrast or T-test values. While its good to be concerned about odd warning messages like this one, this warning doesn't seem to impact the processing streams.

Perhaps one of the SPM authors could provide more details on why this happens for some models.

Best Regards, Donald McLaren
=================
D.G. McLaren, Ph.D.
Research Fellow, Department of Neurology, Massachusetts General Hospital and
Harvard Medical School
Postdoctoral Research Fellow, GRECC, Bedford VA
Website: http://www.martinos.org/~mclaren
Office: (773) 406-2464
=====================
This e-mail contains CONFIDENTIAL INFORMATION which may contain PROTECTED
HEALTHCARE INFORMATION and may also be LEGALLY PRIVILEGED and which is
intended only for the use of the individual or entity named above. If the
reader of the e-mail is not the intended recipient or the employee or agent
responsible for delivering it to the intended recipient, you are hereby
notified that you are in possession of confidential and privileged
information. Any unauthorized use, disclosure, copying or the taking of any
action in reliance on the contents of this information is strictly
prohibited and may be unlawful. If you have received this e-mail
unintentionally, please immediately notify the sender via telephone at (773)
406-2464 or email.

On Fri, Mar 6, 2015 at 4:36 AM, gj <[log in to unmask]> wrote:
Hi,

I'm trying to use Donald Mclaren's nifty gPPI toolbox/PPPI v.13 and although for one contrast in particular, I first get a message saying "Valid contrast," this is followed by the warning:

---
c is not a proper contrast in +c->Tsp in spm_SpUtil
!!! projecting...
---

I see that spm_SpUtil.m returns a vector that reweights where the condition occurs in the different sessions and includes an additional small weight for one of the session constants. I guess this has something to do with orthogonality, but would appreciate if someone could explain to me when this happens, how/why the reweighting happens the way it does, and whether this warning is a big warning or one to just take under advisement.

Thanks for any clarification!
g