From dad40eefc4e90349eb0e15dc47048fed5ec6acf6 Mon Sep 17 00:00:00 2001
From: Emma Rand <emma.rand@york.ac.uk>
Date: Mon, 4 Nov 2024 08:54:10 +0000
Subject: [PATCH] plan week 6

---
 update-notes.txt | 43 ++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 42 insertions(+), 1 deletion(-)

diff --git a/update-notes.txt b/update-notes.txt
index ea106a6..20a181a 100644
--- a/update-notes.txt
+++ b/update-notes.txt
@@ -55,4 +55,45 @@ bibtex::write.bib(entry = pkgs, file = "references_libs.bib", append = FALSE)
 
 labelling several particular genes
 You need to do external_gene_name %in% ....
-where ... is a list of the gene names
\ No newline at end of file
+where ... is a list of the gene names
+
+WEEK 6
+
+reminder on organising work
+folders for different types of data
+make inuts and outputs clear
+include all inputs and outputs
+you will be submitting either:
+-  an RStudio project (i.e., a folder structure 
+containing an .RProj in the top folder
+
+-  a folderstructure which includes an RStudio Project
+
+not one correct organisationbut should be as self-explanatory 
+as possible
+
+self explanatory does not mean youdon't explain. it means you
+save people mental load
+
+Curate your and reorganise your code
+- does it make sense to use more than one script
+- do any of your files need renaming and reorganising
+- do any variables need renaming for consistency
+- remember you want to be systematic
+- write down conventions you decide to follow
+- go through week 2 and apply
+
+restart R to try. exchange projects with a friend. Do they understand?
+
+Readme
+- how to make
+- what goes in
+- software including versions
+- session info
+- instructions for use
+- issues, problems
+- what the project is about
+- data and data provenence
+- description o the project organisation
+- description of the files
+