<?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" > <channel rdf:about="http://www.nitrc.org/export/rss_sfnews.php"> <copyright>Copyright 1999-2000 VA Linux Systems, Inc.</copyright> <title>NeuroStars News</title> <link>http://www.nitrc.org</link> <description>NeuroStars Latest News</description> <items> <rdf:Seq> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9123" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9124" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9125" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9126" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9127" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9128" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9129" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9130" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9131" /> <rdf:li rdf:resource="http://www.nitrc.org/forum/forum.php?forum_id=9132" /> </rdf:Seq> </items> </channel> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9123"> <title>ICA AROMA agg vs non-agg</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9123</link> <description> <p>I just want to clarify something. If we’re using the aggressive denoising strategy on the <code>_desc-preproc_bold.nii.gz</code> data, do we also need to include the motion parameters (<code>trans_x trans_y trans_z rot_x rot_y rot_z</code>) in our nuisance regression, or will they already be regressed out by the ICA-AROMA confounds?</p><br /> <p>I realize that we would want to include these motion parameters in a nuisance regression if we were just using the <code>_desc-preproc_bold.nii.gz</code> data without ICA-AROMA denoising; however, does it make sense to include them with <code>_desc-preproc_bold.nii.gz</code> + aggressive ICA-AROMA confounds, (or even for analyzing the non-aggressive <code>smoothAROMAnonaggr_bold.nii.gz</code> data?).</p><br /> <p>Thanks for the clarification.</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 8:01:08 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9124"> <title>Dmriprep: an fmriprep for diffusion?</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9124</link> <description> <p>I’m also working on a pipeline for diffusion image processing <a href="https://github.com/pennbbl/qsiprep" rel="nofollow noopener">https://github.com/pennbbl/qsiprep</a> and across-software reconstruction. The preprocessing part is mostly done and the reconstruction part is coming along.</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 7:16:24 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9125"> <title>BIDS - b0 correction for DWI</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9125</link> <description> <p>Dear all,</p><br /> <p>We acquired a b0 with a reverse phase encoding direction to be used to correct DWI (topup). I would like to know where to put such images in the BIDS format. Should it go to the dwi folder or fmap folder ?</p><br /> <p>Thank you in advance<br><br /> Arnaud</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 7:10:57 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9126"> <title>GSoC Project Idea 7: Implementing automatic white matter parcellation in Nighres</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9126</link> <description> <p>Hello <a class="mention" href="/u/piloubazin">@piloubazin</a>. I’m interested in working on the topic ‘’ as a part of GSoC 2019. I’m currently pursuing a Master’s degree in Computer Science and have worked extensively on MR images and machine learning. In order to proceed working on this topic, I’ve started going through the paper mentioned above. Regarding the same, I would like to know whether there are any already preprocessed images available that I can use? If not then I would proceed with the preprocessing steps mentioned in the paper.</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 6:57:22 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9127"> <title>GSoC Project Idea 14: Producing publication-ready brain network analysis results and visualisations from the command line</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9127</link> <description> <p>Hi <a class="mention" href="/u/kirstiejane">@KirstieJane</a> . I’m interested to work on this topic as part of the GSoC 2019. I’ve worked on nilearn, matplotlib and networkx. Currently, I’m working on structural connectivity analysis of normal and diseased brains using complex networks and machine learning. In order to start with this topic, I was thinking of using scona and networkx to generate a connectivity matrix. Could you please let me know whether this would be a good way to get started on this topic? If this is not a good idea then could you please suggest some tasks for the same?</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 6:09:30 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9128"> <title>Video Data of Subjects in BIDS</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9128</link> <description> <p>So, to be clear, we have video data of every run for each of our subjects. There is a part of the standard, at least as originally published in Nature, that seems to suggest that it is permissible to place non-BIDS-compliant data in the standard directories wherever common sense would suggest it would go, and hope a standard will come out some day. Is that correct? "For example one may want to include eye tracking data in a vendor specific format that is not covered by this standard. The most sensible place to put it is next to the continuous recording file with the same naming scheme but different extensions. "</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 4:16:08 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9129"> <title>Freesurfer error FOV > 256</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9129</link> <description> <p>Hi, Chris,<br><br /> I also encountered similar problem with my own data when using recon function (with --fs-no-reconall, I could finish the preprocessing)</p><br /> <p>Here is the log from recon-all.log:</p><br /> <blockquote><br /> <p>Mon Mar 11 00:13:28 UTC 2019<br><br /> /out/out/freesurfer/sub-001<br><br /> /opt/freesurfer/bin/recon-all<br><br /> -autorecon1 -i /data/sub-001/ses-d1/anat/sub-001_ses-d1_T1w.nii.gz -noskullstrip -cw256 -hires -openmp 7 -subjid sub-001 -sd /out/out/freesurfer -expert /work/fmriprep_wf/single_subject_001_wf/anat_preproc_wf/surface_recon_wf/autorecon1/expert.opts<br><br /> subjid sub-001<br><br /> setenv SUBJECTS_DIR /out/out/freesurfer<br><br /> FREESURFER_HOME /opt/freesurfer<br><br /> Actual FREESURFER_HOME /opt/freesurfer<br><br /> build-stamp.txt: freesurfer-Linux-centos6_x86_64-stable-pub-v6.0.1-f53a55a<br><br /> Linux 3e5932778b80 4.15.0-46-generic <span class="hashtag">#49-Ubuntu</span> SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux<br><br /> cputime unlimited<br><br /> filesize unlimited<br><br /> datasize unlimited<br><br /> stacksize 8192 kbytes<br><br /> coredumpsize unlimited<br><br /> memoryuse unlimited<br><br /> vmemoryuse unlimited<br><br /> descriptors 1048576<br><br /> memorylocked 16384 kbytes<br><br /> maxproc unlimited<br><br /> maxlocks unlimited<br><br /> maxsignal 63302<br><br /> maxmessage 819200<br><br /> maxnice 0<br><br /> maxrtprio 0<br><br /> maxrttime unlimited</p><br /> <pre><code> total used free shared buff/cache available<br /> </code></pre><br /> <p>Mem: 16284864 4278568 2888448 294604 9117848 11211380<br><br /> Swap: 7812092 456192 7355900</p><br /> <p>########################################<br><br /> program versions used<br><br /> $Id: recon-all,v 1.580.2.16 2017/01/18 14:11:24 zkaufman Exp $<br><br /> $Id: mri_motion_correct.fsl,v 1.15 2016/02/16 17:17:20 zkaufman Exp $<br><br /> mri_convert.bin -all-info<br><br /> ProgramName: mri_convert.bin ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:28-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_convert.c,v 1.226 2016/02/26 16:15:24 mreuter Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> FLIRT version 5.5<br><br /> $Id: talairach_avi,v 1.13 2015/12/23 04:25:17 greve Exp $<br><br /> mri_convert.bin --version<br><br /> stable6<br><br /> ProgramName: tkregister2_cmdl ProgramArguments: --all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:28-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: tkregister2.c,v 1.132.2.1 2016/08/02 21:17:29 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> Program nu_correct, built from:<br><br /> Package MNI N3, version 1.12.0, compiled by nicks@terrier (x86_64-unknown-linux-gnu) on 2015-06-19 at 01:25:34<br><br /> ProgramName: mri_make_uchar ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:28-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_make_uchar.c,v 1.4 2011/03/02 00:04:14 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_normalize ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:28-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_normalize.c,v 1.88.2.3 2016/12/27 16:47:13 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_watershed ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:28-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_watershed.cpp,v 1.103 2016/06/17 18:00:49 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_gcut ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_gcut.cpp,v 1.14 2011/03/02 00:04:16 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_segment ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_segment.c,v 1.43.2.1 2016/10/27 22:24:52 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_label2label.bin ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_label2label.c,v 1.48.2.2 2016/12/12 14:15:26 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_em_register ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_em_register.c,v 1.105.2.1 2016/10/27 22:25:10 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_ca_normalize ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_ca_normalize.c,v 1.67.2.2 2016/10/27 22:25:09 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_ca_register ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_ca_register.c,v 1.96.2.3 2016/10/27 22:25:10 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_ca_label ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_ca_label.c,v 1.113.2.2 2016/10/27 22:25:10 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_pretess ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_pretess.c,v 1.22 2013/08/30 18:12:25 mreuter Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_fill ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_fill.c,v 1.119 2011/10/25 14:09:58 fischl Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_tessellate ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_tessellate.c,v 1.38.2.1 2016/07/26 18:46:38 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_concatenate_lta.bin ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_concatenate_lta.c,v 1.16 2015/11/21 00:06:20 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_normalize_tp2 ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_normalize_tp2.c,v 1.8 2011/03/02 00:04:23 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_smooth ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_smooth.c,v 1.30 2014/01/21 18:48:21 fischl Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_inflate ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_inflate.c,v 1.45 2016/01/20 23:42:15 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_curvature ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_curvature.c,v 1.31 2011/03/02 00:04:30 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_sphere ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_sphere.c,v 1.61 2016/01/20 23:42:15 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_fix_topology ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_fix_topology.c,v 1.50.2.1 2016/10/27 22:25:58 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_topo_fixer ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_topo_fixer.cpp,v 1.29 2011/03/02 00:04:34 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_ca_label ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_ca_label.c,v 1.37 2014/02/04 17:46:42 fischl Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_euler_number ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_euler_number.c,v 1.10 2013/01/14 22:39:14 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_make_surfaces ProgramArguments: -all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_make_surfaces.c,v 1.164.2.4 2016/12/13 22:26:32 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_register ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_register.c,v 1.63 2016/01/20 23:43:04 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_volmask ProgramArguments: --all-info ProgramVersion: $Name: $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_volmask.cpp,v 1.26.2.2 2016/11/18 20:05:18 zkaufman Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_anatomical_stats ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_anatomical_stats.c,v 1.79 2016/03/14 15:15:34 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mrisp_paint ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mrisp_paint.c,v 1.12 2016/03/22 14:47:57 fischl Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_curvature_stats ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_curvature_stats.c,v 1.65 2015/06/04 20:50:51 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mris_calc ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mris_calc.c,v 1.54.2.1 2016/09/27 18:51:28 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> $Id: mri_robust_register.cpp,v 1.77 2016/01/20 23:36:17 greve Exp $</p><br /> <p>ProgramName: mri_robust_register.bin ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_robust_register.cpp,v 1.77 2016/01/20 23:36:17 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> $Id: mri_robust_template.cpp,v 1.54 2016/05/05 21:17:08 mreuter Exp $</p><br /> <p>ProgramName: mri_robust_template ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_robust_template.cpp,v 1.54 2016/05/05 21:17:08 mreuter Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_and ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_and.c,v 1.4 2011/03/02 00:04:13 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_or ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_or.c,v 1.5 2013/03/20 15:03:29 lzollei Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_fuse_segmentations ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_fuse_segmentations.c,v 1.8 2011/03/02 00:04:15 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_segstats ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_segstats.c,v 1.121 2016/05/31 17:27:11 greve Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> ProgramName: mri_relabel_hypointensities ProgramArguments: -all-info ProgramVersion: $Name: stable6 $ TimeStamp: 2019/03/11-00:13:29-GMT BuildTimeStamp: Oct 20 2017 13:59:15 CVS: $Id: mri_relabel_hypointensities.c,v 1.13 2015/05/15 18:44:10 nicks Exp $ User: root Machine: 3e5932778b80 Platform: Linux PlatformVersion: 4.15.0-46-generic CompilerName: GCC CompilerVersion: 40400<br><br /> #######################################<br><br /> GCADIR /opt/freesurfer/average<br><br /> GCA RB_all_2016-05-10.vc700.gca<br><br /> GCASkull RB_all_withskull_2016-05-10.vc700.gca<br><br /> AvgCurvTif folding.atlas.acfb40.noaparc.i12.2016-08-02.tif<br><br /> GCSDIR /opt/freesurfer/average<br><br /> GCS DKaparc.atlas.acfb40.noaparc.i12.2016-08-02.gcs<br><br /> #######################################<br><br /> -cw256 option is now persistent (remove with -clean-cw256)<br><br /> /out/out/freesurfer/sub-001</p><br /> <p>mri_convert /data/sub-001/ses-d1/anat/sub-001_ses-d1_T1w.nii.gz /out/out/freesurfer/sub-001/mri/orig/001.mgz</p><br /> <p>mri_convert.bin /data/sub-001/ses-d1/anat/sub-001_ses-d1_T1w.nii.gz /out/out/freesurfer/sub-001/mri/orig/001.mgz<br><br /> $Id: mri_convert.c,v 1.226 2016/02/26 16:15:24 mreuter Exp $<br><br /> reading from /data/sub-001/ses-d1/anat/sub-001_ses-d1_T1w.nii.gz…<br><br /> TR=1900.00, TE=0.00, TI=0.00, flip angle=0.00<br><br /> i_ras = (1, 1.94477e-16, -1.10357e-16)<br><br /> j_ras = (-2e-16, 0.998622, -0.0524728)<br><br /> k_ras = (1e-16, 0.0524728, 0.998622)<br><br /> writing to /out/out/freesurfer/sub-001/mri/orig/001.mgz…<br><br /> <span class="hashtag">#--------------------------------------------</span><br><br /> #@# MotionCor Mon Mar 11 00:13:41 UTC 2019<br><br /> Found 1 runs<br><br /> /out/out/freesurfer/sub-001/mri/orig/001.mgz<br><br /> Checking for (invalid) multi-frame inputs…<br><br /> WARNING: only one run found. This is OK, but motion<br><br /> correction cannot be performed on one run, so I’ll<br><br /> copy the run to rawavg and continue.</p><br /> <p>cp /out/out/freesurfer/sub-001/mri/orig/001.mgz /out/out/freesurfer/sub-001/mri/rawavg.mgz</p><br /> <p>/out/out/freesurfer/sub-001</p><br /> <p>mri_convert /out/out/freesurfer/sub-001/mri/rawavg.mgz /out/out/freesurfer/sub-001/mri/orig.mgz --conform_min</p><br /> <p>mri_convert.bin /out/out/freesurfer/sub-001/mri/rawavg.mgz /out/out/freesurfer/sub-001/mri/orig.mgz --conform_min<br><br /> $Id: mri_convert.c,v 1.226 2016/02/26 16:15:24 mreuter Exp $<br><br /> reading from /out/out/freesurfer/sub-001/mri/rawavg.mgz…<br><br /> TR=1900.00, TE=0.00, TI=0.00, flip angle=0.00<br><br /> i_ras = (1, 1.94477e-16, -1.10357e-16)<br><br /> j_ras = (-2e-16, 0.998622, -0.0524728)<br><br /> k_ras = (1e-16, 0.0524728, 0.998622)<br><br /> changing data type from float to uchar (noscale = 0)…<br><br /> MRIchangeType: Building histogram<br><br /> Reslicing using trilinear interpolation<br><br /> writing to /out/out/freesurfer/sub-001/mri/orig.mgz…</p><br /> <hr><br /> <p>ERROR! FOV=259.201 &gt; 256<br><br /> Include the flag -cw256 with recon-all!<br><br /> Inspect orig.mgz to ensure the head is fully visible.</p><br /> <hr><br /> <p>Linux 3e5932778b80 4.15.0-46-generic <span class="hashtag">#49-Ubuntu</span> SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux</p><br /> <p>recon-all -s sub-001 exited with ERRORS at Mon Mar 11 00:13:54 UTC 2019</p><br /> <p>To report a problem, see <a href="http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting" rel="nofollow noopener">http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting</a></p><br /> </blockquote> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 4:11:09 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9130"> <title>Siemens "Invert RO/PE polarity" detected by dcm2nii?</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9130</link> <description> <p>Don’t know the details about how dcm2niix accesses the information, but we use the “Invert RO/PE Polarity”-option in the CMRR sequences for our spin echo fieldmaps (Siemens Prisma). And dcm2niix detects this, that is, PhaseEncodingDirection comes out correctly in the associated .json.</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 4:05:33 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9131"> <title>Siemens "Invert RO/PE polarity" detected by dcm2nii?</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9131</link> <description> <p>Many thanks for looking into the documentation and code base, <a class="mention" href="/u/rwblair">@rwblair</a>. I am reassured that this is not something so obvious that I should have known about it already, and I will keep an eye out for it in our sequences going forward.</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 2:27:33 GMT</dc:date> </item> <item rdf:about="http://www.nitrc.org/forum/forum.php?forum_id=9132"> <title>GSoC Project Idea 6.2: Improve accessibility and interactivity for datasets in CATMAID</title> <link>http://www.nitrc.org/forum/forum.php?forum_id=9132</link> <description> <p>I might be able to help…how can I begin? I’ve the skillset which is required for this project</p> </description> <dc:subject>NeuroStars</dc:subject> <dc:creator>David Kennedy</dc:creator> <dc:date>Mon, 11 Mar 2019 1:50:13 GMT</dc:date> </item> </rdf:RDF>