Onboarding
Thank you for using Drexel’s URCF Proteus high performance computing cluster. We hope this facility will help you achieve your research goals.
Policies
Definitive policies are posted on the main Office of Research - URCF website:
https://drexel.edu/core-facilities/facilities/research-computing/policies/
User accounts
Proteus user accounts are managed solely by URCF staff and are not associated with your normal Drexel account. Each member of a research group must have their own account: accounts are not to be shared. (Sharing of accounts may trigger penalties.) The PI has final approval on accounts for their group members. Collaborators external to Drexel may also be granted accounts.
Group members should request URCF accounts using this web form:
https://drexel.edu/core-facilities/facilities/research-computing/about/contact-us/get-account/
If any user account should be terminated, please contact urcf-support@drexel.edu
User account policies and the URCF participation policy are laid out here: https://drexel.edu/core-facilities/facilities/research-computing/policies/picotte-user-accounts/
Charge Rates
The definitive rate schedule is posted at
https://drexel.edu/core-facilities/facilities/research-computing/policies/rates/
Picotte
Rates are computed per Service Unit (SU). Rate for both compute and storage: $0.0123 per SU
Compute
| Resource type | Slurm partition | SU per unit resource |
|---|---|---|
| Standard compute | def | 1 per core-hour |
| Big memory | bigmem | 68 per RAM TiB-hour |
| GPU | gpu | 43 per GPU device-hour |
While logged in to picotte001, the billing_report command can show
SUs consumed and associated charge. Do "billing_report --help" for
online documentation.
Storage
Rate: 1081 SU per TiB-month
This is equivalent to $13.30 per TiB-month, or about $3.32 per TiB-week.
Usage in user home directories is free of charge.
Facility Description for Proposals
Boilerplate text for the URCF Proteus facility description can be found here: Facility Description for Proposals
Acknowledgement of URCF in Publications
We would appreciate an acknowledgement of the use of URCF Proteus in your publications. The following line should appear in your publication:
Work reported here was run on hardware supported by Drexel's University Research Computing Facility.
Please also forward to urcf-support@drexel.edu citations for any work done utilizing Proteus to be published on the URCF website: https://drexel.edu/core-facilities/facilities/research-computing/research/publications/
This may also include dissertations.
This boilerplate and email link are also here: Acknowledging URCF in Publications
Documentation and Support
There is extensive documentation in the online wiki: https://proteusmaster.urcf.drexel.edu/urcfwiki/
All requests for support should be emailed to: urcf-support@drexel.edu This generates a ticket in our issue tracking system and maintains a record of all correspondence related to the issue.
Software Installation
Research groups are expected to maintain the specialized research software they require, and to ensure correctness of operation. While URCF staff may assist in installing software, URCF staff’s first priority is issues that affect the entire operation of Proteus and the URCF data center. URCF staff may also lack the specialized knowledge to evaluate the correctness of research software.
There are many (~200) software packages already installed on Proteus, so the software required for your work may already be available. Please see the documentation wiki.
Use for Coursework
Use for Coursework URCF Proteus may be used in coursework. Notice should be given to URCF staff at least 3 weeks before the end of the term prior to the one when the course is to be taught. URCF Governing Board approval is required for coursework to be performed on URCF Proteus. Restrictions on coursework usage may be imposed to reduce the impact on research workloads.
Policies for coursework accounts are laid out [https://drexel.edu/core-facilities/facilities/research-computing/policies/fair-share/#:~:text=COURSEWORK%20TERMS%20OF%20USE here].