ARCC Policies
The following is a list of general computer use policies, procedures, and security rules that apply to individual end-users of the Advanced Research Computing Center (ARCC) resources. These policies and procedures are intended to ensure that UW Research Computing resources are used effectively to support UW's research programs.
...
Table of Contents |
---|
...
General Policies
...
Terms of Use Policy
...
Expand | ||||
---|---|---|---|---|
| ||||
Applicable Policies and AcceptanceAcceptanceThe process of requesting an allocation on an ARCC resource includes acceptance of any policies specific to that resource, and of this Terms of Use which applies to all ARCC resources. UW Acceptable Use PolicyARCC clusters and other resources (the resources) are made available to the University community, and as such are covered by the general University Acceptable Use Policy (AUP). All users of ARCC resources are required to adhere to the campus AUP in addition to the policies specific to the ARCC resources. You should read and familiarize yourself with the University AUP. The AUP includes the following provisions which might be particularly applicable to users of the ARCC resources, but the list below is NOT complete and you are bound by all of the policies in the AUP:
ARCC PoliciesIn addition to the University AUP, the ARCC resources have their own policies which are available at ARCC Policies. The use of any ARCC resource requires compliance with all General Policies linked from this page and any Resource-Specific Policies that apply to that particular ARCC resource. User ResponsibilitiesResponsibilities of PIs and Users
Responsibilities of All Users
Appropriate UseARCC resources may only be used for activities authorized by the University. Prohibited actions include, but are not limited to, the following:
Software, Data, Security and Access ControlARCC Use by Foreign NationalsARCC use by foreign nationals is generally permitted regardless of whether access to ARCC resources is from the United States or abroad. However, the U.S. Department of Treasury’s Office of Foreign Assets Control (OFAC) regulations prohibit the use of ARCC resources by citizens of Cuba, Iran, Syria or Sudan while residing and/or working in one of those countries. Restricted DataThe use of UW/ARCC resources to store, manipulate, or remotely access information, software or data (materials) that require additional controls or that could negatively impact or compromise administrative and business operations of ARCC resources requires prior written approval from the University. Such materials include, but are not limited to, export-controlled software or technical data subject to Export Administration Regulations (EAR) or International Traffic in Arms Regulations (ITAR); Personally Identifiable Information (PII) or health information subject to the Health Information Portability and Accountability Act (HIPAA), and materials subject to "Official Use Only" or similar government restrictions.
System SecurityUW/ARCC resources control data access via username and password authentication for network access and UNIX directory and file permissions for data storage. Network access and data storage systems provide no explicit encryption. ARCC users are responsible for protecting data files and acknowledge and understand that UW/ARCC security control implementation is sufficient for research data access and storage. Software Licensing and Copyright Compliance
Data Retention
Policy Violations
Disclaimer
|
Privacy Policy
...
Expand | ||
---|---|---|
| ||
Data Collection
MonitoringARCC users have no explicit or implicit expectation of privacy. UW retains the right to actively monitor all ARCC resources, activities on ARCC resources and networks and to access any file without prior knowledge or consent of ARCC users, senders, or recipients. UW/ARCC may retain copies of any network traffic, computer files, or messages indefinitely without user's prior knowledge or consent. Data Sharing
|
Acknowledgment Policy
...
Expand | ||
---|---|---|
| ||
A requirement of all allocations and use of ARCC resources is to acknowledge ARCC and UW support for your research. Our ability to identify supported scientific results helps ensure continued support from the State of Wyoming, federal agencies and other sources for future HPC/HPS systems. Annual Reporting
Citation
|
Resource-Specific Policies
...
Expand | ||
---|---|---|
| ||
These policies and procedures are intended to ensure that ARCC HPC facilities are fairly shared, effectively used, and support the University of Wyoming's research programs that rely on computational facilities not available elsewhere at the University. Definitions Cluster an assembly of computational hardware designed and configured to function together as a single system, much the way neurons work together to form a brainCondo a computational resource that is shared among many users — condo compute resources are used simultaneously by multiple users HPC - high-performance computing generally refers to systems that perform parallel processes at a level above a teraflop or 1012 floating-point operations per second HPS - high-performance storage system, usually a tiered system with media covering a range of speeds to optimize performance while reducing cost customer a person, or group to whom ARCC provides a service General Policies For policies that apply to all ARCC resources, see ARCC Policies. |
HPC Policies
...
Usage of Login Nodes
...
Expand | ||||
---|---|---|---|---|
| ||||
The login nodes are provided for authorized users to access the Teton cluster.
|
Account Policy
...
Expand | ||
---|---|---|
| ||
HPC/HPS AccountsOverviewHPC/HPS accounts are available for all University faculty, staff and students for the purpose of research. Account Sponsorship by a PI
General Terms of UseThe following conditions apply to all account types. Additional details on how the different account types of work can be found elsewhere on this page.
Account requestsAll HPC accounts can be requested through the ARCC Access Request Form. Note that all requests, for creating projects and adding users to a project, must be made by the project PI. For questions about HPC account procedures not addressed below, please contact ARCC. DefinitionsPrincipal Investigator (PI) Account account of a faculty member who has an extended-term position with UW (e.g. not Adjunct Faculty)Sponsored Researcher a member (e.g. Student/Graduate Assistant, Faculty, or Researcher from another Institution) of a research project for which a UW faculty member is the PISystem Account account of a staff member who has a permanent relationship with UW Account TypesPI AccountsPI accounts are for individual PIs only. These accounts are for research only and are not to be shared with anyone else. These accounts are subject to periodic review and can be deleted if the account holders change their University affiliation or fail to comply with UW and ARCC account policies. Sponsored AccountsPIs may sponsor any number of accounts, but these accounts must be used for research only. UW faculty are responsible for all of their sponsored account users. These accounts are subject to periodic review and will be deleted if the sponsoring faculty or the account holders change their University affiliation or fail to comply with UW and ARCC account policies. Instructional AccountsPIs may sponsor HPC accounts and projects for instructional purposes on the ARCC systems by submitting a request through the ARCC Access Request Form. Instructional requests are subject to denial only when the proposed use is inappropriate for the systems and/or when the instructional course would require resources that exceed available capacity on the systems or substantially interfere with research computations. HPC accounts for instructional purposes will be added by the Sponsor into a separate group created with the 'class group' designation. Class group membership is to be sponsored for one semester and the Sponsor will remove the group at the end of the semester. Class/Instructional group jobs should only be submitted to the 'class' queue, which will be equivalent in priority to the 'windfall' queue, and only available on the appropriate nodes of the ARCC systems. System AccountsSystem accounts are for staff members who have a permanent relationship with UW and are responsible for system administration. Account LifecycleAccount CreationARCC HPC/HPS accounts will be created to match existing UWYO accounts whenever possible. PIs may request accounts for existing projects/allocations or courses. Account RenewalAccount TransferA PI who is leaving the project or the University can request that their project be transferred to a new PI. Any non-PI accounts can be transferred from one PI's zone of control to another as necessary as students move working from one researcher to another. Account transfer requests will also be made by contacting the Help Desk (766-4357). Account TerminationThe VP of Research, the University and UW CIO, and University Provost comprise the University of Wyoming's Research Computing Executive Steering Committee (UW-ESC). The UW-ECS will govern the termination of Research Computing accounts, following other University policies as needed. Non-PI accounts may be terminated at the request of the UW-ESC. Any users found in violation of this Research Computing Allocation Policy or any other Policies may have access to their accounts suspended for review by the Director of Research Support, IT and the UW-ESC. |
Job Scheduling Policy
...
Expand | ||
---|---|---|
| ||
This section reflects the general ARCC policy for scheduling jobs on all HPC systems administered by ARCC. Since the purpose of HPC systems varies from system to system, please refer to the specific system below for policies particular to that system. HPC Systems
|
Software Policy
...
Expand | ||
---|---|---|
| ||
Software Acquisition, Installation, and Support (AIS) PolicyOverviewThis document defines the ARCC's software policy regarding software acquisition, installation, and support. ARCC will help UW users through:
General software usage, functionality and application questions should be addressed by the research computing community. To support the community support model, ARCC will make available a community-driven Known Error Database in the form of a Wiki with discussion board features. The ARCC will review the software policy annually during the Change Advisory Board meeting with input from the Faculty Advisory Committee (FAC) members. Software RequestsThe ARCC will maintain a list of currently supported software for each HPC system that ARCC supports. Supported software is evaluated biannually. The ARCC reserves the right to discontinue support for underutilized software. Software proposed for discontinued support will be placed in a "deprecated" section of the software modules interface. Movement of applications to a deprecated status will happen twice per year during system upgrades. Faculty can submit a request for continued software support of deprecated applications using the ARCC Resource Request Form. New software requests must be initiated by a faculty member via the ARCC Resource Request Form. The information on this form (e.g. estimates on the number of users, software and licensing details, software cost, and the timeline for installation) will be utilized to determine the degree of support provided by the ARCC. Software AcquisitionFinancial SupportWhenever possible, researchers are encouraged to use open-source software. The costs for discipline-specific, proprietary software will typically be born by the PIs requesting the software. A small number of one-time 'seed funding' opportunities may be made with input from the FAC. Financial support for the software is dependent on the user base, as follows:
Technical SupportARCC staff will provide support in the identification of efficient and cost-effective software packages to meet the research objectives of faculty members. Where suitable the ARCC will coordinate software acquisitions of faculty with similar objectives to better leverage research investment. Software InstallationLicensing SupportThe ARCC, with the help of UW-IT and UW General Council, will help provide guidance on research software licensing and suitable installation/controlled access. Technical SupportARCC staff will provide software installation services for software to be run on ARCC resources. Department IT consultants will help with the installation of software on researchers' workstations. The ARCC will also provide centralized license server services for software on ARCC resources when needed. Software Support
|
Storage Policy
...
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
OverviewCode-named Teton, the ARCC high-performance storage system (HPS) is a high speed, tiered storage system designed to maximize performance while minimizing cost. Teton is intended to be used for storing data that is actively being used. The following policies discuss the use of this space. In general, the disk space is intended for support of research using the cluster, and as a courtesy to other users of the cluster, you should try to delete any files that are no longer needed or being used. All data on the HPS, are considered to be related to your research and not to be of a personal nature. As such, all data is considered to be owned by the principal investigator for the allocation through which you have access to the cluster. Teton is for the support of active research using the clusters. You should remove data files, etc. from the cluster promptly when you no longer actively working on the computations requiring them. This is to ensure that all users can avail themselves of these resources.
Storage AllocationsEach individual researcher is assigned a standard storage allocation or quota on Directory Descriptions Directory Summary Table
Augmenting Capacity of Disk AllocationResearchers working with or generating massive data sets that exceed the default 5 TB allocation, or having significant I/O needs should consider the following options:
File Deletion PolicyThis describes ARCC's file deletion policy:
|
petaLibrary Policies
...
Expand | ||
---|---|---|
| ||
Data Protection BackupsData Protection/Backups Policy:
UsageGroups, departments, or researchers can request access for several projects, but it will be up to the Research Office and ARCC to determine acceptable allocations of the petaLibrary. |