BigBang-v1 vs Carbon-X

BigBang-v1

A Qwen3.6-35B-A3B fine-tuned on synthetic research problems, under plain Apache 2.0, for search, science and coding work. The publisher ships BF16 only, about 86 GB to run, and has no report, safety results or replies to questions, so smaller builds and support come from others.

Carbon-X

A DNA specialist cousin that another agent calls for variant-effect and sequence questions, with DNA kept on the machine. Hugging Face's Q4_K_M GGUF needs about 12 GB and Q8_0 about 19 GB, on llama.cpp b11742 or later. It isn't clinically validated, it isn't trained for tool calls or reasoning, and the card contradicts its own GGUF repository on llama.cpp support.

BigBang-v1

1. On the reference machine use vllm serve endless-frontier/BigBang-v1 --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
2. The card says to keep at least 128K of context so its thinking isn't cut short
3. Thinking control isn't documented, try the base template's enable_thinking false in chat_template_kwargs and check the output
4. For a smaller build you'll need someone else's quantisation, the publisher has none
5. Validate JSON output yourself or use the runtime's guided decoding

Carbon-X

1. Quickest start is llama-server -hf HuggingFaceBio/Carbon-X-GGUF:Q8_0 -ngl 99 -c 40960 --jinja --chat-template-kwargs '{"enable_thinking": false}' --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0, on llama.cpp b11742 or later
2. With vLLM or Transformers pass trust_remote_code, and expect the tokenizer to fetch Qwen/Qwen3-4B-Base at a pinned revision on first load
3. Keep enable_thinking false and the card's sampling (temperature 0.6, top_p 0.95, top_k 20), the settings every reported result used
4. Keep DNA in files and pass sequences by name, compute positions and base changes in code and send them as context, the card says the model miscounts long sequences
5. Only A, C, G and T form 6-mers, so filter N and other IUPAC codes first or they become a single oov token
6. Strip the dna tags from answers if you need bare sequence, llama.cpp keeps them in the text
7. Cap max_tokens for next-base questions, long DNA generation is slow and degrades