AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
In general, when you execute code in a notebook chunk, it will do exactly the same thing as it would if that same code were typed into the console. If you do not want the chunk to run, you can click on the icon to remove it from the execution queue.įIGURE 3.7: The indicator in the gutter to show the execution progress of a code chunk in the notebook. When a chunk is waiting to execute, the Run button in its toolbar will change to a “queued” icon. You can click on this meter at any time to jump to the currently executing chunk. If at least one chunk is waiting to be executed, you will see a progress meter appear in the editor’s status bar, indicating the number of chunks remaining to be executed. Lines of code that have been sent to R are marked with dark green lines that have not yet been sent to R are marked with light green. When you execute code in a notebook, an indicator will appear in the gutter to show you execution progress (Figure 3.7). This allows execution to stop if a line raises an error. The primary difference is that when executing chunks in an R Markdown document, all the code is sent to the console at once, but in a notebook, only one line at a time is sent. There are other ways to run a batch of chunks if you click the menu Run on the editor toolbar, such as Run All, Run All Chunks Above, and Run All Chunks Below. Running a single statement is much like running an entire chunk consisting only of that statement. Press Ctrl + Enter (macOS: Cmd + Enter) to run just the current statement. Use the green triangle button on the toolbar of a code chunk that has the tooltip “Run Current Chunk,” or Ctrl + Shift + Enter (macOS: Cmd + Shift + Enter) to run the current chunk.
0 Comments
Read More
Leave a Reply. |