Hi Dan,
The recognition memory (REC) "task" is just remembering (subject decides
whether they remember/know an item or if it is a new item) the items presented
in the working memory task. The E-Prime files and picture stimuli for the REC
task are part of the 3T E-Prime scripts
I have been trying to find the E-prime download for the recognition memory
task. I have been able to find the WM task and use it, but not the accompanying
recognition memory task. Is it unavailable? Or have I simply missed it
somewhere?
Best,
Dan
In workbench, we do not do things this way at all. Putting both surfaces
into a single file is neither necessary nor recommended, even for
visualization. wb_view will happily display both left and right surfaces
in a single tab, just load the surfaces as separate left and right gifti
files.
Oh, I see. Yes, the —combrain-data-flag in DiffPreprocPipeline.sh was 1 since I
did not touch it.
I will try to use "2".
Thank you so much.
Sang-Young
> On Aug 25, 2017, at 12:30 PM, Harms, Michael wrote:
>
>
> See the --combine-data-flag in DiffPreprocPipeline.sh
>
See the --combine-data-flag in DiffPreprocPipeline.sh
The default value of 1 is intended for acquisitions in which you have acquired
the full vector table with both polarities, which isn’t how you acquired your
data.
In your case, you’ll need to use a value of ‘2’ for that flag.
Cheers,
-MH
Dear HCP users:
I have another problem for running Diffusion Preprocessing pipeline. After eddy
current correction, the pipeline proceeded to run eddy_postproc.sh. But I got
error message as follow:
**
Traceback (most recent call last):
Thank you.
I'll try a couple of other things and see where it takes me.
On Fri, Aug 25, 2017 at 10:31 AM, Glasser, Matthew
wrote:
> Like I said, I don’t think you could do this with surface registration
> because you cannot easily inflate a combined surface to a sphere.
Like I said, I don’t think you could do this with surface registration because
you cannot easily inflate a combined surface to a sphere. You would need to
project to the volume and then back to the surface. I don’t know that it
really matters what volume you use.
Peace,
Matt.
From: Thomas
You might actually have to remap that to the subject’s volume using the
individual surfaces and then back to the merged surface. The reason is that by
merging the surfaces you change the topology, and in such a way that we cannot
use surface registration to handle things. Tim may have