<?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=1049" ?>
<?xml-stylesheet type="text/css" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.css" ?>
<rss version="2.0"> <channel>
  <title>NITRC Camino Forum: help</title>
  <link>http://www.nitrc.org/forum/forum.php?forum_id=1049</link>
  <description>Get Public Help</description>
  <language>en-us</language>
  <copyright>Copyright 2000-2026 NITRC OSI</copyright>
  <webMaster></webMaster>
  <lastBuildDate>Thu, 14 May 2026 9:40:33 GMT</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>NITRC RSS generator</generator>
  <item>
   <title>procstreamlines problem - too many seeds</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4685&amp;forum_id=1049</link>
   <description>Hi,&lt;br /&gt;
&lt;br /&gt;
So I have converted a trk file (around 889419 tracts) into Bfloat using camino-trackvis and am trying to create connectivity matrix which ends up with a lot of 0s in the excel file and in the matrix itself, which I know is not correct especially since I have also done tracking with camino and then repeated the connectivity matrix.&lt;br /&gt;
When I run procstreamliens on the converted trk file (so the new Bfloat) somehow it sees 1334780 seeds which is substantially more than it's supposed to be and so the processing stops and there is a communication:&lt;br /&gt;
&lt;br /&gt;
Processing ROI 1 of 1&lt;br /&gt;
&lt;br /&gt;
Processing seed 889419 of 1334780Jul 22, 2014 5:10:39 PM misc.LoggedException logException&lt;br /&gt;
SEVERE: Exception in thread &amp;quot;main&amp;quot; class misc.LoggedException: No more tracts in input after processing seed 889419 of 1334780&lt;br /&gt;
at apps.ProcessStreamlines.execute(ProcessStreamlines.java:1060)&lt;br /&gt;
at apps.EntryPoint.main(EntryPoint.java:284)&lt;br /&gt;
Exception in thread &amp;quot;main&amp;quot; misc.LoggedException: No more tracts in input after processing seed 889419 of 1334780&lt;br /&gt;
at apps.ProcessStreamlines.execute(ProcessStreamlines.java:1060)&lt;br /&gt;
at apps.EntryPoint.main(EntryPoint.java:284)&lt;br /&gt;
&lt;br /&gt;
Does anyone have any idea why this happens and how do I fix this?&lt;br /&gt;
&lt;br /&gt;
Thanks for the help in advance,&lt;br /&gt;
&lt;br /&gt;
Joanna</description>
   <author>Joanna Goc</author>
   <pubDate>Tue, 22 Jul 2014 15:32:42 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4685&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>ActiveAx / impose fiber direction</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4495&amp;forum_id=1049</link>
   <description>Hi,&lt;br /&gt;
&lt;br /&gt;
I want to use the mmwmdinvivo model to fit my data. Those were taken in the spinal cord with diffusion directions perpendicular to the spine (XY plane). &lt;br /&gt;
I think the model should work on my data if I impose the fiber direction. Is there an option or can I impose theta and phi to 0 in the code?&lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
Tanguy</description>
   <author>Tanguy DUVAL</author>
   <pubDate>Sat, 03 May 2014 0:42:13 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4495&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>RE: recommended tensor models for 1, 2, 3 tensors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</link>
   <description>Huh... so that is interesting.&lt;br /&gt;
&lt;br /&gt;
Let me ask you this then - our acquisition protocol has an additional, 6-direction b=500 series (on top of the 60-direction b=1000) with reverse phase-encode for unwarping.&lt;br /&gt;
&lt;br /&gt;
So far I am using only the b=0 image of that series (for said unwarping), but would it be a genuine gain for the multi-tensor fit to add the b=500 images into the recon also? &lt;br /&gt;
&lt;br /&gt;
Or would we need moree than 6 directions on the second shell also to get any benefit?&lt;br /&gt;
&lt;br /&gt;
Thanks Phil!&lt;br /&gt;
&lt;br /&gt;
Torsten</description>
   <author>Torsten Rohlfing</author>
   <pubDate>Thu, 14 Nov 2013 1:28:32 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>RE: recommended tensor models for 1, 2, 3 tensors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</link>
   <description>I think your strategy is sensible. FA will be underestimated by the single-tensor model, but MD might be more stable.&lt;br /&gt;
