Comments (14)
@tkphd I would say that grid and cloud computing are not out of scope -- I'd like to see this lessons adapted to use on a system like the Open Science Grid, which is not traditional HPC.
I have an alternative proposal for forming the glossary. How about going through the lessons and pulling out the terms that could use a definition?
from hpc-intro.
from hpc-intro.
good idea and thanks for putting that into an issues. But always remember: Top priority for good teaching is reduction. There are many things in that list which I'd drop. I don't feel too polite to edit your issues directly. How about #38 ?
from hpc-intro.
Please feel free to edit the issue.
I would prefer strikethrough tags over straight deletion. Discussion of what to include is more natural in an issue than in a PR.
For a start, Beowulf clusters are obsolete, grid and cloud computing are out of scope, GPGPU is to deep in the weeds...
from hpc-intro.
Good suggestion, @ChristinaLK.
Perhaps a hybrid approach: go through the existing lessons, tagging or linking instances of jargon to the glossary, then reviewing what's undefined and what's never referenced? Not a trivial task...
from hpc-intro.
Yep. Reviewing the lessons seems like a manageable task and could be done piecemeal.
from hpc-intro.
Good point. I'll focus on #40 and then come back to this.
from hpc-intro.
Reviewing this list, I'm honestly not sure the glossary is useful. When terms relevant to, and within scope for, the lessons come up, we define them. Anything that doesn't come up, is out-of-scope for us to define; a Web search is better suited than a glossary. Anything that does come up, but isn't adequately explained, we need to address within the lesson.
from hpc-intro.
Never noticed a glossary in the shell-novice reference page, but there it is. As a result, I don't think I'd abandon the glossary entirely, but it definitely shouldn't include terms we never use in the lessons (looks like the shell-novice glossary is keeping with that rule except maybe for "REPL"). Being able to point people at a single reference page including a review of terms seems useful, without them having to scroll through the entire lesson or hope for the best on a search. Not sure what else might go on a more complete reference page yet.
from hpc-intro.
some learners have asked for a glossary here and there during my HPC intro courses.
some automation would be helpful here I believe, so that if we define a term during a lesson, it is automagically appended to the glossary.
from hpc-intro.
I would like to vote to keep glossaries.
We can choose to link to the glossaries page with anchors from individual lesson materials.
from hpc-intro.
May be helpful to have this, but could be in extra materials as done for shell-lesson
from hpc-intro.
It already is: Extras -> Reference.
from hpc-intro.
The glossary is no longer in reference.md, it's now in _extras/guide.md. Edited the leading comment on this issue to reflect the new location.
from hpc-intro.
Related Issues (20)
- Images in the jargon presentation are not rendering
- Provide reading resources for backup of essential data
- record jargon presentation
- incorporate firewall gif
- Amdahl code deployment strategy HOT 1
- propagate script name through snippet library
- Jargon buster presentation - presenter notes repeated
- ENH: Possible addition of Netlify-bot HOT 2
- Interesting forks of the `hpc-intro` lesson
- scp introduced during ssh keygen without explanation
- Broken link to Python code
- Add some material on environment variables? HOT 1
- use MagicCastle as the default snippet library HOT 1
- Question about username on the cluster HOT 3
- Confused with "shell application with SSH"
- Shell prerequisites for hpc-intro
- Tiny self-hosted cluster for HPC Carpentry workshop? HOT 2
- Adopting the Carpentries Workbench...and reducing divergent forks! HOT 4
- Provide guidance to Instructors about commonly-encountered technical issues
- curl -o amdahl.tar.gz ... retrieves empty file HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hpc-intro.