-
Notifications
You must be signed in to change notification settings - Fork 9
Updated renv and conda-env-yaml instructions #35
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
base: main
Are you sure you want to change the base?
Conversation
Merge recent changes from CHTC/recipes main into my own fork of the repo.
… it could help visualize the flow of information.
…-up, and instructions.
…simple environment you want to design a def file directly for.
…xist, and there are no tar.gz file examples I could find in this repo.
| - https://conda.anaconda.org/conda-forge | ||
| - https://repo.anaconda.com/pkgs/main | ||
| - https://repo.anaconda.com/pkgs/r |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - https://repo.anaconda.com/pkgs/r |
Apologies for unasked for "drive by" PR comments, but as the Anaconda r channel is deprecated and no longer maintained (c.f. https://www.anaconda.com/blog/changes-to-anacondas-r-channel-support) mentioning it at all should probably be avoided in documentation. As mentioned in Anaconda's blog post, conda-forge has rather good coverage of CRAN these days and so between the conda-forge and bioconda channels this should cover all modern use cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's good to know - I agree we could remove the line mentioning the r channel in the example printout on the documentation to avoid confusion then.
|
Sorry for the delay; I'm planning to review this PR today or tomorrow. |
Hi CHTC team,
I was working with some students on the
renvandconda-env-yamlfull workflow from their laptops to CHTC, and took on the task to add onto the existing README instructions based on the feedback and questions from students.For the
recipes/software/R/renvworkflow, I added a workflow figure to demonstrate what/how/where files should be located. Students have mentioned that visuals can help. I also added instructions on how to solve the Linux dependencies problem, which were TBD previously (ticket #118430 - thanks @xamberl ). I reformatted the layout and added callout bubbles with extra tips. I added a section linking to the HTC guides/docs for skills mentioned in the readme file.For the
recipes/software/conda/conda-yamlreadme file, I mainly reformatted the readme file and added some more details.In both cases, I added an overview section at the beginning that previews the steps and general concepts. I tried to keep it general not not domain-specific.
I added a folder
docs/to store screenshots/images that are linked in the workflow, but I'm not sure if that follows your stylistic guidelines.Hope this helps in some way! Suggestions welcomed. And thank you for the example recipes and instructions.
Patricia