Skip to content

ICCV 2025 — writing by contribution type

Plan the evidence before polishing the format

Choose the route closest to your main contribution, then adapt it. Architecture, objective, theory, analysis, resource, system, application and position arguments carry different evidence obligations. Only types present in this inspected corpus appear below. These editorial routes do not replace the conference's official track definitions.

For a new design, prepare a readable computation or representation overview, a comparison with matched conditions, and controls that test the changed component. Add pseudocode when iteration, state, sampling or gradient routing would otherwise be ambiguous. Add a theorem only when making a formal claim. A position paper instead needs a defensible thesis, substantive alternatives and implications; it is not required to pretend to be a leaderboard method.

Observed medians describe source versions. Suggested display packages are conditional editorial starting points, not official requirements or evidence of a necessary number of figures. Small groups provide examples, not robust estimates of a conference-wide standard.

Architecture & representation

The central deliverable changes the model's representation, component arrangement, information flow or reusable inference pipeline. Data, objectives and efficiency can still be substantial supporting contributions.

Corpus context · 23 papers: median 6 main figures and 4 main tables; body span ≈ 8.1 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Explain the failure that motivates a component, show the relevant data path, then test the component in the conditions where it should matter. Distinguish training from inference and learned modules from external pretrained dependencies. Use an architecture or train/inference comparison only when ownership, dependencies or different paths are central to the claim. Use component controls with a shared protocol; retain task-specific non-wins and indicate resource-sensitive settings. A complex diagram or a sequence of cumulative ablations is not by itself evidence that every component is necessary or independently causal.

Argument and section order

  1. Task, available inputs and the failure of the current representation
  2. One running example and input/output contract
  3. Overview diagram, followed by each genuinely changed component
  4. Training versus inference procedure and inherited components
  5. Main comparisons and controlled component/representation tests
  6. Efficiency, transfer, non-winning cases and scope limits

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Representation or architecture overview

Start with one overview; add insets only when they resolve different questions

Label inputs, outputs, inherited versus new components, frozen/trainable blocks and training-only paths.

When: Core when the novelty is computational organization; use a simple representation cartoon before the full diagram if the data object is unfamiliar.

Worked input/output or failure example

One compact example or aligned qualitative grid

Make the claimed representational problem visible and reuse the same example through the mechanism.

When: Especially useful for 3D geometry, multimodal tokens, articulated objects or structured outputs; do not add a gallery that does not test the claim.

Main comparison table

One focused table per incompatible task or information regime

Keep metric direction, data, backbone, reference inputs and refinement policy next to the results.

When: Separate single-model inference from per-instance optimization and privileged-input baselines.

Component/representation ablation

A compact switch table or matched diagnostic panels

Test the named reason for each component rather than removing modules without preserving compute or capacity.

When: Use matched controls when the mechanism claim depends on architecture rather than more parameters or more supervision.

Algorithm or mathematical statement

Only when the procedure or guarantee requires it

Expose iteration, state, branching or assumptions not recoverable from the diagram.

When: A feed-forward module does not require pseudocode or a theorem simply to look like an accepted paper.

Appendix plan

If implementation variants or resolution sweeps cannot fit, supply exact settings and dependency versions in a clearly named supplement; do not substitute a pointer for accessible evidence.

Examples behind the synthesis

Boundary: This route contains 23 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 23 category members and classification rationale

Training, objectives & optimization

The argument primarily changes a loss, supervision signal, optimization/update rule, distillation recipe or adaptation procedure. Some assigned methods update at inference time; the label refers to the objective-driven argument, not only offline training.

Corpus context · 9 papers: median 6 main figures and 6 main tables; body span ≈ 8.06 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Define what the objective is intended to preserve, where its supervision comes from and how the signal changes across stages before reporting downstream scores. Show supervision, frozen/trainable boundaries and information flow when these distinguish the objective from an architectural change. Compare the proposed signal against simpler or removed-signal controls under matched input and training access; report downstream metrics separately from the objective’s own proxy. Improvement in a proxy or attribution-selection criterion is not automatic evidence of downstream validity, faithfulness or embodiment-independent control.

