<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2501 (Posts about linux)</title><link>http://www.project2501.ca/</link><description></description><atom:link href="http://www.project2501.ca/categories/linux.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Thu, 10 Aug 2023 01:58:08 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>GLC16 Python Workshop Materials</title><link>http://www.project2501.ca/posts/glc16-python-workshop-materials/</link><dc:creator>BW Keller</dc:creator><description>&lt;p&gt;The Sunday graduate student python workshop was a great success!
Huge thanks to Nathan Goldbaum and Andrew Pontzen for graciously 
providing the Jupyter notebooks they used in their talks. You can
download the slides and demo material from here.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.physics.mcmaster.ca/~kellerbw/GLC16_python/Keller.tar.gz"&gt;Ben Keller's Python Plotting Tricks &amp;amp; Astropy Demo&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.physics.mcmaster.ca/~kellerbw/GLC16_python/Goldbaum.tar.gz"&gt;Nathan Goldbaum's yt tutorial&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.physics.mcmaster.ca/~kellerbw/GLC16_python/Pontzen.ipynb"&gt;Andrew Pontzen's pynbody tutorial&lt;/a&gt;&lt;/p&gt;</description><category>guides</category><category>linux</category><category>simulations</category><guid>http://www.project2501.ca/posts/glc16-python-workshop-materials/</guid><pubDate>Wed, 22 Jun 2016 13:45:46 GMT</pubDate></item><item><title>Setting Up Your Laptop for the GLC16 Workshop</title><link>http://www.project2501.ca/posts/setting-up-your-laptop-for-the-glcc-workshop/</link><dc:creator>BW Keller</dc:creator><description>&lt;div&gt;&lt;p&gt;The 2016 Great Lakes Cosmology Conference will begin on Sunday, June 19, with a
graduate student workshop on scientific python, and two popular analysis
toolkits: pynbody and yt.  Pynbody is a simulation analysis tool for working
(primarily) with particle-based datasets, such as the outputs of SPH or N-body
simulations.  yt is a community-developed analysis and visualization toolkit for
volumetric data. yt has been applied mostly to astrophysical simulation data,
but it can be applied to many different types of data including seismology,
radio telescope data, weather simulations, and nuclear engineering simulations.&lt;/p&gt;
&lt;p&gt;The workshop will begin with an introduction to python and the Jupyter notebook,
and then have two in-depth presentations on yt and pynbody.  In order to make
things easy for you, it would be helpful if you brought a laptop with some tools
pre-installed, to follow along with the tutorials.  This post is a brief set of
instructions on how I'd recommend you set things up.  If you are a super class-A
hacker, and you can do all of this in your sleep, feel free to skip these
instructions.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.project2501.ca/posts/setting-up-your-laptop-for-the-glcc-workshop/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>guides</category><category>linux</category><category>simulations</category><guid>http://www.project2501.ca/posts/setting-up-your-laptop-for-the-glcc-workshop/</guid><pubDate>Mon, 13 Jun 2016 19:10:31 GMT</pubDate></item><item><title>Building Minimal Cosmological Zoomin ICs</title><link>http://www.project2501.ca/posts/building-minimal-cosmological-zoomin-ics/</link><dc:creator>BW Keller</dc:creator><description>&lt;div&gt;&lt;div class="cell border-box-sizing text_cell rendered"&gt;&lt;div class="prompt input_prompt"&gt;
&lt;/div&gt;&lt;div class="inner_cell"&gt;
&lt;div class="text_cell_render border-box-sizing rendered_html"&gt;
&lt;h2 id="Cubes,-Ellipsoids,-and-Convex-Hulls-are-non-optimal"&gt;Cubes, Ellipsoids, and Convex Hulls are non-optimal&lt;a class="anchor-link" href="http://www.project2501.ca/posts/building-minimal-cosmological-zoomin-ics/#Cubes,-Ellipsoids,-and-Convex-Hulls-are-non-optimal"&gt;¶&lt;/a&gt;&lt;/h2&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="cell border-box-sizing text_cell rendered"&gt;&lt;div class="prompt input_prompt"&gt;
&lt;/div&gt;&lt;div class="inner_cell"&gt;
&lt;div class="text_cell_render border-box-sizing rendered_html"&gt;
&lt;p&gt;When building a cosmological zoom-in simulation, the strategy is to run a low resolution, dark matter only simulation, select halos of interest, trace the particles that form that halo back to the initial conditions, and then build a new set of ICs with the regions that form the halo given higher resolution.  In order to minimize the number of high-resolution elements needed in the zoom-in IC, the volume that is refined should hug the particles of interest as tightly as possible.  Unfortunately, because the cosmic web is composed of sheets and filaments, the regions in an IC that need refinement can have complex shapes (they often look like &lt;a href="https://www.deliverance.co.uk/Images/MenuItemProduct/211/4066"&gt;prawn crackers&lt;/a&gt;).  This means that simple shapes that enclose the region (cubes, ellipsoids and convex hulls are often used) will frequently contain many times the volume just traced by the particles, giving much larger (and computationally expensive).  &lt;a href="https://youtu.be/bR3S690EF2U?t=10s"&gt;THERE HAS TO BE ANOTHER WAY!&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;a href="http://www.project2501.ca/posts/building-minimal-cosmological-zoomin-ics/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description><category>guides</category><category>linux</category><category>mathjax</category><category>simulations</category><guid>http://www.project2501.ca/posts/building-minimal-cosmological-zoomin-ics/</guid><pubDate>Mon, 29 Feb 2016 21:40:49 GMT</pubDate></item><item><title>RAMSES on the Scinet GPC</title><link>http://www.project2501.ca/posts/ramses-on-the-scinet-gpc/</link><dc:creator>BW Keller</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;a href="http://www.itp.uzh.ch/~teyssier/ramses/RAMSES.html"&gt;RAMSES&lt;/a&gt; is an AMR
MHD cosmological code.  This is a short guide on how to run it on the Scinet
GPC.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.project2501.ca/posts/ramses-on-the-scinet-gpc/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>guides</category><category>linux</category><category>ramses</category><category>simulations</category><guid>http://www.project2501.ca/posts/ramses-on-the-scinet-gpc/</guid><pubDate>Tue, 13 Oct 2015 18:23:04 GMT</pubDate></item><item><title>Making Mock Observations with Sunrise &amp; Docker</title><link>http://www.project2501.ca/posts/making-mock-observations-with-sunrise-docker/</link><dc:creator>BW Keller</dc:creator><description>&lt;p&gt;In a previous post, I described how&lt;/p&gt;
&lt;h2&gt;Setting up the docker instance&lt;/h2&gt;
&lt;h3&gt;Data volumes for file sharing&lt;/h3&gt;
&lt;p&gt;We will need somewhere to place our simulation outputs, configuration files, and
ultimately, the output of sunrise.  We will also need to let our docker
container read and write to this directory.  All you need to do in order to do
this is use the &lt;code&gt;-v host_directory:container_directory&lt;/code&gt; switch when starting
your container.  This will mount &lt;code&gt;host_directory&lt;/code&gt; in the docker container at the
&lt;code&gt;container_directory&lt;/code&gt; mountpoint.  In other words, we start our docker image
with something like this command:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code literal-block"&gt;docker run -t -i -v ~/sunrise_data:/sunrise_data bwkeller/sunrise:latest 
/bin/bash
&lt;/pre&gt;&lt;/div&gt;

