How should I import the Mario class using this convention?

You should use 'from maxfuse import Mario' instead of legacy paths or direct submodule imports.

What is the primary goal of this MaxFuse skill?

The primary goal is to standardize how the MaxFuse package is imported and how data files are referenced within Jupyter notebooks to ensure code reproducibility.

Does this skill help with the transition from mario-py?

Yes, it specifically identifies failed attempts to use the old mario-py directory and provides the correct maxfuse package alternatives.

Which Python version is this skill verified for?

These conventions have been verified for Python 3.12 environments using the maxfuse package.

Why are relative paths like '../data/' discouraged?

Because VS Code and Jupyter typically set the working directory to the repository root, making paths relative to the root (e.g., 'data/file.tsv') more reliable than those relative to the 'notebooks/' folder.

MaxFuse Notebook Import Conventions

Name: MaxFuse Notebook Import Conventions
Author: smith6jt-cop

bysmith6jt-cop

Ciencia de Datos y ML

Standardizes import patterns and file paths for MaxFuse Jupyter notebooks to ensure reliable package integration.

Acerca de

This skill provides a comprehensive set of verified import patterns and file path conventions specifically tailored for the MaxFuse library. It facilitates the migration from legacy structures to the unified MaxFuse package, resolving common issues related to submodule access, outdated directory references, and working directory inconsistencies. By implementing these standards, users can ensure their data science notebooks remain reproducible and correctly integrated with core modules like Fusor and Mario, particularly when working within VS Code or Jupyter environments.

Características Principales

Corrects submodule access for core utilities and MARIO matching
Standardizes top-level imports for Fusor and Mario classes
Identifies and prevents legacy mario-py directory errors
Optimized for VS Code and Jupyter root working directory defaults
Enforces root-relative file pathing for data and results
0 GitHub stars

Casos de Uso

Troubleshooting module resolution errors in multi-directory repositories
Migrating legacy notebooks from the old mario-py structure to MaxFuse
Standardizing data loading paths across collaborative research projects

Acerca de

Características Principales

Corrects submodule access for core utilities and MARIO matching
Standardizes top-level imports for Fusor and Mario classes
Identifies and prevents legacy mario-py directory errors
Optimized for VS Code and Jupyter root working directory defaults
Enforces root-relative file pathing for data and results
0 GitHub stars

Casos de Uso

Troubleshooting module resolution errors in multi-directory repositories
Migrating legacy notebooks from the old mario-py structure to MaxFuse
Standardizing data loading paths across collaborative research projects