Argument and section order

  1. Observed failure or mismatch between objective and desired behavior
  2. Notation, conventional objective and information access
  3. Proposed loss/update with a reason for each term or branch
  4. Executable procedure, sampling, schedules and approximations
  5. Matched main comparisons plus mechanism-specific diagnostics
  6. Sensitivity, overhead, supervision dependence and remaining failures

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Mechanism or gradient-flow diagram

One diagram when multiple paths or update stages matter

Mark teachers, students, pseudo-labels, frozen weights, detached gradients and inference-only operations.

When: Use gradient arrows or phase panels when an ordinary module diagram would hide the actual intervention.

Objective and update specification

An explicit objective; an algorithm box if iterative or stateful

Define variables, positive/negative samples, weights, updates and stopping rather than listing an unexplained weighted sum.

When: A short closed-form loss may need no pseudocode; a multistage update usually does.

Matched comparison table

One task-specific table or paired baseline/new-rule rows

Hold backbone, supervision and budget fixed where possible so a training-rule claim is not merely a larger-model claim.

When: Show unmatched leaderboard context separately from causal design comparisons.

Mechanism diagnostic

One appropriate panel per central explanatory claim

Measure the suspected mismatch: gradient behavior, confusing classes, reliability, alignment or temporal persistence.

When: Use the quantity the paper actually claims to improve, not an arbitrary feature visualization.

Ablation and sensitivity package

A compact control table and consequential parameter curves

Distinguish new supervision, loss terms, schedules and extra compute; retain collapse or negative runs.

When: Do not invent large sweeps for inconsequential parameters or hide tuning costs.

Formal guarantee

Optional

State assumptions and whether the implemented approximation satisfies them.

When: A proof is needed for a formal claim, not as decoration for an empirical improvement.

Appendix plan

Provide exact loss weights, schedules, negative/positive construction and selection rules when these affect reproducibility.

Examples behind the synthesis

Boundary: This route contains 9 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 9 category members and classification rationale

Theory & formal analysis

A formal characterization, algebraic result, guarantee or theoretically derived explanation organizes the main argument, with algorithms and experiments testing consequences or practical approximations.

Corpus context · 4 papers: median 3.5 main figures and 3.5 main tables; body span ≈ 8.05 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

State the mathematical obstacle and assumptions, expose a failure or counterexample when useful, then distinguish the guarantee from approximate computation and empirical accuracy. Use a geometric counterexample, calibration/propagation diagram or failure illustration when it explains an assumption better than notation alone. Where a computational guarantee is claimed, report certificate/tightness or coverage with accuracy, compactness and cost; do not let one metric stand for the others. These are writing observations. The studies did not independently validate proofs, certificates or guaranteed coverage after approximation.

Argument and section order

  1. Precise question and closest existing limitation or guarantee
  2. Definitions, assumptions and a worked geometric or algebraic example
  3. Main result with its conditions and an interpretation
  4. Proof roadmap or constructive step
  5. Practical solver/update and departures from the idealized setting
  6. Controlled consequences, boundary cases and complete proofs

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Worked example or construction diagram

One when it makes unfamiliar definitions operational

Connect algebraic symbols to camera geometry, representations or update behavior.

When: Prefer a reusable symbolic example over an unrelated network schematic.

Assumption/result roadmap

One short map or comparison table when several regimes are involved

Keep quantifiers, non-degeneracy conditions, approximation regimes and guarantee types visible.

When: Especially important when exact theory motivates an approximate practical solver.

Theorem and proof sketch

As many as the actual logical claims need

State what is proved and identify the central argument before full technical details.

When: No target theorem count; empirical observations must not be promoted to universal guarantees.

Theory-linked diagnostic

Only when there is an empirical consequence to test

Test the predicted difficult regime, scaling, geometry or optimizer behavior under stated assumptions.

When: A finite experiment illustrates or challenges a consequence; it does not prove an asymptotic statement.

Boundary or counterexample

Include where needed to prevent a tempting overgeneralization

Explain the role of assumptions and distinguish sufficient from necessary conditions.

When: A theoretical paper need not manufacture a broad benchmark leaderboard if it is irrelevant to the result.

Appendix plan

Route derivations and proof details to precise theorem-specific locations, retaining assumptions and claim boundaries in the main paper.

