Accounts and Credit Allocations
The Roman Research Nexus uses a credit system to track and manage compute, storage, and data egress resource usage.
Individual Accounts
Any user with a valid MyST account account may launch a session under their individual account. Individual accounts are intended for exploratory work, including learning the platform, running tutorials and workflows, and developing small-scale analysis ideas.
Individual accounts include a small pedagogical credit allocation designed to help users become familiar with compute, storage, and data egress usage in the cloud. Each individual account receives a default allocation of 30 credits, replenished at a rate of 1 credit per day up to the 30-credit maximum. The purpose of this allocation is not to restrict users, but to help them build intuition for cloud resource use. Individual account credit limits are generally not strictly enforced, although unusually high or inappropriate resource usage may be subject to review.
When a session is launched under an individual account, resource use is recorded against the user's credit balance. Users retain all access permissions granted to them, including access to files associated with teams of which they are members. Selecting an individual account affects resource accounting, not file access or permissions.
Individual accounts provide access to smaller compute configurations suited for interactive exploration, tutorials, workflow development, and light analysis tasks. Larger analyses and collaborative projects are generally best suited to team accounts, which provide access to additional resources.
Team Accounts
Team accounts support collaborative and project-based work and provide access to shared resources that enable groups to work together within the Nexus. Team members can collaborate through shared workspaces, shared storage, and Real-Time Collaboration (RTC) servers. Unlike individual accounts, team accounts may launch any available server configuration, providing access to larger compute resources for more demanding analyses and workflows.
Each team account includes a shared credit allocation that is used to track compute, storage, and data egress usage across the team. During the current operations cycle, team accounts can receive allocations of up to 4,000 credits. Credit allocations are distributed incrementally, typically beginning with 500 credits, and team administrators may request additional credits through MyST as needed, up to the current allocation limit. Allocation limits and policies may evolve as Nexus capabilities, usage patterns, and available resources continue to develop.
Roman programs approved through the proposal process automatically receive a Nexus team account. During the current operations cycle, approved programs receive the standard Bin 1 allocation (4,000 credits). Proposers anticipating resource requirements beyond the standard allocation may request additional credits as part of the proposal submission process. Requests above Bin 1 require justification supported by resource estimates and benchmarking. See the Benchmarking and Resource Estimation documentation for guidance.
When a session is launched under a team account, resource use is recorded against the team's shared credit balance. Unlike individual accounts, team credit limits are strictly enforced. The Nexus notifies team members as they approach their credit limit through both email notifications and in-session credit warnings, allowing teams to monitor usage and take corrective action before credits are exhausted. Once a team reaches a negative credit balance, compute resources are disabled until additional credits are allocated. Team files remain accessible through users' individual accounts, even when a team account is unable to launch new compute resources because of insufficient credits.
Team Management in MyST
Team creation and administration are managed through the MyST account interface. Users may request new Nexus team accounts through the Science Platform section of their MyST account. Team requests include basic project information, designated team administrators and backup contacts, and a brief project justification. Requests are reviewed by STScI prior to approval.
Once approved, team administrators can use the MyST interface to:
- View team information and current credit allocations.
- Add and remove team members.
- Manage team administrators and backup contacts.
- Request additional Nexus credits.
- Monitor allocation status and available credits.
All team requests and credit allocation requests are reviewed by STScI to ensure alignment with Roman community activities. Typical review times are approximately two weeks, although processing times may vary depending on request volume.
For information on requesting additional credits beyond the standard allocation for proposal-supported programs, see the Computational Benchmarks and the Estimating Resource Usage and Costs documentation. Team administrators may request dedicated Amazon S3 buckets for team storage, as described in the Storage Resources documentation.
Credit Usage and Resource Management
Credit usage on the Nexus includes contributions from compute, storage, and data egress. Users can monitor their credit activity through the cost-monitor dashboard available on the Nexus, which provides a summary of total credits used, a breakdown across compute, storage, and egress, and a record of recent server activity. The dashboard updates automatically as sessions run and is intended to help users understand how their workflows translate into resource consumption. Additional documentation on the dashboard is available within the Nexus.
Compute costs depend on the server configuration selected at launch. Additional information about available server configurations is provided in the Compute Resources documentation.
Storage costs are based on the amount of data retained within Nexus-managed storage resources. Additional information data storage is provided in the Storage Resources documentation.
Egress is permitted for all users, although it is generally discouraged because Roman workflows are designed to run within the cloud environment, where data and tools are co-located. The current egress cost is 84 credits per terabyte (TB) of data transferred out of the platform. For team accounts, any egress required as part of account closeout is covered by STScI.
Together, compute, storage, and egress provide a transparent accounting model that helps users understand and manage their use of shared Nexus resources.
For additional questions not answered in this article, please contact the Roman Help Desk.
