File size: 1,846 Bytes
a3e28f5
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
# Contributing to Q-TensorFormer

Thank you for your interest in contributing to **Q-TensorFormer**! We welcome contributions from researchers, systems engineers, and open-source practitioners in tensor networks, efficient inference, and hardware-aware computing.

---

## 🛠️ Development Environment Setup

1. **Clone the repository**:
   ```bash
   git clone https://huggingface.co/Premchan369/Q-TensorFormer
   cd Q-TensorFormer
   ```

2. **Create a virtual environment**:
   ```bash
   python -m venv venv
   source venv/bin/activate  # On Windows: .\venv\Scripts\activate
   ```

3. **Install dependencies**:
   ```bash
   pip install -r requirements.txt
   ```

---

## 🧪 Running the Test Suite

Before submitting any Pull Request, ensure that all unit and integration tests pass:

```bash
pytest -v
```

The test suite covers:
* `tests/test_model.py`: Forward pass shapes, causal mask handling, GQA attention, attention sinks, and PID stability.
* `tests/test_frontier_v10.py`: Triton/JIT kernels, GGUF serialization, ONNX export, and Multimodal Vision-Language reasoning.

---

## 📐 Guidelines for Contributions

1. **Scientific Integrity**:
   * Never fabricate or invent benchmark numbers.
   * Every result must be explicitly tagged as `[MEASURED]`, `[ESTIMATED]`, `[SIMULATED]`, or `[PROJECTED]`.
2. **Zero-Overhead Contract**:
   * Dynamic rank switching must remain $\mathcal{O}(1)$ without runtime SVD or memory allocations.
3. **Backward Compatibility**:
   * Preserve Hugging Face Hub `trust_remote_code=True` compatibility with `AutoConfig` and `AutoModelForCausalLM`.

---

## 📬 Submitting Changes

1. Create a feature branch: `git checkout -b feat/my-improvement`.
2. Commit your changes with clear semantic commit messages (`feat: ...`, `fix: ...`, `docs: ...`).
3. Push to your branch and open a Pull Request.