Common ErroRs & Debugging R Code

Different types of helpful info is displayed when there are problems with our code:

Common ErroRs & Debugging R Code

Different types of helpful info is displayed when there are problems with our code:

Messages - the good 😇

• Often harmless & can sometimes be ignored (i.e. when loading packages)

• Can sometimes hint that something might be wrong or missing

Common ErroRs & Debugging R Code

Different types of helpful info is displayed when there are problems with our code:

Messages - the good 😇

• Often harmless & can sometimes be ignored (i.e. when loading packages)

• Can sometimes hint that something might be wrong or missing

Warnings - the bad 😈

• Function is executed but something unusual is happening

• Can highlight potential problems

What To Do?

What To Do?

Step 1: Don't panic - read the error message for clues 🕵

What To Do?

Step 1: Don't panic - read the error message for clues 🕵

Step 2: Find where the error is 📍

• Error messages in the console tend to give an approx. location of where the problem lies
• Look for red underline & red crosses
• Run/knit each chunk in turn from top to bottom
• Run each line of code in a chunk/each step of a pipeline %>%

What To Do?

Step 1: Don't panic - read the error message for clues 🕵

Step 2: Find where the error is 📍

• Error messages in the console tend to give an approx. location of where the problem lies
• Look for red underline & red crosses
• Run/knit each chunk in turn from top to bottom
• Run each line of code in a chunk/each step of a pipeline %>%

Step 3: Check over code for common mistakes 👀

• Typos, brackets, commas, speech marks, spaces..

What To Do?

Step 1: Don't panic - read the error message for clues 🕵

Step 2: Find where the error is 📍

• Error messages in the console tend to give an approx. location of where the problem lies
• Look for red underline & red crosses
• Run/knit each chunk in turn from top to bottom
• Run each line of code in a chunk/each step of a pipeline %>%

Step 3: Check over code for common mistakes 👀

• Typos, brackets, commas, speech marks, spaces..

Step 4: Check the output from a function is what you're expecting 🔍

What To Do?

Step 1: Don't panic - read the error message for clues 🕵

Step 2: Find where the error is 📍

• Error messages in the console tend to give an approx. location of where the problem lies
• Look for red underline & red crosses
• Run/knit each chunk in turn from top to bottom
• Run each line of code in a chunk/each step of a pipeline %>%

Step 3: Check over code for common mistakes 👀

• Typos, brackets, commas, speech marks, spaces..

Step 4: Check the output from a function is what you're expecting 🔍

Step 5: Use the help pane & package documentation to check function arguments & ordering 📂