Policies

Policies and Service Level Agreements (SLAs)

The Discovery cluster is a shared resource. The RC team and the Research Computing Advisory Committee have developed the following policies to ensure that this resource is used in an efficient manner, so the entire Northeastern research community benefits. If you have a Discovery account, you are expected to abide by these policies. Failure to follow these policies could result in the revocation of your access and/or disciplinary action by the university. If you have any questions or concerns about these policies, please contact us.

Policies and Service Level Agreements (SLAs)

The Discovery cluster is a shared resource. The RC team and the Research Computing Advisory Committee have developed the following policies to ensure that this resource is used in an efficient manner so that the entire Northeastern research community will benefit from this resource. If you have a Discovery account, you are expected to abide by these policies. Failure to follow these policies could result in the revocation of your access and/or disciplinary action by the university. If you have any questions or concerns about these policies, please contact us.

General

General

Access

  • Every person who uses Discovery must have his or her own account. Get started by visiting our documentation.
  • You must never share your login ID or password with any other person, whether they are affiliated with the university or not.
  • Three general partitions (long, large, and multigpu) have additional access guidelines. See the Partitions page on our documentation site.

Access

  • Every person who uses Discovery must have his or her own account. Request access through Service Now.
  • You must never share your login ID or password with any other person, whether they are affiliated with the university or not.
  • Three general partitions (long, large, and multigpu) have additional access guidelines. See the Partitions page on our documentation site.

Scratch Space

The /scratch space is a shared space. Make sure you are familiar with the following guidelines. 

  • Do not store files on /scratch.  
  • Be aware that /scratch is not backed up. Always make sure to have a copy of any file you put on /scratch. 
  • Files are regularly checked for how long they have been on /scratch. If you have files older than 21 days on /scratch, you will be sent an email warning you that any files older than 28 days files will be removed from /scratch and moved to archive storage for 30 days. After 30 days, if you do not move your data from archive, it will be purged from archive storage.  
  • If your /scratch account has consumed a total of 10,000,000 or more inodes, you will not be able to run any jobs until you reduce the amount of data on /scratch.  
  • If you attempt to avoid your files being purged by modifying file times, such as through touch, your account will be suspended and possibly revoked pending a review by the RC team and the Research Computing Advisory Committee. 

Scratch Space

The /scratch space is a shared space. Make sure you are familiar with the following guidelines. 

  • Do not store files on /scratch.  
  • Be aware that /scratch is not backed up. Always make sure to have a copy of any file you put on /scratch. 
  • Files are regularly checked for how long they have been on /scratch. If you have files older than 21 days on /scratch, you will be sent an email warning you that any files older than 28 days files will be removed from /scratch and moved to archive storage for 30 days. After 30 days, if you do not move your data from archive, it will be purged from archive storage.  
  • If your /scratch account has consumed a total of 10,000,000 or more inodes, you will not be able to run any jobs until you reduce the amount of data on /scratch.  
  • If you attempt to avoid your files being purged by modifying file times, such as through touch, your account will be suspended and possibly revoked pending a review by the RC team and the Research Computing Advisory Committee. 

Maintenance

The RC team performs routine maintenance on Discovery to ensure that it is kept up to date.

  • Maintenance will be the first Wednesday of the month.
  • During the maintenance window, you will not be able to run jobs on Discovery. This includes private partitions on Discovery.
  • We send out reminders and updates about maintenance through the Discovery mail list. We also post updates to the ITS Systems Status page.

Maintenance

The RC team performs routine maintenance on Discovery to ensure that it is kept up to date.

  • Maintenance will be the first Wednesday of the month.
  • During the maintenance window, you will not be able to run jobs on Discovery. This includes private partitions on Discovery.
  • We send out reminders and updates about maintenance through the Discovery mail list. We also post updates to the ITS Systems Status page.

Acknowledgements

If you have used the Discovery cluster and/or received assistance from a member of the research computing team, we ask that you include an acknowledgement statement in any publication that details your research, such as journal articles, conference proceedings, dissertations, etc. See the homepage for a list of selected publications that acknowledge Discovery.

 

Example Acknowledgement Statements:

“This work was completed in part using the Discovery cluster, supported by Northeastern University’s Research Computing team.”

“The authors thank the Northeastern University Research Computing team for their [specify type of support/assistance] that contributed to this paper’s findings.”

“The authors thank [specify staff member’s name and title] of the Northeastern University Research Computing team for [specify type of support/assistance] that contributed to this paper’s findings.”

Acknowledgements

If you have used the Discovery cluster and/or received assistance from a member of the research computing team, we ask that you include an acknowledgement statement in any publication that details your research, such as journal articles, conference proceedings, dissertations, etc. The following are examples for adding an acknowledgement. Please modify as appropriate. See the homepage for a list of selected publications that acknowledge Discovery.

 

Example Acknowledgement Statements:

“This work was completed in part using the Discovery cluster, supported by Northeastern University’s Research Computing team.”

“The authors thank the Northeastern University Research Computing team for their [specify type of support/assistance] that contributed to this paper’s findings.”

“The authors thank [specify staff member’s name and title] of the Northeastern University Research Computing team for [specify type of support/assistance] that contributed to this paper’s findings.”

 Service Level Agreements

Service Level Agreements (SLAs) detail the services we provide to the research community through our ServiceNow catalog. All RC catalog items have a corresponding SLA that you can view below.

Let’s Work Together

Enabling you to advance your research is our mission. Reach out to us with questions, issues, and concerns so we can provide you with the assistance you need.