In this lesson, you will learn how to "onboard" a new model into the Jarvis ecosystem. By the end, you will have generated a Physics Datasheet that allows Jarvis to manage the model's VRAM efficiently.
- Jarvis is installed and configured.
- The model you want to add is downloaded (e.g.,
ollama pull qwen2.5:0.5b).
Jarvis needs to "see" the model run once to understand its memory signatures.
- Open your terminal.
- Start the model manually to generate an initialization log:
- Ollama:
ollama run qwen2.5:0.5b - vLLM: Run a test plan containing the model (e.g.,
python tests/runner_component.py plans/VLM_fast.yaml).
- Ollama:
During the run, the engine produces logs containing its internal memory allocations.
- If you used Ollama: Your system log is located at
%LOCALAPPDATA%\Ollama\server.log. - If you used vLLM: Capture the docker log:
docker logs vllm-server > startup.log.
Now, use the Zero-Config calibration tool to translate that log into a physics datasheet.
# Simply point the script to the log file.
# It will auto-detect the engine and the model name.
python tools/calibrate_models.py C:\Path\To\Your\startup.logNote: For vLLM models, this step is MANDATORY. Jarvis will refuse to run a vLLM model that has not been calibrated.
- Navigate to the
model_calibrations/directory in the project root. - You should see a new
.yamlfile named after your model (e.g.,vl_qwen2-vl-2b-instruct.yaml). - Open it. You will see the
base_vram_gbandcapabilitiesJarvis discovered.
Jarvis now understands the "physics" of this model. The next time you use it, the system will automatically optimize the VRAM allocation or provide guardrail warnings.