-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update wrap-tool.Rmd #20
Conversation
Added section headers and tentative schedule.
No spelling errors! 🎉 |
No broken url errors! 🎉 |
Re-rendered previews from the latest commit:
* note not all html features will be properly displayed in the "quick preview" but it will give you a rough idea. Updated at 2024-10-17 with changes from the latest commit a56f90e |
Updated schedule table and fix headers to be numbered.
|
||
Workflow Description Language (WDL) not in your programming skillset? No problem! Learn to wrap your pipelining tool in WDL and run it in an AnVIL workspace in this CoFest session. We’ll go over WDL basics and how to run pipelines in AnVIL, then walk through how to run your own Unix/Python/R script. Along the way, you’ll write a WDL and build a custom Docker to run it with. Come and wrap a tool of interest! All experience levels are welcome. If time allows, we’ll emerge with some resources for others to run their non-WDL tool in AnVIL. | ||
Workflow Description Language (WDL) not in your programming skillset? No problem! Learn to wrap your pipelining tool in WDL and run it in an AnVIL workspace in this CoFest! session. We’ll go over WDL basics and how to run pipelines in AnVIL, then walk through how to run your own Unix/Python/R script. Along the way, you’ll write a WDL and build a custom Docker to run it with. Come and wrap a tool of interest! All experience levels are welcome. We’ll brainstorm and, if time allows, we’ll create resources (tutorials? AnVIL book? Cheat sheet?) for others to use to run their non-WDL tool in AnVIL. |
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.
Maybe we could add links? e.g., [Docker](https://www.docker.com/)
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.
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.
I'll merge this, and I could modify the blurb with the links in a later PR :)
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.
Sounds good!
Added section headers and tentative schedule.
I wonder if something like this could work for the final version of the Cofests! main. Let me know!