<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Academia on bocklund.io</title>
		<link>https://bocklund.io/tags/academia/</link>
		<description>Recent content in Academia on bocklund.io</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>Brandon Bocklund</copyright>
		
		
			<lastBuildDate>Sun, 29 Jul 2018 00:00:00 -0400</lastBuildDate>
		
			<atom:link href="https://bocklund.io/tags/academia/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Why Jupyter Notebooks Won&#39;t Replace Academic Papers</title>
				<link>https://bocklund.io/jupyter-notebooks-papers/</link>
				<pubDate>Sun, 29 Jul 2018 00:00:00 -0400</pubDate>
				<guid>https://bocklund.io/jupyter-notebooks-papers/</guid>
				<description>&lt;p&gt;Recently there has been some buzz around Jupyter Notebooks in science, especially in light of the LIGO team sharing their &lt;a href=&#34;https://losc.ligo.org/tutorials/&#34;&gt;detection and analysis of gravitational waves&lt;/a&gt; in Jupyter Notebooks. Others have claimed that Jupyter Notebooks will &lt;a href=&#34;https://www.theatlantic.com/science/archive/2018/04/the-scientific-paper-is-obsolete/556676/&#34;&gt;render traditional academic journal articles obsolete&lt;/a&gt;. The notebook or literate programming format improves on the reproducibility and disseminating of scientific work, however several key factors limit the notebook as a way to communicate science. In the article, I&#39;ll touch on these issues and explain why I believe that the current model of sharing computational science is here to stay.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Atomate - reproducible computational materials science workflows in Python</title>
				<link>https://bocklund.io/atomate-paper/</link>
				<pubDate>Sat, 05 Aug 2017 00:00:00 -0400</pubDate>
				<guid>https://bocklund.io/atomate-paper/</guid>
				<description>&lt;p&gt;If you&#39;ve done any computational work on a high-performance computing system, odds are you are very familiar with shell scripting and running code in at least 3 different languages that was passed down through the years. You know the theory of how it all works, but can never find the time to weed through, organize and update someone else&#39;s FORTRAN code (that was out of date when it was written in 2002) to use the latest techniques. &lt;a href=&#34;https://hackingmaterials.lbl.gov/atomate/&#34;&gt;Atomate&lt;/a&gt; aims to solve these problems by leveraging the community developed materials science tools and analyses in &lt;a href=&#34;http://pymatgen.org/&#34;&gt;pymatgen&lt;/a&gt; and the workflow management/database creation of &lt;a href=&#34;https://materialsproject.github.io/fireworks/&#34;&gt;FireWorks&lt;/a&gt; to document and allow for easy execution of community standardized and easily customizable workflows managed and written using Python.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Getting Papers Remotely</title>
				<link>https://bocklund.io/getting-papers-remotely/</link>
				<pubDate>Thu, 06 Jul 2017 00:00:00 -0400</pubDate>
				<guid>https://bocklund.io/getting-papers-remotely/</guid>
				<description>&lt;p&gt;Whether you are at home or traveling to a conference, it can be helpful to have access to all of the literature online that you would have at your institution.&#xA;This article covers some easy and practical ways to connect to your institution&#39;s library easily.&#xA;Some of these techniques work on any website, and others are for Google Scholar, or with the Alfred app for the Mac.&#xA;The examples here are specifically for connecting to the Penn State library, but the methods are general enough to work at many or all institutions.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
