Papers › Mixture-of-Subspaces in Low-Rank Adaptation

Mixture-of-Subspaces in Low-Rank Adaptation

16 Jun 2024arXiv:2406.11909archive 2025-07-28

Taiqiang Wu, Jiahao Wang, Zhe Zhao, Ngai Wong

In this paper, we introduce a subspace-inspired Low-Rank Adaptation (LoRA) method, which is computationally efficient, easy to implement, and readily applicable to large language, multimodal, and diffusion models. Initially, we equivalently decompose the weights of LoRA into two subspaces, and find that simply mixing them can enhance performance. To study such a phenomenon, we revisit it through a fine-grained subspace lens, showing that such modification is equivalent to employing a fixed mixer to fuse the subspaces. To be more flexible, we jointly learn the mixer with the original LoRA weights, and term the method Mixture-of-Subspaces LoRA (MoSLoRA). MoSLoRA consistently outperforms LoRA on tasks in different modalities, including commonsense reasoning, visual instruction tuning, and subject-driven text-to-image generation, demonstrating its effectiveness and robustness. Codes are available at https://github.com/wutaiqiang/MoSLoRA.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 6 samples from 1 repository, 4 ran (1 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 4 samples that ran has no recorded date.

wutaiqiang/moslora officialmentioned in papermentioned on GitHubpytorchSyntology: 6 samples, 4 ran (3 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

6 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong
1ran
2unverified

Licence: 6 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from wutaiqiang/moslora. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

wutaiqiang/moslora official repository 6 samples, 4 ran (3 instrument-failed) · 2 unverified
determine_scheduler_type subject_driven_generation/train_dreambooth_lora_sdxl.py ran no licence file found · pointer only · 03e1c6795642a8db · report fixture: signature pretrained_model_name_or_path:str/0/str, revision:str/0/str · returned str · level recorded 2026-09-24
generate_prompt in 110 papers commonsense_reasoning/finetune.py ran · our draft was wrong no licence file found · pointer only · 56e674752db00649 · report fixture: signature data_point:dict/0/? · returned str · level recorded, date not recorded
generate_prompt in 110 papers commonsense_reasoning/commonsense_evaluate.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 1c6b8be890b6118a · report fixture: signature instruction:str/0/str, input:str/0/str · returned str · level recorded 2026-09-22
load_data in 700 papers commonsense_reasoning/commonsense_evaluate.py ran · our draft was wrong no licence file found · pointer only · 56a9466ff35b35bb · report fixture: signature args:Args/0/? · returned list · level recorded 2026-09-22
import_model_class_from_model_name_or_path in 64 papers subject_driven_generation/train_dreambooth_lora_sdxl.py unverified no licence file found · pointer only · 86965b6bae051ea4 · report
main in 235 papers commonsense_reasoning/commonsense_evaluate.py unverified no licence file found · pointer only · b8da7d64c2442014 · report

Tasks

Common Sense ReasoningImage GenerationQuestion AnsweringSentence CompletionText to Image GenerationText-to-Image GenerationVisual Question Answering

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Common Sense Reasoning ARC (Challenge) LLaMA 3 8B + MoSLoRA (fine-tuned) Accuracy 81.5 #16 of 54 Archive leaderboard report
Common Sense Reasoning ARC (Easy) LLaMA 3 8B+MoSLoRA (fine-tuned) Accuracy 90.5 #2 of 47 Archive leaderboard report
Common Sense Reasoning WinoGrande LLaMA3 8B+MoSLoRA Accuracy 85.8 #10 of 77 Archive leaderboard report
Question Answering BoolQ LLaMA3+MoSLoRA Accuracy 74.6 #38 of 65 Archive leaderboard report
Question Answering OpenBookQA LLaMA-3 8B+MoSLoRA Accuracy 86.8 #14 of 45 Archive leaderboard report
Question Answering PIQA LLaMA3 8B+MoSLoRA Accuracy 89.7 #2 of 67 Archive leaderboard report
Question Answering SIQA LLaMA-3 8B+MoSLoRA (fine-tuned) Accuracy 81.0 #5 of 24 Archive leaderboard report
Sentence Completion HellaSwag LLaMA3+MoSLoRA Accuracy 95.0 #5 of 89 Archive leaderboard report
Visual Question Answering MM-Vet LLaVA-InternLM2-7B-ViT + MoSLoRA GPT-4 score 35.2 #159 of 231 Archive leaderboard report
Visual Question Answering MM-Vet InternLM2+ViT (QMoSLoRA) GPT-4 score 35.2 #160 of 231 Archive leaderboard report
Visual Question Answering MMBench LLaVA-InternLM2-ViT + MoSLoRA GPT-3.5 score 73.8 #1 of 5 Archive leaderboard report
Visual Question Answering MMBench LLaVA-LLaMA3-8B-ViT + MoSLoRA GPT-3.5 score 73.0 #3 of 5 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Diffusion

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections