Difference between revisions of "RPR-Console"

From "A B C"
Jump to navigation Jump to search
m
m
 
(One intermediate revision by the same user not shown)
Line 38: Line 38:
 
<b>Deliverables:</b><br />
 
<b>Deliverables:</b><br />
 
<section begin=deliverables />
 
<section begin=deliverables />
−
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-time_management" -->
+
<li><b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.</li>
−
*<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
+
<li><b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these.</li>
−
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-journal" -->
+
<li><b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]].</li>
−
*<b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these.
 
−
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-insights" -->
 
−
*<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]].
 
 
<section end=deliverables />
 
<section end=deliverables />
 
<!-- ============================  -->
 
<!-- ============================  -->
Line 49: Line 46:
 
<section begin=prerequisites />
 
<section begin=prerequisites />
 
<b>Prerequisites:</b><br />
 
<b>Prerequisites:</b><br />
−
<!-- included from "./data/ABC-unit_components.txt", section: "notes-prerequisites" -->
+
This unit builds on material covered in the following prerequisite units:<br />
−
This unit builds on material covered in the following prerequisite units:
 
 
*[[RPR-Installation|RPR-Installation (Installing R and RStudio)]]
 
*[[RPR-Installation|RPR-Installation (Installing R and RStudio)]]
 
<section end=prerequisites />
 
<section end=prerequisites />
Line 68: Line 64:
  
  
 +
=== Evaluation ===
 +
<b>Evaluation: NA</b><br />
 +
<div style="margin-left: 2rem;">This unit is not evaluated for course marks.</div>
 
== Contents ==
 
== Contents ==
−
<!-- included from "./components/RPR-Console.components.txt", section: "contents" -->
 
 
===Typing code or executing it?===
 
===Typing code or executing it?===
  
Line 81: Line 79:
 
However, note the following: '''it is convenient to copy/paste code, but you don't learn how to write code through that'''. Practice has shown that it is better to actually type commands, even if you are just re-typing code from a book or online. Actively typing out the code character by character ensures you are reading and translating the code, and notice if anything is not entirely clear.<ref>We use a predictive mental contents-model when we type - something like an inbuilt autocorrect-suggestion mechanism; thus if you type something unfamiliar or surprising (e.g. a subtle detail of syntax), you will notice and be able to figure out the issue. ''Pasting'' code is a merely mechanical activity.</ref> In computer code, every single character matters. For example, I expect that by typing out commands you will be much less likely to confuse <code>=</code> with <code><-</code> or even <code>==</code>. Also, you will sometimes mistype and create errors. That's actually good, because you quickly learn to spot errors, fix them, and resume. That way you build confidence.
 
However, note the following: '''it is convenient to copy/paste code, but you don't learn how to write code through that'''. Practice has shown that it is better to actually type commands, even if you are just re-typing code from a book or online. Actively typing out the code character by character ensures you are reading and translating the code, and notice if anything is not entirely clear.<ref>We use a predictive mental contents-model when we type - something like an inbuilt autocorrect-suggestion mechanism; thus if you type something unfamiliar or surprising (e.g. a subtle detail of syntax), you will notice and be able to figure out the issue. ''Pasting'' code is a merely mechanical activity.</ref> In computer code, every single character matters. For example, I expect that by typing out commands you will be much less likely to confuse <code>=</code> with <code><-</code> or even <code>==</code>. Also, you will sometimes mistype and create errors. That's actually good, because you quickly learn to spot errors, fix them, and resume. That way you build confidence.
  
