Flywheel Core 19.1
September 2024
19.1.0
FEATURES
Bulk Export & Import
Any number of imports and exports may be run in parallel without blocking each other, and the system automatically scales up and down to meet varying demand while minimizing costs.
Project Locking with MFA Digital Signature
Locking a Project ensures no data within it can be added, moved, modified, or deleted by any user (including Site Admin), gear, device etc. Project lock/unlock actions require a digital signature, which includes additional identify verification via MFA (Multi Factor Authentication).
Enablement
- A Validated Instance of Flywheel Core is compliant with US 21 CFR Part 11.
- Customers may implement this by buying an audit and a deployment of a validated instance.
- There are two optional service options available for validated instances:
- Enhanced day-to-day support
- Process migration support defined by a customer-specific SOW
If you are interested in finding out more about Validated Instances and compliance with US 21 CFR Part 11, contact your salesperson.
Gear Access Controls
Full Release for Gear Access
The Gear Access Controls feature is exiting BETA and now available for all Flywheel customers.
By default, installed gears are accessible site-wide. However, there are situations where sites may want to restrict gear access to certain projects or users to:
- Ensure only specific gears are used on a particular project.
- Ensure gears in development are rolled out to a limited number of users or projects.
- Prevent unauthorized use of protected gears.
Site Administrators or Site Developers can now limit access for specific Gears to designated users and/or projects via both the UI and SDK.
Shielded VM option
Shielded VM on GCP offers an additional level of security for gear compute by providing verifiable integrity of Compute Engine VM instances. It provides the ability to assure instances haven't been compromised by boot- or kernel-level malware or rootkits.
For more technical information see GCP Shielded VM. This option is available for GCP sites and can be requested through Flywheel Customer Support.
Viewer
- Viewer should attempt to directly index the entire session when no files have been indexed.
- Viewer should display a detailed error message when unsupported modalities are found.
- Viewer should display a detailed error message when data cannot be indexed due to header parsing errors.
- Reader Tasks - Indexing or other Data Loading errors should be simplified in Reader Task context.
- Viewer should display a detailed error message if an attempt to directly index a file fails due to UID Conflict.
- Viewer should attempt to directly index a single file if it does not return in the metadata WADO request.
- Whenever possible, allow the system to be self-recoverable through ad-hoc indexing trigger by the Viewer when data is unavailable. Additionally, allow a larger class of issues to be self-diagnosable through improved error messaging and user-facing documentation.
FIXES
Data Management
- Resolved an issue where project Stats don't update from data added via the Dicom Web Uploader.
- Updated the Project filter on Basic Search so it is clear when all projects are selected.
- Resolved an issue where the Flywheel Search API does not return an error and message when an unsupported return type is requested.
Gears & Compute
- SDK Gears triggered from a Gear Rule configured to use a Role will fail with permission error when the SDK makes requests to the Flywheel API.
- Resolved an issue impacting HPC Client users where only GPU jobs were picked up, and non-GPU jobs were being left in the queue.
- Resolved issue with compute operational logging no longer working on an AWS site due to an image change.
- Improved subnet selection process for sites on Azure that require multiple subnets for their compute infrastructure. This should result in less job failures due to lack of available subnet. This issue has been resolved for AWS and GCP in previous releases.
- Fixed an issue where a batch run on one file would require selecting the input file, even though the batch functionality can infer the input files.
Ingest
- Fixed an issue with
ingest
using the--detect-duplicates
and--copy-duplicates
options where in rare circumstances the sidecar project attempted to be creating using the wrong name (multiple suffixes).
New (BETA) CLI
- Added note to the new (BETA) CLI installation instructions explaining that the
xz
library is a required dependency on macOS and Linux.
Viewer
- Fixed an issue where data in RGB color format was not correctly displayed in the V3 viewer.
- Added
WideFieldOphthalmicPhotographyStereographicProjectionImageStorage
to the list of supported SOP Class UIDs.
19.1.1
FIXES
Gears & Compute
- Improved gear compute resilience to network issues and increased visibility to the issue in the gear log.
19.1.2
FIXES
Viewer
- Improved error messaging when the V2 viewer tries indexing a session that contains non-DICOM files.
Jupyter Workspace
- Resolved issue where the "Save and Publish to Flywheel" menu selection in JupyterLab was no longer available in the File menu.
- Added retry logic to JupyterLab server requests to help deal with intermittent network errors for a particular site.
- Resolved an issue with Jupyter Workspace where the storage changes after the user sets it.
Core
- Resolved a database error deploying new Flywheel version 19.1 sites.
19.1.3
FIXES
Infrastructure
- Fixed an infrastructure issue introduced in Flywheel 19.1.0 where storage volumes would be created when services are scaled up but not reclaimed when services are scaled down, resulting in an unnecessary growth in the quantity of storage volumes.
19.1.4
FIXES
Compute
- Corrected issue with configuration logic that was causing a utility gear on a static engine to be stuck in pending.
- Resolved issue where GPU compute was not using the correct AMI, and so GPUs were not available in the compute.
- Resolved issue on a site where a job status was not updated as failed when it was stopped due to encountering lack of core response.
19.1.5
FIXES
Compute
- Resolves an issue with the compute container environment (Env Variables handling and executable file status) caused by maintenance upgrades to the compute platform. This was causing certain gears to fail depending on their use of the container environment.
19.1.6
FIXES
Core
- Resolves an issue where a user without the "Files Create/Upload" permission could upload files to Project, Subject, Session, or Acquisition containers. This issue was caused by a change in Flywheel Version 19.0.0, and does not impact the Web UI.
19.1.7
FIXES
Compute
- Resolves the issue where gears were failing on Azure & GCP sites. The OS version of the compute image for these sites was not compatible with latest compute container environment. The OS version was reverted to resolve the issue.