You can use our service desk portal for getting RIS support. RIS also offers 15 min. virtual office hours session Mon-Thru..
User Agreements and Policies
User Agreements
User Policy
The use of research storage is primarily for research data, which may include information classified as confidential and protected. Users of the storage who are unsure of the sensitivity of the data they intend to store should refer to the University’s information classification policies (see the Information Classification Policy) or contact the Information Security Office at infosec@wustl.edu for guidance.
Agency regulation and university policy require information in the protected class to be encrypted in transit and at rest. Sensitive information in the Research Storage should not be removed to unprotected networks and computing resources. It is required to be encrypted if it is not in an approved university data center, on a mobile device, or another computing system. See the Encryption policy.
It is the responsibility of the storage user to always ensure adequate protection of the information when using
this service.
Users of this service:
Agree to store only data that pertains to official business and is authorized to be stored within the service.
Agree to ensure that sensitive information stored within the service is restricted to authorized team members on a need-to-know basis.
Agree to ensure that access to sensitive data is based on your role or research.
Agree not to retrieve information for someone who does not have authorization to access that information.
Agree to ensure that all Protected Data is encrypted in transit and at rest, and strongly recommend encryption of Confidential Data. Data in transit refers to data actively moving from one location to another (e.g., from local storage to the cloud, sent via email). Data at rest refers to data in storage (e.g., on a server, hard drive, or in the cloud). Protecting data in transit and at rest may involve encrypting emails, files, systems, and/or devices. (See the Encryption policy.)
Agree to coordinate your user access requirements and user access parameters with the Research Infrastructure Services (RIS) WashU IT group.
Agree to notify the service provider (RIS) if access to the storage resources is beyond that which you or they have authorized.
Agree to report all security incidents or suspected incidents to the RIS (ris@wustl.edu) and/or INFOSEC. (infosec@wustl.edu)
Agree to discontinue use of the service from any resources that show signs of being infected by a virus or other malware and report the suspected incident.
Agree to safeguard storage resources against waste, loss, abuse, unauthorized users, and misappropriation.
Agree to ensure that hard or electronic copies of Confidential and Protected information are destroyed after it is no longer needed. (See the Media Policy.)
Agree not to store U.S. classified national security information or Controlled Unclassified Information (CUI) on the service.
Agree to the monitoring of your use of this service for any violations of the above.
An unprotected network or networks with insufficient protection include any network other than WUCON or a High Trust Domain. Consult with the RIS or INFOSEC groups if you do not know what network you are on or where the data will reside.
Any device that stores protected information but does not encrypt the information and does not have a
password/passcode is considered unsafe and in violation of policy.
Separation Policy
Users of this service:
Agree upon departure from the university, their data management falls under the associated department, including decisions regarding storage within Research Infrastructure Services (RIS) and other computational services.
Agree upon departure from the university, they will retain access to services as long as their WashU Key remains in an active (student, employee, or contingent employee) status.
Please note: Alumni status is not considered an active status.Agree in the absence of specific instructions from the department, data and access to data will be retained for the benefit of other researchers.
Agree that a request to transfer, reassign ownership to another sponsor, or to delete their data can be made.
In addition to above usage agreements, the users of RIS also recognize and adhere to the usage policies of our compute and storage platforms as listed under:
Compute Platform Policies
Data/Storage Platform Policies
RIS AI Policy
All use of Artificial Intelligence (AI) agents in RIS must comply with the WashU Use of Artificial Intelligence policy.
For additional WashU AI information, please visit the WashU AI page.
AI agents must be run on compute nodes and must not be used on login nodes. Please refer to the WashU Misuse of Resources policy.
Violation of this policy may result in jobs or processes being terminated. This page documents how to set up Visual Studio Code to run remote processes as Slurm jobs on Compute2.
Other Usage Guidelines
Supported methods to transfer data into and out of the Scientific Compute Platform are:
Submitting a job on the Compute Platform(s) using a data transfer tool (e.g.
rsync,wget,curl,scp)Please do not use these data transfer tools directly on the compute1 client nodes. This type of activity can slow down the client node and negatively affect all users connected to the client nodes.
If you require assistance submitting jobs using these tools, please open a ticket at our Service Desk.
We strive to provide help with software debugging and support to the best of our abilities and time. With that being said, there may be times when we cannot solve an issue related to a specific piece of software or script that is not supported by RIS. In those cases, we will attempt to provide a solution to the problem, but we cannot guarantee that the solution will be successful. We recommend reading this section for more help debugging your software as well as for guidance on software development best practices.
Below are some links to information about debugging. Something necessary for software development.
Below are some links to what are considered some of the software best practices and should be kept in mind while developing.
https://distantjob.com/blog/software-engineering-best-practices/
https://www.classicinformatics.com/blog/a-handbook-to-successful-software-development-practices
https://www.tiempodev.com/blog/software-development-best-practices/
https://www.techicy.com/best-practices-for-software-development-to-follow-in-2021.html
File names should be precise as NTFS file name size has a limit of 255 characters
This is a hard limit of the system that the Storage/Compute platform uses.
Any files to be transferred to Storage/Compute need to be created following this limit or they cannot be transferred.
Files should be named consistently.
File names should be short but descriptive.
Avoid special characters or spaces in a file name.
Avoid using PHI or anything other protected data in the name.
Use capitals and underscores instead of periods or spaces or slashes.
Use date format ISO 8601:
YYYYMMDD.Include a version number.
Write down naming convention in data management plan.
Elements to consider using in a naming convention are.
Date of creation
Short Description
Work
Location
Project name or number
Sample
Analysis
Version number
@Elyn Fritz-Waters compute1 user agreement hyperlink is invalid.