<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://stage.nitrcce.org/themes/nitrc3.0/css/rss.xsl.php?feed=https://stage.nitrcce.org/export/rss20_forum.php?forum_id=1278" ?>
<?xml-stylesheet type="text/css" href="https://stage.nitrcce.org/themes/nitrc3.0/css/rss.css" ?>
<rss version="2.0"> <channel>
  <title>NITRC BrainVoyager Forum: open-discussion</title>
  <link>http://stage.nitrcce.org/forum/forum.php?forum_id=1278</link>
  <description>General Discussion</description>
  <language>en-us</language>
  <copyright>Copyright 2000-2026 NITRC OSI</copyright>
  <webMaster></webMaster>
  <lastBuildDate>Tue, 07 Apr 2026 19:50:50 GMT</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>NITRC RSS generator</generator>
  <item>
   <title>RE: Brainvoyager is usable</title>
   <link>http://stage.nitrcce.org/forum/forum.php?thread_id=1236&amp;forum_id=1278</link>
   <description>NITRC is agnostic with respect to commercial or non-commercial&lt;br /&gt;
resources for neuroimaging; NITRC's mission is to help the community&lt;br /&gt;
find ALL options available to them. All resources at NITRC are, in&lt;br /&gt;
some sense, 'advertising' themselves, and that is exactly appropriate. &lt;br /&gt;
All resources are treated equally with respect to the bandwidth, disk&lt;br /&gt;
space and other resources that is available to them at NITRC; and at&lt;br /&gt;
this time, no project (commercial or non-commercial; well-funded or&lt;br /&gt;
not funded) is abusing that infrastructure.&lt;br /&gt;
&lt;br /&gt;
While resources with commercial licenses may pose an additional factor&lt;br /&gt;
in execution of inter-resource comparison, it is only one of many&lt;br /&gt;
factors that make proper, valid and useful comparisons between&lt;br /&gt;
resources challenging. That said, I have every confidence in the&lt;br /&gt;
neuroimaging community, that through direct or indirect collaboration&lt;br /&gt;
and teamwork, the potential benefits of commercial products can be&lt;br /&gt;
directly compared to their non-commercial counterparts.&lt;br /&gt;
&lt;br /&gt;
In fact, just by listing with NITRC makes each resource more 'findable' &lt;br /&gt;
(with respect to the features that are offered) and 'comparable' (with &lt;br /&gt;
respect to other resources offering similar functionality). This promotes &lt;br /&gt;
comparison and cost benefit assessment, and hence moves the overall field &lt;br /&gt;
forward.&lt;br /&gt;
&lt;br /&gt;
[Note, as this thread is more NITRC-specific, as opposed to &lt;br /&gt;
BrainVoyager-specific, further community conversation on this point &lt;br /&gt;
is encouraged, but better suited to the NITRC open-discussion forum: &lt;br /&gt;
http://www.nitrc.org/forum/forum.php?forum_id=2]</description>
   <author>David Kennedy</author>
   <pubDate>Fri, 07 May 2010 14:15:39 GMT</pubDate>
   <guid>http://stage.nitrcce.org/forum/forum.php?thread_id=1236&amp;forum_id=1278</guid>
  </item>
  <item>
   <title>Brainvoyager is unusable</title>
   <link>http://stage.nitrcce.org/forum/forum.php?thread_id=1236&amp;forum_id=1278</link>
   <description>These packages are useless without a license (cannot be compared against other tools).  I'm assuming this means Brain Innovation B.V. is using NITRC to advertise it's product as well as to free up costly bandwidth on their own servers by utilizing free bandwidth on NITRC, something NITRC was not created for.  Does anyone else feel this way?</description>
   <author>Nick Jones</author>
   <pubDate>Mon, 14 Dec 2009 21:25:30 GMT</pubDate>
   <guid>http://stage.nitrcce.org/forum/forum.php?thread_id=1236&amp;forum_id=1278</guid>
  </item>
  <item>
   <title>Welcome to Open-Discussion</title>
   <link>http://stage.nitrcce.org/forum/forum.php?thread_id=1213&amp;forum_id=1278</link>
   <description>Welcome to Open-Discussion</description>
   <author>Christian Haselgrove</author>
   <pubDate>Wed, 09 Dec 2009 16:55:25 GMT</pubDate>
   <guid>http://stage.nitrcce.org/forum/forum.php?thread_id=1213&amp;forum_id=1278</guid>
  </item>
 </channel>
</rss>
