Page Not Found
Abstract
Sorry, but the page you were trying to view does not exist.
A variety of common markup showing how the theme styles them.
Single line blockquote:
Quotes are cool.
| Entry | Item | Â |
|---|---|---|
| John Doe | 2016 | Description of the item in the list |
| Jane Doe | 2019 | Description of the item in the list |
| Doe Doe | 2022 | Description of the item in the list |
| Header1 | Header2 | Header3 |
|---|---|---|
| cell1 | cell2 | cell3 |
| cell4 | cell5 | cell6 |
| cell1 | cell2 | cell3 |
| cell4 | cell5 | cell6 |
| Foot1 | Foot2 | Foot3 |
Make any link standout more when applying the .btn class.
Watch out! You can also add notices by appending {: .notice} to a paragraph.
This is an example of a link.
The abbreviation CSS stands for âCascading Style Sheetsâ.
âCode is poetry.â âAutomattic
You will learn later on in these tests that word-wrap: break-word; will be your best friend.
This tag will let you strikeout text.
The emphasize tag should italicize text.
This tag should denote inserted text.
This scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.
This tag styles large blocks of code.
.post-title {
margin: 0 0 5px;
font-weight: bold;
font-size: 38px;
line-height: 1.2;
and here's a line of some really, really, really, really long text, just to see how the PRE tag handles it and to find out how it overflows;
}
Developers, developers, developersâŠ
âSteve Ballmer
This tag shows bold text.
Getting our science styling on with H2O, which should push the â2â down.
Still sticking with science and Isaac Newtonâs E = MC2, which should lift the 2 up.
This allows you to denote variables.
Sorry, but the page you were trying to view does not exist.
A variety of common markup showing how the theme styles them.
Single line blockquote:
Quotes are cool.
| Entry | Item | Â |
|---|---|---|
| John Doe | 2016 | Description of the item in the list |
| Jane Doe | 2019 | Description of the item in the list |
| Doe Doe | 2022 | Description of the item in the list |
| Header1 | Header2 | Header3 |
|---|---|---|
| cell1 | cell2 | cell3 |
| cell4 | cell5 | cell6 |
| cell1 | cell2 | cell3 |
| cell4 | cell5 | cell6 |
| Foot1 | Foot2 | Foot3 |
Make any link standout more when applying the .btn class.
Watch out! You can also add notices by appending {: .notice} to a paragraph.
This is an example of a link.
The abbreviation CSS stands for âCascading Style Sheetsâ.
âCode is poetry.â âAutomattic
You will learn later on in these tests that word-wrap: break-word; will be your best friend.
This tag will let you strikeout text.
The emphasize tag should italicize text.
This tag should denote inserted text.
This scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.
This tag styles large blocks of code.
.post-title {
margin: 0 0 5px;
font-weight: bold;
font-size: 38px;
line-height: 1.2;
and here's a line of some really, really, really, really long text, just to see how the PRE tag handles it and to find out how it overflows;
}
Developers, developers, developersâŠ
âSteve Ballmer
This tag shows bold text.
Getting our science styling on with H2O, which should push the â2â down.
Still sticking with science and Isaac Newtonâs E = MC2, which should lift the 2 up.
This allows you to denote variables.
{% include base_path %} {% for post in site.pages %} {% include archive-single.html %} {% endfor %}
{% include base_path %} {% include group-by-array collection=site.posts field=âcategoriesâ %}
{% for category in group_names %} {% assign posts = group_items[forloop.index0] %}
{% for post in posts %} {% include archive-single.html %} {% endfor %} {% endfor %}
{% include base_path %} {% capture written_label %}âNoneâ{% endcapture %}
{% for collection in site.collections %} {% unless collection.output == false or collection.label == âpostsâ %} {% capture label %}{{ collection.label }}{% endcapture %} {% if label != written_label %} <h2 id="{{ label | slugify }}" class="archive__subtitle">{{ label }}</h2> {% capture written_label %}{{ label }}{% endcapture %} {% endif %} {% endunless %} {% for post in collection.docs %} {% unless collection.output == false or collection.label == âpostsâ %} {% include archive-single.html %} {% endunless %} {% endfor %} {% endfor %}
{% include base_path %}
{% include base_path %}
Bem-vindo Ă minha pĂĄgina!
Meu nome Ă© Gustavo, sou um fĂsico nascido em Minas Gerais. Atualmente estou concluindo meu doutorado e iniciarei uma posição de pĂłs-doutorado conjunta no Fermilab e na Northwestern University em 1Âș de outubro.
Minha pesquisa se concentra nas oportunidades Ășnicas que os neutrinos oferecem para investigar a fĂsica alĂ©m do Modelo PadrĂŁo (MP). Diversas questĂ”es em aberto no MP, como a origem das massas dos neutrinos e se eles sĂŁo partĂculas de Dirac ou de Majorana, estĂŁo profundamente ligadas aos mistĂ©rios do setor de neutrinos. AlĂ©m disso, os neutrinos funcionam como interferĂŽmetros naturais devido Ă s suas oscilaçÔes, o que proporciona uma poderosa janela para estudar suas propriedades e possibilita a aplicação de tĂ©cnicas de diferentes ĂĄreas da pesquisa Ă fĂsica de partĂculas, uma conexĂŁo interdisciplinar que tenho grande interesse em explorar com mais profundidade. TambĂ©m me interesso por aplicaçÔes inovadoras, como o uso de interferĂŽmetros atĂŽmicos na fĂsica de partĂculas e o estudo de modelos de decoerĂȘncia para investigar setores ocultos.
AlĂ©m disso, tenho interesse amplo no estudo de outros setores desconhecidos, desde a investigação da natureza da matĂ©ria escura atĂ© a possĂvel existĂȘncia de estados alĂ©m do MP. Pretendo contribuir com o campo propondo abordagens inovadoras para essas questĂ”es, atuando na interface entre teoria e experimento e integrando ideias de diferentes ĂĄreas de forma criativa.
Welcome to my page!
My name is Gustavo, and Iâm a physicist from Brazil. I am currently a postdoctoral researcher at Fermilab and Northwestern University.
My research focuses on the unique opportunities neutrinos offer for probing physics beyond the Standard Model (SM). Several open questions in the SM, such as the origin of neutrino masses and whether neutrinos are Dirac or Majorana particles, are deeply rooted in the mysteries of the neutrino sector. Neutrinos also serve as natural interferometers due to their oscillations, providing a powerful portal into their properties and enabling the application of techniques from diverse research fields to particle physics, an interdisciplinary connection Iâm eager to explore further. I am also interested in novel applications, including the use of atomic interferometers in particle physics and the study of decoherence models to investigate hidden sectors.
In addition, I am broadly interested in searches for dark sectors, from exploring the nature of dark matter to probing the possible existence of heavy sterile states. I aim to contribute to the field by proposing innovative approaches to these questions, working at the intersection of theory and experiment, and integrating ideas across disciplines in creative ways.
/*
@import âvendor/breakpoint/breakpointâ,
"themes",
"theme/default",
"theme/dark",
"include/mixins",
"vendor/susy/susy",
"layout/reset",
"layout/base",
"include/utilities",
"layout/tables",
"layout/buttons",
"layout/notices",
"layout/masthead",
"layout/navigation",
"layout/footer",
"syntax",
"layout/forms",
"layout/page",
"layout/archive",
"layout/sidebar",
"vendor/font-awesome/fontawesome",
"vendor/font-awesome/solid",
"vendor/font-awesome/brands" ;
{% include toc %}
Your CV can be written using either Markdown (preview) or generated via JSON (preview) and the layouts are slightly different. You can update the path to the one being used in _data/navigation.yml with the JSON formatted CV being hidden by default.
Support for MathJax (version 3.* via jsDelivr, documentation) is included in the template:
\[\displaylines{ \nabla \cdot E= \frac{\rho}{\epsilon_0} \\\ \nabla \cdot B=0 \\\ \nabla \times E= -\partial_tB \\\ \nabla \times B = \mu_0 \left(J + \varepsilon_0 \partial_t E \right) }\]The default delimiters of $$...$$ and \\[...\\] are supported for displayed mathematics, while \\(...\\) should be used for in-line mathematics (ex., \(a^2 + b^2 = c^2\))
Note that since Academic Pages uses Markdown which cases some interference with MathJax and LaTeX for escaping characters and new lines, although some workarounds exist. In some cases, such as when you are including MathJax in a citation field for publications, it may be necessary to use \(...\) for inline delineation.
Academic Pages includes support for Mermaid diagrams (version 11.* via jsDelivr) and in addition to their tutorials and GitHub documentation the basic syntax is as follows:
```mermaid
graph LR
A-->B
```
Which produces the following plot with the default theme applied:
graph LR
A-->B
While a more advanced plot with the forest theme applied looks like the following:
---
config:
theme: 'forest'
---
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
Academic Pages includes support for Plotly diagrams via a hook in the Markdown code elements, although those that are comfortable with HTML and JavaScript can also access it via those routes.
In order to render a Plotly plot via Markdown the relevant plot data need to be added as follows:
```plotly
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"type": "scatter"
},
{
"x": [1, 2, 3, 4],
"y": [16, 5, 11, 9],
"type": "scatter"
}
]
}
```
Important! Since the data is parsed as JSON all of the keys will need to be quoted for the plot to render. The use of a tool like JSONLint to check syntax is highly recommended.
Which produces the following:
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"type": "scatter"
},
{
"x": [1, 2, 3, 4],
"y": [16, 5, 11, 9],
"type": "scatter"
}
]
}
Essentially what is taking place is that the Plotly attributes are being taken from the code block as JSON data, parsed, and passed to Plotly along with a theme that matches the current site theme (i.e., a light theme, or a dark theme). This allows all plots that can be described via the data attribute to rendered with some limitations for the theme of the plot.
{
"data": [
{
"x": [1, 2, 3, 4, 5],
"y": [1, 6, 3, 6, 1],
"mode": "markers",
"type": "scatter",
"name": "Team A",
"text": ["A-1", "A-2", "A-3", "A-4", "A-5"],
"marker": { "size": 12 }
},
{
"x": [1.5, 2.5, 3.5, 4.5, 5.5],
"y": [4, 1, 7, 1, 4],
"mode": "markers",
"type": "scatter",
"name": "Team B",
"text": ["B-a", "B-b", "B-c", "B-d", "B-e"],
"marker": { "size": 12 }
}
],
"layout": {
"xaxis": {
"range": [ 0.75, 5.25 ]
},
"yaxis": {
"range": [0, 8]
},
"title": {"text": "Data Labels Hover"}
}
}
{
"data": [{
"x": [1, 2, 3],
"y": [4, 5, 6],
"type": "scatter"
},
{
"x": [20, 30, 40],
"y": [50, 60, 70],
"xaxis": "x2",
"yaxis": "y2",
"type": "scatter"
}],
"layout": {
"grid": {
"rows": 1,
"columns": 2,
"pattern": "independent"
},
"title": {
"text": "Simple Subplot"
}
}
}
{
"data": [{
"z": [[10, 10.625, 12.5, 15.625, 20],
[5.625, 6.25, 8.125, 11.25, 15.625],
[2.5, 3.125, 5.0, 8.125, 12.5],
[0.625, 1.25, 3.125, 6.25, 10.625],
[0, 0.625, 2.5, 5.625, 10]],
"type": "contour"
}],
"layout": {
"title": {
"text": "Basic Contour Plot"
}
}
}
Academic Pages uses kramdown for Markdown rendering, which has some differences from other Markdown implementations such as GitHubâs. In addition to this guide, please see the kramdown Syntax page for full documentation.
Single line blockquote:
Quotes are cool.
| Entry | Item | Â |
|---|---|---|
| John Doe | 2016 | Description of the item in the list |
| Jane Doe | 2019 | Description of the item in the list |
| Doe Doe | 2022 | Description of the item in the list |
| Header1 | Header2 | Header3 |
|---|---|---|
| cell1 | cell2 | cell3 |
| cell4 | ce | Â |
| ll5 | cell6 | Â |
| cell1 | cell2 | cell3 |
| cell4 | cell5 | cell6 |
| Foot1 | Foot2 | Foot3 |
Make any link standout more when applying the .btn class.
Basic notices or call-outs are supported using the following syntax:
**Watch out!** You can also add notices by appending `{: .notice}` to the line following paragraph.
{: .notice}
which wil render as:
Watch out! You can also add notices by appending {: .notice} to the line following paragraph.
Footnotes can be useful for clarifying points in the text, or citing information.1 Markdown support numeric footnotes, as well as text as long as the values are unique.2
This is the regular text.[^1] This is more regular text.[^note]
[^1]: This is the footnote itself.
[^note]: This is another footnote.
This is an example of a link.
The abbreviation CSS stands for âCascading Style Sheetsâ.
âCode is poetry.â âAutomattic
You will learn later on in these tests that word-wrap: break-word; will be your best friend.
You can also write larger blocks of code with syntax highlighting supported for some languages, such as Python:
print('Hello World!')
or R:
print("Hello World!", quote = FALSE)
The HTML <details> tag works well with Markdown and allows you to include collapsible sections, see W3Schools for more information on how to use the tag.
The source code:
<details>
<summary>Collapsed by default</summary>
This section was collapsed by default!
</details>
Or, you can leave a section open by default by including the open attribute in the tag:
The emphasize tag should italicize text.
This tag should denote inserted text.
This scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.
This tag styles large blocks of code.
.post-title {
margin: 0 0 5px;
font-weight: bold;
font-size: 38px;
line-height: 1.2;
and here's a line of some really, really, really, really long text, just to see how the PRE tag handles it and to find out how it overflows;
}
Developers, developers, developersâŠ
âSteve Ballmer
This tag will let you strikeout text.
This tag shows bold text.
Getting our science styling on with H2O, which should push the â2â down.
Still sticking with science and Isaac Newtonâs E = MC2, which should lift the 2 up.
This allows you to denote variables.
Footnotes
The footnotes in the page will be returned following this line, return to the section on Markdown Footnotes.
This is a page not in the menu. You can use markdown in this page.
{% include base_path %} {% for post in site.pages %} {% include archive-single.html %} {% endfor %}
{% include base_path %}
{% for post in site.portfolio %} {% include archive-single.html %} {% endfor %}
{% if site.author.googlescholar %}
{% endif %}
{% include base_path %}
{% if site.publication_category %} {% for category in site.publication_category %} {% assign title_shown = false %} {% for post in site.publications reversed %} {% if post.category != category[0] %} {% continue %} {% endif %} {% unless title_shown %} <h2>{{ category[1].title }}</h2><hr /> {% assign title_shown = true %} {% endunless %} {% include archive-single.html %} {% endfor %} {% endfor %} {% else %} {% for post in site.publications reversed %} {% include archive-single.html %} {% endfor %} {% endif %}
{% if site.author.googlescholar %}
{% endif %}
{% include base_path %}
{% if site.publication_category %} {% for category in site.publication_category %} {% assign title_shown = false %} {% for post in site.publications reversed %} {% if post.category != category[0] %} {% continue %} {% endif %} {% unless title_shown %} <h2>{{ category[1].title }}</h2><hr /> {% assign title_shown = true %} {% endunless %} {% include archive-single.html %} {% endfor %} {% endfor %} {% else %} {% for post in site.publications reversed %} {% include archive-single.html %} {% endfor %} {% endif %}
{% include base_path %}
A list of all the posts and pages found on the site. For you robots out there, there is an XML version available for digesting as well.
{% for post in site.pages %} {% include archive-single.html %} {% endfor %}
{% for post in site.posts %} {% include archive-single.html %} {% endfor %}
{% capture written_label %}âNoneâ{% endcapture %}
{% for collection in site.collections %} {% unless collection.output == false or collection.label == âpostsâ %} {% capture label %}{{ collection.label }}{% endcapture %} {% if label != written_label %}
{% capture written_label %}{{ label }}{% endcapture %} {% endif %} {% endunless %} {% for post in collection.docs %} {% unless collection.output == false or collection.label == âpostsâ %} {% include archive-single.html %} {% endunless %} {% endfor %} {% endfor %}
{% include base_path %} {% include group-by-array collection=site.posts field=âtagsâ %}
{% for tag in group_names %} {% assign posts = group_items[forloop.index0] %}
{% for post in posts %} {% include archive-single.html %} {% endfor %} {% endfor %}
This map is generated from a Jupyter Notebook file in talkmap.ipynb, which mines the location fields in the .md files in _talks/.
{% if site.talkmap_link == true %}
See a map of all the places I've given a talk!
{% endif %}
{% for post in site.talks reversed %} {% include archive-single-talk.html %} {% endfor %}
{% if site.talkmap_link == true %}
See a map of all the places I've given a talk!
{% endif %}
{% for post in site.talks reversed %} {% include archive-single-talk.html %} {% endfor %}
{% include base_path %}
{% for post in site.teaching reversed %} {% include archive-single.html %} {% endfor %}
{% include base_path %} {% include toc %}
The privacy of my visitors is extremely important. This Privacy Policy outlines the types of personal information that is received and collected and how it is used.
First and foremost, I will never share your email address or any other personal information to anyone without your direct consent.
Like many other websites, this site uses log files to help learn about when, from where, and how often traffic flows to this site. The information in these log files include:
All of this information is not linked to anything that is personally identifiable.
When you visit this site âconvenienceâ cookies are stored on your computer when you submit a comment to help you log in faster to Disqus the next time you leave a comment.
Third-party advertisers may also place and read cookies on your browser and/or use web beacons to collect information. This site has no access or control over these cookies. You should review the respective privacy policies on any and all third-party ad servers for more information regarding their practices and how to opt-out.
If you wish to disable cookies, you may do so through your web browser options. Instructions for doing so can be found on the specific web browsersâ websites.
Google Analytics is a web analytics tool I use to help understand how visitors engage with this website. It reports website trends using cookies and web beacons without identifying individual visitors. You can read Google Analytics Privacy Policy.
{% include base_path %} {% capture written_year %}âNoneâ{% endcapture %} {% for post in site.posts %} {% if post.lang == page.lang %} {% capture year %}{{ post.date | date: â%Yâ }}{% endcapture %} {% if year != written_year %} <h2 id="{{ year | slugify }}" class="archive__subtitle">{{ year }}</h2> {% capture written_year %}{{ year }}{% endcapture %} {% endif %} {% include archive-single-blog.html %} {% endif %} {% endfor %}
{% include base_path %} {% capture written_year %}âNoneâ{% endcapture %} {% for post in site.posts %} {% if post.lang == page.lang %} {% capture year %}{{ post.date | date: â%Yâ }}{% endcapture %} {% if year != written_year %} <h2 id="{{ year | slugify }}" class="archive__subtitle">{{ year }}</h2> {% capture written_year %}{{ year }}{% endcapture %} {% endif %} {% include archive-single-blog.html %} {% endif %} {% endfor %}
{â/resume-jsonâ:âhttps://gfsalves.github.io/cv-json/â,â/resumeâ:âhttps://gfsalves.github.io/en/cv/â,â/â:âhttps://gfsalves.github.io/en/â,â/md/â:âhttps://gfsalves.github.io/markdown/â,â/markdown.htmlâ:âhttps://gfsalves.github.io/markdown/â,â/nmp/â:âhttps://gfsalves.github.io/non-menu-page/â,â/nmp.htmlâ:âhttps://gfsalves.github.io/non-menu-page/â,â/wordpress/blog-posts/â:âhttps://gfsalves.github.io/en/blog-posts/â}
These .ipynb files are Jupyter notebook files that convert a TSV containing structured data about talks (talks.tsv) or presentations (presentations.tsv) into individual markdown files that will be properly formatted for the academicpages template. The notebooks contain a lot of documentation about the process. The .py files are pure python that do the same things if they are executed in a terminal, they just donât have pretty documentation.
| <?xml version=â1.0â encoding=âutf-8â?>{% if page.xsl %}<?xml-stylesheet type=âtext/xmlâ href=â{{ â/feed.xslt.xmlâ | absolute_url }}â?>{% endif %}<feed xmlns=âhttp://www.w3.org/2005/Atomâ {% if site.lang %}xml:lang=â{{ site.lang }}â{% endif %}> |
absolute_url }}â rel=âselfâ type=âapplication/atom+xmlâ /><link href=â{{ â/â | absolute_url }}â rel=âalternateâ type=âtext/htmlâ {% if site.lang %}hreflang=â{{ site.lang }}â {% endif %}/> |
date_to_xmlschema }}</updated> |
absolute_url | xml_escape }}</id>{% assign title = site.title | default: site.name %}{% if page.collection != âpostsâ %}{% assign collection = page.collection | capitalize %}{% assign title = title | append: â | â | append: collection %}{% endif %}{% if page.category %}{% assign category = page.category | capitalize %}{% assign title = title | append: â | â | append: category %}{% endif %}{% if title %} |
smartify | xml_escape }}</title>{% endif %}{% if site.description %} |
xml_escape }}</subtitle>{% endif %}{% if site.author %} |
default: site.author | xml_escape }}</name>{% if site.author.email %} |
xml_escape }}</email>{% endif %}{% if site.author.uri %} |
xml_escape }}</uri>{% endif %}</author>{% endif %}{% if page.tags %}{% assign posts = site.tags[page.tags] %}{% else %}{% assign posts = site[page.collection] %}{% endif %}{% if page.category %}{% assign posts = posts | where: âcategoriesâ, page.category %}{% endif %}{% unless site.show_drafts %}{% assign posts = posts | where_exp: âpostâ, âpost.draft != trueâ %}{% endunless %}{% assign posts = posts | sort: âdateâ | reverse %}{% assign posts_limit = site.feed.posts_limit | default: 10 %}{% for post in posts limit: posts_limit %}<entry{% if post.lang %}{{â â}}xml:lang=â{{ post.lang }}â{% endif %}>{% assign post_title = post.title | smartify | strip_html | normalize_whitespace | xml_escape %} |
absolute_url }}â rel=âalternateâ type=âtext/htmlâ title=â{{ post_title }}â /> |
date_to_xmlschema }}</published> |
default: post.date | date_to_xmlschema }}</updated> |
absolute_url | xml_escape }}</id>{% assign excerpt_only = post.feed.excerpt_only | default: site.feed.excerpt_only %}{% unless excerpt_only %}<content type=âhtmlâ xml:base=â{{ post.url | absolute_url | xml_escape }}â><![CDATA[{{ post.content | strip }}]]></content>{% endunless %}{% assign post_author = post.author | default: post.authors[0] | default: site.author %}{% assign post_author = site.data.authors[post_author] | default: post_author %}{% assign post_author_email = post_author.email | default: nil %}{% assign post_author_uri = post_author.uri | default: nil %}{% assign post_author_name = post_author.name | default: post_author %} |
default: ââ | xml_escape }}</name>{% if post_author_email %} |
xml_escape }}</email>{% endif %}{% if post_author_uri %} |
xml_escape }}</uri>{% endif %}</author>{% if post.category %}<category term=â{{ post.category | xml_escape }}â />{% elsif post.categories %}{% for category in post.categories %}<category term=â{{ category | xml_escape }}â />{% endfor %}{% endif %}{% for tag in post.tags %}<category term=â{{ tag | xml_escape }}â />{% endfor %}{% assign post_summary = post.description | default: post.excerpt %}{% if post_summary and post_summary != empty %}<summary type="html"><![CDATA[{{ post_summary | strip_html | normalize_whitespace }}]]></summary>{% endif %}{% assign post_image = post.image.path | default: post.image %}{% if post_image %}{% unless post_image contains â://â %}{% assign post_image = post_image | absolute_url %}{% endunless %}<media:thumbnail xmlns:media=âhttp://search.yahoo.com/mrss/â url=â{{ post_image | xml_escape }}â /><media:content medium=âimageâ url=â{{ post_image | xml_escape }}â xmlns:media=âhttp://search.yahoo.com/mrss/â />{% endif %}</entry>{% endfor %}</feed> |
<?xml version=â1.0â encoding=âUTF-8â?> {% if page.xsl %}<?xml-stylesheet type=âtext/xslâ href=â{{ â/sitemap.xslâ | absolute_url }}â?> {% endif %}
{% if doc.last_modified_at or doc.date %}
{% if page.last_modified_at %}
</url> {% endfor %}</urlset>