&lt;br /&gt;
With a single shell of DWI, there's no unique solution to the multi-tensor parameters:&lt;br /&gt;
&lt;br /&gt;
http://crl.med.harvard.edu/publications/Scherrer_ISBI2010.pdf</description>
   <author>Philip Cook</author>
   <pubDate>Wed, 13 Nov 2013 21:09:54 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>RE: recommended tensor models for 1, 2, 3 tensors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</link>
   <description>[color=#000000]So I am going to partly answer myself here...&lt;br /&gt;
[/color][i] [/i]&lt;br /&gt;
&lt;br /&gt;
Turns out I overlooked the need to tell &amp;quot;track&amp;quot; the fact that it's multi-tensor data, as well as the maximum number of components, and now things are making more sense.&lt;br /&gt;
&lt;br /&gt;
Sorry for the noise.&lt;br /&gt;
&lt;br /&gt;
[i]Originally posted by Torsten Rohlfing:[/i][quote]&lt;br /&gt;
These seem to produce a lot of fibers for 1-tensor field, fewer for 2 tensors, and fewer yet for 3 tensors[/quote]</description>
   <author>Torsten Rohlfing</author>
   <pubDate>Tue, 29 Oct 2013 4:04:25 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>RE: recommended tensor models for 1, 2, 3 tensors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</link>
   <description>And a follow-up question:&lt;br /&gt;
&lt;br /&gt;
Would you suggest different &amp;quot;track&amp;quot; parameters for the 1, 2, and 3-tensor fields?&lt;br /&gt;
&lt;br /&gt;
I am currently playing with the following:&lt;br /&gt;
&lt;br /&gt;
 -curvethresh 60 -anisthresh 0.1&lt;br /&gt;
&lt;br /&gt;
These seem to produce a lot of fibers for 1-tensor field, fewer for 2 tensors, and fewer yet for 3 tensors.&lt;br /&gt;
&lt;br /&gt;
Would this be expected?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
Torsten</description>
   <author>Torsten Rohlfing</author>
   <pubDate>Mon, 28 Oct 2013 19:35:43 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>recommended tensor models for 1, 2, 3 tensors</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</link>
   <description>Hi Guys:&lt;br /&gt;
&lt;br /&gt;
I was wondering if you could provide some guidance on good choices for tensor models using 1, 2, 3 tensors with the goal of fiber tracking.&lt;br /&gt;
&lt;br /&gt;
We are using a 60-direction, b=1000 (plus 2 b=0) acquisition scheme, 2.5mm isotropic voxels.&lt;br /&gt;
&lt;br /&gt;
My intuitive choices for tensor reconstruction (i.e., using modelfit) are these:&lt;br /&gt;
&lt;br /&gt;
1 tensor - nldt_pos&lt;br /&gt;
2 tensors - pospos&lt;br /&gt;
3 tensors - pospospos&lt;br /&gt;
&lt;br /&gt;
Is there anything obviously wrong or suboptimal with these choices?&lt;br /&gt;
&lt;br /&gt;
Also, having had little luck with the FA/MD etc. maps derived from multi-tensor fields in the past, I was planning to use the multi-tensor fields for fiber tracking, but then evaluate measures such as FA along the fibers based on the single-tensor FA map (analogous for MD, L1, LT).&lt;br /&gt;
&lt;br /&gt;
Do you have any words of caution regarding this plan also?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
Torsten</description>
   <author>Torsten Rohlfing</author>
   <pubDate>Mon, 28 Oct 2013 18:29:50 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4142&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>Definition of Colour Code </title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4064&amp;forum_id=1049</link>
   <description>Hi,&lt;br /&gt;
I need the definition of the colour code which is used in Camino to show the directions of the Eigenvectors. I think it might be the same definition which is also used in ColFa images and Fibretracks. Can somebody tell me where i can find it? I'd appreciate that.&lt;br /&gt;
&lt;br /&gt;
greets&lt;br /&gt;
&lt;br /&gt;
Olivier</description>
   <author>Olivier  Tannert</author>
   <pubDate>Wed, 28 Aug 2013 12:21:07 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4064&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>How to get numerical eigenvectors?</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4037&amp;forum_id=1049</link>
   <description>Hey,&lt;br /&gt;
I need to get numerical eigenvectors of a DTI studi processed with camino. I already managed to get the .Bdouble file of the principle eigenvector but as far as I understand the tutorial this file is good for producing images with mathlab, but not for getting the real eigenvectors in every voxel. Has anyone an idea how that could be managed?&lt;br /&gt;
&lt;br /&gt;
a fast answer would be apreciated&lt;br /&gt;
&lt;br /&gt;
thanks&lt;br /&gt;
&lt;br /&gt;
Olivier</description>
   <author>Olivier  Tannert</author>
   <pubDate>Thu, 01 Aug 2013 15:48:57 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4037&amp;forum_id=1049</guid>
  </item>
  <item>
   <title>visualization of fiber clustering result</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=3688&amp;forum_id=1049</link>
   <description>hi,&lt;br /&gt;
&lt;br /&gt;
I run a clustering algorithm on tracts I got from &amp;quot;tract&amp;quot; command and have a cluster id for each individual tract. I want to visualize them in paraview or something similar by colouring according to their cluster ids (a single colour for each id). How can I do that? &lt;br /&gt;
&lt;br /&gt;
vtkstreamlines asks for a scalar file which makes it really hard.</description>
   <author>Birkan Tunc</author>
   <pubDate>Wed, 21 Nov 2012 18:25:54 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=3688&amp;forum_id=1049</guid>
  </item>
 </channel>
</rss>
