# strip.white = TRUE, # if FALSE knitr will not remove white spaces at the beg or end of code chunk # message = FALSE, # if FALSE knitr will not display any messages generated by code # echo = TRUE, # in FALSE knitr will not display code in the code chunk above it's results # results = 'asis', # knitr will pass through results without reformatting them # fig.path = 'figs/', # file path to the directory where knitr shall store the graphics files # fig.align = 'center', # how to align graphics in the final doc. # cache = TRUE, # if TRUE knitr will cache the results to reuse in future knits A code chunk always begins with three ticks \(\text A code chunk is a specific section of the R Markdown document where code-specific syntax is placed and executed. Lines 6-8 contain what is called a code chunk. The default values include “title” and “output.” YAML (short for “Yet Another Markup Language” or “YAML aint a Markup Language”) is a necessary component of the initiation of any R Markdown file, and should be placed in the file up top starting with three -, and ending with the same. Take notice that the code window has now become pre-populated with several lines of helper code for formatting/ starting the R Markdown file with the correct syntax. In this case, an example title is set to “Reticulate_Demo.” The author field can either be filled in or left blank, and it is best to select the “HTML” radio button since knitting (compiling) the outputs between PDF and HTML can always be switched between at a later time. The following window will pop-up, prompting you to save the file according to various selections. Navigate to the “File” menu up top, click on “New File,” follow by “R Markdown.”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |