2017-08-18 20:04:01 +00:00
# ABC-units.R
#
# Purpose: A Bioinformatics Course: R code for learning units
#
# Version: 0.
#
# Date: 2017 08 18
# Author: Boris Steipe (boris.steipe@utoronto.ca)
#
# V 0.1 First code
#
# TODO:
#
#
2017-09-12 20:09:20 +00:00
# == HOW TO WORK WITH LEARNING UNIT FILES ======================================
2017-08-18 20:04:01 +00:00
#
2017-09-12 20:09:20 +00:00
# Expect that the learning unit files will be continuously updated.
2017-08-18 20:04:01 +00:00
#
2017-09-12 20:09:20 +00:00
# If you wish to edit any of the code, for example to add your own comments and
# examples, save any edited version under a different name. Otherwise you will
# have problems with git when you update the project to a new version.
# DO NOT SIMPLY source() THESE FILES!
# If there are portions you don't understand, use R's help system, Google for an
# answer, or ask your instructor. Don't continue if you don't understand what's
# going on. That's not how it works ...
#
# While this file itself should not be edited by you this is YOUR project
# directory, and files that you create (notes etc.) will not be harmed when you
# pull updated version of the master, or other new files, from github.
2017-08-18 20:04:01 +00:00
#
2017-09-12 20:09:20 +00:00
# If you pull from github and get the following type of error ...
# ---------------
# error: Your local changes to the following files would be
# overwritten by merge
# ...
# Please commit your changes or stash them before you can merge.
# ---------------
# ... then, you need to bring the offending file into its original state.
# Open the Commit window, select the file, and click on the Revert button.
2017-08-18 20:04:01 +00:00
#
2017-09-12 20:09:20 +00:00
# Of course, you can save a local copy under a different name before you revert,
# in case you want to keep your changes.
#
#
# ==============================================================================
# Once you have typed and executed the function init(), you will find a file
# called myScript.R in the project directory.
2017-08-18 20:04:01 +00:00
#
2017-09-12 20:09:20 +00:00
# Open it, you can place all of your code-experiments and notes into that
# file. This will complement your "Course Journal". If you keep all contents in
# this one file, you can find everything by using the <cmd>-F find function. To
# cross-reference code in your journal, create section headings.
2017-08-18 20:04:01 +00:00
#
#
# ==============================================================================
" I n t r o d u c t i o n :
...
"
# ==============================================================================
# PART ONE: REVIEW
# ==============================================================================
# == SECTION ===================================================================
# == Subsection
# Continue ...
# ==============================================================================
# APPENDIX: OUTLOOK
# ==============================================================================
" There are many more functions for ... that this tutorial did not cover. You should know about the following. Look up the function and write a short bit of example code that uses it:"
? subset
? sweep
? with # ... and within()
" T h e n y o u s h o u l d k n o w a b o u t t h e f o l l o w i n g p a c k a g e s . O p e n t h e v i g n e t t e a n d b r o w s e t h r o u g h i t . Y o u s h o u l d k n o w b e a b l e t o c o m e u p w i t h l e a s t o n e u s e - c a s e w h e r e t h e p a c k a g e f u n c t i o n s w o u l d b e u s e f u l :
https : / / cran.r - project.org / web / packages / magrittr /
"
# [END]