# Iris Guide for Users¶

## Getting Started¶

The Iris system is a web portal that contains user, login name, usage, and allocations information.

### First Time Login¶

The first time you log in to Iris, you will have to change your NERSC password. Your NERSC password is also your Iris password and all NERSC passwords must abide by certain requirements.

### Logging In¶

To log into the Iris system, point your web browser to the URL https://iris.nersc.gov. Please use this URL as a bookmark for Iris. If you have bookmarked a different URL, you may have to log in twice.

Click the Login button, and you will be redirected to the NERSC login selector webpage. Log in either with your home institution credentials (if enabled) or enter your NERSC username, password, and MFA one-time password (OTP).

#### Reset MFA tokens¶

If you have to reset all your MFA tokens because, for example, you lost the device where MFA tokens were configured, please follow the instructions in the 'If You Lost Your Tokens' section of the MFA webpage.

#### Problems accessing Iris?¶

If you still have a problem with your username or password, contact the NERSC Account Support Office by sending email to accounts@nersc.gov.

If you can't log in due to a different reason, get help from a NERSC consultant by opening a trouble ticket from NERSC Help Portal (https://help.nersc.gov).

### Obtaining a User Account¶

If you don't have an active user account, please follow the instructions in the Accounts page.

The menu bar at the top of the page has several menus, allowing you to access different parts of Iris.

• The Iris icon in the top left corner is clickable and serves as the Home button. When clicked, it brings you back to the "Homepage" which displays your CPU compute allocation usage summary info.

• The Projects pull-down lists the projects that you have access to and allows you to see usage info for each.

• The Reports pull-down provides various usage report options.

• The search box allows you to quickly get information that you want about an individual user or a project.

• The account pull-down under your account name in the top right corner contains a menu. There is a quick link to your Profile page. Another is for displaying your project roles (e.g., User, PI, ...) and what permissions you have in Iris. Your project's PI, a PI proxy or a Project Resource Manager can set in Iris how much compute time a project member is allowed to use or whether the premium QOS can be used in running batch jobs.

To logout from Iris, select Logout.

For certain menu items, there is also a sub menu bar under the top menu bar with several menu tabs. When this bar appears, the first value on the left is to give you the context for the page displayed. For example, if the page content is about your account itself (that is, when the Iris icon is selected), the label will be your full name, as shown in the above figure. If the content is about a project account, it will display the project's name.

These menu bars are fixed in the page and do not scroll away even when you scroll down the page.

### Sorting the Display Data¶

Displayed data can be sorted by a column by clicking on the column heading. By default data is sorted in the ascending order. Clicking on the heading again, you can toggle the sorting order.

The column selected for data sorting has its column heading marked as chosen.

## Iris Icon (in the top left corner)¶

When you login to Iris, the Iris icon in the menu bar is selected by default. This menu contains info about your account, your allocation usage, records of jobs that you ran, file storage usage, your NERSC MFA (Multi-Factor Authentication) setting, and your profile etc. -- all about your account.

It has several tabs to show different aspects of your account: CPU, GPU, Jobs, Storage, Roles, Groups, MFA, Profile, and History. See the above figure.

Allocations of NERSC computer time are awarded into project accounts.

### CPU¶

This menu lists all the compute allocation accounts on the machines with CPU architectures (in contrast to GPUs) that you have access to, and shows YTD (year-to-date) usage for each. This page shows the following, for each allocation account:

• Project: All the compute allocation projects that you belong to. If you click on a project, it will show details about the allocation account itself. A project can have both a CPU allocation account (see the second column) and a GPU allocation account (see the second column under the GPU tab).

• Account: All the CPU allocation accounts that your allocation projects access to. The name of an CPU allocation account is the same as the project name (the first column).

• Default: The default allocation account to charge your usage on CPU architectures to when the charging account is not explicitly specified during batch job submission. If you want to change the default account, just click the box in the corresponding row.

• Node Hours Charged: Charged CPU Node Hours; compute usage times are charged according to the scheme explained in the Queues and Charges page.

Click on the charge value, and the page will display detailed info about your daily usage for the allocation account.

• Node Hours: Raw node hours used.

• Machine Hours: Node hours after factoring in the architecture charge factor.

• Avg CF: Average QOS cost factor ratio. If all of your batch jobs ran with the 'regular' QOS with no discount, the ratio will be 1.0.

• Remaining: Remaining balance in CPU Node Hours.

• % Remaining: Remaining balance as the percentage of the project allocation.

