geanders / geanders/RProgrammingForResearch
Suggestion for Chapter 5.2
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 83
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Discuss knitr:purl() command - extract r script from markdown document.
I found it useful in my troubleshooting of homework #2. Seeing the code by itself (outside the markdown document) made it easier to track the flow and ID where I made errors.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Chapter 5.2 and review how its existing material is organized. Add a discussion of the knitr::purl() command for extracting an R script from a Markdown document, including why viewing the code separately can help troubleshoot homework; done when the suggestion is covered in that chapter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100