Ah excellent! Using TextWrangler removed the hidden characters and all is working now.
Thats strange though.. I thought TextEdit was known for removing hidden characters, oops.  

Thanks a ton Mark,
Daniel


On Fri, Apr 19, 2013 at 9:30 AM, Mark Jenkinson <[log in to unmask]> wrote:
Hi,

Try using a native plain text editor rather than TextEdit.
Something like emacs or nano as I suspect that Excel is creating some characters that TextEdit is still passing on, or failing to put in proper Unix newline characters.
If you run "wc" on the file you'll see if it can correctly determine the number of lines or not.

All the best,
Mark



On 19 Apr 2013, at 14:25, Daniel Cole <[log in to unmask]>
 wrote:

Hi Mark,

Thanks a lot for the response.  A 1 column EV seems to work but after creating a 2 column EV in Excel it gives me the error message.  I always make sure to change TextEdit to plain text format as well.

My functional input data is 144 volumes with no volumes being deleted and my text files are 144 rows/timepoints.  There are no dummy scans.

Is there anything else it could possibly be?

Thanks,
Daniel




On Thu, Apr 18, 2013 at 6:33 PM, Mark Jenkinson <[log in to unmask]> wrote:
Hi Daniel,

You could test to see if it was TextEdit (which needs to be put into plain text mode, and that is not the default) by creating a single column version and then importing that as a normal EV.  If this is successful and you can view the design OK then it isn't likely to be the text file.

Otherwise, the most likely problem is a mismatch in the dimensions.  Do you have any dummy scans?

All the best,
Mark


On 18 Apr 2013, at 21:33, Daniel Cole <[log in to unmask]> wrote:

Hello FSLers,
I'm having some problems inputting confound EVs to my 1st-level FEAT analysis.  I have a text file, 2 columns, 144 timepoints with the timecourse for white matter and for CSF.  I created the file in Excel and then copied into plain text format TextEdit.  However whenever I try to run the FEAT GLM I get the error "Problem with processing the model: terminate called throwing an exception".  Any ideas?  I don't believe there are any hidden characters since it was created in TextEdit.

Thanks,
Daniel


--
Daniel Cole
University of Rochester
Brain and Cognitive Sciences




--
Daniel Cole
University of Rochester
Brain and Cognitive Sciences




--
Daniel Cole
University of Rochester
Brain and Cognitive Sciences
[log in to unmask]