• 'Allocated Hours' or 'Allocation % of Project': Quota for the CPU allocation hours that your project's PI, PI proxy or PI Resource Manager allocates for your usage. They allocate an amount using either the absolute CPU Node Hours or a percentage.

• 'Last Updated': Time stamp for the last usage update in Iris.

There is a section 'QOS' at the bottom, listing special QOS' that your account is permitted to access to, in order to use special resources (e.g., the premium QOS, Cori Large Memory Nodes, ...) by PI's permission or under a special arrangement. If you don't have any special QOS, then the table is empty.

### GPU¶

This menu lists all the GPU allocation accounts associated with user's project accounts. Computation usage on GPU nodes is charged to a GPU allocation account.

See the CPU section above to see the meaning of the column names in the table. Please note the following.

• The name of a GPU allocation account is its project name appended by _g.
• The default GPU account to be charged to is not set and users need explicitly specify the GPU account name with Slurm's -A flag when a batch job is submitted.
• There is no separate 'QOS' section under the GPU tab. The allowed QOS' set in the 'QOS' section of the CPU tab apply to both CPU and GPU batch jobs.

### Jobs¶

This page lists jobs that you ran on NERSC machines, along with a time-series plot for the jobs on the top and individual jobs at the bottom.

By default, the page lists the jobs you ran during the last one month. To view job data with different start and end dates or for a specific host (e.g., cori haswell, cori knl, perlmutter gpu, ...), etc., enter the appropriate values for your search, and click the 'Load Jobs' button.

Clicking on a job ID link from the displayed result, you will see a summary about the job such as host; job name; allocation account; charge info; submit, start and end times; the compute nodes used, etc.

Below there is a section titled 'Job Transfers'. This area provides a record of all deposits and withdrawals made to/from your project's allocation accounts.

Below it, there is another section titled 'DataCollect Info'. When the 'More Info' button is clicked, it shows details for individual job steps (that is, individual srun instances), such as the working directory, arguments, srun parameters, etc.

At the bottom of the page, there is the 'Display Job Metrics' section, still in an experimental stage, which, when fully implemented, will display plots of some performance data (e.g, instructions per cycle (ipc_by_step and ipc_by_step_and_node) and memory usage) and power usage of the job. Select a metric and then click the 'View graph' button.

### Storage¶

This area is about your usage of the HPSS archive system and the global home file system.

• HPSS Archive: Space quota and usage data ('User Quota' or '% Allowed by Project', and 'Storage Used', respectively) for the HPSS archive system.

This area shows usage and account settings per user for the project's HPSS allocation. PIs and project managers can assign user quotas.

The HPSS storage system tracks usage for each user, but it does not know which allocation account the user belongs to. HPSS user usage information is transmitted to Iris once a day. Iris distributes the user's usage into their storage allocations using their '% of Your Data to Charge to Each Project' values. To change the values, type in the percent to assign to each project and click the 'Update HPSS Allocations' button above the table. Iris initially assigns your project percents based on the relative sizes of your storage allocations. It is user's responsibility to set appropriate percentage values in the user account, if they use multiple allocation accounts. For more info on HPSS charging, please see HPSS archive system.

• HPSS Tokens: You can manually generate HPSS tokens which can be used for accessing the HPSS archive system on your local machine, from an external IP address or within NERSC.

To generate a token, enter the IP address of the machine you will access HPSS from if you are outside the NERSC network, and click the 'Generate' button. For more info, check the Manual Token Generation section.

• Home Directory Usage: Space and inode usage data ('Storage Used' and 'Files Used', respectively) for the global home file system.

### Roles¶

This page shows user's roles in three different context: Iris Role, Project Role and DOE Administrative Role. To see detailed info on the Roles and their permissions, select the 'Iris Roles' menu under the account pull-down menu.

• Iris Role: Various Iris administrative roles mainly for NERSC staff in Iris web portal. The role that most NERSC users will find themselves in is No Role.

• Project Role: A role of a user in a project is PI (Principal Investigator), PI proxy, Project Resource Manager, Project Membership Manager, or User. When a user has a high enough project role, the user is able to edit other member's roles in the project. For example, if you are the PI of your project, you can edit compute allocation for your members in Iris. To see what project managers can do, you can go to the Iris Guide for PIs and Project Managers.

• DOE Administrative Role: This role is relevant to only DOE managers and NERSC allocation staff members, for managing allocations.

### Groups¶

