Simon:
If you are running a bunch of cases and then want to do basic visual
inspection QA, it can be helpful to script tkmedit and tksurfer to generate
screen caps at various angles and positions which you can then view rapidly.
I've just posted some sample scripts to do this:
https://surfer
look for the accuracy of the ?h.white and ?h.pial surfaces, and the
aseg.mgz boundaries
On Wed, 2 Jan 2008, Simon Rushton wrote:
Any tips regarding how to do the visual inspection, ie what to look at, and
what to look for?
simon
On 2 Jan 2008, at 11:05PM, Bruce Fischl wrote:
your concern i
Any tips regarding how to do the visual inspection, ie what to look
at, and what to look for?
simon
On 2 Jan 2008, at 11:05PM, Bruce Fischl wrote:
your concern isn't misplaced. We *always* visually inspect every
dataset. It's just that things work so frequently now that we don't
stop in
your concern isn't misplaced. We *always* visually inspect every dataset.
It's just that things work so frequently now that we don't stop in the
middle to do so anymore.
Bruce
On Wed, 2 Jan 2008, Simon Rushton wrote:
I feel somewhat uneasy simply assuming that the process worked just because
I feel somewhat uneasy simply assuming that the process worked just
because it didn't exit with an error. Is my concern misplaced?
Should I feel happy about submitting a ms based on freesurfer analyses
that have not been independently checked?
If it is necessary/advisable to do some indep