&lt;h2&gt;&lt;/h2&gt;</description><category>docker</category><category>linux</category><category>sunrise</category><guid>http://www.project2501.ca/posts/making-mock-observations-with-sunrise-docker/</guid><pubDate>Wed, 16 Sep 2015 02:54:37 GMT</pubDate></item><item><title>Sunrise on Docker</title><link>http://www.project2501.ca/posts/sunrise-on-docker/</link><dc:creator>BW Keller</dc:creator><description>&lt;div&gt;&lt;p&gt;Sunrise is a popular "Monte-Carlo Radiation Transfer code for calculating
absorption and scattering of light in astrophysical situations" (it's hosted on
bitbucket &lt;a href="https://bitbucket.org/lutorm/sunrise"&gt;here&lt;/a&gt;).  Unfortunately, it is
notoriously finnicky to get installed, as it relies on specific point release
versions of nearly a dozen different libraries.  This is exactly the sort of
problem that &lt;a href="https://docker.com"&gt;Docker&lt;/a&gt; is supposed to solve, at scale:
distributing packages along with all of the library infrastructure they require
in one self-contained image.  If you are skeptical about docker's performance,
check out this paper IBM Research has published:  &lt;a href="http://domino.research.ibm.com/library/cyberdig.nsf/papers/0929052195DD819C85257D2300681E7B/%24File/rc25482.pdf"&gt;in nearly every metric, docker
performance is within 5% of native
bare-metal&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I'm going to build a docker image with a working
install of sunrise, that should save me and my fellow grad students days of
wrestling with angry, old C++ libraries.  Details below the fold.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.project2501.ca/posts/sunrise-on-docker/"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>docker</category><category>guides</category><category>linux</category><category>sunrise</category><guid>http://www.project2501.ca/posts/sunrise-on-docker/</guid><pubDate>Sat, 01 Aug 2015 15:42:19 GMT</pubDate></item><item><title>Dell XPS 13 2015 Developer Edition</title><link>http://www.project2501.ca/posts/dell-xps-13-2015-developer-edition/</link><dc:creator>BW Keller</dc:creator><description>&lt;div&gt;&lt;p&gt;What a pain in the butt this machine has been.  For a machine that comes with
Linux pre-installed, this thing sure doesn't play nicely with it.  Out of the
box, it comes with Ubuntu 14.04 installed, and mine came with the A03 BIOS.
When I first booted, the installation tool crashed halfway through, leaving me
with a semi-working system.  I had to re-flash the machine back to the factory
settings, and then try again (luckily it didn't crash the second round through).  &lt;/p&gt;
&lt;p&gt;Even after getting Ubuntu set up, there is a horrendous bug in the touchpad
driver that makes the cursor jerk wildly around every few minutes.  I tried to
solve this issue by upgrading the OS to 14.10, but that had the unfortunate
effect of nuking the networking and leaving the machine in an unbootable state!
YAY!  Finally, doing a fresh install of 15.04 actually got everything working.
With this, the thing is actually pretty sweet.  The HW is amazing, from the
screen to the battery to the keyboard.  After a day of frustration, I'm pretty
satisfied.  I'll be posting updates to my experiences here.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.project2501.ca/posts/dell-xps-13-2015-developer-edition/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>hardware</category><category>linux</category><category>xps13</category><guid>http://www.project2501.ca/posts/dell-xps-13-2015-developer-edition/</guid><pubDate>Thu, 28 May 2015 17:24:57 GMT</pubDate></item></channel></rss>