The display shows which Unix file groups you are a member of. You will see file group names, their GIDs (numeric group identifiers), and the associated allocation project accounts.

### MFA¶

The page lists your MFA (Multi-Factor Authentication) tokens. For more info on this topic, please see the MFA webpage.

You can create, delete, and test each token. To add a new one, click the '+ Add Token' button on the right. You can have up to four tokens. To delete one, click the '- Delete' button.

You can request NERSC to clear login failures accumulated on the NERSC OTP (one-time password) server as a result of entering the wrong OTP too many times. These failures could prevent you from logging in. However, they are automatically cleared after 15 minutes. Note that the login failures mentioned here are different from the login failures that would lock you out of a NERSC host (e.g., Cori) indefinitely for entering the incorrect password too many times. This kind of failures can be cleared from the 'Profile' menu below.

To generate backup one-time passwords, click the 'Backup Passwords' button.

The '- Delete All Tokens' button is reserved only for NERSC administrators. So is the 'Clear All Failures' button.

### Profile¶

This page is broken into several sections related to user profile and access modes for NERSC resources. The first two sections are about your contact info. In order to communicate effectively with users and in order to abide by DOE computer use regulations we must have the following information for each user: name, email address, work phone number, and work institution (organization), etc. Please keep your personal information current. This is important so that we can contact you.

• User Organization: Information about your work institution. Note that you cannot edit this section directly -- this is generated automatically from the info you provided in the next section.

• Self-service User Info: User contact information. If your information changes, please correct the info and then click the Update button at the right.

If you are locked out of a host after entering incorrect password too many times, click the 'Account Locked?' button.

You can reset your NERSC password by clicking the 'Reset Password' button. For instructions, please see the How To Change Your Password in Iris section.

If you want to view your Iris project data of a previous allocation year, click the 'Project History' link at the right, and select the allocation year.

If you cannot find your organization from the provided institution list, you can click the 'I can't find my organization' link in this section and provide the requested info about your institution.

Changes in the Citizenship or Organization fields could trigger a re-vetting of your account depending on the changes that were made. Your account access will be disabled during the process, which is normally quick but in some cases can take up to a week to complete.

• Registered External Identities: This is to link your home institution's identity to your NERSC account for Federated identity so that you can use it to authenticate to NERSC web resources. For detailed instructions, please see the Connecting Your Identity with NERSC section.

• Server Logins: The NERSC hosts that you have access to (e.g., perlmutter, cori, datatran, etc.) are listed. The login shell and other login account information for each host are displayed.

You can change the login shell for a host by clicking on the 'Edit' button under the 'Actions' column for the corresponding host.

• SSH Keys: If you are allowed under a special arrangement with NERSC to use ssh keys for accessing a collaboration account, you can register the public key here. In that case, click the '+ New SSH Key' button to add a public key.

For accessing a regular user account, registering an ssh public key has no effect at all because using a personal key pair for authentication is not allowed.

• Gridcerts: You can register your grid certificate here. To add a new grid cert, click the '+ New Cert' button.

• User Settings: This section is reserved only for NERSC staff for administrative work in handling user ticket requests.

• Publications: To enter your publication records, click the '+ Add Publication' button and enter the publication's DOI number.

• Superfacility API Clients: To create a new Superfacility API client, click the '+New Client' button. For instructions, please see the Create a Superfacility API Client in Iris seciton.

• API Token: You may generate an API token in order to use the Iris API. You can have one API token at a time. To generate a token, click the 'Generate API Token' button to the right. Then, the text box below indicates that you have one. To revoke the existing token, click the 'Revoke API Token' button.

### History¶

This page records user event history regarding account and allocation support, such as password reset, generation of a MFA token, assignment to a project account, etc. It shows when such events were created and by whom. To see the record of a specific event, click the 'View Log' button in the corresponding row.

## Projects¶

While the previous menu focuses on resource usage by you, this menu is about resource usage for an allocation project as a whole. To select a project for which you want to check the resource usage, first click the 'Projects' pull-down menu from the top menu bar. It lists all the allocation projects that you have access to. Select a project that you are interested in. Iris will display similar tab menus as above.

### CPU ¶

The display shows YTD (year-to-date) usage of the CPU allocation account (in contrast to the GPU account below) of the selected project, with a quick summary about the allocation account, followed by a usage graph over time and then a table for usage per member of the project.

The summary lists the CPU Node Hours charged, raw node hours used, the average QOS factor ratio, the initial allocation award, the balance, etc. Please see the Queues and Charges page to see how the usage charge is computed.

