<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.xsl.php?feed=https://www.nitrc.org/export/rss20_forum.php?forum_id=1456" ?>
<?xml-stylesheet type="text/css" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.css" ?>
<rss version="2.0"> <channel>
  <title>NITRC PESTICA & SLOMOCO: physio and motion correction tools Forum: open-discussion</title>
  <link>http://www.nitrc.org/forum/forum.php?forum_id=1456</link>
  <description>General Discussion</description>
  <language>en-us</language>
  <copyright>Copyright 2000-2026 NITRC OSI</copyright>
  <webMaster></webMaster>
  <lastBuildDate>Tue, 07 Apr 2026 12:48:07 GMT</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>NITRC RSS generator</generator>
  <item>
   <title>Coregistration to MNI-template - adjusted FOV</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=13550&amp;forum_id=1456</link>
   <description>Dear Pestica-community,&lt;br /&gt;
&lt;br /&gt;
I had a problems regarding the coregistration of my EPI to the MNI-template recently when using PESTICA, version 5. The Pestica [url=https://www.nitrc.org/frs/download.php/4774/pestica_tutorial_v2.pdf]tutorial[/url] (version 2, pages 22 and 23) states that one should check the coregistration to MNI EPI template while making &amp;quot;sure resp_PESTICA.nii and card_PESTICA.nii line up over your data&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
I have worked on two different datasets run within the same patients and MRI run: &lt;br /&gt;
1) EPI of wholebrain in low resolution (3*3*3mm) and &lt;br /&gt;
2) EPI of reduced FOV covering only the brainstem. &lt;br /&gt;
&lt;br /&gt;
When checking the coregistration of dataset 1) in fsleyes, everything looks fine. However, dataset 2) with the reduced FOV seems not aligned that well, even though my final results look promising. So, I was wondering how Pestica uses card_PESTICA and resp_PESTICA in further processing and whether I could/should change something in the script to fix this (for example adding 3dAllineate as suggested in [url=https://www.nitrc.org/forum/forum.php?thread_id=4107&amp;amp;forum_id=1456]this [/url]post).&lt;br /&gt;
&lt;br /&gt;
Best, Melissa Thalhammer</description>
   <author>mthalhammer</author>
   <pubDate>Tue, 07 Jun 2022 6:40:57 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=13550&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>RE: Ubuntu Update causing errors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=10118&amp;forum_id=1456</link>
   <description>Hi!&lt;br /&gt;
&lt;br /&gt;
I realize this was posted quite a while ago, but right now I'm encountering the exact same problem with SLOMOCO (using a Mac, OSX Big Sur 11.1). Has anybody found a solution to this problem by now?&lt;br /&gt;
&lt;br /&gt;
Any help would be appreciated :)&lt;br /&gt;
&lt;br /&gt;
Thanks!</description>
   <author>Marlene Tahedl</author>
   <pubDate>Wed, 08 Dec 2021 21:17:35 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=10118&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>RE: afni_matlab problem</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=3866&amp;forum_id=1456</link>
   <description>I had the same problem after upgrading to MATLAB 2021b. This trick solved the problem. Thanks a lot!</description>
   <author>Marlene Tahedl</author>
   <pubDate>Wed, 08 Dec 2021 18:04:39 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=3866&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>Lacking A TAXIS OFFSET</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=10712&amp;forum_id=1456</link>
   <description>Hello,&lt;br /&gt;
&lt;br /&gt;
I just downloaded this program. I am trying to run a BOLD scan through this, but it turns out, in BrickInfo.m, when I try to display BRIKinfo, there is no TAXIS_OFFSETS section for the program to grab and store. This is causing the program to crash. Is there anything that I can do?&lt;br /&gt;
&lt;br /&gt;
Best regards,&lt;br /&gt;
Jimi</description>
   <author>hmri</author>
   <pubDate>Thu, 14 Nov 2019 17:34:59 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=10712&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>Multi-band acceleration factor</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=10488&amp;forum_id=1456</link>
   <description>Hi all,&lt;br /&gt;
&lt;br /&gt;
I was wondering if the slice_timing matlab functions also take into account the multi-band acceleration factor?&lt;br /&gt;
&lt;br /&gt;
Many thanks &lt;br /&gt;
&lt;br /&gt;
David</description>
   <author>davidb</author>
   <pubDate>Tue, 20 Aug 2019 9:29:05 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=10488&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>RE: a tip for matlab error in csh/tcsh envirn</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=8210&amp;forum_id=1456</link>
   <description>[color=#000000]Hi,[/color]&lt;br /&gt;
&lt;br /&gt;
Would it be possible to know what exactly should be added to the setup_pestica.sh file without modifying the .bashrc file so that the program can use matlab?&lt;br /&gt;
&lt;br /&gt;
Many thanks for your help&lt;br /&gt;
&lt;br /&gt;
Best&lt;br /&gt;
&lt;br /&gt;
David&lt;br /&gt;
&lt;br /&gt;
[i]Originally posted by Wanyong Shin:[/i][quote][color=#000000]Thanks, Hang Joon.[/color]&lt;br /&gt;
&lt;br /&gt;
[color=#000000]You can modify setup_pestica.sh to modify path and &amp;quot;MATLABLINE&amp;quot; [/color]&lt;br /&gt;
&lt;br /&gt;
-Wanyong&lt;br /&gt;
&lt;br /&gt;
[i]Originally posted by Hang Joon Jo:[/i][quote]I have no idea whether it's discussed before.&lt;br /&gt;
&lt;br /&gt;
If you run pestica in csh/tcsh environment, &amp;quot;no matlab command&amp;quot; error might be shown up in particular systems.&lt;br /&gt;
&lt;br /&gt;
I found a workaround in that case - &amp;quot;Add matlab path and alias in .bashrc&amp;quot; even you don't use bash. In my case:&lt;br /&gt;
&lt;br /&gt;
export PATH=$PATH:/Applications/MATLAB_R2015a.app/bin&lt;br /&gt;
alias matlab='/Applications/MATLAB_R2015a.app/bin/matlab -nodesktop'&lt;br /&gt;
&lt;br /&gt;
Hope this help.&lt;br /&gt;
&lt;br /&gt;
- H[/quote][/quote]</description>
   <author>davidb</author>
   <pubDate>Wed, 19 Jun 2019 11:38:02 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=8210&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>Ubuntu Update causing errors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=10118&amp;forum_id=1456</link>
   <description>Hello,&lt;br /&gt;
&lt;br /&gt;
I recently updated ubuntu to 18.04.2.&lt;br /&gt;
&lt;br /&gt;
Since doing this I've been receiving 3drefit errors while using slicemoco_newalgorithm.sh. Specifically, the error reads:&lt;br /&gt;
&lt;br /&gt;
mri_read_ascii: couldn't open file 242 31 77002 -999 -999 -999 -999 -999&lt;br /&gt;
&lt;br /&gt;
I've attached the full output in a text file.&lt;br /&gt;
&lt;br /&gt;
Has anyone run into a similar problem?&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
   <author>David Cunningham</author>
   <pubDate>Wed, 03 Apr 2019 15:41:21 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=10118&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>a tip for background intensity correction after pestica</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=9993&amp;forum_id=1456</link>
   <description>Hi Folks,&lt;br /&gt;
&lt;br /&gt;
PESTICA processes could increase the background intensity, and there might be a trouble to perform further processes (i.e. getting a wrong brain mask from the output irfretroicor file during afni_proc.py process).&lt;br /&gt;
&lt;br /&gt;
Few AFNI command lines can correct the background intensity problem:&lt;br /&gt;
&lt;br /&gt;
# pick the time course intensities at voxel index 1 1 1&lt;br /&gt;
3dmaskdump -quiet -noijk -ibox 1 1 1 [output irfretroicor file here]+orig. &gt; temp.1D&lt;br /&gt;
# sort the intensities&lt;br /&gt;
1dTsort temp.1D\' &gt; tempsort.1D&lt;br /&gt;
&lt;br /&gt;
# For tcsh, get the minimum number of background, but mostly identical to each other.&lt;br /&gt;
set mm = '1dcat tempsort.1D'{0}''&lt;br /&gt;
&lt;br /&gt;
# subtract the minimum background intensity across time points&lt;br /&gt;
3dcalc -a pb01.irfretroicor+orig. -expr 'a-'${mm}'' -prefix irfretroicor_bg_fix&lt;br /&gt;
&lt;br /&gt;
I hope this helps.&lt;br /&gt;
&lt;br /&gt;
H</description>
   <author>Hang Joon Jo</author>
   <pubDate>Thu, 14 Feb 2019 6:05:56 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=9993&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>sharing a solution to fixing errors running slomoco</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=9182&amp;forum_id=1456</link>
   <description>I recently started using pestica4 and kept getting errors running slicemoco_newalgorithm.sh. After some inspections I fixed it, and want to share with other uses. &lt;br /&gt;
&lt;br /&gt;
So after typing slicemoco_newalgorithm.sh -d , I got errors below during secondorder motor correction:&lt;br /&gt;
&lt;br /&gt;
----------------------------------------------------&lt;br /&gt;
----------------------------------------------------&lt;br /&gt;
finished slicewise in-plane motion correction&lt;br /&gt;
&lt;br /&gt;
Exiting&lt;br /&gt;
Running Secondorder Motion Correction using SLOMOCO output&lt;br /&gt;
matlab -nodesktop -nosplash  addpath /Users/yuqiliu/Downloads/pestica4/slomoco; addpath /Users/yuqiliu/Downloads/pestica4/afni_matlab; addpath /Users/yuqiliu/Downloads/pestica4/pestica_matlab; slicemoco_newalgorithm_input('tactile_run1.slicemocoxy_afni+orig','tactile_run1.brain+orig','tempslmoco_volslc_alg_vol_tactile_run1.slicemocoxy_afni/motion.wholevol_zt'); exit;&lt;br /&gt;
&amp;lt; M A T L A B (R) &amp;gt;&lt;br /&gt;
Copyright 1984-2016 The MathWorks, Inc.&lt;br /&gt;
R2016b (9.1.0.441655) 64-bit (maci64)&lt;br /&gt;
September 7, 2016&lt;br /&gt;
To get started, type one of these: helpwin, helpdesk, or demo.&lt;br /&gt;
For product information, visit www.mathworks.com.&lt;br /&gt;
&amp;gt;&amp;gt; Note: SMS acquisition is applied (MB acc. fac = 6).&lt;br /&gt;
[color=#ff0000]Output argument &amp;quot;tranmat_zt&amp;quot; (and maybe others) not assigned during call to[/color]&lt;br /&gt;
[color=#ff0000]&amp;quot;convert_1dmat_into_tranmatarray&amp;quot;.[/color]&lt;br /&gt;
[color=#ff0000]Error in slicemoco_newalgorithm_input (line 25)[/color]&lt;br /&gt;
[color=#ff0000]tranmat_zt = convert_1dmat_into_tranmatarray(transmat1d_zt);% tranmat_zt =[/color]&lt;br /&gt;
[color=#ff0000]reshape(tranmat_zt,[zmbdim tdim 3 4]); % (v1) debugged[/color]&lt;br /&gt;
&lt;br /&gt;
-----------------------------------------------------------------------------------------------&lt;br /&gt;
-----------------------------------------------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
I went back to functions involved in the error message and figured it the problem was due to the command [b]gawk[/b] not found. Installing gawk solved my problem. &lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
Yuqi</description>
   <author>Yuqi Liu</author>
   <pubDate>Thu, 12 Apr 2018 17:31:11 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=9182&amp;forum_id=1456</guid>
  </item>
  <item>
   <title>&amp;quot;out of memory&amp;quot; issue running pestica4</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=9167&amp;forum_id=1456</link>
   <description>Hi all,&lt;br /&gt;
&lt;br /&gt;
  This is a relatively general question and I am wondering if any one has any suggestions. I am implementing pestica4 on an Ubuntu 16.04 system, and I got an error in Stage 3 of run_pestica.sh:&lt;br /&gt;
&lt;br /&gt;
Running Stage 3: Filtering PESTICA estimators, cardiac first, then respiratory&lt;br /&gt;
&lt;br /&gt;
........(omitted)&lt;br /&gt;
&lt;br /&gt;
Range of typical human cardiac rate: 62+-8bpm (range 48-85)&lt;br /&gt;
use a buffer of at least 20bpm around the peaks you like for cardiac&lt;br /&gt;
*************************************************************&lt;br /&gt;
*************************************************************&lt;br /&gt;
[color=#ff0000][b]Error using fread[/b][/color]&lt;br /&gt;
[color=#ff0000][b]Out of memory. Type HELP MEMORY for your options.[/b][/color]&lt;br /&gt;
Error in BrikLoad (line 651)&lt;br /&gt;
V = fread(fidBRIK, (Info.DATASET_DIMENSIONS(1) .* Info.DATASET_DIMENSIONS(2) .*&lt;br /&gt;
Info.DATASET_DIMENSIONS(3) .* Info.DATASET_RANK(2)) , [Opt.OutPrecision,typestr]);&lt;br /&gt;
Error in view_and_correct_estimator (line 5)&lt;br /&gt;
[err, ima, ainfo, ErrMessage]=BrikLoad(ep2d_filename, Opt);&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  Has anyone had similar issues and any suggestions on how to work this around?&lt;br /&gt;
&lt;br /&gt;
Thank you!&lt;br /&gt;
Yuqi</description>
   <author>Yuqi Liu</author>
   <pubDate>Sat, 07 Apr 2018 15:49:34 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=9167&amp;forum_id=1456</guid>
  </item>
 </channel>
</rss>