Examples behind the synthesis

  • Certifiably Optimal Anisotropic Rotation Averaging · Sections4.1–4.3 pp3–6; Figure1 p3; Table1 p8

    Anisotropic rotation averaging connects uncertainty to a determinant-constraint failure and replacement relaxation; solution rank is reported alongside reconstruction error and runtime.

  • Deterministic Object Pose Confidence Region Estimation · Sections3.2–3.3 pp4–5; Table4 and Figure5 p8; conclusion p8

    Pose-region estimation separates calibration from nonlinear propagation and reports coverage alongside region volume, while acknowledging Gaussian/nonlinear coverage limitations.

Boundary: This route contains 4 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 4 category members and classification rationale

Empirical analysis, diagnosis & auditing

The main new knowledge is a controlled measurement, diagnostic, comparison, failure analysis or audit. A proposed remedy, model or tool can follow from that evidence.

Corpus context · 5 papers: median 8 main figures and 5 main tables; body span ≈ 8.09 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Make the question, controlled factors, evaluation unit and uncertainty construction explicit before interpreting a trend. Separate measured behavior from scaling extrapolations and mechanism hypotheses. Use controlled sweeps or paired contrasts when trends are the contribution; show observed ranges, baselines, uncertainty units and extrapolation boundaries. Specify splits, sample units, repeated-run conditions and exceptions; distinguish oracle from usable selection rules. Repeated frames are not necessarily independent samples, correlation is not a causal mechanism, and a fitted scaling forecast is not an observed result.

Argument and section order

  1. Question, surprising observation and scope
  2. Operational definitions and the unit of analysis
  3. Controlled protocol: what varies and what stays fixed
  4. Finding-led sections with evidence, interpretation and competing explanations
  5. Remedy or practical consequence if supported
  6. Transfer, counterexamples, measurement limitations and reproducibility

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Study/control diagram or protocol table

One compact view

Expose information access, sampling, intervention and matched controls.

When: Essential when teacher labels, dataset splits, task direction or model access determine the interpretation.

Primary phenomenon plot or table

One clear entry point

Display the relationship, denominator and variability before a proposed explanation.

When: Show representative ranges rather than selected successes alone.

Alternative-explanation controls

One destination per central explanatory claim

Distinguish the proposed mechanism from compute, label quality, dataset composition or evaluation artifacts.

When: Correlation and a fitted trend require different language from a controlled causal intervention.

Case or failure gallery

A small aligned set with selection criteria

Make measured failures inspectable and include ambiguous/negative cases where relevant.

When: Qualitative cases illustrate a study; they do not replace prevalence estimates.

Transfer and resource summary

As needed by generalization or practicality claims

Repeat the protocol on different tasks/models/settings and report the actual cost.

When: Keep missing, unavailable or diverged results distinct from zero.

Appendix plan

Supply robustness sweeps and uncertainty details that allow the trend to be challenged, not merely more favorable examples.

Examples behind the synthesis

  • Towards Foundational Models for Single-Chip Radar · Section4.4 p5; Table4 p6; Figures6–7 p7; Section5.4 p8

    Radar scaling accounts for temporal dependence through effective sample size, uses geographic test separation and paired comparisons, and calls the100M-sample forecast a projection.

  • Scaling Laws for Native Multimodal Models · Section5 and Table4 p7; Section7 p8

    Native multimodal scaling distinguishes pretraining-loss trends from downstream task measurements and preserves a task-specific non-win instead of making the scaling claim universal.

  • Diffusion Image Prior · Figure4 p5; Table3 p6; Sections4–5 pp6–8

    DIIP separates observable stopping behavior from oracle diagnostics; the study records the source’s inconsistent oracle water-image values rather than silently harmonizing them.

Boundary: This route contains 5 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 5 category members and classification rationale

Datasets, benchmarks & measurement

A new corpus, acquisition/annotation process, evaluation suite or measurement protocol is the primary reusable deliverable. A companion model demonstrates utility without replacing the need to validate the resource.

Corpus context · 4 papers: median 5.5 main figures and 6.5 main tables; body span ≈ 8.14 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Explain the coverage gap in acquisition/task terms, then connect curation choices, splits, targets and scoring to that gap before showing benchmark results. Use an acquisition or curation schematic when it explains what existing benchmarks omit. Include dataset units, coverage, split logic, target provenance and task-specific metrics; distinguish native ground truth from constructed or pseudo targets. Dataset size alone does not establish diverse independent samples, and a benchmark’s approximate target should not be described as authoritative physical ground truth.

