Library Structure

Before diving into the modules, notebooks, or installation steps, it helps to know how the JuSPICE repository is laid out on disk — what’s already there when you clone it, and what gets created automatically once you install JuSPICE and start running notebooks.

Fixed Structure

The full repository tree, plus what's already there the moment you clone JuSPICE — the package, notebooks, sample data, tests, and dependency files.

Auto-Generated Folders

What appears on disk only once you install and start running things — virtual environments, generated images, trained models — and what's actually written inside each folder.

See also

• Modules — the processing/analysis capabilities in juspice/

• Installation — setting up venvs/

• Sample Data — details on what’s in Sample_data/

• Notebook Examples — running the notebooks that create the auto-generated folders above