Difference between revisions of "Draft:Software Installation Policies and Guidelines"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* Recommendations on using our prebuilt e.nys vs building their own in the context of speed of customization vs. maintaining functional environments. Focus on R and python at first. | * Recommendations on using our prebuilt e.nys vs building their own in the context of speed of customization vs. maintaining functional environments. Focus on R and python at first. | ||
==Prebuilt Environments for Reference== | ==Prebuilt Environments for Reference== | ||
| − | |||
* Published environment.yml files for the popular environments like pytorch, which users could refer to when starting to build their or use prebuilt containers | * Published environment.yml files for the popular environments like pytorch, which users could refer to when starting to build their or use prebuilt containers | ||
**e.g. pytorch container from NVIDIA. | **e.g. pytorch container from NVIDIA. | ||
==Availabile Linux Software installed in lapps in ResVault== | ==Availabile Linux Software installed in lapps in ResVault== | ||
*Enter here | *Enter here | ||
Revision as of 15:42, 10 February 2023
- User login server abuse: Describe the functionality of the main R and python environments vs more specific environments like pytorch and tensorflow or domain-specific collections like geopython or DJppytt)Q0
- Recommendations on using our prebuilt e.nys vs building their own in the context of speed of customization vs. maintaining functional environments. Focus on R and python at first.
Prebuilt Environments for Reference
- Published environment.yml files for the popular environments like pytorch, which users could refer to when starting to build their or use prebuilt containers
- e.g. pytorch container from NVIDIA.
Availabile Linux Software installed in lapps in ResVault
- Enter here