• Current Allocation: The total allocation in CPU Node Hours.

• NERSC Hours Charged: The CPU Node Hours used so far.

• Available Hours: The remaining balance.

• Remaining %: The remaining balance as a percentage.

• Node Hours Used: The aggregate sum of node hours used over all NERSC computational systems.

• Machine Hours Used: The aggregate sum of node hours after factoring in respective machine charge factors.

• Average Charge Factor: Average QOS factor ratio. If all the batch jobs ran with the 'regular' QOS with no discount, the ratio will be 1.0.

• ERCAP Request: The allocation amount requested by the PI in the allocation request (ERCAP).

• ERCAP Award: The allocation amount awarded for the ERCAP by the allocation managers. The 'Current Allocation' value can differ from this if an additional amount was successfully granted after exhaustion of the initial allocation.

• Premium Threshold Reached?: This indicates whether usage of the premium QOS by the project is over the threshold value, which will cause the premium charge factor to be doubled. For info, see QOS Limits and Charges section.

The usage graph includes charged CPU Node Hours and machine node hours over time. The plot for the charged CPU Node Hour trend can be compared with the uniform charge rate plot as a reference, to give you a sense whether your allocation is being drained too fast or slow. You can zoom in on a rectangular region by using mouse click and drag. To go back to the full graph, clink on 'Reset zoom'.

The usage table in the Per-User compute allocations panel includes the following columns:

• User: All the members belonging to the project. If you click on a user, it will show info about the user.

• Username: NERSC account name.

• Account: CPU allocation account associated with this project account.

• Charged Hours: Charged CPU Node Hours; compute usage is charged according to the scheme explained in the Queue Policy page.

Click on the charge value, and the page will display detailed info about your daily usage logs for the allocation account since the beginning of the allocation year.

• Machine Hours: Raw node hours used.

• Node Hours: Raw node hours used.

• Avg CF: Average QOS cost factor ratio. If all of the batch jobs ran with the 'regular' QOS with no discount, the ratio will be 1.0.

• Remaining: Remaining balance in CPU Node Hours.

• % Remaining: Remaining balance as the percentage of the CPU Node Hour quota.

• 'Allocated Hours' or 'Allocation % of Project': Quota for the CPU allocation hours that your project's PI, PI proxy or PI Resource Manager allocates for users. They allocate an amount using either the absolute CPU Node Hours or a percentage of the project's total allocation.

• 'QOS': Special QOS' (e.g., premium) users are allowed to use for the project.

• 'Last Updated': Time stamp for the last usage update in Iris.

At the bottom, you will see the Project/QOS associations panel. This is to create a mapping between this project and a QOS so that every member of the project (including future members) will have the QOS. For example, if the premium QOS is shown here, all project members are entitled to use the QOS for their batch jobs. If there is no such a project-wide QOS, this table is empty. A mapping in this table applies to both CPU and GPU accounts.

### GPU ¶

This menu lists the GPU allocation account associated with the project account. Computation usage on GPU nodes is charged to a GPU allocation account. See the CPU section above to see the meaning of the accounting-related terms. Please note the following.

• The name of the GPU allocation account is the project name appended by _g.
• There is no separate 'Project/QOS associations' section under the GPU tab. The project-wide QOS' set in the CPU tab apply to both CPU and GPU batch jobs.

### Jobs ¶

This page lists jobs run by all the project members, displaying a time-series plot for the jobs completed, followed by the list of individual jobs.

By default, the page lists the CPU jobs run for the last 1 month. To view job data with different start and end dates or for a specific host (e.g., perlmutter cpu, perlmutter gpu, cori haswell, cori knl, ...), etc., enter the appropriate values for your search in the boxes at the top, and click the 'Load Jobs' button.

Note that, in order to display Perlmutter GPU jobs, you need to use the GPU account name (e.g., m1234_g) in the 'Account name' field. On the other hand, Cori GPU (cgpu) jobs are displayed with the CPU account name (e.g., m1234, not m1234_g) since the GPU account name came into existence only with introduction of Perlmutter and Cori GPU jobs had been running before then. The hostname for Cori GPU jobs is gpu.

Clicking on a job ID link from the displayed result, you will see a summary about the job such as host; job name; allocation account; charge info; submit, start and end times; the compute nodes used, etc.

Scrolling down the page, you can find a section titled 'Job Transfers'. This area provides a record of all deposits and withdrawals made to/from your project's allocation accounts.

