I don't know. It might be that the other ones are close to being badly
conditioned and just don't meet my (arbitrary) threshold.
doug
On 03/01/2013 06:30 PM, Katie Bettencourt wrote:
> Ok, I understand that, except that all of my runs are like that, but
> only a few of them errored out. Why is
Ok, I understand that, except that all of my runs are like that, but only a
few of them errored out. Why is that?
Katie
On Fri, Mar 1, 2013 at 3:38 PM, Douglas N Greve
wrote:
> Hi Katie, the problem is that eventtypes 1 and 2 are synchronized 32 sec
> apart. What this means is that they are eff
Hi Katie, the problem is that eventtypes 1 and 2 are synchronized 32 sec
apart. What this means is that they are effectively one event if you set
the time window longer than 32 sec (you have it set to 34). There is no
way around this. If you want a longer window, use 30 sec (32 might work).
doug
Here it is for one of the failed runs. Let me know if you need anything
else.
Katie
On Thu, Feb 28, 2013 at 3:27 PM, Douglas N Greve
wrote:
> Can you send me the Xtmp.mat file from the outputdirectory?
> doug
>
> On 02/28/2013 07:34 AM, Katie Bettencourt wrote:
>
>> Still looking for an answer
Can you send me the Xtmp.mat file from the outputdirectory?
doug
On 02/28/2013 07:34 AM, Katie Bettencourt wrote:
> Still looking for an answer why my analysis gives me an ill
> conditioned error. I have run this analysis fine before, with a
> timewindow of 22, but when I tried to change the ti
Still looking for an answer why my analysis gives me an ill conditioned
error. I have run this analysis fine before, with a timewindow of 22, but
when I tried to change the time window to 34, selxavg3-sess gives me an ill
conditioned error on some of the runs (each run is being analyzed
separatel
No, each condition has at least 3 instances of it in each run. The runs
are all set up exactly the same, just the order changes, so there is
nothing different about the runs that work than the runs that fail, and
again, all of these runs worked fine with the exact same paradigm files and
set up, b
Hi katie, I'm guessing that you have one event type that only has one
event? If so, you can do what Sebastian suggests, but you won't be able
to look at contrasts related to that condition.
doug
On 02/19/2013 03:24 PM, Katie Bettencourt wrote:
> I am having a problem with selxavg3-sess (for FS
Hi Katie,
On Feb 19, 2013, at 13:57 , Katie Bettencourt wrote:
> Hmm, I think that might not help given that I get an XCond = 2.75109e+17
> right before that error, so bumping to 6 probably isn't going to help.
Well replace 1e6 by 1e18 then? Just to get it going and then compare
the r
Hmm, I think that might not help given that I get an XCond = 2.75109e+17
right before that error, so bumping to 6 probably isn't going to help.
I can't figure out why it is doing this now with just the change in
timewindow, but I'm obviously missing something. I actually only have 3
conditions in
Hi Katie,
what about just modifying the matlab code that gives the ill-conditioned error?
So for free surfer 4.5 you will find in
$FREESURFER_HOME/fsfast/toolbox/fast_selxavg3.m:
XCond = cond(XtX);
fprintf('XCond = %g (normalized)\n',XCond);
if(XCond > 1e4)
fprintf('ERROR: design is il
I am having a problem with selxavg3-sess (for FS 4.5) where it is giving me
an Ill-conditioned error that I can't trace out.
I have 8 runs that I am running separately (same basic analysis for each
run, but each run gets it's own analysis for svm purposes). Originally for
this subject, I created
12 matches
Mail list logo
