Deceema Portal¶

The Deceema Portal brings interactive computing into your browser. It gives you a clear, visual path to discover available applications, request the resources they need, launch sessions, and return to work already in progress.

Use the portal when you want the power of Deceema without building every workflow around a terminal.

For a complete walkthrough of browser-based files, shells, jobs, and interactive applications, continue to Open OnDemand on Deceema.

Discover Applications

Find interactive tools and environments available to your account.
Choose Resources

Match compute, memory, GPU, time, project, and QoS settings to your work.
Launch Sessions

Start an application on Deceema and connect from your browser when ready.
Manage Your Work

Track active sessions, reconnect when appropriate, and stop resources you no longer need.

Make sure you have:

An active Deceema account.
A project code and corresponding Quality of Service (QoS).
Access to the application or service you intend to use.
A clear estimate of the time, CPU, memory, and GPU resources your work needs.
Input files in a Deceema storage location accessible to the application.

Confirm your project and its corresponding QoS from your Deceema access approval or account details in Deceema Admin. If the expected project or QoS is missing, resolve the access issue before launching a session. See Requesting Access.

Launch an Interactive Session¶

Open the Deceema Portal address supplied by your organization and authenticate with your Deceema account. Never share your password, authentication code, or active browser session.

2. Choose an application¶

Open the application catalog and select the tool or environment that matches your work. Availability can depend on your project membership and assigned services.

Before continuing, check whether the application expects a particular file format, software environment, working directory, or project allocation.

3. Configure the session¶

The launch form may ask for some or all of the following:

Setting	What it controls	Choose carefully because
Project / account	The allocation used by the session.	It must match a project assigned to your account.
QoS	The service class under which the work runs.	It must correspond to the selected project.
Run time	The maximum duration of the session.	Sessions end when their requested time expires.
CPU or tasks	The processing capacity available to the application.	Requesting too little can slow the work; requesting too much can delay scheduling.
Memory	The working memory available to the session.	Insufficient memory can cause an application or session to fail.
GPU	Accelerator resources for supported workloads.	Request a GPU only when the application and workload use one.
Working directory	The initial location for project files and output.	The application must have permission to read and write there.

Keep project and QoS together

If you have access to multiple projects or QoS options, select a project code that corresponds to the required QoS. Do not guess—verify the pairing against your approved account details.

4. Launch and wait¶

Submit the launch form. The portal requests the resources from Deceema and shows the session's progress. A session may wait until suitable resources are available.

Do not repeatedly submit identical sessions because one is waiting. Check its state first; duplicate sessions consume allocations and make troubleshooting more difficult.

5. Connect and work¶

When the session is ready, use the portal's connect or launch action to open the application. Save important output to the appropriate Deceema storage location as you work.

Understand Session States¶

Labels vary by application, but an interactive session generally moves through these stages:

Stage	Meaning	What you should do
Requested	The portal has accepted your launch settings.	Confirm that only one intended request exists.
Queued	The session is waiting for suitable resources.	Review its requested resources and wait for scheduling.
Starting	Resources have been assigned and the application is initializing.	Allow startup to complete; avoid launching a duplicate.
Running	The application is ready or in use.	Connect, work, and save output regularly.
Ending	The session is stopping or its time is expiring.	Save final work and allow cleanup to finish.
Completed / Failed	The session has stopped.	Review available messages and diagnostics before retrying.

Closing a tab is not the same as stopping a session

Depending on the application, closing the browser tab may leave the Deceema session running. Return to the portal's session view and stop work you no longer need.

Work with Files Safely¶

Prepare large datasets in the appropriate Deceema storage before launching an application.
Choose a working directory that your project can access.
Save important work frequently and before the session reaches its time limit.
Keep source data separate from temporary output when possible.
Verify that expected output exists before ending a session.
Do not place credentials, private keys, or access tokens in notebooks, scripts, images, or shared directories.

For large or repeated workflows, use established data-transfer and storage methods instead of relying on browser uploads.

Applications, VMs, and Containers¶

The Deceema Portal can provide a browser-based entry point to available interactive applications and hosted environments. Depending on the services assigned to your project, the catalog may include:

Scientific and engineering applications.
Notebook or development environments.
Graphical desktop sessions.
Project-specific virtual machines.
Container-backed applications and reproducible environments.

The catalog is account-aware. If a service you expect is not visible, confirm your project access and then contact Support with the application name, project code, and expected access.

Use Resources Responsibly¶

Interactive work still consumes shared Deceema resources.

Start with the smallest sensible request and scale from evidence.
Choose a realistic run time rather than the maximum available value.
Stop idle sessions instead of leaving them to expire.
Avoid opening duplicate sessions for the same task.
Move repeatable or unattended workloads to a Slurm job when appropriate.
Save results to durable storage; do not treat a running session as storage.

For scheduled and repeatable compute, continue to Jobs on Deceema.

Troubleshoot the Portal¶

I cannot sign in

Confirm that account activation is complete and that you are using the portal address supplied by your organization. Record the exact error and time of the attempt. Never send your password, authentication code, or private key to support.

An application is missing

Confirm the expected project in your access approval or Deceema Admin. Include the application name, project code, and expected entitlement in your support request.

My session remains queued

Review the project, QoS, run time, CPU, memory, and GPU request. A queued session may simply be waiting for suitable resources. Capture the session identifier and current state before contacting support.

The session failed to start

Do not immediately submit multiple copies. Capture the session identifier, application name, launch time, project, QoS, requested resources, and the complete visible error. Check Service Status, then submit those details to support.

The browser disconnected

Return to the portal and inspect the session before launching another one. If it is still running, reconnect using the available session action. If it stopped, record its final state and any visible message.

My files are not visible

Verify the working directory, exact path, project membership, and file permissions. Check whether the same path is visible from a Deceema login node, then follow the storage guidance.

Send a Portal Support Request¶

Include the following information so the problem can be reproduced and routed quickly:

Portal support details

Deceema username:
Project code and QoS:
Application or environment:
Session identifier:
Launch date, time, and time zone:
Requested CPU, memory, GPU, and run time:
Browser and version:
Expected result:
Actual result:
Exact visible error:
Steps already tried:

Attach a sanitized screenshot only if it adds useful context. Remove personal data, credentials, tokens, and confidential project information first.

Open Support Check Service Status Explore Open OnDemand

First-Session Checklist¶

My Deceema account is active.
I verified the project and QoS I intend to use against my approved access.
My input files are in an accessible Deceema storage location.
My CPU, memory, GPU, and run-time requests fit the workload.
I know where the application will save its output.
I will stop the session when the work is complete.