Stage1Model / Stage2OneShot / Stage2Autoregressive duplicate ~80 lines of scaffolding #39
Notifications
Due Date
No due date set.
Depends on
Reference: lars/giant#39
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stage1Model,Stage2OneShotandStage2Autoregressiveeach independentlyimplement: build-or-share
cond_enc,has_time→time_emb,merged_cond_dim,in_dimselection,build_trunk,n_sec_head,type_head,particle_type_cfgnormalisation. That's ~80 near-identical linesacross three classes, and it's why the objective/trunk/conditioning-injection
issues each have "×3" in their edit count.
Proposal: a
StageModelbase owning all of it, with the subclass supplyingonly its conditioning assembly (
_cond_embedvs_base_cond/_token_cond)and its output width. Do this after the trunk registry, conditioning
injection registry, and heads-factory issues, when what belongs in the base is
settled — otherwise the base gets refactored twice.
Migrated from
issues.md(v0.3.0 branch review, 2026-08-13), Issue 14.