Conversation
…ting up project workspace
|
@audiracmichelle I've included a new section on the nsaph computing spaces to this branch. Here is a summary of my changes: SummaryRestructured the handbook to focus on Cannon and ReD as the primary computing environments, removing legacy FASSE-specific content and consolidating setup documentation. ChangesAdded
Renamed & Substantially Revised
Updated
Removed
|
daniellebraun
left a comment
daniellebraun
left a comment
There was a problem hiding this comment.
added various comments throughout, thanks
| - Purpose: general HPC cluster for data that do not require the regulated controls of ReD. | ||
| - Use Cannon for environmental and geospatial datasets, simulations, and analysis that exclude regulated health data. | ||
| - Cluster usage guidance and fairshare details are in [Cannon](cannon.md) and [Fairshare](fairshare.md). | ||
| - Git/GitHub are available; follow [project setup](project_setup.md) guidelines for consistent workspace structure. |
There was a problem hiding this comment.
are we only doing git for Cannon and not recommending it at all for ReD? even to copy/paste code at the end?
handbook/project_setup.md
Outdated
|
|
||
| ### ReD: | ||
|
|
||
| GitHub is not currently configured to work with ReD, so push/pull to/from GitHub is not possible. |
There was a problem hiding this comment.
but we are still recommending copy/paste of code for reproducibility?
| >* Copy/import data into the appropriate lab_share location. | ||
| >* Update catalogs or tracking systems. | ||
|
|
||
| ## Code Imports on ReD |
There was a problem hiding this comment.
are we adding instructions on this?
There was a problem hiding this comment.
i think we need something about efficient compute use on RED
…tency across all pages (ReD, cannon, and project set up guidelines)
4 participants
fixed FASSE references throughout handbook