[VoxBo] bad jobs for glm

[Golbarg Tarighat Saber]

Hi, 

Thanks for your reply. For creating GLMs, I have been using 'glm' and not 'vbmakeglm'. The last successful glm that I ran was about three weeks ago. As for the path, I actually replaced my actual long path to the analysis folder with the word 'path' to make my email more concise. We have several versions of voxbo (including v1.8.5pre) in the lab. I tend to choose the hrf filter for GLM  from the folder voxbo- 1.8.5pre/elements. However, I'm not sure which version is called when I type glm in the command line. "voxq -v" prints out the voxbo version 'v1.8.4Jan 26 2007). You can attached .glm files attached. 
 
----- Original Message -----
From: Daniel Kimberg <kimberg at mail.med.upenn.edu>
Date: Sunday, December 20, 2009 12:59 pm
Subject: Re: [VoxBo] bad jobs for glm
To: VoxBo Discussion List <voxbo-general at voxbo.org>

> >  Executing script command: makematkg -m <path to the analysis folder>
> ...
> 
> Normally you should see an actual path (and GLM stem) there, not just 
> the phrase "path to the analysis folder" in angle brackets.  I'm not 
> sure where that phrase came from, it doesn't seem to be in the 
> codebase currently.  Are you using the 1.8.5pre version of the VoxBo 
> code?  How did you create the GLM, using "glm" or "vbmakeglm?"  In 
> either case, it might help if you posted the contents of the .glm 
> file, either the one you created or if you didn't make one, the one 
> that was created for you in the glm directory.
> 
> > The only files created in the analysis folder are *.G, *.glm, *.preG,
> > *.ref, *.sub, averages.txt, and contrasts.txt. I first encountered
> > this problem while running GLM on mfbrt*.tes files, and later I
> > noticed that running GLM on sbrt*.tes files also fails due to similar
> > bad jobs. I reran GLMs which I had run successfully before, but I
> > couldn't replicate any of those. I'd be grateful if you can help me
> > fix this problem.
> 
> If you're seeing the same problem with previously run analyses, it's 
> likely that something has changed in your configuration.  How long ago 
> were the old analyses run?
> 
> dan