−
Regarding the larger scripts we load from GitHub - these are too long to be retyped. Select the line, or parts of the line, or a larger block of code that you want to execute, then press <code>&lt;command&gt; R</code>, or <code>&lt;command&gt;&lt;enter&gt;</code> (depending on your operating system) to execute the selected block. In this case you'll need extra effort to discipline yourself and actually read and understand every single character and command. The point is not to execute the scripts. The point is to '''understand''' their contents. The best way to do this is to edit the code, vary parameters, try alternatives and in general '''play'''.
+
Regarding the larger scripts we load from GitHub - these are too long to be retyped. Select the line, or parts of the line, or a larger block of code that you want to execute, then press <code>&lt;command&gt; R</code>, or <code>&lt;command&gt;&lt;enter&gt;</code> (depending on your operating system) to execute the selected block. In this case you'll need extra effort to discipline yourself and actually read and understand every single character and command.
 +
 
 +
'''The point is not to execute the scripts. The point is to understand the contents.'''
 +
 
 +
The best way to do this is to edit the code, vary parameters, try alternatives and in general '''play'''.
  
 
Actually '''working''' with code - i.e. developing code for the lab - is another story. In this case scripts are indispensable for development. I type all my R code into a script, never directly into the console - in this way it is much easier to come back, change things and recreate whatever analysis I was doing: this is essential for "reproducible research". I type into the script, save the script from time to time, and execute commands from the script, not the console - that's the easiest way to modify and develop. Making script and console work hand in hand is the way to work with '''R'''. There are four major advantages:
 
Actually '''working''' with code - i.e. developing code for the lab - is another story. In this case scripts are indispensable for development. I type all my R code into a script, never directly into the console - in this way it is much easier to come back, change things and recreate whatever analysis I was doing: this is essential for "reproducible research". I type into the script, save the script from time to time, and execute commands from the script, not the console - that's the easiest way to modify and develop. Making script and console work hand in hand is the way to work with '''R'''. There are four major advantages:
Line 118: Line 120:
  
 
-->
 
-->
−
== Notes ==
 
−
<!-- included from "./components/RPR-Console.components.txt", section: "notes" -->
 
−
<!-- included from "./data/ABC-unit_components.txt", section: "notes" -->
 
−
<references />
 
 
== Further reading, links and resources ==
 
== Further reading, links and resources ==
 
<!-- {{#pmid: 19957275}} -->
 
<!-- {{#pmid: 19957275}} -->
 
<!-- {{WWW|WWW_GMOD}} -->
 
<!-- {{WWW|WWW_GMOD}} -->
 
<!-- <div class="reference-box">[http://www.ncbi.nlm.nih.gov]</div> -->
 
<!-- <div class="reference-box">[http://www.ncbi.nlm.nih.gov]</div> -->
 +
== Notes ==
 +
<references />
  
 
{{Vspace}}
 
{{Vspace}}
  
−
 
−
<!-- included from "./data/ABC-unit_components.txt", section: "ABC-unit_ask" -->
 
−
 
−
----
 
−
 
−
{{Vspace}}
 
−
 
−
<b>If in doubt, ask!</b> If anything about this learning unit is not clear to you, do not proceed blindly but ask for clarification. Post your question on the course mailing list: others are likely to have similar problems. Or send an email to your instructor.
 
−
 
−
----
 
−
 
−
{{Vspace}}
 
  
 
<div class="about">
 
<div class="about">
Line 150: Line 138:
 
:2017-08-05
 
:2017-08-05
 
<b>Modified:</b><br />
 
<b>Modified:</b><br />
−
:2018-05-03
+
:2020-09-15
 
<b>Version:</b><br />
 
<b>Version:</b><br />
−
:1.0.1
+
:1.1
 
<b>Version history:</b><br />
 
<b>Version history:</b><br />
 +
*1.1 Removed GeSHi calls. Maintenance
 
*1.0.1 Maintenance
 
*1.0.1 Maintenance
 
*1.0 Completed to first live version
 
*1.0 Completed to first live version
 
*0.1 Material collected from previous tutorial
 
*0.1 Material collected from previous tutorial
 
</div>
 
</div>
−
[[Category:ABC-units]]
 
−
<!-- included from "./data/ABC-unit_components.txt", section: "ABC-unit_footer" -->
 
  
 
{{CC-BY}}
 
{{CC-BY}}
  
 +
[[Category:ABC-units]]
 +
{{UNIT}}
 +
{{LIVE}}
 
</div>
 
</div>
 
<!-- [END] -->
 
<!-- [END] -->

Latest revision as of 09:28, 25 September 2020

Console and scripts

(Code interactively or fom scripts.)


 


Abstract:

This unit discusses use working from the RStudio console vs. working from scripts.

Objectives:
This unit discusses principles of working interactively vs. working from scripts.

Outcomes:
After working through this unit you ...

  • ... are familiar with the advantages of working from script files;
  • ... should begin always working from script files in your own practice.

Deliverables:

  • Time management: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
  • Journal: Document your progress in your Course Journal. Some tasks may ask you to include specific items in your journal. Don't overlook these.
  • Insights: If you find something particularly noteworthy about this unit, make a note in your insights! page.

    • Prerequisites:
    This unit builds on material covered in the following prerequisite units:


     



     



     


    Evaluation

    Evaluation: NA

    This unit is not evaluated for course marks.

    Contents

    Typing code or executing it?

    The RStudio "console" is the bottom-left pane into which you can type commands for execution, and which will contain the output of print() orcat() commands.

    Commands can be ...

    • directly typed into the console;
    • copied by you from the Wiki and pasted into the console;
    • or executed from a script (i.e. a text-file of R commands that can run as a program), either by selecting and executing the code, or by executing the entire script with the source("<filename>") command.

    However, note the following: it is convenient to copy/paste code, but you don't learn how to write code through that. Practice has shown that it is better to actually type commands, even if you are just re-typing code from a book or online. Actively typing out the code character by character ensures you are reading and translating the code, and notice if anything is not entirely clear.[1] In computer code, every single character matters. For example, I expect that by typing out commands you will be much less likely to confuse = with <- or even ==. Also, you will sometimes mistype and create errors. That's actually good, because you quickly learn to spot errors, fix them, and resume. That way you build confidence.

    Regarding the larger scripts we load from GitHub - these are too long to be retyped. Select the line, or parts of the line, or a larger block of code that you want to execute, then press <command> R, or <command><enter> (depending on your operating system) to execute the selected block. In this case you'll need extra effort to discipline yourself and actually read and understand every single character and command.

    The point is not to execute the scripts. The point is to understand the contents.

    The best way to do this is to edit the code, vary parameters, try alternatives and in general play.

    Actually working with code - i.e. developing code for the lab - is another story. In this case scripts are indispensable for development. I type all my R code into a script, never directly into the console - in this way it is much easier to come back, change things and recreate whatever analysis I was doing: this is essential for "reproducible research". I type into the script, save the script from time to time, and execute commands from the script, not the console - that's the easiest way to modify and develop. Making script and console work hand in hand is the way to work with R. There are four major advantages:

    1. The script is an accurate record of my procedure so I know exactly what I have done;
    2. I add numerous comments, to record what I was thinking when I developed it;
    3. I can immediately reproduce the entire analysis from start to finish, simply by rerunning the script;
    4. I can reuse parts easily, thus making new analyses quick to develop;
    5. If I keep my script under version control, I can return to previous versions and undo errors. These were actually five points.


     

    User interface

    Both R and RStudio have a GUI[2] to lay out common tasks. For example, there are a number of menu items, many of which are similar to other programs you will have worked with ("File", "Edit", "Format", "Window", "Help" ...). But note: all of these tasks can also be accessed through the command line in the console.

    In general, GUIs are useful when you are not sure what you want to do or how to go about it; the command line is much more powerful when you have more experience and know your way around in principle. R gives you both options.


     

    Self-evaluation

    Further reading, links and resources

    Notes

    1. ↑ We use a predictive mental contents-model when we type - something like an inbuilt autocorrect-suggestion mechanism; thus if you type something unfamiliar or surprising (e.g. a subtle detail of syntax), you will notice and be able to figure out the issue. Pasting code is a merely mechanical activity.
    2. ↑ A GUI is a Graphical User Interface, it has windows and menu items, as opposed to a "command line interface".


     


    About ...
     
    Author:

    Boris Steipe <boris.steipe@utoronto.ca>

    Created:

    2017-08-05

    Modified:

    2020-09-15

    Version:

    1.1

    Version history:

    • 1.1 Removed GeSHi calls. Maintenance
    • 1.0.1 Maintenance
    • 1.0 Completed to first live version
    • 0.1 Material collected from previous tutorial

    CreativeCommonsBy.png This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.

    Retrieved from "http://steipe.biochemistry.utoronto.ca/abc/index.php?title=RPR-Console&oldid=11735"