<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Peter Steinbach on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/author/peter-steinbach/</link><description>Recent content in Peter Steinbach on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/author/peter-steinbach/index.xml" rel="self" type="application/rss+xml"/><item><title>Incubator Lesson Spotlight: Introduction to Deep Learning</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2022/05/incubator-lesson-spotlight-deep-learning/</link><pubDate>Wed, 11 May 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2022/05/incubator-lesson-spotlight-deep-learning/</guid><description>&lt;p>The Incubator Lesson Spotlight highlights a lesson under development by our community in &lt;a href="https://github.com/carpentries-incubator/">The Carpentries Incubator&lt;/a>. In this edition, we look at the progress being made on &lt;a href="https://carpentries-incubator.github.io/deep-learning-intro">the &lt;em>{{page.lesson_title}}&lt;/em> lesson&lt;/a>, and hear from the authors about how The Carpentries community can get involved with the ongoing development of this lesson.&lt;/p>
&lt;h2 id="lesson-profile">Lesson Profile&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Title:&lt;/strong> {{page.lesson_title}}&lt;/li>
&lt;li>&lt;strong>Lesson Pages:&lt;/strong> &lt;a href="https://carpentries-incubator.github.io/deep-learning-intro">https://carpentries-incubator.github.io/deep-learning-intro&lt;/a>&lt;/li>
&lt;li>&lt;strong>Lesson Repository:&lt;/strong> &lt;a href="https://github.com/carpentries-incubator/deep-learning-intro">https://github.com/carpentries-incubator/deep-learning-intro&lt;/a>&lt;/li>
&lt;/ul>
&lt;h3 id="learning-objectives">Learning Objectives&lt;/h3>
&lt;ul>
&lt;li>Prepare input data for use for deep learning&lt;/li>
&lt;li>Design and train a Deep Neural Network&lt;/li>
&lt;li>Troubleshoot the learning process&lt;/li>
&lt;li>Measure the performance of the network&lt;/li>
&lt;li>Visualize data and results&lt;/li>
&lt;/ul>
&lt;h3 id="target-audience">Target Audience&lt;/h3>
&lt;p>The main audience of this lesson is considered to have an academic background at any level. More importantly, we expect them to know basics of statistics and machine learning to follow through with the material.&lt;/p></description></item><item><title>HPC in a day?</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2017/06/hpccarpentry/</link><pubDate>Tue, 20 Jun 2017 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2017/06/hpccarpentry/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>&lt;strong>Preface&lt;/strong>&lt;/p>
&lt;p>In today&amp;rsquo;s scientific landscape, computational methods or efficient use thereof can be at the heart of the race for new insights, if not at the heart of the race with the academic competition. Learning how to automate tasks from data analysis to data preprocessing as taught by the carpentries provides the technical concepts to enter this race with an advantage.&lt;/p>
&lt;p>If you just graduated a software/data carpentry boot camp and want to go beyond your laptop&amp;rsquo;s capabilities, the next step in academia is typically to approached the data center of your university or alike. There, a user account application has to be filed for the High Performance Computing (HPC) facilities. After some more formalities, storage and computing time is awarded and you can successfully log into the cluster. And then? Then either our carpenter is given a link to the wiki of the local cluster and how to use it. Sometimes there can be a short course on the mechanics of the HPC cluster and how to use tools that are installed on the cluster. That&amp;rsquo;s it and good luck.&lt;/p></description></item><item><title>Pulling In Those Left Behind</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/10/pulling-along-those-behind/</link><pubDate>Thu, 29 Oct 2015 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/10/pulling-along-those-behind/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 A common challenge that arises before or during a workshop is that
 participants' prior expertise in programming or broadly speaking
 their abilities of using computers for science is distributed
 randomly. At best, this distribution peaks at the expectations of
 the instructor. Usually, this distribution is quite wide and thus a
 considerable portion of the participants do lack the necessary
 predispositions for the workshop level, or have a slower learning
 rate or simply are too shy to ask questions. I recently taught a
 follow-up workshop to the Software Carpentry (SWC) Novice material
 and struggled to keep the pace of teaching at a level so all
 learners would come along. Given the feedback on the SWC mailing
 list (see the
 &lt;a href="{{site.mailing_lists}}/pipermail/discuss/2015-October/003396.html">original post&lt;/a>),
 this problem occurs quite often. Thus, this blog post is
 a summary of the discussion initiated among fellow SWC instructors
 on how to pull in those learners again that fall behind or how to
 pace/design a course so that a minimal portion of learners fall
 behind.
&lt;/p></description></item><item><title>Particle Physicists Pulling Themselves From The Swamp</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/10/physicists-learning-to-develop-code/</link><pubDate>Fri, 31 Oct 2014 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/10/physicists-learning-to-develop-code/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 What does it mean to work on a modern particle physics experiment like ATLAS
 (&lt;a href="http://en.wikipedia.org/wiki/ATLAS_experiment">wikipedia&lt;/a>,
 &lt;a href="http://atlas.ch">public&lt;/a>)
 or CMS (&lt;a href="http://en.wikipedia.org/wiki/Compact_Muon_Solenoid">wikipedia&lt;/a>,
 &lt;a href="http://cms.web.cern.ch/">public&lt;/a>)
 at the &lt;a href="http://home.web.cern.ch/topics/large-hadron-collider">Large Hadron Collider&lt;/a>
 in the 21st century?
 It's fun,
 it's collaborating with great and interesting people,
 it's challenging,
 it's making you enjoy finding things out,
 it's what I always wanted to do.
 Also:
 it is painful,
 discouraging,
 and tends to suck the life out of a young mind.
 Confused?
 Let's rewind...</description></item></channel></rss>