Argument and section order

  1. What existing resources cannot measure or cover
  2. Unit of data/annotation and intended use
  3. Collection or generation, verification, provenance and split design
  4. Composition, challenge taxonomy and protocol definitions
  5. Baselines with matched inputs and resource-specific metrics
  6. Biases, limitations, access and maintenance/reproducibility

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Coverage/comparison table

One compact resource table

Compare capabilities, annotation units, acquisition conditions and evaluation tasks, not only total size.

When: Use explicit partial or unavailable coverage rather than forcing binary superiority.

Collection and annotation pipeline

One process diagram with examples

Show raw inputs, transformations, human/machine verification and final annotations.

When: Distinguish generated labels, human corrections and measured ground truth.

Composition and split visualization

A distribution, hierarchy or protocol matrix suited to the labels

Show subjects/scenes/classes, long tails, acquisition diversity and what is held out.

When: Avoid conflating frames, tracks, objects, rendered variants and independent subjects.

Baseline results by challenge

Focused tables with the same taxonomy used in the protocol

Demonstrate what the resource reveals and expose non-dominating models or hard subgroups.

When: A high average score alone does not validate label quality or benchmark relevance.

Quality/reliability study

One verification analysis when annotation or metric validity is a claim

Document agreement, quality checks, adversarial controls, contamination checks or calibration.

When: Select the check that addresses this resource's actual failure risks; do not imply a single check proves complete validity.

Appendix plan

Provide annotation/quality-control procedures, licenses and curation details when applicable, with accessible files and explicit gaps.

Examples behind the synthesis

Boundary: This route contains 4 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 4 category members and classification rationale

Efficiency, inference & systems

The central contribution changes execution, inference, memory, acquisition cost or resource scaling while preserving a stated quality or correctness contract.

Corpus context · 8 papers: median 7.5 main figures and 4.5 main tables; body span ≈ 8.09 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Locate the expensive operation, explain the replacement or removal, and report quality together with resource use under a clearly bounded execution protocol. Show the removed bottleneck or execution/capture sequence when it is the mechanism of savings. Pair quality with latency, memory/storage, hardware, resolution and workload; use the resource actually claimed rather than a convenient proxy. Mixed-hardware inherited timings, disk-size labels, training-only costs and capture-count differences must remain visible; do not turn them into an unconditional speedup.

Argument and section order

  1. Workload and measured bottleneck
  2. Quality/correctness contract and existing computation
  3. Changed representation, execution, acquisition or reuse policy
  4. Implementation, device and timing protocol
  5. Component accounting plus end-to-end quality/resource comparisons
  6. Scaling, operating-point sensitivity and unfavorable regimes

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Bottleneck profile or oracle diagnostic

One focused breakdown or controlled comparison

Explain which stage is costly and why the proposed decision variable could help.

When: Use matched budgets when an oracle analysis motivates an approximate implementation.

Execution/data-flow diagram

One overview with needed stage or memory insets

Mark preprocessing, cache/reuse, training versus inference, hardware calls and synchronization.

When: The figure should expose added overhead as well as removed work.

Quality–resource table or frontier

One panel per materially different workload

Pair quality with latency, throughput, memory or acquisition effort at comparable operating points.

When: State hardware, precision, batch/sequence/image size and what the timer includes.

End-to-end and component cost accounting

A table or stacked breakdown

Show whether an isolated saving survives the entire pipeline.

When: Do not substitute FLOPs, token count or number of steps for wall-clock measurements without qualification.

Scaling and sensitivity

Curves only for the dimensions the system claims to scale

Measure view/frame count, problem size, cache refresh or device constraints and retain adverse regimes.

When: Changing hardware or input capacity is a different comparison from identical-workload acceleration.

Algorithm or correctness explanation

As needed for the execution contract

Make reuse, selection, fallback, stopping and approximation explicit.

When: A claimed exact or distribution-preserving procedure needs a precise argument beyond similar output scores.

Appendix plan

Disclose timing protocol, implementation details, breakdowns and failure/OOM conditions needed to reproduce the trade-off.

