-
Notifications
You must be signed in to change notification settings - Fork 11
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
Revamping Chapel lessons #22
Comments
The update can be done in this repository. Can make a pull request to do this if that would be helpful. |
There has been some prior work on converting lessons to the Carpentries Worksbench, there's a small list of resources on the related issue on the HPC Intro repo. Not sure if that's super-helpful, one of the challenges there is the snippets and templating, which I think are less of an issue for this lesson, but it may still be worth a look. |
Submitted a pull request to convert to the new Carpentries Workbench #23 |
Thanks. Can review in next couple of days.
|
Earlier today (2024-Aug-22) we had a Chapel training coordination meeting organized by the Chapel development team and focused on revamping the HPC Carpentry Chapel lessons. Over the next few months we would like to update and significantly expand http://www.hpc-carpentry.org/hpc-chapel (that I wrote first back in 2017 and pretty much neglected since then) to adapt it to a wider spectrum of users. We will switch from the single "heat diffusion" working example to three separate tracks ("heat diffusion" for physicists and engineers, "Julia set" for people who aren't interested in solving PDEs, and a third problem to focus on explicit task synchronization without large grids). We will also update everything to the latest Chapel release and add GPU Chapel materials.
There was also a suggestion to switch http://www.hpc-carpentry.org/hpc-chapel to the Carpentry's new lesson template https://github.com/carpentries/workbench-template-md to make the lesson page more dynamic. If I am not mistaken (please correct me if I am), that would require creation of a new repository in lieu of the old one. What is the HPC Carpentry's position on this, and what is the process? I would like to preserve or migrate all the currently open issues and work on them one by one over the next few months.
The text was updated successfully, but these errors were encountered: