-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove prince config #541
Remove prince config #541
Conversation
Before we remove this, let me check whether the NYU Greene cluster can use the basically same configurations as prince did and we can recycle this config. I no longer work at NYU but I do know people are still using nextflow and maybe also nf-core. |
Tagging @genericdata to verify whether these nf-core config files that were originally used for NYU Prince can be used with NYU Greene. |
I submitted another pull request as nyu_hpc as a more general listing. I guess I could have renamed everything and updated the original. |
@genericdata Oh I am a dummy - totally didn't realize this was your PR, sorry it's my vacation brain. |
cf #607 |
name: Remove Prince config
about: Removal of a config of a retired cluster
The NYU Prince cluster was decommissioned on February 1st, 2021.
https://sites.google.com/nyu.edu/nyu-hpc/hpc-systems/retired-clusters#h.h5dd1cn9akn2
conf/
directorydocs/
directorynfcore_custom.config
file in the top-level directoryREADME.md
file in the top-level directoryprofile:
scope in.github/workflows/main.yml