bringing in updates from main

docs/Resources/hpc.md

@@ -49,6 +49,9 @@ To get started visit this page for [some info](https://docs.ycrc.yale.edu/cluste
     5. `mpi`: for highly-parallelized code
     6. `pi_NAME`: PI and lab specific nodes available for purchace from YCPC
 
+### QOS-Based GPU Allocation
+By default, jobs are submitted with standard priority. This means that when cluster resources are scarce, these jobs can be preempted, or terminated, in favor of high-priority jobs. This isn't generally a problem for shorter jobs, but for long jobs that are resource-intensive, it may make sense to submit a high-priority job using a SLURM mechanism called QOS (Quality of Service). Our lab has a certain number of guaranteed resources which you can gain access by using the `--qos=qos_levenstein` along with `salloc` or `sbatch`. See the [Misha Guide](https://ood-misha.ycrc.yale.edu/public/misha/04-qos.html) for more info. It's also recommended to use checkpoints in case a job does get terminated.
+
 ### Cheat Sheet
 
 * Interactive jobs:

docs/Resources/presentations.md

@@ -53,6 +53,8 @@ When presenting, your job is not to get through your slides. It's to make sure e
 
 **Watch good talks and PAY ATTENTION.** You'll learn more about presenting from actively watching great speakers than from any list of tips (including this one). Pay attention to how they structure their story, how they use their slides, how they handle transitions, how they explain figures.
 
+**Present to the least knowledgable person in the room.** A common mistaken assumption most students have is that everyone else knows everything they know, and more. However, most of your audience (including professors!) will not know everything you know about your project or its background. If the students in the audience come away understanding your project, its motivation, and results, that's a win. Present as if you're presenting for THEM, not as if you're presenting to the one expert.
+
 
 ### Structuring a Talk (Beyond Lab Meeting)