Quick-and-dirty knowledge base for ODU RCS.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Wirawan Purwanto d87de85f44 * Added notes on how to inspect & modify SLURM job(s). 2 years ago
R * added Rstudio cheatsheets. 2 years ago
ansible * Tentative placeholder for Ansible major updates. 2 years ago
carpentries * Added live coding tips for Carpentries-style teaching. 2 years ago
containers * Added note on storage overlay on Singularity. 3 years ago
data-compliance * Added initial overview of protected data: different types, 3 years ago
graphics * Added initial doc for Virginia-centric graphics etc. for our websites, 2 years ago
hpc * Added tools, services, and best practices to set up HPC-like 4 years ago
matlab * Added notes on how to run Matlab with no GUI. 4 years ago
ondemand * Initial insert of various notes. 4 years ago
publications * Collected preprint policies for various journal publishers. 2 years ago
python * Added published URL. 3 years ago
python-software * Added notes on basic pip operation. 3 years ago
security * Security: Added initial stub for random password generators. 2 years ago
singularity * Added noteset on Singularity persistant overlay. 3 years ago
slurm * Added notes on how to inspect & modify SLURM job(s). 2 years ago
tensorflow * File rename. 2 years ago
vm * Added note on how to run Windows from physical partition on a VM. 2 years ago
.gitignore * Added .gitignore 5 years ago
README.md * Added warning not to store sensitive info. 2 years ago

README.md

ODU RCS Knowledge Base Workspace

This git-based KB is to complement RC2 OneNote document and our HPC wiki as a quick-and-dirty, programmer-friendly, collaborative space for storing knowledge, pointers, etc. to non-sensitive information about research computing in general. The target audience of this KB is our own staff (primarily) and the students who are working with us.

Documents in this space is meant to be rather quick and dirty, allowing us to capture information & knowledge and somewhat organize them, without being bogged down with tedious polishing. Once a certain bit of topic has crystallized and matured, we can edit and polish the KB article to become a wiki article or Q&A.

NOTE: WP started this KB as a personal project in 2019, but would like to invite all other RCS staff to work together to create a library of our collective knowledge.

WARNING:

  • This KB is intended to store public and internal knowledge base that is NOT confidential.
  • Do not store sensitive information on this KB at all!