Panomics Documentation
  • Overview
  • Projects
    • Project Structure
    • Project Visibility
    • Project Access
  • Samples
    • Sample Lifecycle
    • Sample Ingestion
    • Sample Metadata
  • Analyses
    • Create an Analysis
    • Delete an Analysis
    • Change Analysis Status
    • Publish an Analysis
    • View Analysis Audit Trail
    • Analysis Workbench
      • Quality Control
      • Gene Expression
      • Compute Statistics
      • Sample/Cell Explorer
        • Normalization
        • UMAP
      • Cell Composition
      • Marker Genes
      • Differential Gene Expression
      • Differential Pathway Activity
      • WGCNA
      • Gene Set Enrichment
    • Data Slices
  • OmicsBrowser
  • Gene Signature Similarity
  • Compute Runtimes
    • Codeless Compute
    • Code-based Compute
  • API Keys
  • Administration
    • Roles
    • Users
    • Ontologies
    • Metadata Fields
    • Collections
    • Gene Set Collections
    • Organization Settings
  • Release Notes
  • Technical Support
  • Legal
Powered by GitBook
On this page
  • Spinning-up a JupyterLab runtime
  • Copying assets to and from a JupyterLab runtime
  • Terminating a JupyterLab runtime
  1. Compute Runtimes

Code-based Compute

Spin-up JupyterLab or RStudio runtimes to run custom bioinformatics analyses.

PreviousCodeless ComputeNextAPI Keys

Last updated 7 months ago

JupyterLab and RStudio runtimes enable users to perform custom analyses without leaving Panomics' secure environment. Assets generated using Standard Compute can be seamlessly copied to JupyterLab and RStudio from any project's Assets tab.

Spinning-up a JupyterLab runtime

Copying assets to and from a JupyterLab runtime

JupyterLab runtimes have a panomics folder that ensures communication with the Panomics platform. That folder is mounted in all projects, under the Assets tab.

Terminating a JupyterLab runtime

Before terminating a JupyterLab runtime, make sure to copy all desired files to your Project mount.

In order to terminate a JupyterLab runtime, the panomics folder must be empty. This ensures no accidental data loss can take place.

Spin-up a JupyterLab runtime
Copying assets
Terminate a JupyterLab runtime