For the complete documentation index, see llms.txt. This page is also available as Markdown.

Release Notes 2.21 (June 2024)

New Visual Design

The user interface has been updated to enhance accessibility and match the new Code Ocean color palette.

GPU RAM Visible in Dedicated Resource Description

For AI/ML use cases, it can be important to know how much of the RAM available in a compute resource is specifically GPU RAM. This information is now included in the description of every dedicated compute resource as shown below.

Pipelines Enhancements

Nextflow Artifacts Moved from Results Folder to Run Sub-Menu

Previously, a Pipeline's results also included the Nextflow artifacts associated with the run (dag.html, nextflow.log, timeline.html, report.html, trace.txt) and would therefore be included in a Data Asset created from the run's results. Now, these Nextflow artifacts are located in a separate sub-menu of the run context menu accessed by clicking the three dots next to any run in the Pipeline Timeline.

Pipeline Export: Added Support for Secrets and App Panel Params

Until now, Capsule secrets and App Panel parameters were not supported/included when exporting a Pipeline. As of v2.21, if a user has defined their secrets as an environment variables (e.g. as Custom Keys) the exported Pipeline's autogenerated nextflow.config will now be configured to white list these variables and the REPRODUCING.md file will provide instructions for creating the appropriate secrets locally. The nextflow.config file will also now include the Pipeline's App Panel parameters.

Public API Extended

Import Result of External Computation via API

As the next phase of Code Ocean's support for on-prem resources, when users obtain results from the external execution of a Capsule/Pipeline, those results can now be imported to Code Ocean via the public Data Assets API while maintaining lineage and provenance.

Create Result Data Asset from External Result

Last updated