Mase/NewComputeBench/PLENA/../ repo Separation

[Aaron-Zhao123]

Repo Separation - Task List

Updated Goal (2 Feb 2026)

We will create five independent GitHub repositories, each responsible for a minimal, well-defined functional unit, with no redundant or overlapping functionality between them.

1. MASE: Provides core compiler functionality, including quantization, PLENA-based passes, and other necessary passes.

2. MASE Acceleration Gen (could be a different name): Imports mase.passes and independently maintains its own pass set, effectively mase.passes + own.passes.

3. PLENA: Defines the single-core, full-stack NPU design flow. Imports mase.passes is necessary.

4. PLENA-Dist (could be a different name): Implements system-level multi-chip interconnection simulation based on PLENA.

5. NewComputeBench: Imports mase.passes and updates the previous fine-tuning workflow to a pre-training workflow.

MASE Acceleration Gen (new repo build @firemountain154B ):

• Build a new repo named MASE Acceleration Gen
• Only keep the hardware acceleration generation dataflow
  • import mase if dependent
• Documentation
  • Write tutorial
• Tests
  • Unit tests
  • Create a minimal test in CI

MASE (integrate quantization @JiaYi):

• Integrate quantization passes
• Documentation
  • Write tutorial
• Tests
  • Unit tests and pass CI

MASE (remove overlap @Binglei):

• Clean the code
  • remove NewComputeBench passes
  • remove hardware flow
  • keep the rest (lab, bert.. stuff for Aaron)
• Documentation
  • Update doc for MASE
• Tests
  • Unit tests and pass CI

PLENA (@GeorgeWu1204 @firemountain154B ):

• before open source
  • Pass RTL testbench simulation/synthesis
  • Pass ASM simulation (single-layer Transformer)
• UV env, import mase
• Documentation
  • Write tutorial
• Tests
  • Unit tests
  • Build CI

PLENA-Dist (@przemekff ):

• Documentation
  • Write tutorial

NewComputeBench (@JeffreyWong20 @ChengZhang-98 @przemekff @firemountain154B @GeorgeWu1204 @Binglei ):

Follow the previous task goal below

Previous Goal (1 Nov 2025)

We would like to add all NewComputeBench related code change in a single PR.

---

Core Module Transformation Passes

For each module-level transformation pass on New Compute Paradigm, complete the following:

SNN pass (SpikeZIP-TF @JeffreyWong20 ):

• Rename model name to snn rather than ann2snn
• Implement new module transform pass
  • Integrate into existing pipeline
• Documentation
  • Write tutorial (under docs/tutorials/newcompute)
  • Add to main documentation (docs/source/modules/documentation)
  • Add module-level documentation (docs/source/modules/chop/module_transform)
• Tests
  • Unit tests
  • Integrate a minimal test in current CI
• Result reporting on project website

SNN pass (STA @GeorgeWu1204 ):

• Implement new module transform pass
  • Integrate into existing pipeline
• Documentation
  • Write tutorial (under docs/tutorials/newcompute)
  • Add to main documentation (docs/source/modules/documentation)
  • Add module-level documentation (docs/source/modules/chop/module_transform)
• Tests
  • Unit tests
  • Integrate a minimal test in current CI
• Result reporting on project website

ONN pass (STA @ChengZhang-98):

• Implement new module transform pass
  • Integrate into existing pipeline
• Documentation
  • Write tutorial (under docs/tutorials/newcompute)
  • Add to main documentation (docs/source/modules/documentation)
  • Add module-level documentation (docs/source/modules/chop/module_transform)
• Tests
  • Unit tests
  • Integrate a minimal test in current CI
• Result reporting on project website

PIM pass (PIM @firemountain154B ):

• Implement new module transform pass
  • Integrate into existing pipeline
• Documentation
  • Write tutorial (under docs/tutorials/newcompute)
  • Add to main documentation (docs/source/modules/documentation)
  • Add module-level documentation (docs/source/modules/chop/module_transform)
• Tests
  • Unit tests
  • Integrate a minimal test in current CI
• Result reporting on project website

---

Documentation & Testing Review (@Binglei @przemekff)

• Review and update existing tests (pytest)
  • Verify all tests pass (if not skipped)
  • Fix broken tests
  • Add missing test coverage
• Review and update tutorials
  • Verify all tutorials work end-to-end
  • Update outdated content
  • Add missing examples
• Review current documentation
  • Fix errors and inconsistencies
  • Update for new features

---

Optimizations (To Consider, @przemekff)

• Package Management Migration
  • Evaluate UV-based package management
  • Create migration plan if approved
  • Implement migration
  • Update documentation
• Code Formatting
  • Migrate from Black to Ruff
  • Configure Ruff for automated reformatting
  • Apply formatting to entire codebase
  • Update CI/CD pipelines
  • Update contributor guidelines