forked from alshedivat/al-folio
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update 2023-12-03-Dendrite-Inhibition.md
- Loading branch information
1 parent
a4c7c83
commit 69a2649
Showing
1 changed file
with
12 additions
and
321 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,336 +1,27 @@ | ||
--- | ||
layout: distill | ||
layout: post | ||
title: Dendrite Inhibition | ||
date: 2023-12-03 14:37:00-0400 | ||
description: Dendrite Inhibition Strategy | ||
tags: distill formatting | ||
tags: PhaseField | ||
categories: sample-posts | ||
giscus_comments: false | ||
date: 2023-01-01 | ||
featured: true | ||
|
||
authors: | ||
- name: Musanna Galib | ||
url: "https://scholar.google.com/citations?user=BwQZTTkAAAAJ&hl=en&oi=ao" | ||
affiliations: | ||
name: UBC, Vancouver | ||
- name: Okan K. Orhan | ||
url: "" | ||
affiliations: | ||
name: UBC, Vancouver | ||
- name: Mauricio Ponga | ||
url: "" | ||
affiliations: | ||
name: UBC, Vancouver | ||
|
||
bibliography: 2018-12-22-distill.bib | ||
|
||
# Optionally, you can add a table of contents to your post. | ||
# NOTES: | ||
# - make sure that TOC names match the actual section names | ||
# for hyperlinks within the post to work correctly. | ||
# - we may want to automate TOC generation in the future using | ||
# jekyll-toc plugin (https://github.com/toshimaru/jekyll-toc). | ||
toc: | ||
- name: Abstract | ||
- name: Equations | ||
# if a section has subsections, you can add them as follows: | ||
# subsections: | ||
# - name: Example Child Subsection 1 | ||
# - name: Example Child Subsection 2 | ||
- name: Citations | ||
- name: Footnotes | ||
- name: Code Blocks | ||
- name: Interactive Plots | ||
- name: Layouts | ||
- name: Other Typography? | ||
|
||
# Below is an example of injecting additional post-specific styles. | ||
# If you use this post as a template, delete this _styles block. | ||
_styles: > | ||
.fake-img { | ||
background: #bbb; | ||
border: 1px solid rgba(0, 0, 0, 0.1); | ||
box-shadow: 0 0px 4px rgba(0, 0, 0, 0.1); | ||
margin-bottom: 12px; | ||
} | ||
.fake-img p { | ||
font-family: monospace; | ||
color: white; | ||
text-align: left; | ||
margin: 12px 0; | ||
text-align: center; | ||
font-size: 16px; | ||
} | ||
related_posts: true | ||
datatable: true | ||
related_publications: Galib2020 | ||
|
||
--- | ||
## Abstract | ||
Aqueous zinc (Zn)-ion batteries (AZIB) are promising candidates for the next-generation energy store systems due to their high capacity and low cost. Despite their nominal performance, Zn anodes tend to rapidly develop dendrite and fracture, leading to substantial capacity loss and cycling stability failure. Well-controlled coating using organic–inorganic hybrid molecules is highly promising to substantially improve their chemo-mechanical stability without compromising their performance. We herein present a critical assessment of the chemical and mechanical stability of alucone-coated Zn surfaces using first-principles simulations. Negative adsorption energies indicate strong cohesive strengths between alucone and the selected Zn surfaces. Energetically favorable alucone coatings are further verified by charge transfer at interfaces as seen through Bader charge analysis. Negative surface stress profiles at the alucone-coated interface are mostly responsible for surface reconstruction. The contributions of surface elastic constants are dependent on the selection of slip planes and the thickness of the thin film. By considering plane stress conditions, we calculate the mechanical properties that indicate the ductility of the alucone-coated basal thin film. | ||
|
||
|
||
|
||
# Tweet | ||
An example of displaying a tweet: | ||
{% twitter https://twitter.com/galib_musanna/status/1624818564128710656 %} | ||
|
||
|
||
|
||
|
||
|
||
## Equations | ||
|
||
This theme supports rendering beautiful math in inline and display modes using [MathJax 3](https://www.mathjax.org/) engine. | ||
You just need to surround your math expression with `$$`, like `$$ E = mc^2 $$`. | ||
If you leave it inside a paragraph, it will produce an inline expression, just like $$ E = mc^2 $$. | ||
|
||
To use display mode, again surround your expression with `$$` and place it as a separate paragraph. | ||
Here is an example: | ||
|
||
$$ | ||
\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right) | ||
$$ | ||
|
||
Note that MathJax 3 is [a major re-write of MathJax](https://docs.mathjax.org/en/latest/upgrading/whats-new-3.0.html) that brought a significant improvement to the loading and rendering speed, which is now [on par with KaTeX](http://www.intmath.com/cg5/katex-mathjax-comparison.php). | ||
|
||
*** | ||
|
||
## Citations | ||
|
||
Citations are then used in the article body with the `<d-cite>` tag. | ||
The key attribute is a reference to the id provided in the bibliography. | ||
The key attribute can take multiple ids, separated by commas. | ||
|
||
The citation is presented inline like this: <d-cite key="gregor2015draw"></d-cite> (a number that displays more information on hover). | ||
If you have an appendix, a bibliography is automatically created and populated in it. | ||
|
||
Distill chose a numerical inline citation style to improve readability of citation dense articles and because many of the benefits of longer citations are obviated by displaying more information on hover. | ||
However, we consider it good style to mention author last names if you discuss something at length and it fits into the flow well — the authors are human and it’s nice for them to have the community associate them with their work. | ||
|
||
*** | ||
|
||
## Footnotes | ||
|
||
Just wrap the text you would like to show up in a footnote in a `<d-footnote>` tag. | ||
The number of the footnote will be automatically generated.<d-footnote>This will become a hoverable footnote.</d-footnote> | ||
|
||
*** | ||
|
||
## Code Blocks | ||
|
||
Syntax highlighting is provided within `<d-code>` tags. | ||
An example of inline code snippets: `<d-code language="html">let x = 10;</d-code>`. | ||
For larger blocks of code, add a `block` attribute: | ||
|
||
<d-code block language="javascript"> | ||
var x = 25; | ||
function(x) { | ||
return x * x; | ||
} | ||
</d-code> | ||
|
||
**Note:** `<d-code>` blocks do not look good in the dark mode. | ||
You can always use the default code-highlight using the `highlight` liquid tag: | ||
|
||
{% highlight javascript %} | ||
var x = 25; | ||
function(x) { | ||
return x * x; | ||
} | ||
{% endhighlight %} | ||
|
||
*** | ||
|
||
## Interactive Plots | ||
|
||
You can add interative plots using plotly + iframes :framed_picture: | ||
|
||
<div class="l-page"> | ||
<iframe src="{{ '/assets/plotly/demo.html' | relative_url }}" frameborder='0' scrolling='no' height="500px" width="100%" style="border: 1px dashed grey;"></iframe> | ||
</div> | ||
|
||
The plot must be generated separately and saved into an HTML file. | ||
To generate the plot that you see above, you can use the following code snippet: | ||
|
||
{% highlight python %} | ||
import pandas as pd | ||
import plotly.express as px | ||
df = pd.read_csv( | ||
'https://raw.githubusercontent.com/plotly/datasets/master/earthquakes-23k.csv' | ||
) | ||
fig = px.density_mapbox( | ||
df, | ||
lat='Latitude', | ||
lon='Longitude', | ||
z='Magnitude', | ||
radius=10, | ||
center=dict(lat=0, lon=180), | ||
zoom=0, | ||
mapbox_style="stamen-terrain", | ||
) | ||
fig.show() | ||
fig.write_html('assets/plotly/demo.html') | ||
{% endhighlight %} | ||
|
||
*** | ||
|
||
## Details boxes | ||
|
||
Details boxes are collapsible boxes which hide additional information from the user. They can be added with the `details` liquid tag: | ||
|
||
{% details Click here to know more %} | ||
Additional details, where math $$ 2x - 1 $$ and `code` is rendered correctly. | ||
{% enddetails %} | ||
|
||
*** | ||
|
||
## Layouts | ||
|
||
The main text column is referred to as the body. | ||
It is the assumed layout of any direct descendants of the `d-article` element. | ||
|
||
<div class="fake-img l-body"> | ||
<p>.l-body</p> | ||
</div> | ||
|
||
For images you want to display a little larger, try `.l-page`: | ||
|
||
<div class="fake-img l-page"> | ||
<p>.l-page</p> | ||
</div> | ||
|
||
All of these have an outset variant if you want to poke out from the body text a little bit. | ||
For instance: | ||
|
||
<div class="fake-img l-body-outset"> | ||
<p>.l-body-outset</p> | ||
</div> | ||
|
||
<div class="fake-img l-page-outset"> | ||
<p>.l-page-outset</p> | ||
</div> | ||
|
||
Occasionally you’ll want to use the full browser width. | ||
For this, use `.l-screen`. | ||
You can also inset the element a little from the edge of the browser by using the inset variant. | ||
|
||
<div class="fake-img l-screen"> | ||
<p>.l-screen</p> | ||
</div> | ||
<div class="fake-img l-screen-inset"> | ||
<p>.l-screen-inset</p> | ||
</div> | ||
In this study, | ||
|
||
The final layout is for marginalia, asides, and footnotes. | ||
It does not interrupt the normal flow of `.l-body` sized text except on mobile screen sizes. | ||
|
||
<div class="fake-img l-gutter"> | ||
<p>.l-gutter</p> | ||
<div class="row mt-3"> | ||
<div class="col-sm mt-3 mt-md-0"> | ||
{% include video.html path="https://www.youtube.com/embed/4Q30xnX-hcc?si=nMsWbI9-BakjvUfX" class="img-fluid rounded z-depth-1" %} | ||
</div> | ||
</div> | ||
|
||
*** | ||
|
||
## Other Typography? | ||
|
||
Emphasis, aka italics, with *asterisks* (`*asterisks*`) or _underscores_ (`_underscores_`). | ||
|
||
Strong emphasis, aka bold, with **asterisks** or __underscores__. | ||
|
||
Combined emphasis with **asterisks and _underscores_**. | ||
|
||
Strikethrough uses two tildes. ~~Scratch this.~~ | ||
|
||
1. First ordered list item | ||
2. Another item | ||
⋅⋅* Unordered sub-list. | ||
1. Actual numbers don't matter, just that it's a number | ||
⋅⋅1. Ordered sub-list | ||
4. And another item. | ||
|
||
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown). | ||
|
||
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅ | ||
⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅ | ||
⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.) | ||
|
||
* Unordered list can use asterisks | ||
- Or minuses | ||
+ Or pluses | ||
|
||
[I'm an inline-style link](https://www.google.com) | ||
|
||
[I'm an inline-style link with title](https://www.google.com "Google's Homepage") | ||
|
||
[I'm a reference-style link][Arbitrary case-insensitive reference text] | ||
|
||
[I'm a relative reference to a repository file](../blob/master/LICENSE) | ||
|
||
[You can use numbers for reference-style link definitions][1] | ||
|
||
Or leave it empty and use the [link text itself]. | ||
|
||
URLs and URLs in angle brackets will automatically get turned into links. | ||
http://www.example.com or <http://www.example.com> and sometimes | ||
example.com (but not on Github, for example). | ||
|
||
Some text to show that the reference links can follow later. | ||
|
||
[arbitrary case-insensitive reference text]: https://www.mozilla.org | ||
[1]: http://slashdot.org | ||
[link text itself]: http://www.reddit.com | ||
|
||
Here's our logo (hover to see the title text): | ||
|
||
Inline-style: | ||
![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1") | ||
|
||
Reference-style: | ||
![alt text][logo] | ||
|
||
[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2" | ||
|
||
Inline `code` has `back-ticks around` it. | ||
|
||
```javascript | ||
var s = "JavaScript syntax highlighting"; | ||
alert(s); | ||
``` | ||
|
||
```python | ||
s = "Python syntax highlighting" | ||
print s | ||
``` | ||
|
||
``` | ||
No language indicated, so no syntax highlighting. | ||
But let's throw in a <b>tag</b>. | ||
``` | ||
|
||
Colons can be used to align columns. | ||
|
||
| Tables | Are | Cool | | ||
| ------------- |:-------------:| -----:| | ||
| col 3 is | right-aligned | $1600 | | ||
| col 2 is | centered | $12 | | ||
| zebra stripes | are neat | $1 | | ||
|
||
There must be at least 3 dashes separating each header cell. | ||
The outer pipes (|) are optional, and you don't need to make the | ||
raw Markdown line up prettily. You can also use inline Markdown. | ||
|
||
Markdown | Less | Pretty | ||
--- | --- | --- | ||
*Still* | `renders` | **nicely** | ||
1 | 2 | 3 | ||
|
||
> Blockquotes are very handy in email to emulate reply text. | ||
> This line is part of the same quote. | ||
Quote break. | ||
|
||
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote. | ||
|
||
|
||
Here's a line for us to start with. | ||
|
||
This line is separated from the one above by two newlines, so it will be a *separate paragraph*. | ||
|
||
This line is also a separate paragraph, but... | ||
This line is only separated by a single newline, so it's a separate line in the *same paragraph*. |