-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcoordinatefreereg.html
230 lines (218 loc) · 15.6 KB
/
coordinatefreereg.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Applying Coordinate-Free Registration — CoCoTools 0.0.1 documentation</title>
<link rel="stylesheet" href="_static/sphinxdoc.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '',
VERSION: '0.0.1',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="top" title="CoCoTools 0.0.1 documentation" href="index.html" />
<link rel="up" title="Processing Pipeline in Detail" href="details.html" />
<link rel="next" title="Post-Processing" href="postprocessing.html" />
<link rel="prev" title="Pre-Processing Query Results" href="preprocessing.html" />
</head>
<body>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="postprocessing.html" title="Post-Processing"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="preprocessing.html" title="Pre-Processing Query Results"
accesskey="P">previous</a> |</li>
<li><a href="index.html">CoCoTools 0.0.1 documentation</a> »</li>
<li><a href="documentation.html" >CoCoTools’s documentation</a> »</li>
<li><a href="details.html" accesskey="U">Processing Pipeline in Detail</a> »</li>
</ul>
</div>
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Applying Coordinate-Free Registration</a><ul>
<li><a class="reference internal" href="#objective-relaional-transformation-ort">1) Objective Relaional Transformation (ORT):</a><ul>
<li><a class="reference internal" href="#subtle-flaw-in-ort-logic">Subtle flaw in ORT logic:</a></li>
<li><a class="reference internal" href="#treats-source-and-target-extent-information-independently">Treats Source and Target Extent information independently:</a></li>
</ul>
</li>
<li><a class="reference internal" href="#modified-objective-relation-transformation-mort">2) Modified Objective Relation Transformation (mORT):</a></li>
<li><a class="reference internal" href="#coordinate-free-registration-steps">Coordinate-Free Registration steps</a></li>
<li><a class="reference internal" href="#coordinate-free-registration-examples">Coordinate-Free Registration Examples</a></li>
<li><a class="reference internal" href="#coordinate-free-registration-concepts-and-work-flow">Coordinate-free registration Concepts and Work-Flow</a></li>
<li><a class="reference internal" href="#references">References</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="preprocessing.html"
title="previous chapter">Pre-Processing Query Results</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="postprocessing.html"
title="next chapter">Post-Processing</a></p>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="_sources/coordinatefreereg.txt"
rel="nofollow">Show Source</a></li>
</ul>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="applying-coordinate-free-registration">
<h1>Applying Coordinate-Free Registration<a class="headerlink" href="#applying-coordinate-free-registration" title="Permalink to this headline">¶</a></h1>
<p id="detail-coordinate-free">Next, what is needed is to bring together and translate the connectivity statements (stored in congraph) in various different parcellation schemes into a single parcellation scheme.
As the basis for this translation, we will need to use the logical spatial relationships that exist between regions in the various parcellation schemes (stored in mapgraph).
With this data, we will then apply an algorithm that contains, at its core, a formal transformation logic that produces a transparent, unambiguous and as best as possible, accurate translations.</p>
<p>In CoCoTools, we have implemented two <em>coordinate-free registration</em> algorithms that contain different transformation logic.</p>
<div class="section" id="objective-relaional-transformation-ort">
<h2>1) Objective Relaional Transformation (ORT):<a class="headerlink" href="#objective-relaional-transformation-ort" title="Permalink to this headline">¶</a></h2>
<p>Proposed and described by Stephan, Kotter and colleagues through several articles and one book chapter. Our implementation integrates features in all of these different descriptions to provide what we found to be the most sensible and least error-prone algorithm. It is important to note that:</p>
<ul class="simple">
<li>We follow most closely the description of Stephan and Kotter (1998) <a class="footnote-reference" href="#id2" id="id1">[1]</a> for assembling the set of mapping relations and connectivity statement needed to determine the cortical space shared by regions in different parcellation schemes.</li>
<li>Unlike prior descriptions, we allow the “U” extension code to be used as input into ORT. We assign “U” to unstudied connections. This allows CoCoTools to handle situations when information from some regions is absent from CoCoMac.</li>
<li>ORT uses the full set of Relation Codes (RC’s) in the mapgraph in its transformation ruleset.</li>
</ul>
<div class="section" id="subtle-flaw-in-ort-logic">
<h3>Subtle flaw in ORT logic:<a class="headerlink" href="#subtle-flaw-in-ort-logic" title="Permalink to this headline">¶</a></h3>
<p>There is a small flaw in the logic of ORT, and in practice this leads to a subset of edges being mistranslated:</p>
<blockquote>
<div><ul class="simple">
<li>ORT’s use of the full set of RC’s is based on the assumption that extent of staining = extent of connectivity.</li>
<li>For this assumption to hold, both retrograde and anterograde tracer needs to be injected in each region per parcellation scheme to determine the origin and termination points.</li>
<li>Unfortunately, CoCoMac does not capture this information, and thus we can not logically justify using extent information.</li>
<li>In practice, this leads ORT to be overly liberal – assigning connections as either present or absent when not fully justified by the data (i.e unknown connections)</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="treats-source-and-target-extent-information-independently">
<h3>Treats Source and Target Extent information independently:<a class="headerlink" href="#treats-source-and-target-extent-information-independently" title="Permalink to this headline">¶</a></h3>
<p>Another consequence of ORT relying on EC’s is that the translation of each edge’s source and target are handled separately, and this can lead to mistranslations.</p>
</div>
</div>
<div class="section" id="modified-objective-relation-transformation-mort">
<h2>2) Modified Objective Relation Transformation (mORT):<a class="headerlink" href="#modified-objective-relation-transformation-mort" title="Permalink to this headline">¶</a></h2>
<p>We designed mORT to address these issues:</p>
<p>In mORT:</p>
<ul class="simple">
<li>A single label is applied to each translated edge (‘Present’, Absent’, and ‘Unknown’) that integrates information about the presence/absence of tracer in the source and target regions</li>
<li>The fact that mORT ignores whether stain is ‘Partial’ or ‘Complete’ in a region, might seem to imply that mORT will generally label fewer connections in the target map as present compared to ORT, but this is not neccessarily always the case, as ORT oversteps not only in its assignments of connection presence, but also when affirming a connection’s absence.</li>
</ul>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">In practice, we have found only small differences between the results of these approaches. mORT has the main advantages of being more conservative, faster and theoretically more accurate.</p>
</div>
</div>
<div class="section" id="coordinate-free-registration-steps">
<h2>Coordinate-Free Registration steps<a class="headerlink" href="#coordinate-free-registration-steps" title="Permalink to this headline">¶</a></h2>
<p>You will need to initialize a new type of cocotools directed graph container (or class); the <a class="reference internal" href="api.html#cocotools.EndGraph" title="cocotools.EndGraph"><tt class="xref py py-class docutils literal"><span class="pre">cocotools.EndGraph</span></tt></a></p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">endg</span><span class="o">=</span><span class="n">coco</span><span class="o">.</span><span class="n">EndGraph</span><span class="p">()</span>
</pre></div>
</div>
<dl class="docutils">
<dt>Next you can run coordinate-free registration using</dt>
<dd><p class="first"><a class="reference internal" href="api.html#cocotools.EndGraph.add_translated_edges" title="cocotools.EndGraph.add_translated_edges"><tt class="xref py py-meth docutils literal"><span class="pre">cocotools.EndGraph.add_translated_edges()</span></tt></a></p>
<p class="last">you supply this method with the pre-processed mapgraph and congraphs, the CoCoMac acronym of the output space you want to register to, and the method you want to use (<em>‘original’</em> for ORT and <em>‘modified’</em> for mORT).</p>
</dd>
</dl>
</div>
<div class="section" id="coordinate-free-registration-examples">
<h2>Coordinate-Free Registration Examples<a class="headerlink" href="#coordinate-free-registration-examples" title="Permalink to this headline">¶</a></h2>
<p><strong>ORT</strong>:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">endg</span><span class="o">=</span><span class="n">coco</span><span class="o">.</span><span class="n">EndGraph</span><span class="p">()</span> <span class="c">#initialize an empty endgraph</span>
<span class="n">endg</span><span class="o">.</span><span class="n">add_translated_edges</span><span class="p">(</span><span class="n">mapg</span><span class="p">,</span> <span class="n">cong</span><span class="p">,</span> <span class="s">'PHT00'</span><span class="p">,</span> <span class="s">'modified'</span><span class="p">)</span> <span class="c">#perform original ORT, registering to the PHT00 space</span>
</pre></div>
</div>
<p><strong>mORT</strong>:</p>
<div class="highlight-python"><div class="highlight"><pre><span class="n">endg</span><span class="o">=</span><span class="n">coco</span><span class="o">.</span><span class="n">EndGraph</span><span class="p">()</span> <span class="c">#initialize an empty endgraph</span>
<span class="n">endg</span><span class="o">.</span><span class="n">add_translated_edges</span><span class="p">(</span><span class="n">mapg</span><span class="p">,</span> <span class="n">cong</span><span class="p">,</span> <span class="s">'R00'</span><span class="p">,</span> <span class="s">'modified'</span><span class="p">)</span> <span class="c">#perform modified ORT, registering to the Relational Map space</span>
</pre></div>
</div>
</div>
<div class="section" id="coordinate-free-registration-concepts-and-work-flow">
<h2>Coordinate-free registration Concepts and Work-Flow<a class="headerlink" href="#coordinate-free-registration-concepts-and-work-flow" title="Permalink to this headline">¶</a></h2>
<p>It is hard to appreciate the complexity of the problems that must be overcome by coordinate-free registration algorithms to obtain a meaniningful final connectivity graphs. Our methods paper describes ORT and mORT in much more detail PUT REF HERE.
For a some-what more detailed look at the guts for how cocotools performs coordinate-free registration proceed <a class="reference internal" href="endgraphguts.html#endgraph-guts"><em>here</em></a> .</p>
<blockquote>
<div><ul class="simple">
<li>We also have prepared an IPython Notebook on github that will allow you to work through the individual steps of ORT or mORT for one edge, more or less by hand. Check it out <a class="reference external" href="https://github.com/cocotools/CoCoTools/tree/master/examples#a-collection-of-notebooks-for-using-cocotools">here</a></li>
</ul>
</div></blockquote>
<p>Warning::
<em>In CoCoTools, we do not claim that the algorithms that we provide will converge on the “ground truth”, but rather we aim for our methods to be clearly defined and transparent,
but most of all, we aim for our coordinate-free registrations methods to be easy-to-use and produce sensible results given the complexity of the data.</em></p>
</div>
<div class="section" id="references">
<h2>References<a class="headerlink" href="#references" title="Permalink to this headline">¶</a></h2>
<table class="docutils footnote" frame="void" id="id2" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id1">[1]</a></td><td>Stephan, K. E., & Kotter, R. (1998). A formal approach to the translation of cortical maps. In Neural Circuits and Networks (pp. 205 thru 226). Berlin Springer.</td></tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="postprocessing.html" title="Post-Processing"
>next</a> |</li>
<li class="right" >
<a href="preprocessing.html" title="Pre-Processing Query Results"
>previous</a> |</li>
<li><a href="index.html">CoCoTools 0.0.1 documentation</a> »</li>
<li><a href="documentation.html" >CoCoTools’s documentation</a> »</li>
<li><a href="details.html" >Processing Pipeline in Detail</a> »</li>
</ul>
</div>
<div class="footer">
© Copyright 2011, Daniel Bliss, Rob Blumenfeld and Fernando Perez.
Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
</div>
</body>
</html>