<?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=945" ?>
<?xml-stylesheet type="text/css" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.css" ?>
<rss version="2.0"> <channel>
  <title>NITRC JIST: Java Image Science Toolkit Forum: open-discussion</title>
  <link>http://www.nitrc.org/forum/forum.php?forum_id=945</link>
  <description>General Discussion</description>
  <language>en-us</language>
  <copyright>Copyright 2000-2026 NITRC OSI</copyright>
  <webMaster></webMaster>
  <lastBuildDate>Wed, 15 Apr 2026 6:45:07 GMT</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>NITRC RSS generator</generator>
  <item>
   <title>one bracket too many?</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=8416&amp;forum_id=945</link>
   <description>Dear Andrew Plassard et al,&lt;br /&gt;
&lt;br /&gt;
I just installed py-jist (which has been a lifesaver!) on a new machine. I got the same message when running setup.py and JIST-run tests:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: pre;&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt;[color=#808080]File &amp;quot;/Users/emmasprooten/Library/Python/2.7/lib/python/site-packages/PyJIST/PyJIST.py&amp;quot;, line 155[/color]&lt;br /&gt;
[color=#808080]&amp;lt;span style=&amp;quot;white-space: pre;&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt;[/color]os.system(full_cmd))&lt;br /&gt;
[color=#808080]&amp;lt;span style=&amp;quot;white-space: pre;&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt;[/color]^&lt;br /&gt;
[color=#808080]&amp;lt;span style=&amp;quot;white-space: pre;&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt;[/color]SyntaxError: invalid syntax&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;white-space: pre;&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt;Based on this I removed the last bracket on line 155 in setup.py: os.system(full_cmd)[b])[/b]&lt;br /&gt;
&lt;br /&gt;
Now it all runs fine. Not sure if this little bracket was added recently but I thought it's worth sharing my experience. &lt;br /&gt;
&lt;br /&gt;
Emma</description>
   <author>Emma Sprooten</author>
   <pubDate>Fri, 25 Aug 2017 14:19:04 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=8416&amp;forum_id=945</guid>
  </item>
  <item>
   <title>The layout file does not work.</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=6561&amp;forum_id=945</link>
   <description>The layout included in the DTI tutorial does not work as described in the tutorial.&lt;br /&gt;
When the layout was called JIST console was idling without further activity. &lt;br /&gt;
It simply does not react. No error or warning message at all. &lt;br /&gt;
My system is CentOS 6.7 with Mipav (7.3) and a recent nightly version of JIST-CRUISE.</description>
   <author>Seongjin Choi</author>
   <pubDate>Thu, 25 Feb 2016 20:30:31 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=6561&amp;forum_id=945</guid>
  </item>
  <item>
   <title>Announcement: PyJIST</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4447&amp;forum_id=945</link>
   <description>We are pleased to announce the first release of PyJIST.&lt;br /&gt;
&lt;br /&gt;
PyJIST is Python-based wrapper for accessing the JIST command line interface (CLI) without the hassle of constructing complicated classpaths and memorizing long module definitions.&lt;br /&gt;
&lt;br /&gt;
It's pretty cool. You should try it. See the link below for the installation instructions and common use cases.&lt;br /&gt;
&lt;br /&gt;
https://www.nitrc.org/plugins/mwiki/index.php/jist:PyJIST</description>
   <author>Andrew Asman</author>
   <pubDate>Sun, 06 Apr 2014 20:28:32 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4447&amp;forum_id=945</guid>
  </item>
  <item>
   <title>JIST installed as JAR</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=4259&amp;forum_id=945</link>
   <description>Using a nightly build of MIPAV and JIST 3.0, you can install JIST by placing the JIST jar in the MIPAV plugin directory (this is the /mipav/plugins directory in your user folder).  This speeds up the installation process of JIST.&lt;br /&gt;
&lt;br /&gt;
-Justin</description>
   <author>Justin  Senseney</author>
   <pubDate>Mon, 23 Dec 2013 15:24:10 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=4259&amp;forum_id=945</guid>
  </item>
  <item>
   <title>New JIST Modules: T1 mapping</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=1307&amp;forum_id=945</link>
   <description>Hi all!&lt;br /&gt;
&lt;br /&gt;
I'd like to introduce two new JIST modules, and a supporting algorithm:&lt;br /&gt;
-plugins.quantitative.UnshuffleT1MappingVolumes&lt;br /&gt;
-plugins.quantitative.T1Mapping_SliceShift&lt;br /&gt;
-algorithms.quantitative.T1Fitting&lt;br /&gt;
&lt;br /&gt;
Although this slice-shift technique is rather specialized, the T1 fitting might appeal to a wider audience, so I thought to share it with all.&lt;br /&gt;
&lt;br /&gt;
This set of modules allows for post-processing of a quantitative T1 sequence using the slice-shift technique. By 'sharing' a global inversion pulse a volume of ~50 slices are acquired at different times. Next repetition, the order in which these slices are acquired is shifted, and in ~25 repetitions all slices are measured at 25 different time points.&lt;br /&gt;
The result is a relatively quick method to acquire 20-30 time points to fit a T1 value to, which allows for high quality T1 fitting. The disadvantage of this slice-shifting is that the slices need to be re-ordered before fitting can be done.&lt;br /&gt;
&lt;br /&gt;
These modules allow for automatic reordering of slices, based on our current implementation of the slice-shift technique (over the dynamics), and the slice-ordering of the sequence (interleaved/ascending/descending) (over one volume).&lt;br /&gt;
&lt;br /&gt;
The second module, responsible for the actual T1 fitting, is an implementation of the Levenberg-Marquardt optimizer. The optimization was -drastically- sped up by using the analytical solutions for the 1st and 2nd derivatives of the function to be optimized (with thanks to Mathematica). Of course this wont work for all functions and applications, but it increased the processing speed from 455 to roughly 7500 voxels per minute. I am in no way a real programmer however, and I am sure there are many more steps that can be taken to optimize this code.&lt;br /&gt;
&lt;br /&gt;
While I think I did a reasonable job at annotating the code and explaining the modules in the description fields, I will have a stab at writing a small manual for the Wiki. Not sure when that will be finished though.&lt;br /&gt;
&lt;br /&gt;
I look forward to getting some feedback, or even -gasp- user questions!&lt;br /&gt;
&lt;br /&gt;
kind regards,&lt;br /&gt;
Daniel&lt;br /&gt;
</description>
   <author>dpolders</author>
   <pubDate>Wed, 03 Mar 2010 15:57:50 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=1307&amp;forum_id=945</guid>
  </item>
  <item>
   <title>Welcome to Open-Discussion</title>
   <link>http://www.nitrc.org/forum/forum.php?thread_id=922&amp;forum_id=945</link>
   <description>Welcome to Open-Discussion</description>
   <author>Christian Haselgrove</author>
   <pubDate>Tue, 02 Jun 2009 23:13:02 GMT</pubDate>
   <guid>http://www.nitrc.org/forum/forum.php?thread_id=922&amp;forum_id=945</guid>
  </item>
 </channel>
</rss>