Below it, there is a panel titled 'DataCollect Info'. When the 'More Info' button is clicked, it shows details for individual job steps (that is, individual srun instances), such as the working directory, arguments, srun parameters, etc.

At the bottom of the page, there is the 'Display Job Metrics' section, still in an experimental stage, which, when fully implemented, will display plots of some performance data (e.g, instructions per cycle (ipc_by_step and ipc_by_step_and_node) and memory usage) and power usage of the job. Select a metric and then click the 'View graph' button.

### Storage ¶

This area is about the project team's usage of the Community File System (CFS) and the HPSS archive system.

A summary of the CFS storage allocation and usage for the project is provided at the top of the page, followed by a plot of CFS storage usage by the team over time.

Below are the meaning of the terms used:

• Storage Allocation: CFS storage allocation (or quota) for the project.
• Storage Allocated to Directories: If the project has multiple CFS directories for the project, the project team can distribute the allocation among the directories. This is the sum of the maximum storage usage for the directories, and cannot be great than the storage allocation.
• Unallocated Storage: The storage that is not allocated to any CFS directory of the project.
• Storage Used and % Storage Allocation Used: CFS storage usage.
• Files Allocation: CFS inode allocation (or quota) for the project.
• Files Allocated to Directories: The sum of the maximum inode set for the CFS directories of the project; cannot be great than the CFS inode allocation.
• Unallocated Files: The inode allocation not allocated to any CFS directory of the project
• Files Used and % File Allocation Used: CFS inode usage.

You can find the CFS Directory Usage section, too. It shows space and inode usage for the Community File System per individual project members

At the bottom of the page, you can find the HPSS Archive section, which shows the HPSS allocation and usage for the project.

This area shows usage per user of the project's HPSS allocation. PIs, PI proxies and project resource managers can assign user quotas in the '% Allowed by Project' field. For more info, please read the Iris Guide for PIs and Project Managers page.

### Roles ¶

This page displays project roles for all members in a project. The possible project roles are: PI (Principal Investigator), PI proxy, Project Resource Manager, Project Membership Manager, or User.

PIs and PI proxies can change the project role for users. Also, they can add or remove users to/from his/her project account. For more info, please read the Iris Guide for PIs and Project Managers page.

### Groups ¶

The display shows what Unix groups are associated with a project allocation account and who are members of each group.

PIs, PI proxies, project resource managers, and project membership managers can request to create a new Unix group by clicking the '+ New Group' button. PIs, PI proxies and project membership managers can add a user to a specific group or remove a user. For more info, please read the Iris Guide for PIs and Project Managers page.

### Details¶

This page shows detailed info about a project itself, such as its PI, PI proxies, project description, allocation pool, allocation type, DOE Office Science Category, ERCAP info, etc. Project managers can also add publications to the 'Publications' section by clicking the '+ Add Publication' button.

### History ¶

This tab menu shows all the updates made to the project (such as adding a user to the project) with info on who created the event and when. To see the record of a specific event, click the 'View Log' button in the corresponding row.

## Reports¶

When you click the 'Reports' pull-down menu from the top menu bar, you will see various report generation options, with which you can view compute and storage usage information for allocation accounts. For example, you can generate compute usage for a certain date or a month, for an allocation account or a group of accounts.

### Search and Display Options¶

Most report types in the Reports pull-down menu will show four tabs near the top of the page. They are labeled as 'Select Columns', 'Filter Report', 'Select Rollups', and 'Report Results'. We will discuss about these menus here.

#### Select Columns¶

This is to select columns that will appear in a search result. The default set of columns is pre-set depending on the report type. The 'Daily Compute Activity' report includes 'Day', 'User', 'Project', 'Host Name', 'Science Category', 'Program', 'Office', 'Hours Charged', 'Raw Hours', 'Machine Hours', '% Used', and 'Balance' while the 'Monthly Compute Activity' report includes the 'Month' column instead of the 'Day' column.

There are other columns available (e.g., 'Premium Hours'), and you can add more by clicking the '+ Add Column' button. To include all available columns, click '+ Add All Columns'.

You can remove a column by clicking on the trash can icon. The order of the columns can be changed with the up and down arrows. If you click the triangle with an exclamation mark inside, all the columns after the column are removed en masse.

The number in the tab is the number of selected columns.

By selecting an optional aggregation operation, a column can be set to show an aggregated value over the data of the same set of attributes (column values), instead of individual data entries. The result of the aggregation will be shown in the column. The supported aggregations are count (frequency of the case with the same set of attributes), count distinct (frequency for the distinct set of attributes), sum (sum of the values over the entries with the same set of attributes), avg, min and max. The header of the column will change to reflect the aggregation operation: 'count of ...', 'sum of ...', etc.

