Common Location to Maintain Codes and Shared Data
BC Project: FY10-07
Date of Policy: 30 Sep 2011
Last Updated: 26 Feb 2026 (see Revision Log)
This policy ensures a common location to place applications, codes, and data that are shared by
multiple users without making use of home directories or scrubbed scratch. To support this policy,
archives and allocated HPCs will provide two distinct project locations accessible via pre-defined
environment variables: $PROJECTS_HOME and $PROJECTS_ARCHIVE.
To ensure data integrity and to manage system resources, all project directories are subject to the policies outlined below.
| Variable | Purpose | Accessibility | Data Management |
Quota Policy |
|
|---|---|---|---|---|---|
| Active Project Space |
$PROJECTS_HOME | For maintaining shared applications, codes, and active data | Available on all allocated HPC login and compute nodes | BACKED UP * These directories are backed up on the same schedule as user home directories, as specified in BC Policy FY12-01 |
Quotas are enforced by some centers. |
| Archive Storage |
$PROJECTS_ARCHIVE | For long-term storage and archival project repository for inactive data | Available on the archive system | NOT BACKED UP Data in this location is not backed up by the center. |
While generally larger, storage is not unlimited. Responsible usage is expected. |
* Backups exist for disaster recovery purposes only. Users are responsible for safeguarding their data from accidental deletion or errors.
Requesting a Project Directory
All individual projects may request a directory under $PROJECTS_HOME and/or
$PROJECTS_ARCHIVE. To request a project directory, the subproject's designated Point
of Contact (POC) should submit a request to the HPC Help Desk
with the following information:
- DSRC System: The specific system where the directory is needed.
- POC Information: The POC's full name, username, and contact details.
- Reasoning: A brief summary explaining need and where the directory is required (HPC and/or Archive).
- Desired Directory Name: The name for the new directory.
- Estimated Size Requirement in Gigabytes: This will help centers with quota requirements accommodate your request.
Ownership and Permissions
The directory is managed according to the following rules:
| Rule | |
|---|---|
| Owner | The directory is owned by the POC's username |
| Access | The POC has full control and manages the directory with their standard user account (no special account needed) |
| Group Permissions | By default, access is granted to the POC's default user group. The POC may request using a different or new group |
| Security | The POC is fully responsible for setting correct file permissions to protect any sensitive or restricted data |
Data Retention Policy for Inactive POCs
Project directories will be handled according to the user data retention policies as defined in BC policy FY13-02 if the project directory POC ceases being an account holder on the system.
| Date | Revision |
|---|---|
| 26 Feb 2026 | BC Team Audit, re-write for clarification and to include structure. |
| 08 Oct 2021 | BC Team Audit |
| 05 Mar 2021 | Added $PROJECTS_ARCHIVE |
| 18 Apr 2019 | Added a new section on "Backup and Quota" |
| 31 May 2018 | BC Team Audit |
| 09 Jun 2016 | BC Team Audit |
| 05 May 2014 | BC Team Audit |
| 22 Oct 2013 | Clarified scrubbing and backup requirements |
| 23 Sep 2013 | Removed reference to the HPC Help Desk web site |
| 25 Apr 2012 | BC Team Audit |