MedicineBow

Table of Contents

Medicinebow SubPages

Overview

MedicineBow Project and Account Requests

MedicineBow and other ARCC hosted resources are available to PI’s (typically faculty researchers) and any UW faculty, staff and students subject to the project PI’s supervision and approval. Users may request accounts on ARCC resources by filling out a request through our portal and PIs may request project allocations on the MedicineBow cluster by filling out a project request form, here. Note: PIs may submit an initial set of users for your research project using the same form. Users can be added in the project request or added after project creation, using the Request a Change to Your Project form.

Once you have been provisioned an account on MedicineBow, and you have been granted access to a project, the cluster is accessible both over the web through the MedicineBow OnDemand Interface here or via SSH (secure shell) at medicinebow.arcc.uwyo.edu by configuring your client for authentication using an SSH key.

See the above (Medicinebow Subpage List) for information to Access Medicinebow over the Web, or SSH access using SSH key authentication.

MedicineBow User Data Locations

MedicineBow’s user storage is divided into three directory types to ensure that researchers have control of where their data is, and who can access it. 

• /home: for configuration files and user specific software installations. Data stored here is, by default, only accessible to the user.

• /project: a collaborative area shared among project members.

  • Data stored here is, by default, read accessible to all project users.

  • Subdirectories within the project directory are by default only writable by the owner of the subdirectory.

  • Within every project file is a directory for project shared software installation called /software

• /gscratch: a large and fast storage area to temporarily store large data sets while they are being processed. This area is not backed up and is subject to periodic purges of old data.

Information detailing the Medicinebow Filesystem is available in the Medicinebow Subpage list at the top of this page. MedicineBow data and storage is subject to ARCC’s general storage policy detailing default allocation sizes, costs for storage increases, and purge policy.

Software

With the migration to MedicineBow, cluster, ARCC is updating and evolving our software policy. Our software migration policy is available here. A summary of the MedicineBow software and MedicineBow software list available here.

Condo Model

Our MedicineBow cluster follows a condominium-style model of resource management. Investors, which are individual researchers or groups of researchers, work with us at ARCC to purchase compute nodes and storage. Investors receive priority to their investment nodes. Nodes must be approved by ARCC before investments are purchased. (See node purchase estimates for examples)

Condo computing resources are used simultaneously by multiple users. When the investor-purchased resources aren’t in use by the investor defined users, those resources will be made available to the community. Within the condo model investors have priority on invested resources; This is implemented through preemption. General access to investor-owned resources can be immediately revoked when the investors wish to use their resources. The job will automatically be re-queued to ease the burden on users.

MedicineBow includes a number of non-investor resources in a non-investor partition. These nodes are available to the general research community for use on a first-come-first-serve basis and you may view the status of all partitions by running the sinfo command on the cluster.

Citing MedicineBow

As an upcoming resource, information on citing MedicineBow is forthcoming. In the meantime, please reference the citing section under Documentation and Help.