Examples behind the synthesis

  • Removing Cost Volumes from Optical Flow Estimators · Figure3 p3; Tables1–3 pp4–5; Table5 p7; Section4.3 p8

    ReCoVEr separates whether, when and how to remove the cost volume, then pairs endpoint error with runtime/memory and records failure modes.

  • EVER: Exact Volumetric Ellipsoid Rendering for Real-time View Synthesis · Figures2–3 p3; Sections4–5 pp3–5; Table1 p6; Section6.3 p7

    EVER explains exact integration for its chosen primitives, separates derivation from implementation, and defines memory as disk size while disclosing GPU/resolution differences.

  • Spatially-Varying Autofocus · Table1 p2; Figure3 p4; Section5 p6; Figures11–12 and Section6 p8

    Spatially-varying autofocus reports capture counts, quality/MTF and light/aperture costs; no post-capture reconstruction does not mean no computation.

Boundary: This route contains 8 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 8 category members and classification rationale

Domain-grounded methods & physical systems

The primary argument is a task-specific capability, physical measurement/reconstruction system or domain-grounded method whose validity depends on real acquisition, task assumptions and domain-appropriate evidence.

Corpus context · 11 papers: median 7 main figures and 3 main tables; body span ≈ 8.05 pages; attached appendix span ≈ Not resolved pages (0 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.

Pattern to learn

Translate the domain constraint into a measurable task, show how intermediate estimates connect to the final output, and evaluate against a reference whose provenance is explicit. Show a domain workflow or intermediate measurement chain when application constraints are part of the contribution. Report task-specific errors, reference provenance and operating conditions; include intermediate diagnostics when a final score hides distinct failure sources. A convincing demonstration is not automatically clinical, safety or broad real-world validation; preserve the studied population, equipment and reference-standard limits.

Argument and section order

  1. Domain problem and why ordinary assumptions fail
  2. Measurement/data provenance, task inputs and ground-truth limitations
  3. Physical or domain model and changed method
  4. Implementation, acquisition and evaluation protocol
  5. Domain-appropriate main results and mechanism controls
  6. Deployment cost, failure regimes and limits of interpretation

What to prepare for this type

Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.

Acquisition or domain-contract figure

One setup or input/output view

Show sensors/modalities, calibration, measured versus generated quantities and what is available at use time.

When: Essential when hardware, multimodal cohorts or nonstandard labels determine the claim.

Mechanism/physical model diagram

One overview with necessary physical or anatomical labels

Connect variables, modules and losses to the domain problem rather than only showing generic network boxes.

When: Keep measured inputs, latent physical quantities and predicted outputs visually distinct.

Aligned qualitative diagnostic

A compact grid or profile plot

Compare matched scenes/patients/objects with relevant maps, spectra, overlays or error views.

When: Label simulation, real data, pseudo-ground-truth and unavailable measurements; an appealing image is not independent validation.

Task-specific quantitative table

One table per incompatible endpoint

Report the relevant physical/clinical/behavioral metric, units, uncertainty and evaluation split.

When: Separate image quality from geometry, survival discrimination, calibration or downstream behavior.

Ablation and independent validation

Controls chosen for the proposed mechanism

Test key physical assumptions, modality use or pipeline components; include an independent reference when feasible.

When: Do not label a model-derived pseudo-label as independent truth or infer clinical benefit from a technical benchmark.

Cost and limitations panel

As appropriate to the deployment claim

State calibration, capture, annotation, compute and failure requirements.

When: A successful laboratory demonstration does not establish unrestricted field or clinical reliability.

Appendix plan

Provide acquisition, calibration, annotation and participant/scene scope where relevant; retain material deployment limitations in the main paper.

Examples behind the synthesis

  • Event-based Visual Vibrometry · Sections3.2–3.4 pp4–6; Figure3 p5; Figures4–5 and Table2 p7; limitations p8

    Event vibrometry connects coarse motion to learned refinement and displacement, then states material/illumination conditions and identifies manufacturer moduli as its reference.

  • Counting Stacked Objects · Figure2 p2; Sections3–4 pp3–7

    Stacked-object counting separates total-volume and average-instance-volume estimation, allowing branch errors to be distinguished from the final count.

  • Teeth Reconstruction and Performance Capture Using a Phone Camera · Sections5–7 pp5–8

    Teeth reconstruction evaluates acquisition and tracking constraints in its limited participant setting rather than supplying clinical validation.

Boundary: This route contains 11 primary editorial assignments in the 64-paper inspected subset (64 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 11 category members and classification rationale