HPC Development & Testing Workflow FAQs

Question 1

Does this work with Jupyter Notebooks?

Accepted Answer

Yes, it specifically includes patterns for using editable installs and %autoreload 2, allowing notebook-based testing to reflect code changes in the repository immediately.

Question 2

How does this skill help maintain Claude's context?

Accepted Answer

By utilizing VS Code Multi-Root Workspaces, Claude can access both your code repository and external data folders simultaneously. This prevents the session from ending when switching between different directory roots on the HPC.

Question 3

Is this workflow specific to HiperGator?

Accepted Answer

While verified on HiperGator, the strategies for multi-root workspaces, editable installs, and test data extraction are applicable to any SLURM-based HPC environment using VS Code Remote SSH.

Question 4

Why use a 2x2 grid for test data instead of a single tile?

Accepted Answer

A 2x2 grid is the minimum viable configuration to test multi-tile algorithms such as stitching, registration, and snake-pattern processing, while remaining small enough (~3GB) for rapid development iteration.

Question 5

How does it handle large data indexing issues?

Accepted Answer

The skill provides JSON configuration patterns for 'search.exclude' that prevent VS Code from attempting to index massive data directories, which otherwise causes high CPU usage and lag on login nodes.

HPC Development & Testing Workflow

Key Features

Use Cases

HPC Development & Testing Workflow

Key Features

Use Cases