Hi,<div><br></div><div>Two issues related to patch files.</div><div><br></div><div>Issue number 1:</div><div><br></div><div>If I generate an ascii flat patch file like so:</div><div><br></div><div>$ bin_patch=fsaverage/surf/lh.cortex.patch.flat </div>


<div>$ mris_convert -p $bin_patch lh.cortex.patch.flat.asc</div><div><br></div><div>And then inspect the file that gets created:</div><div><br></div><div>$ head lh.cortex.patch.flat.asc </div><div><div>#!ascii version of patch fsaverage/surf/lh.orig. The 1st index is not a vertex number</div>


<div>149297 296943</div><div>1 vno=0</div><div>-60.013611  4.446770  0.000000</div><div>2 vno=1</div><div>-56.163204  88.759064  0.000000</div><div>3 vno=2</div><div>-112.137077  -18.977211  0.000000</div><div>4 vno=3</div>


<div>-34.436668  -72.297958  0.000000</div></div><div><br></div><div>This is sort of annoying if I want to read it into Matlab, etc. (actually Python) using routines that expect an array of numbers.  Is there any way to suppress the intercoordinate output?</div>


<div><br></div><div>Issue number 2:</div><div><br></div><div>Even if I get around the text file formatting issues, I run into some problems when I try and generate meshes with the resulting data.  It seems like the triangles component of the surface makes references to vertex ids that don&#39;t exist anymore.  In other words, the triangles array contains values that are larger than the number of rows in the vertices array.  </div>

<div><br></div><div>Obviously I&#39;m doing things that aren&#39;t officially supported by Freesurfer there, but does that jive with your knowledge of how the patch files are written?</div><div><br></div><div>Thanks!</div>

<div><br></div><div>Michael</div>