You can mark the 'Single total line (needs aggregations + no rollups)' checkbox to generate a single summary line at the end of the report dataset. It will show the aggregated value over the entire data for the columns containing numeric values with an aggregation operation turned on. Thus, you need to have at least a column with aggregation enabled in order to use this feature. Also, a rollup (see below) should not be set. Columns containing numeric values but without an aggregation enabled will show meaningless numbers: zeros (0.0 and 0.0%).

#### Filter Report¶

You can set search criteria that need to be satisfied for a report by using various search categories. Available filter categories are pre-set, depending on the report type. For a 'Daily Compute Activity' report, you can use filters such as 'Day', 'User', 'Project', 'PI', 'Hours Charged', etc. while a 'Monthly Compute Activity' report uses 'Month' instead 'Day'.

To add more filters to narrow down your search, click the '+ Add Filter' button. Select the field name from the pull-down menu. Choose a comparison operator (=, !=, <=, >=, <, >, contains, starts with, is null, or is not null), and enter the field value, if required.

The number in the tab is the number of the filters set.

To generate a report about a previous allocation year, choose the year in the 'Year' pull-down menu. It is set by default to the current allocation year.

#### Select Rollups¶

Rollups are an advanced feature that allows for the creation of, for example, subtotal rows of aggregated data. To create a rollup, first there should be at least one aggregated column and at least one non-aggregated column. An aggregation is performed over a non-aggregated column that is set for a rollup, and the end result is generation of a partially aggregated result (e.g., a subtotal) over all attribute values in the column. Note that an aggregation type is set in the 'Select Columns' tab.

On the 'Select Rollups' tab, you can decide which of the non-aggregated columns you want to roll up to create partial aggregations.

The figure below shows a report on computational usage for a project over a few days, generated with the 'Day', 'Host Name', 'Hours Charged' (aggregated with sum) and 'Premium Hours' (aggregated with sum) columns. The first 18 rows are the usage data generated with 3 filters (the start and end dates, and the project, in this example). As shown above, a rollup is set for the 'Host Name' column, to show in essence the daily usage, regardless of where individual jobs ran. The bottom 3 rows are the result of the rollup. You can sort in the chronological order by clicking on the 'Day' column header.

Multiple columns can be set for rollups. The result will also include intermediate results from progressive rollups over one more columns at a time, starting from the last one. The number in the 'Select Rollups' tab is the number of the rollup columns.

#### Report Results¶

Click the 'Run Report' button to generate results that satisfy the specified conditions. You can see the search result by selecting the 'Report Results' tab.

The number in the 'Report Results' tab is the number of the generated data items (rows).

### Types of reports¶

#### Daily Compute Activity¶

This report shows computational usage for a specified date, or over a time period that is defined with dates.

#### Monthly Compute Activity¶

This is similar to the 'Daily Compute Activity' above, but the report period is based on a calendar month.

#### Jobs ¶

This report shows details about user jobs. Available search filters are 'Job', 'User', 'Project', 'Program', 'Host Name', 'Partition', 'QOS', 'Submit', 'Start', 'End', 'Wait Time', 'Elapsed Secs', 'CPUs', 'Nodes Allocated', 'Hours Charged', 'Raw Hours', 'Machine Hours', 'Charge Factor', 'Reservation ID', and 'Has Transfer'.

If you click the job ID link, you will see a summary for the job, as explained above.

This is reserved only for NERSC staff for administrative work.

#### Projects ¶

This report shows details such as the CPU account name, GPU account name, PI name, allocation amount, CPU/GPU Node Hours charged, balance, etc. for all project accounts.

#### QOS Users¶

A QOS enables a user to use a certain resource - premium for using the premium queue, cmem for using Cori Large Memory Nodes, gpu for using Cori GPU Nodes, etc. This menu shows which QOS' users have access to.

#### Project Directories¶

This is to show details such as the owner, quotas, usage, etc. about the Community File System (CFS) directories created for projects.

#### Allocation Transfers¶

This menu is only for NERSC staff and DOE allocation managers for administrative work.

#### Server Users¶

This shows which login servers a user has access to. You can narrow down your search with the 'User', 'User Name', 'Email', and 'Login Server' filters.

#### Publications¶

This menu shows publications linked to NERSC users or projects.