Hi - <div><br></div><div>I&#39;m using freesurfer with an ex-vivo MTR of a monkey, at 0.25mm. unfortunately the data doesn&#39;t fit into 256^3, and anyway things are much faster, and decent results are to be had by downsampling to 0.5mm.</div>
<div><br></div><div>I did notice this mris_refine_surfaces. That looked great. I can fit 0.32mm into 256^3, so I did that, and called it 0.64mm, and treated it the same way I treated the 0.5mm (nu_correct etc etc) to get my &quot;hires.mgz&quot; for mris_refine_surfaces</div>
<div><br></div><div>then I noticed mris_refine_surfaces wants ?h_hires.label as well.</div><div><br></div><div>a) how would I make ?h_hires.label </div><div>b) does my hires.mgz even have to be 256^3? If not, I could use the actual 250um data to refine the surface, and that would be nice.</div>
<div>c) I don&#39;t suppose there would be any chance of not only using a hi res volume to refine the surfaces, but also upsampling the surfaces too? There is a reason I might want them upsampled. It would be nice for the ?h.white mesh to sort of approximately have a node for each voxel face. It&#39;s to do with more accurately mapping certain data in CARET later on.</div>
<div><br></div><div>I&#39;d settle for just how to make ?h_hires.label and use mris_refine_surfaces though :) </div><div><br></div><div>cheers,</div><div><br></div><div>Colin</div>