Deploying to gh-pages from @ 98aec5d 🚀

core/week-6/overview.html

@@ -270,7 +270,7 @@ <h3 class="anchored" data-anchor-id="learning-objectives">Learning objectives</h
 <ul>
 <li><p>Describe the purpose of a README file</p></li>
 <li><p>List the key components of a README file</p></li>
-<li><p>Use <code>sessioninfo</code> to document the software used in an R project</p></li>
+<li><p>Use packages to discover the packages used in a project</p></li>
 <li><p>Write a README file for a project</p></li>
 </ul>
 </section>

core/week-6/workshop.html

@@ -339,7 +339,10 @@ <h2 class="anchored" data-anchor-id="non-scripted-parts-of-the-analysis">Non-scr
 </div>
 </div>
 <div class="callout-body-container callout-body">
-<p>Images were converted to: Manual cropping: Projection type used: etc</p>
+<p>Images were converted to:</p>
+<p>Manual cropping:</p>
+<p>Projection type used:</p>
+<p>etc</p>
 </div>
 </div>
 </section>

search.json

@@ -50,7 +50,7 @@
     "href": "core/week-6/overview.html",
     "title": "Overview",
     "section": "",
-    "text": "We considered how to organise reproducible data analyses in Core: Supporting Information 1. This week we will consider how to document and curate reproducible data analyses. You will add a README to your project and discover all the software you are using in R. The workshop will also include a questions and answers section.\n\nLearning objectives\nThe successful student will be able to:\n\nDescribe the purpose of a README file\nList the key components of a README file\nUse sessioninfo to document the software used in an R project\nWrite a README file for a project\n\n\n\nInstructions\n\nPrepare\n\nRevise Core: Supporting Information 1 and make a note of queries you have\n\nWorkshop\nConsolidate",
+    "text": "We considered how to organise reproducible data analyses in Core: Supporting Information 1. This week we will consider how to document and curate reproducible data analyses. You will add a README to your project and discover all the software you are using in R. The workshop will also include a questions and answers section.\n\nLearning objectives\nThe successful student will be able to:\n\nDescribe the purpose of a README file\nList the key components of a README file\nUse packages to discover the packages used in a project\nWrite a README file for a project\n\n\n\nInstructions\n\nPrepare\n\nRevise Core: Supporting Information 1 and make a note of queries you have\n\nWorkshop\nConsolidate",
     "crumbs": [
       "Core Supporting Info",
       "Week 6: Supporting Information 2",
@@ -98,7 +98,7 @@
     "href": "core/week-6/workshop.html#non-scripted-parts-of-the-analysis",
     "title": "Workshop",
     "section": "Non-scripted parts of the analysis",
-    "text": "Non-scripted parts of the analysis\nNon-scripted parts of the analysis such as manual data cleaning or using software that does not have a script to analyse data presented in the report should be documented. This includes the steps taken, parameter settings and the decisions made. It need not be written as a narrative - you can use bullet points and be concise.\n🎬 Go through any code you have written and edit your comments.\n🎬 Make a text file for each non-scripted part of the analysis and document the steps taken, parameter settings and decisions made. You likely will not be able to complete now where you will be analysing data in semester 2, but you can write down “place holders” where possible. For example, in using Fiji to analyse images:\n\n\n\n\n\n\nimage_processing_in_fiji.txt\n\n\n\nImages were converted to: Manual cropping: Projection type used: etc",
+    "text": "Non-scripted parts of the analysis\nNon-scripted parts of the analysis such as manual data cleaning or using software that does not have a script to analyse data presented in the report should be documented. This includes the steps taken, parameter settings and the decisions made. It need not be written as a narrative - you can use bullet points and be concise.\n🎬 Go through any code you have written and edit your comments.\n🎬 Make a text file for each non-scripted part of the analysis and document the steps taken, parameter settings and decisions made. You likely will not be able to complete now where you will be analysing data in semester 2, but you can write down “place holders” where possible. For example, in using Fiji to analyse images:\n\n\n\n\n\n\nimage_processing_in_fiji.txt\n\n\n\nImages were converted to:\nManual cropping:\nProjection type used:\netc",
     "crumbs": [
       "Core Supporting Info",
       "Week 6: Supporting Information 2",