Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

READMEs using .Rmd/.ipynb? #41

Open
mschubert opened this issue Apr 8, 2015 · 10 comments
Open

READMEs using .Rmd/.ipynb? #41

mschubert opened this issue Apr 8, 2015 · 10 comments

Comments

@mschubert
Copy link
Owner

The couple of READMEs we have got now highlight some functionality of the modules they are in.

Does it make sense to have .Rmd files instead that generate those READMEs to showcase functionality?

Advantages

  • functionality can be checked by re-generating the .mds
  • we'd have some high-level docs for "type x and y comes out"
  • could also incorporate plots

Disadvantages

  • we version-control an automatically generated file (this is minor) and possibly images
@barzine
Copy link
Contributor

barzine commented Apr 8, 2015

For the disadvantage point: do you really need to keep the md file?

@mschubert
Copy link
Owner Author

I'd want the docs to be visible in the repository, and Github renders .md but not .Rmd.

So yes, I think the .mds are necessary.

@barzine
Copy link
Contributor

barzine commented Apr 8, 2015

Well Github renders my .Rmd pretty fine in my case. Or I don't understand what you mean.
On side note, I have the same behaviour with Readme.md and Readme.Rmd (Github displays it on the first page)
The only thing would be that the expected result would have to be added as a comment or something

screen shot 2015-04-08 at 18 30 21

@mschubert
Copy link
Owner Author

Interesting, I didn't know.

However, it won't be able to show the result of R commands. If the READMEs are there to showcase functionality, it could never show the output. This kind of defeats the purpose.

@barzine
Copy link
Contributor

barzine commented Apr 8, 2015

Ok, I am probably slow to understand what you want: you want to be able to showcase the functionality, right?

So why can't you just add the expected results in another chunk instead with echo=FALSE and eval=FALSE? In the example I provided, the first chunk is defined as :


### 

but you can still see it.

Then, the Rmd can be used as a checking tool as well (which was the first reason you wanted to shift to .Rmd, no?)

@mschubert
Copy link
Owner Author

@klmr @barzine, what do you think of docs using ipynbs?

advantages

  • can host text, code, graphics, etc.
  • is both a static reference and executable
  • can be used to test if examples still produce the right results

disadvantages

  • frequent updates or graphics will increase repository size

@mschubert mschubert changed the title READMEs using .Rmd? READMEs using .Rmd/.ipynb? Aug 6, 2015
@klmr
Copy link
Contributor

klmr commented Aug 16, 2015

I’ve never used Jupyter, if the R integration isn’t too convoluted (such as having to wrap every R call into a Python wrapper …), I have no objections.

@mschubert
Copy link
Owner Author

After installing the kernel and a couple of packages, it's just selecting R from a dropdown menu.

@barzine
Copy link
Contributor

barzine commented Aug 26, 2015

Just have seen this.
Never used ipynbs myself and very eager to learn about any new method that would help with the reporting.

This seems pretty nice. Can you confirm how it behaves with an extensive use?

@mschubert
Copy link
Owner Author

I haven't used them extensively, but so far they are working well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants