-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.xml
512 lines (373 loc) · 29.7 KB
/
index.xml
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
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Sancar Adali - personal website on Sancar Adali - personal website</title>
<link>https://adalisan.github.io/</link>
<description>Recent content in Sancar Adali - personal website on Sancar Adali - personal website</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<copyright>&copy; 2016 Sancar Adali</copyright>
<lastBuildDate>Sun, 10 Mar 2019 00:00:00 +0000</lastBuildDate>
<atom:link href="/" rel="self" type="application/rss+xml" />
<item>
<title>Seeded Graph Matching</title>
<link>https://adalisan.github.io/publication/sgm/</link>
<pubDate>Sun, 10 Mar 2019 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/sgm/</guid>
<description></description>
</item>
<item>
<title>graph matching and spaces</title>
<link>https://adalisan.github.io/post/graph-matching-and-spaces/</link>
<pubDate>Thu, 26 Jul 2018 21:06:09 -0400</pubDate>
<guid>https://adalisan.github.io/post/graph-matching-and-spaces/</guid>
<description><p>Part of <a href="{{&lt; ref &quot;publication/thesis.md&quot; &gt;}}" target="_blank">my dissertation research</a> was on the graph matching problem. For solving this problem in real settings, it is useful to think of vertices as elements of a space with the edges determining some sort of locality, (I guess this can be formalized with topology ). Then the graph/vertex matching problem becomes sort of a point cloud matching problem where you don&rsquo;t know where the points are , just the neighborhood relationships between them ( several manifold learning uses these relationships to find the manifolds defined by the points ). That is why embedding the vertices of the two graph using dissimilarities between vertex pairs can be used to match graphs. This is how we have used <a href="{{&lt; ref &quot;publication/SGMviaJOFC.md&quot; &gt;}}" target="_blank">JOFC</a> for seeded graph matching.</p>
<p>The same paradigm works with point cloud registration or matching manifolds. For example, see <a href="https://arxiv.org/pdf/1710.04087.pdf" target="_blank">this paper by Facebook researchers </a> for matching between monolingual word embeddings in different languages. They start by finding a rigid transformation between the two word embeddings in different languages (say english and french), based on closest matches using Procrustes method. They then modify the distance between an english vector mapped french and a french vector to solve the point density problem: hub words (that are common words in either corpora) will have emeddings that are close to many other words will be matched to many other words , and easily confused . I think this also applies to hub vertices that are connected to many other vertices in graph matching. The distance modification uses the number of words in the neighborhood of a common word , so that more dense regions of the embedding spaces will see this cross-domain distance increase. Another possible solution to this nonhomogenous point density in the embedding spaces may be using hyperbolic embeddings which I will summarize in another post.</p>
</description>
</item>
<item>
<title>ALADDIN</title>
<link>https://adalisan.github.io/project/aladdin/</link>
<pubDate>Mon, 15 May 2017 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/aladdin/</guid>
<description><p>Software Development &amp; Research for interactive system that carries out training and search for events in big video collections. <a href="https://www.iarpa.gov/index.php/research-programs/aladdin-video" target="_blank">IARPA website for the ALADDIN program</a></p>
</description>
</item>
<item>
<title>CVRG</title>
<link>https://adalisan.github.io/project/cvrg/</link>
<pubDate>Mon, 15 May 2017 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/cvrg/</guid>
<description><p>I was a researcher in the machine learning group for the Cardiovascular Research Grid project. We worked with the cardiologists who are custodians of a dataset involving patients with ICD implants. Our objective was to come up with robust, interpretable predictors that predicted either high risk of ICD utilization , or sudden cardiac death. An important challenge was to create predictors that both utilized both survival data and did not become biased due to not-missing-at-random data.</p>
</description>
</item>
<item>
<title>Fidelity-Commensurability Tradeoff in Joint Embedding of Disparate Dissimilarities</title>
<link>https://adalisan.github.io/publication/fidcommjofc/</link>
<pubDate>Thu, 10 Nov 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/fidcommjofc/</guid>
<description><p>Let&rsquo;s say our data does not consist of $n$ observations of $d$-dimensional vectors, but instead an $n \times n$ matrix, whose entries consist of the dissimilarities between the $n$ observations as measured by a bivariate function $\delta(.,.)$. We refer to the computation of $n$ separate $d$-dimensional vectors/points that is as consistent as possible with a dissimilarity matrices as &ldquo;embedding&rdquo; this dissimilarity matrix.</p>
<p>Consider the embedding of $K$ dissimilarity(distance-like) matrices between $n$ objects (coming from $K$ different bivariate functions $\delta_k(.,.)$ ) or observations of $n$ $K-tuples$ of similar objects. In any case the different dissimilarity matrices are related in a statistical or causal sense. We refer to this relation as &ldquo;matched&rdquo;. Say $K=2$. A joint embedding of these dissimilarity matrices will result in $2n$ points that consist of $n$ matched points.</p>
<p>To embed multiple dissimilarities ${\Delta_k},k=1,2$ into a commensurate space, so that the information represented in different dissimality matrices can be used for a data exploitation task, an omnibus dissimilarity matrix $M \in \mathbb{R}^{nk \times nk}$ is constructed. Consider, for $K=2$,
$$
M= \left[ \begin{array}{cc}
\Delta_1 &amp; L<br />
L^T &amp; \Delta_2
\end{array} \right] \label{omnibus}
$$ where $L$ is an imputed or estimated matrix for the two dissimilarities between $n$ objects. The embedding of this matrix will result in $2n$ observations of $d$-dimensional vectors.</p>
<p>If we minimize a common multidimensional scaling objective function known as raw stress to embed, the objective function can be decomposed into three terms that are interpretable.
Fidelity describes how well the embedding in commensurate space preserves the original dissimilarities ${\Delta_k},k=1,2$. These terms would be the only ones that are minimized if we embedded the dissimilarity matrices separately.</p>
<p>Commensurability is how well the embedding in commensurate space preserves matchedness of matched observations. These terms correspond to the deviation from the real dissimilarities between matched observations and the distances between matched points in the embedding.</p>
<p>Separability is how well the embedding in commensurate space preserves the disparateness of unmatched observations.
These terms correspond to the deviation from the real dissimilarities between unmatched observations and the distances between unmatched points in the embedding.</p>
<p>We show that a weight parameter that controls the terms&rsquo; importance in the minimization of raw stress is essential for data exploitation task such as detection of new matched observations, given a set of matched observations.</p>
</description>
</item>
<item>
<title>Joint Optimization of Fidelity and Commensurability for Manifold Alignment and Graph Matching</title>
<link>https://adalisan.github.io/publication/thesis/</link>
<pubDate>Thu, 10 Nov 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/thesis/</guid>
<description><p>More detail can easily be written here using <em>Markdown</em> and $\rm \LaTeX$ math code.</p>
</description>
</item>
<item>
<title>Learning spatiotemporal features for infrared action recognition with 3d convolutional neural networks</title>
<link>https://adalisan.github.io/publication/infracv/</link>
<pubDate>Thu, 10 Nov 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/infracv/</guid>
<description></description>
</item>
<item>
<title>Seeded Graph Matching Via Joint Optimization of Fidelity and Commensurability</title>
<link>https://adalisan.github.io/publication/sgmviajofc/</link>
<pubDate>Thu, 10 Nov 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/sgmviajofc/</guid>
<description></description>
</item>
<item>
<title>Data Fusion from Disparate Dissimilarities and Joint Optimization of Fidelity and Commensurability</title>
<link>https://adalisan.github.io/project/jofc/</link>
<pubDate>Wed, 27 Apr 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/jofc/</guid>
<description><p>My PhD thesis was on joint embedding of disparate dissimilarities for solving various inference tasks such as transfer learning, match detection and graph matching. I have dealt with various issues such as robustness to noise and compared with alternative approaches such as Canonical Correlational Analysis.
<a href="https://github.com/adalisan/JOFC-GraphMatch" target="_blank">Github repo</a></p>
</description>
</item>
<item>
<title>External Project</title>
<link>https://adalisan.github.io/project/example-external-project/</link>
<pubDate>Wed, 27 Apr 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/example-external-project/</guid>
<description></description>
</item>
<item>
<title>Seeded Graph Matching</title>
<link>https://adalisan.github.io/project/sgm/</link>
<pubDate>Wed, 27 Apr 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/sgm/</guid>
<description><p>This variant of the graph matching problem provides an opportunity for the application of JOFC and also the adaptation of a state-of-the-art graph matching algorithm.
My work on this variant of the graph matching problem constituted part of my dissertation research. This work is presented in <a href="http://arxiv.org/abs/1209.0367" target="_blank">this</a> and <a href="http://arxiv.org/abs/1401.3813http://arxiv.org/abs/1401.3813" target="_blank">this</a> arxiv papers.</p>
<p>The code for the algorithm and analysis is at
<a href="https://github.com/adalisan/SeededGraphMatch" target="_blank">https://github.com/adalisan/SeededGraphMatch</a></p>
</description>
</item>
<item>
<title>XDATA</title>
<link>https://adalisan.github.io/project/xdata/</link>
<pubDate>Wed, 27 Apr 2016 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/project/xdata/</guid>
<description>
<h4 id="darpa-program-for-organizing-big-data-analysis-and-visualization-efforts">DARPA program for organizing big data analysis and visualization efforts.</h4>
<p>The different data analysis tasks we accomplished are <a href="http://www.cis.jhu.edu/~parky/XDATA/" target="_blank">here</a>.</p>
<p>See the <a href="https://docs.google.com/presentation/d/1PjKrZE0zIsT6egd2p4jNx7XvaOxjYDkB_OP8tSZI6LY/pub?start=false&amp;loop=false&amp;delayms=5000" target="_blank">midpoint presentation</a>
and <a href="xdata_ppt1/XDATA-Midpoint.html" target="_blank">final presentation</a> for the summer workshop.</p>
</description>
</item>
<item>
<title>Migration</title>
<link>https://adalisan.github.io/post/migrating-to-hugo/</link>
<pubDate>Wed, 20 Apr 2016 10:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/post/migrating-to-hugo/</guid>
<description><p>I have decided to switch to the academic theme for hugo , as it makes much more sense for a researcher. Now I just need to collect all the things I have done over the years.</p>
</description>
</item>
<item>
<title>Writing content with Markdown, LaTeX, and Shortcodes</title>
<link>https://adalisan.github.io/post/writing-markdown-latex/</link>
<pubDate>Wed, 20 Apr 2016 10:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/post/writing-markdown-latex/</guid>
<description><p>Content can be written using <a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet" target="_blank">Markdown</a>, <a href="https://en.wikibooks.org/wiki/LaTeX/Mathematics" target="_blank">LaTeX math</a>, and <a href="http://gohugo.io/extras/shortcodes/" target="_blank">Hugo Shortcodes</a>. Additionally, HTML may be used for advanced formatting.</p>
<p>This article gives an overview of the most common formatting options.</p>
<h2 id="sub-headings">Sub-headings</h2>
<pre><code>## Heading 2
### Heading 3
#### Heading 4
##### Heading 5
###### Heading 6
</code></pre>
<h2 id="emphasis">Emphasis</h2>
<pre><code>Italics with *asterisks* or _underscores_.
Bold with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough with ~~two tildes~~.
</code></pre>
<h2 id="ordered-lists">Ordered lists</h2>
<pre><code>1. First item
2. Another item
</code></pre>
<h2 id="unordered-lists">Unordered lists</h2>
<pre><code>* First item
* Another item
</code></pre>
<h2 id="images">Images</h2>
<p>Images may be added to a page by placing them in your <code>static/img/</code> folder and referencing them using one of the following two notations:</p>
<p>A general image:</p>
<pre><code>![alternative text for search engines](/img/screenshot.png)
</code></pre>
<p>A numbered figure with caption:</p>
<pre><code>{{&lt; figure src=&quot;/img/screenshot.png&quot; title=&quot;Figure Caption&quot; &gt;}}
</code></pre>
<h2 id="links">Links</h2>
<pre><code>[I'm a link](https://www.google.com)
[A post]({{&lt; ref &quot;post/hi.md&quot; &gt;}})
[A publication]({{&lt; ref &quot;publication/hi.md&quot; &gt;}})
[A project]({{&lt; ref &quot;project/hi.md&quot; &gt;}})
[Another section]({{&lt; relref &quot;hi.md#who&quot; &gt;}})
</code></pre>
<h2 id="emojis">Emojis</h2>
<p>See the <a href="http://www.webpagefx.com/tools/emoji-cheat-sheet/" target="_blank">Emoji cheat sheet</a> for available emoticons. The following serves as an example, but you should remove the spaces between each emoji name and pair of semicolons:</p>
<pre><code>I : heart : Academic : smile :
</code></pre>
<p>I ❤️ Academic 😄</p>
<h2 id="blockquote">Blockquote</h2>
<pre><code>&gt; This is a blockquote.
</code></pre>
<blockquote>
<p>This is a blockquote.</p>
</blockquote>
<h2 id="footnotes">Footnotes</h2>
<pre><code>I have more [^1] to say.
[^1]: Footnote example.
</code></pre>
<p>I have more <sup class="footnote-ref" id="fnref:1"><a href="#fn:1">1</a></sup> to say.</p>
<h2 id="code-highlighting">Code highlighting</h2>
<p>Pass the <em>language</em> of the code, such as <code>python</code>, as a parameter after three backticks:</p>
<pre><code>```python
# Example of code highlighting
input_string_var = input(&quot;Enter some data: &quot;)
print(&quot;You entered: {}&quot;.format(input_string_var))
```
</code></pre>
<p>Result:</p>
<pre><code class="language-python"># Example of code highlighting
input_string_var = input(&quot;Enter some data: &quot;)
print(&quot;You entered: {}&quot;.format(input_string_var))
</code></pre>
<h3 id="highlighting-options">Highlighting options</h3>
<p>The Academic theme uses <a href="https://highlightjs.org" target="_blank">highlight.js</a> for source code highlighting, and highlighting is enabled by default for all pages. However, several configuration options are supported that allow finer-grained control over highlight.js.</p>
<p>The following table lists the supported options for configuring highlight.js, along with their expected type and a short description. A &ldquo;yes&rdquo; in the <strong>config.toml</strong> column means the value can be set globally in <code>config.toml</code>, and a &ldquo;yes&rdquo; in the <strong>preamble</strong> column means that the value can be set locally in a particular page&rsquo;s preamble.</p>
<table>
<thead>
<tr>
<th>option</th>
<th>type</th>
<th>description</th>
<th>config.toml</th>
<th>preamble</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>highlight</code></td>
<td>boolean</td>
<td>enable/disable highlighting</td>
<td>yes</td>
<td>yes</td>
</tr>
<tr>
<td><code>highlight_languages</code></td>
<td>slice</td>
<td>choose additional languages</td>
<td>yes</td>
<td>yes</td>
</tr>
<tr>
<td><code>highlight_style</code></td>
<td>string</td>
<td>choose a highlighting style</td>
<td>yes</td>
<td>no</td>
</tr>
<tr>
<td><code>highlight_version</code></td>
<td>string</td>
<td>choose the highlight.js version</td>
<td>yes</td>
<td>no</td>
</tr>
</tbody>
</table>
<h4 id="option-highlight">Option <code>highlight</code></h4>
<p>The <code>highlight</code> option allows enabling or disabling the inclusion of highlight.js, either globally or for a particular page. If the option is unset, it has the same effect as if you had specified <code>highlight = true</code>. That is, the highlight.js javascript and css files will be included in every page. If you&rsquo;d like to only include highlight.js files on pages that actually require source code highlighting, you can set <code>highlight = false</code> in <code>config.toml</code>, and then override it by setting <code>highlight = true</code> in the preamble of any pages that require source code highlighting. Conversely, you could enable highlighting globally, and disable it locally for pages that do not require it. Here is a table that shows whether highlighting will be enabled for a page, based on the values of <code>highlight</code> set in <code>config.toml</code> and/or the page&rsquo;s preamble.</p>
<table>
<thead>
<tr>
<th>config.toml</th>
<th>page preamble</th>
<th>highlighting enabled for page?</th>
</tr>
</thead>
<tbody>
<tr>
<td>unset or true</td>
<td>unset or true</td>
<td>yes</td>
</tr>
<tr>
<td>unset or true</td>
<td>false</td>
<td>no</td>
</tr>
<tr>
<td>false</td>
<td>unset or false</td>
<td>no</td>
</tr>
<tr>
<td>false</td>
<td>true</td>
<td>yes</td>
</tr>
</tbody>
</table>
<h4 id="option-highlight-languages">Option <code>highlight_languages</code></h4>
<p>The <code>highlight_languages</code> option allows you to specify additional languages that are supported by highlight.js, but are not considered &ldquo;common&rdquo; and therefore are not supported by default. For example, if you want source code highlighting for Go and clojure in all pages, set <code>highlight_languages = [&quot;go&quot;, &quot;clojure&quot;]</code> in <code>config.toml</code>. If, on the other hand, you want to enable a language only for a specific page, you can set <code>highlight_languages</code> in that page&rsquo;s preamble.</p>
<p>The <code>highlight_languages</code> options specified in <code>config.toml</code> and in a page&rsquo;s preamble are additive. That is, if <code>config.toml</code> contains, <code>highlight_languages = [&quot;go&quot;]</code> and the page&rsquo;s preamble contains <code>highlight_languages = [&quot;ocaml&quot;]</code>, then javascript files for <em>both</em> go and ocaml will be included for that page.</p>
<p>If the <code>highlight_languages</code> option is set, then the corresponding javascript files will be served from the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs server</a>. To see a list of available languages, visit the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs page</a> and search for links with the word &ldquo;languages&rdquo;.</p>
<p>The <code>highlight_languages</code> option provides an easy and convenient way to include support for additional languages to be severed from a CDN. If serving unmodified files from cdnjs doesn&rsquo;t meet your needs, you can include javascript files for additional language support via one of the methods described in the getting started guide.</p>
<h4 id="option-highlight-style">Option <code>highlight_style</code></h4>
<p>The <code>highlight_style</code> option allows you to select an alternate css style for highlighted code. For example, if you wanted to use the solarized-dark style, you could set <code>highlight_style = &quot;solarized-dark&quot;</code> in <code>config.toml</code>.</p>
<p>If the <code>highlight_style</code> option is unset, the default is to use the file <code>/css/highlight.min.css</code>, either the one provided by the Academic theme, or else the one in your local <code>static</code> directory. The <code>/css/highlight.min.css</code> file provided by Academic is equivalent to the <code>github</code> style from highlight.js.</p>
<p>If the <code>highlight_style</code> option <em>is</em> set, then <code>/css/highlight.min.css</code> is ignored, and the corresponding css file will be served from the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs server</a>. To see a list of available styles, visit the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs page</a> and search for links with the word &ldquo;styles&rdquo;.</p>
<p>See the <a href="https://highlightjs.org/static/demo/" target="_blank">highlight.js demo page</a> for examples of available styles.</p>
<p>Missing alert
Not all styles listed on the <a href="https://highlightjs.org/static/demo/" target="_blank">highlight.js demo page</a> are available from the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs server</a>. If you want to use a style that is not served by cdnjs, just leave <code>highlight_style</code> unset, and place the corresponding css file in <code>/static/css/highlight.min.css</code>.
Missing <strong>alert</strong></p>
<p>If you don&rsquo;t want to change the default style that ships with Academic but you do want the style file served from the <a href="https://cdnjs.com/libraries/highlight.js/" target="_blank">cdnjs server</a>, set <code>highlight_style = &quot;github&quot;</code> in <code>config.toml</code>.
Missing <strong>alertend</strong></p>
<p>The <code>highlight_style</code> option is only recognized when set in <code>config.toml</code>. Setting <code>highlight_style</code> in your page&rsquo;s preamble has no effect.</p>
<h4 id="option-highlight-version">Option <code>highlight_version</code></h4>
<p>The <code>highlight_version</code> option, as the name implies, allows you to select the version of highlight.js you want to use. The default value is &ldquo;9.9.0&rdquo;. The <code>highlight_version</code> option is only recognized when set in <code>config.toml</code>. Setting <code>highlight_version</code> in your page&rsquo;s preamble has no effect.</p>
<h2 id="twitter-tweet">Twitter tweet</h2>
<p>To include a single tweet, pass the tweet’s ID from the tweet&rsquo;s URL as parameter to the shortcode:</p>
<pre><code>{{&lt; tweet 666616452582129664 &gt;}}
</code></pre>
<h2 id="youtube">Youtube</h2>
<pre><code>{{&lt; youtube w7Ft2ymGmfc &gt;}}
</code></pre>
<h2 id="vimeo">Vimeo</h2>
<pre><code>{{&lt; vimeo 146022717 &gt;}}
</code></pre>
<h2 id="github-gist">GitHub gist</h2>
<pre><code>{{&lt; gist USERNAME GIST-ID &gt;}}
</code></pre>
<h2 id="speaker-deck">Speaker Deck</h2>
<pre><code>{{&lt; speakerdeck 4e8126e72d853c0060001f97 &gt;}}
</code></pre>
<h2 id="rm-latex-math">$\rm \LaTeX$ math</h2>
<pre><code class="language-TeX">$$\left [ – \frac{\hbar^2}{2 m} \frac{\partial^2}{\partial x^2} + V \right ] \Psi = i \hbar \frac{\partial}{\partial t} \Psi$$
</code></pre>
<p>$$\left [ – \frac{\hbar^2}{2 m} \frac{\partial^2}{\partial x^2} + V \right ] \Psi = i \hbar \frac{\partial}{\partial t} \Psi$$</p>
<p>Alternatively, inline math can be written by wrapping the formula with only a single <code>$</code>:</p>
<pre><code>This is inline: $\mathbf{y} = \mathbf{X}\boldsymbol\beta + \boldsymbol\varepsilon$
</code></pre>
<p>This is inline: $\mathbf{y} = \mathbf{X}\boldsymbol\beta + \boldsymbol\varepsilon$</p>
<h2 id="table">Table</h2>
<p>Code:</p>
<pre><code class="language-Markdown">| Command | Description |
| ------------------| ------------------------------ |
| `hugo` | Build your website. |
| `hugo serve -w` | View your website. |
</code></pre>
<p>Result:</p>
<table>
<thead>
<tr>
<th>Command</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>hugo</code></td>
<td>Build your website.</td>
</tr>
<tr>
<td><code>hugo serve -w</code></td>
<td>View your website.</td>
</tr>
</tbody>
</table>
<h2 id="alerts">Alerts</h2>
<p>Alerts are a useful feature that add side content such as tips, notes, or warnings to your articles. They are especially handy when writing educational tutorial-style articles. Use the corresponding shortcodes to enable alerts inside your content.
Missing <em>alert</em> templates:</p>
<p>This will display the following <em>note</em> block:</p>
<p>This will display the following <em>warning</em> block:</p>
<p>Here&rsquo;s some important information&hellip;</p>
<div class="footnotes">
<hr />
<ol>
<li id="fn:1">Footnote example.
<a class="footnote-return" href="#fnref:1"><sup>^</sup></a></li>
</ol>
</div></description>
</item>
<item>
<title>Manifold matching: Joint optimization of fidelity and commensurability</title>
<link>https://adalisan.github.io/publication/manmatch-jofc/</link>
<pubDate>Tue, 01 Sep 2015 00:00:00 +0000</pubDate>
<guid>https://adalisan.github.io/publication/manmatch-jofc/</guid>
<description></description>
</item>
</channel>
</rss>