Re: [HCP-Users] wb_view 1.2.0 volume view error

2016-06-01 Thread Glasser, Matthew
There is a ticket in for fixing this, but we have not yet had a chance to get it fixed. For now I would recommend using a solution like the HCP Pipeline ACPCAlignment.sh module’s approach for rigidly aligning the data to a standard space template. This will eliminate the oblique sform. In

Re: [HCP-Users] MGTR

2016-06-01 Thread Glasser, Matthew
Greg, my suggestion was an aggressive removal of the physiological noise components without needing to rerun ICA+FIX. It is also worth noting that the extant ³motion estimates² may not perform as expected in multi-band fMRI data. Matt. On 6/1/16, 10:08 AM, "Burgess, Greg"

Re: [HCP-Users] wb_view 1.2.0 volume view error

2016-06-01 Thread Maarten Vaessen
Yes, the images were acquired roughly along the AC-PC plane, but that should be pretty common right? Indeed, I see now that the even the HCP pipeline example data (unprocessed) has some strange behavior when scrolling with the A C P boxed (or is this intended?). -M On Wed, Jun 1, 2016 at 3:41

Re: [HCP-Users] wb_view 1.2.0 volume view error

2016-06-01 Thread Harms, Michael
It looks like that fMRI at least are an oblique acquisition?  Is the T1 oblique as well? I’ve never been able to get oblique acquisitions to behave nicely in wb_view 1.1.0, but haven’t had opportunity to test it yet under 1.2.0.  Hopefully one of the wb_view developers can give

[HCP-Users] Postdoctoral Fellow in Pediatric MRI - NYC

2016-06-01 Thread Mihaela Stefan
*The Cognitive Development and Neuroimaging Lab* in the *Division of Child and Adolescent Psychiatry in the Department of Psychiatry, Columbia University Medical Center and the New York State Psychiatric Institute* invites applications for a post-doctoral associate in the area of developmental

[HCP-Users] wb_view 1.2.0 volume view error

2016-06-01 Thread Maarten Vaessen
Hello, I have come across a strange problem with wb_view where an MPRAGE image is not displayed correctly. No image data is shown on screen, except for one column of pixels in the LR-IS view. It is not possible to navigate through the image as the "slice indices/coords" tab gives 0,0,0 values in