Yes, I can view both the left and right white matter surfaces in tksurfer.

Sorry for the delay, and thanks for your help.

Greg

On Thu, 18 Feb 2010, Douglas N Greve wrote:

An Input/Output error often means that the disk is corrupted or possibly full. Can you read the the lh.white with something else? Eg, can you load it with tksurfer?

doug

Gregory Dierksen wrote:

...

Hi,

I'm trying to make a "midgray" surface by inflating the white surface of a subject by 5% using the following command:

mris_expand -thickness rh.white 0.5 rh.midgray.05

I am getting the following output:

using distance as a & of thickness expanding surface rh.white by 0.50% of thickness and writing it to rh.midgray.05 reading thickness... freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error ...

You get the idea. Usually this command takes about 20 minutes or so to expand a surface... when this message comes up (continuous) I've let it run for a couple hours without completing (I haven't let it go to its conclusion because it takes too long).

So, what's going? How can I fix this?

Thanks, Greg Dierksen

--

Ok, there's the problem. rh.thickness will not load as an overlay and returns the Input/Output error message.

So can I just run the command

mris_make_surfaces -noaparc -mgz -T1 brain.finalsurfs <subjid> rh

to re-generate the right hemisphere thickness file?

On Fri, 19 Feb 2010, Douglas N Greve wrote:

Sorry, it looks like it is the thickness file, not the white surface, it is having problems with. Can you load the thickness as an overlay?

Gregory Dierksen wrote:

...

Yes, I can view both the left and right white matter surfaces in tksurfer.

Sorry for the delay, and thanks for your help.

Greg

On Thu, 18 Feb 2010, Douglas N Greve wrote:

...

An Input/Output error often means that the disk is corrupted or possibly full. Can you read the the lh.white with something else? Eg, can you load it with tksurfer?

doug

Gregory Dierksen wrote:

...

Hi,

I'm trying to make a "midgray" surface by inflating the white surface of a subject by 5% using the following command:

mris_expand -thickness rh.white 0.5 rh.midgray.05

I am getting the following output:

using distance as a & of thickness expanding surface rh.white by 0.50% of thickness and writing it to rh.midgray.05 reading thickness... freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error ...

You get the idea. Usually this command takes about 20 minutes or so to expand a surface... when this message comes up (continuous) I've let it run for a couple hours without completing (I haven't let it go to its conclusion because it takes too long).

So, what's going? How can I fix this?

Thanks, Greg Dierksen

--

how about the thickness files? Is there space left on the disk?On Fri, 19 Feb 2010, Gregory Dierksen wrote:

Yes, I can view both the left and right white matter surfaces in tksurfer.

Sorry for the delay, and thanks for your help.

Greg

On Thu, 18 Feb 2010, Douglas N Greve wrote:

...

An Input/Output error often means that the disk is corrupted or possibly full. Can you read the the lh.white with something else? Eg, can you load it with tksurfer?

doug

Gregory Dierksen wrote:

...

Hi,

I'm trying to make a "midgray" surface by inflating the white surface of a subject by 5% using the following command:

mris_expand -thickness rh.white 0.5 rh.midgray.05

I am getting the following output:

using distance as a & of thickness expanding surface rh.white by 0.50% of thickness and writing it to rh.midgray.05 reading thickness... freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error freadFloat: fread failed Input/Output error ...

You get the idea. Usually this command takes about 20 minutes or so to expand a surface... when this message comes up (continuous) I've let it run for a couple hours without completing (I haven't let it go to its conclusion because it takes too long).

So, what's going? How can I fix this?

Thanks, Greg Dierksen