Skip to main content

Rhino FCP Workspaces

The Rhino FCP Workspace is a helpful tool that makes your workflow easier when working in the Trusted Research Environment (TRE). A Rhino FCP Workspace is a user-specific, private, dedicated folder (/workspace) where you can keep your code, configuration, and intermediate files. This folder keeps your work saved across multiple interactive sessions, so you don’t have to manually save and import files as input/output datasets.  

Key Points

Here are some key points about Rhino FCP Workspaces:

  • They are available in Interactive Container code runs and code objects.
  • They are automatically saved to the Rhino Client when an Interactive Container session ends.
  • They are automatically pre-populated with files from your last session, as long as you start on the same Rhino Client and workgroup.
  • Workspaces are strictly scoped to a user and a workgroup. Files saved by one user won’t be visible to others, even within the same workgroup. Also, if a user switches to a different workgroup, they won’t see files from their previous workgroup’s workspace.
  • Workspaces are client-bound, meaning they are stored locally on the specific Rhino Client where the session was run and don’t automatically sync across other Rhino Clients.

The total workspace storage per user is subject to a configurable limit on each Rhino Client (this is a priority requirement). If the /workspace folder contains files when a session ends, those files will overwrite any previously saved contents for that user and workgroup. An empty /workspace folder will be ignored to avoid accidentally deleting a user’s saved workspace.   

Other Considerations

Here are a few things to keep in mind when working with your workspace.

  • If you have two concurrent interactive container sessions for the same user on the same Rhino Client, they can impact each other.  For example, if you rename a file in one interactive container session, it will be renamed in the other one.  
  • If your /workspace folder contains files, its contents will overwrite any previously stored workspace files that have the same name. 
  • Workspaces are not shared between different workgroups, even if those workgroups share the same Rhino Client.

Use care that you do not accidentally save sensitive, row-level data from the interactive session into files in their workspace (e.g., in a Jupyter Notebook). Note that this risk is mitigated because the workspace is client-side, user/workgroup-specific, and there is no direct way to extract its contents outside of the Rhino Client.

Related Articles:

 

 

Was this article helpful?