<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BIRN - Biomedical Informatics Research Network &#187; Tools</title>
	<atom:link href="http://www.birncommunity.org/category/tools-catalog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.birncommunity.org</link>
	<description>The Conduit for Biomedical Research</description>
	<lastBuildDate>Tue, 06 Dec 2011 22:59:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Globus Clients</title>
		<link>http://www.birncommunity.org/tools-catalog/globus-clients/</link>
		<comments>http://www.birncommunity.org/tools-catalog/globus-clients/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 21:22:26 +0000</pubDate>
		<dc:creator>cwilliams</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Collaboration Services]]></category>

		<guid isPermaLink="false">http://www.birncommunity.org/?p=1218</guid>
		<description><![CDATA[The Globus clients software provides MyProxy, GSI security, GridFTP, UberFTP, and RLS client software that enables users and applications to interact with BIRN operated MyProxy, GridFTP, and RLS servers.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>The Globus clients software provides MyProxy, GSI security, GridFTP, UberFTP, and RLS client software that enables users and applications to interact with BIRN operated MyProxy, GridFTP, and RLS servers.</p>
<p>Instructions for BIRN users on how to install the Globus client software are here:<br />
<a href="https://xwiki.nbirn.org:8443/bin/view/BIRNCC+Software/Command%2Dline+Tools+Documentation">https://xwiki.nbirn.org:8443/bin/view/BIRNCC+Software/Command%2Dline+Tools+Documentation</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/globus-clients/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Federated Informatics Research Environment (FIRE)</title>
		<link>http://www.birncommunity.org/tools-catalog/fire/</link>
		<comments>http://www.birncommunity.org/tools-catalog/fire/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 00:04:23 +0000</pubDate>
		<dc:creator>liv</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[Data Sharing & Collaboration]]></category>
		<category><![CDATA[functionBIRN]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=890</guid>
		<description><![CDATA[FIRE (coming in 2010) is an integrated suite of tools to put your data on a gridFTP set of servers, link it to a database which is automatically federated, to be able to retrieve it from multiple sites, with the data wrapped in XCEDE (XML) wrappers. ]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>Federated Informatics Research Environment (FIRE) is an integrated suite of tools to put your data on a GridFTP set of servers, link it to a database which is automatically federated, to be able to retrieve it from multiple sites, with the data wrapped in XCEDE (XML) wrappers. It’s built based on functional and structural neuroimaging, but if you have other data types, you don’t have to start from scratch figuring everything out. These tools are built to generalize to other formats and study designs.</p>
<p>See the <a href="/resources/tools/fire-primer/">FIRE Primer</a> for more information on the suite of tools, both current and coming.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/fire/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GAMA</title>
		<link>http://www.birncommunity.org/tools-catalog/gama/</link>
		<comments>http://www.birncommunity.org/tools-catalog/gama/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 17:28:32 +0000</pubDate>
		<dc:creator>ranantha</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=774</guid>
		<description><![CDATA[Grid Account Management Architecture, GAMA, provides an end-to-end security infrastructure suitable for multi-institution collaborations with support for grid computing, cloud computing, and web portals.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>Grid Account Management Architecture, GAMA, provides an end-to-end security infrastructure suitable for multi-institution collaborations with support for grid computing, cloud computing, and web portals. It makes grid portals easy to use, but maintains the security and delegation capabilities of GSI. GAMA consists of two components, a backend security service that provides secure management of credentials, and a front-end set of portlets that provide tight integration into web/grid portals.</p>
<p>The BIRN CC operates this tool for the BIRN community; however, BIRN does not package it for community download. This tool is available publicly here: <a href="http://code.google.com/p/gamav2/">http://code.google.com/p/gamav2/</a></p>
<p>For questions about the use of GAMA in BIRN, contact Rachana Ananthakrishnan (ranantha at mcs.anl.gov).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/gama/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MyProxy</title>
		<link>http://www.birncommunity.org/tools-catalog/myproxy/</link>
		<comments>http://www.birncommunity.org/tools-catalog/myproxy/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 17:02:05 +0000</pubDate>
		<dc:creator>ranantha</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[updatewikilink]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=771</guid>
		<description><![CDATA[MyProxy is an online credential repository. You can store X.509 proxy credentials in the MyProxy repository, protected by a passphrase, for later retrieval over the network.]]></description>
			<content:encoded><![CDATA[<p><strong>Status: </strong>In production</p>
<p>MyProxy is an online credential repository and can function as an Online CA. You can store X.509 proxy credentials in the MyProxy repository, protected by a passphrase, for later retrieval over the network. This eliminates the need for manually copying private key and certificate files between machines. In the Online CA mode, MyProxy can issue X.509 certificates to authenticated users and supports custom authentication using PAM module.  MyProxy can also be used for authentication to grid portals and credential renewal with job managers.</p>
<p>The BIRN CC operates this tool for the BIRN community; however, BIRN does not package it for community download. This tool is available publicly here: <a href="http://grid.ncsa.uiuc.edu/myproxy/about/">http://grid.ncsa.uiuc.edu/myproxy/about/</a></p>
<p>For information about how this tool is used within BIRN, go to <a href="https://wiki.birncommunity.org/display/BIRNDOC/Credential+Management">https://wiki.birncommunity.org/display/BIRNDOC/Credential+Management</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/myproxy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GridFTP</title>
		<link>http://www.birncommunity.org/tools-catalog/gridftp/</link>
		<comments>http://www.birncommunity.org/tools-catalog/gridftp/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 16:56:16 +0000</pubDate>
		<dc:creator>schuler</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[Data Storage]]></category>
		<category><![CDATA[Data Upload]]></category>
		<category><![CDATA[updatewikilink]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=769</guid>
		<description><![CDATA[GridFTP is a high-performance, secure, reliable data transfer protocol optimized for high-bandwidth wide-area networks. ]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>GridFTP is a high-performance, secure, reliable data transfer protocol optimized for   high-bandwidth wide-area networks. The GridFTP protocol is based on FTP, the highly-popular   Internet file transfer protocol. It includes a set of protocol features and extensions   defined already in IETF RFCs as well as a few additional features to meet requirements from current   data grid projects.</p>
<p>For information specific to using GridFTP in BIRN, see <a href="https://wiki.birncommunity.org/display/BIRNDOC/GridFTP+Guides">https://wiki.birncommunity.org/display/BIRNDOC/GridFTP+Guides</a>.</p>
<p>You can also download it as part of the Globus Toolkit <a href="http://www.globus.org/toolkit/docs/latest-stable/">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/gridftp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Upload Scripts</title>
		<link>http://www.birncommunity.org/tools-catalog/data-upload-scripts/</link>
		<comments>http://www.birncommunity.org/tools-catalog/data-upload-scripts/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 18:30:14 +0000</pubDate>
		<dc:creator>cwilliams</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Data Upload]]></category>
		<category><![CDATA[functionBIRN]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=620</guid>
		<description><![CDATA[The Upload scripts work in concert with the GridFTP servers, XCEDE, and the standardized data hierarchies to put data onto the GridFTP servers and link it to the appropriate database.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>The Upload scripts work in concert with the GridFTP servers, XCEDE, and the standardized data hierarchies to put data onto the GridFTP servers and link it to the appropriate database.</p>
<p>Organizing and locating information, both clinical metadata and imaging information, in a distributed data environment can be challenging. Because each site in the collaboratory maintains its own linked data storage, it is very important to develop standards for how and where the images are stored, metadata descriptions of what the images are, and how to find them.</p>
<p>To address these requirements the BIRN has implemented standardized data storage hierarchies on GridFTP servers. The data storage hierarchy was designed to be amenable to automated processing scripts and robust enough to account for differences in storage requirements across BIRN consortia. Not only is the physical organization of files maintained, but so are XML-based descriptors of what the files mean, which aids in data analysis.</p>
<p>The goals of the data upload scripts are:</p>
<ul>
<li>getting imaging information into the standardized data storage hierarchies,</li>
<li>creating XML-based metadata about the data acquisition,</li>
<li>converting scanner-specific, proprietary data formats into standard &#8220;useable&#8221; formats, and</li>
<li>linking data locations within the distributed file system into a site&#8217;s human imaging database (HID)</li>
</ul>
<p>Once the data has been &#8220;uploaded&#8221; using these scripts, any site in the collaboratory can locate the datasets by querying their local site&#8217;s HID database for particular imaging parameters, protocol specifications, or clinical metadata and downloading the images for further analyses. Using this decentralized approach, the BIRN has put the sites in control of their data while still maintaining shareability and access to the information.</p>
<p>Status: New upload scripts working with the HID and GridFTP are scheduled to be available by the end of 2010. The previous versions which worked with the SRB are <a href="/tools/UploadScripts_10_12_07.tgz">available here</a> for archival purposes.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/data-upload-scripts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Capability Registry</title>
		<link>http://www.birncommunity.org/tools-catalog/capability-registry/</link>
		<comments>http://www.birncommunity.org/tools-catalog/capability-registry/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 00:43:08 +0000</pubDate>
		<dc:creator>liming</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Collaboration Services]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=553</guid>
		<description><![CDATA[Status: In testing (forecast for October 2009)
The Capability Registry capability enables the BIRN community to discover using a central authoritative repository what capabilities the BIRN [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In testing (forecast for October 2009)</p>
<p>The Capability Registry capability enables the BIRN community to discover using a central authoritative repository what capabilities the BIRN community provides. This capability repository includes capability definition information published by capability owners, and capability deployment information published by capability operators.  Users will general use the capability registry thru web sites and other software systems that access the capability registry&#8217;s software interfaces.</p>
<p>The BIRN operates this tool for the BIRN community; however, BIRN does not package it for community download.</p>
<p>To access this tool: <a href="http://info.nbirn.org/">http://info.nbirn.org/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/capability-registry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BIRN_ID Generator</title>
		<link>http://www.birncommunity.org/tools-catalog/birn_id-generator/</link>
		<comments>http://www.birncommunity.org/tools-catalog/birn_id-generator/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 23:59:23 +0000</pubDate>
		<dc:creator>liv</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[Data Sharing & Collaboration]]></category>
		<category><![CDATA[functionBIRN]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=472</guid>
		<description><![CDATA[The BIRN_ID generator can be used to assign a unique ID to subjects in any type of experiment.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>The BIRN_ID generator can be used to assign a unique ID to subjects in any type of experiment. Subjects in experiments, whether human or animal, are often assigned random numbers as identifiers. When data are being shared and compiled across studies, these numbers must be unique. The BIRN_ID Generator can be used to assign a unique identifying 12-digit number for a subject.</p>
<p>The BIRN_ID Generator package generates unique HIPAA-compliant IDs, a BIRN_ID, from scratch or from already-assigned local IDs.  It is a Java application that runs on any platform.  It uses a cryptographically-strong pseudo-random number generating algorithm, SHA1PRNG, provided by Sun, and a one-way MD5 hash.</p>
<p>The BIRN_ID Generator also can find a BIRN_ID for a given local ID when the link table and local ID are provided.  The one-way hash ensures that the user cannot use a BIRN_ID alone to find a local ID and identify a subject.</p>
<p>The birn-id generator can be checked out with this command:</p>
<pre>svn co https://www.nitrc.org/svn/hid/utilities/trunk/utilities/birn-id_gen</pre>
<h3>BIRN_ID GENERATOR README</h3>
<h4>Prerequisites</h4>
<p>Java JDK (or JRE) 1.3.1 or higher needs to be installed on your system</p>
<h4>Installation</h4>
<ul>
<li>Put the BIRN_ID Generator package in a selected installation directory</li>
<li>Create a new environment variable, BIRNIDGEN_HOME, pointing to the installation directory</li>
</ul>
<h4>Usage</h4>
<ul>
<li>To generate BIRNIDs:$BIRNIDGEN_HOME/bin/birnid_gen.sh -create -p &lt;prefix&gt; -l <em>&lt;linkTableFilename&gt;</em> [-cf <em>&lt;clinicalIdsFilename&gt;</em> | -c <em>&lt;clinicalId&gt;</em>]where<em> &lt;linkTableFilename&gt;</em> is a text file to store MD5 one-way hashes of clinicalIDs, <em>&lt;clinicalIdsFilename&gt;</em> is a file that contains a list of clinicalIDs (each line is a clinicalID) and <em>&lt;clinicalId&gt;</em> is a single clinicalID.</li>
</ul>
<ul>
<li>To find the BIRNID from a clinicalID:$BIRNIDGEN_HOME/bin/birnid_gen.sh -find -c <em>&lt;clinicalId&gt;</em> -l <em>&lt;linkTableFilename&gt;</em>where <em>&lt;clinicalId&gt;</em> is a single clinicalID and <em>&lt;linkTableFilename&gt;</em> is a text file to store MD5 one-way hashes of clinicalIDs.</li>
</ul>
<h3>Background Information on the Random Number Generation</h3>
<p>SHA1PRNG: The name of the pseudo-random number generation (PRNG) algorithm supplied by the SUN provider. This implementation follows the IEEE P1363 standard, Appendix G.7: &#8220;Expansion of source bits&#8221;, and uses SHA-1 as the foundation of the PRNG. It computes the SHA-1 hash over a true-random seed value concatenated with a 64-bit counter which is incremented by 1 for each operation. From the 160-bit SHA-1 output, only 64 bits are used.</p>
<p>SHA-1 is the Secure Hash Algorithm, as defined in Secure Hash Standard, NIST FIPS 180-1.</p>
<p>SHA1PRNG is a cryptographically strong pseudo-random number generator (PRNG). A cryptographically strong pseudo-random number minimally complies with the statistical random number generator tests specified in FIPS 140-2, Security Requirements for Cryptographic Modules, section 4.9.1. Additionally, SecureRandom must produce non-deterministic output and therefore it is required that the seed material be unpredictable and that output of SecureRandom be cryptographically strong sequences as described in RFC 1750: Randomness Recommendations for Security.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/birn_id-generator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MRI Studio</title>
		<link>http://www.birncommunity.org/tools-catalog/mri-studio/</link>
		<comments>http://www.birncommunity.org/tools-catalog/mri-studio/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 22:36:14 +0000</pubDate>
		<dc:creator>helmer</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Analysis]]></category>
		<category><![CDATA[Brain Morphometry BIRN]]></category>
		<category><![CDATA[DTI]]></category>
		<category><![CDATA[morphBIRN]]></category>
		<category><![CDATA[Visualization]]></category>
		<category><![CDATA[Visualization & Atlasing]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=456</guid>
		<description><![CDATA[MRI Studio is a Windows-based software package, developed at Johns Hopkins University that includes support for 3D visualization, the processing of diffusion tensor data, and image registration.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>MRI Studio (<a href="https://www.mristudio.org/">https://www.mristudio.org/</a> ) is a Windows-based software package, developed at Johns Hopkins University that includes support for 3D visualization, the processing of diffusion tensor data, and image registration. The package supports a number of different image data types from Philips PAR and REC files to DICOM.  MRI Studio can be obtained from the S. Mori group website here. The package is supported through several mailing lists (<a href="https://lists.mristudio.org/mailman/listinfo">https://lists.mristudio.org/mailman/listinfo</a>).</p>
<p>To access this tool: <a href="https://www.mristudio.org/">https://www.mristudio.org/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/mri-studio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Large Deformation Diffeomorphic Metric Mapping (LDDMM)</title>
		<link>http://www.birncommunity.org/tools-catalog/large-deformation-diffeomorphic-metric-mapping-lddmm/</link>
		<comments>http://www.birncommunity.org/tools-catalog/large-deformation-diffeomorphic-metric-mapping-lddmm/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 16:35:09 +0000</pubDate>
		<dc:creator>helmer</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Acquisition]]></category>
		<category><![CDATA[Brain Morphometry BIRN]]></category>
		<category><![CDATA[Calibration]]></category>
		<category><![CDATA[Distortion Correction]]></category>
		<category><![CDATA[morphBIRN]]></category>

		<guid isPermaLink="false">http://nbirn-misd1.isi.edu/?p=430</guid>
		<description><![CDATA[The Large Deformation Diffeomorphic Metric Mapping (LDDMM) tool is an application which aims to assign metric distances on the space of anatomical images in Computational Anatomy thereby allowing for the direct comparison and quantization of morphometric changes in shapes.]]></description>
			<content:encoded><![CDATA[<p><strong>Status:</strong> In production</p>
<p>The Center for Imaging Science (CIS) at Johns Hopkins University (JHU) has been successful in providing Shape Analysis tools to the BIRN community. These tools are able to compare complex-shaped brain structures and detect differences over the entire surface of the structure. Large-scale shape-analysis processing has been established through the use of Large Deformation Diffeomorphic Metric Mapping (LDDMM, http://cis.jhu.edu/software/lddmm-volume/index.html) and the use of the TeraGrid.</p>
<p>The Large Deformation Diffeomorphic Metric Mapping (LDDMM) tool aims to quantify metric distances on anatomical structures in medical images. This allows for the direct comparison and quantization of morphometric changes due to, for example, disease or aging. As part of these efforts, the Center for Imaging Science at Johns Hopkins University developed techniques to not only compare images, but also to visualize the changes and differences.</p>
<div id="c1.3">
<p>Aspects of this work have been  published:</p>
<blockquote><p>Faisal Beg, Michael Miller, Alain Trouve, and Laurent Younes. Computing Large Deformation Metric Mappings via Geodesic Flows of Diffeomorphisms. <em>International Journal of Computer Vision</em>, Volume 61, Issue 2; February 2005.</p>
<p>M.I. Miller and A. Trouve and L. Younes, On the Metrics and Euler-Lagrange Equations of Computational Anatomy, <em>Annual Review of Biomedical Engineering</em>, 4:375-405, 2002.)</p></blockquote>
<p>A significant source of error in brain image data is spatial distortions due to inhomogeneities in the main magnetic field (B0), which can arise due to imperfect gradient non-linearity, shimming, magnetic susceptibility effects and chemical shift. These effects can become particularly important for longitudinal studies in which different shim settings can result in substantially different distortions between scan sessions. Although these distortions are most pronounced in functional or diffusion-weighted imaging using echo planar imaging (EPI) sequences, the effect can be significant (on the order of several millimeters) even in conventional structural images.</p>
<p>Work by Susumu Mori’s group at the JHU showed that landmark-based distortion correction using the Large Deformation Diffeomorphic Metric Mapping (LDDMM) algorithm can be a viable method to minimize B0 distortion. They have developed software to perform these operations. This software is currently in the testing phase.</p>
<p>To use this tool: <a href="http://www.nitrc.org/projects/lddmm-volume/">http://www.nitrc.org/projects/lddmm-volume/</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.birncommunity.org/tools-catalog/large-deformation-diffeomorphic-metric-mapping-lddmm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

