Skip to content

Accessibility changes for the Policies section#199

Open
tonykew wants to merge 1 commit intoubccr:mainfrom
tonykew:Accessibility_Policies_section
Open

Accessibility changes for the Policies section#199
tonykew wants to merge 1 commit intoubccr:mainfrom
tonykew:Accessibility_Policies_section

Conversation

@tonykew
Copy link
Copy Markdown
Contributor

@tonykew tonykew commented Apr 3, 2026

Accessibility changes for the Policies section

Fixed links at the bottom of the "Communications Policy" (email.md) file

Tony

Fixed links at the bottom of the "Communications Policy" (email.md) file

Tony
Copy link
Copy Markdown
Contributor

@dsajdak dsajdak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just added a method for jumping to the scratch policy section from another section of the docs.


**Scratch Scrubber Policy**
CCR provides free, high throughput scratch storage space for use when running your jobs. However, this is TEMPORARY storage space intended for transient storage while jobs are running. Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete. Any data over 60 days old is deleted automatically nightly. Any efforts to modify file dates to purposely subvert this policy are prohibited. We have sophisticated scripts that monitor for attempts to subvert the system. Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. [See below](##) for more information on this policy.
CCR provides free, high throughput scratch storage space for use when running your jobs. However, this is TEMPORARY storage space intended for transient storage while jobs are running. Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete. Any data over 60 days old is deleted automatically nightly. Any efforts to modify file dates to purposely subvert this policy are prohibited. We have sophisticated scripts that monitor for attempts to subvert the system. Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. See below for more information on this policy.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
CCR provides free, high throughput scratch storage space for use when running your jobs. However, this is TEMPORARY storage space intended for transient storage while jobs are running. Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete. Any data over 60 days old is deleted automatically nightly. Any efforts to modify file dates to purposely subvert this policy are prohibited. We have sophisticated scripts that monitor for attempts to subvert the system. Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. See below for more information on this policy.
CCR provides free, high throughput scratch storage space for use when running your jobs. However, this is TEMPORARY storage space intended for transient storage while jobs are running. Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete. Any data over 60 days old is deleted automatically nightly. Any efforts to modify file dates to purposely subvert this policy are prohibited. We have sophisticated scripts that monitor for attempts to subvert the system. Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. [Refer to the scratch policy](#touch) for more information on file date or access time manipulation.

- Groups have a 10 TB default quota for their global scratch directory
- Groups are also subject to a quota of 200 million files
- We set these group quotas for the total number of files in accordance with our system size and projected usage. Users generating more than a million files per job could affect the performance of the system for everyone. If you feel your research requires this, we’d like to engage with you to determine if there is an alternate approach

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a id="touch"></a>

This will allow us to jump from the above section down to this and fix the fact that that link went no where before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants