You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue reported below highlights one of the main difficulties to start contributing with non-python notebooks. I list below some potential solutions (and their level of difficulty):
Add a new section in EDS book pointing to external resources how to setup non-python kernels and packages in Anaconda (+)
Add a new section in EDS book with own tutorial how to setup non-python and packages in Anaconda (++)
Create docker images with ready-to-use environments and notebook templates (+++). Some inspiration from the Journal of Digital History
Hi @acocac, thank you for checking in. Work has been a little bit crazy, but thank you for following up on this. I don't think the issue is with the R notebook repository template itself, but rather it is my own inexperience in using Jupyter notebooks and Anaconda. I didn't know that it was necessary to install packages in an Anaconda environment and run an environment before opening the notebook, etc, so it has been a bit of a learning curve for me. But it's always good to learn new things. I have been able to run a Jupyter kernel in R, and to install most of the R packages that are needed. I will keep working on this, sorry again for the delay!
The issue reported below highlights one of the main difficulties to start contributing with non-python notebooks. I list below some potential solutions (and their level of difficulty):
Add a new section in EDS book pointing to external resources how to setup non-python kernels and packages in Anaconda (+)
Add a new section in EDS book with own tutorial how to setup non-python and packages in Anaconda (++)
Create docker images with ready-to-use environments and notebook templates (+++). Some inspiration from the Journal of Digital History
Originally posted by @Jacqui-123 in #175 (comment)
The text was updated successfully, but these errors were encountered: