Papers › GaussianAvatar: Towards Realistic Human Avatar Modeling from a Single Video via...

GaussianAvatar: Towards Realistic Human Avatar Modeling from a Single Video via Animatable 3D Gaussians

4 Dec 2023CVPR 2024 1arXiv:2312.02134archive 2025-07-28

Liangxiao Hu, Hongwen Zhang, Yuxiang Zhang, Boyao Zhou, Boning Liu, Shengping Zhang, Liqiang Nie

We present GaussianAvatar, an efficient approach to creating realistic human avatars with dynamic 3D appearances from a single video. We start by introducing animatable 3D Gaussians to explicitly represent humans in various poses and clothing styles. Such an explicit and animatable representation can fuse 3D appearances more efficiently and consistently from 2D observations. Our representation is further augmented with dynamic properties to support pose-dependent appearance modeling, where a dynamic appearance network along with an optimizable feature tensor is designed to learn the motion-to-appearance mapping. Moreover, by leveraging the differentiable motion condition, our method enables a joint optimization of motions and appearances during avatar modeling, which helps to tackle the long-standing issue of inaccurate motion estimation in monocular settings. The efficacy of GaussianAvatar is validated on both the public dataset and our collected dataset, demonstrating its superior performances in terms of appearance quality and rendering efficiency.

PaperPDFConference PDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 10 ran (5 with no instrument failure; 5 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 10 samples that ran has no recorded date.

aipixel/gaussianavatar officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 10 ran (5 instrument-failed) · 0 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

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

2ran · honoured contract
3ran · our draft was wrong
2ran; the contract check could not run
3ran

Licence: 2 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from aipixel/gaussianavatar. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

aipixel/gaussianavatar official repository 10 samples, 10 ran (5 instrument-failed) · 0 unverified
find_joint_kin_chain submodules/smplx/utils.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed fingerprinted MIT (permissive) here; the stored copy is pointer only · 3b5f8cde1dc64833 · report fixture: signature joint_id:int/0/int, kinematic_tree:list/1/int · returned list · level recorded 2026-09-22
gaussian in 218 papers
census: 8 implementations from 9 papers, 8 distinct outputs across 4 buckets, one shared input per bucket
utils/loss_utils.py ran · honoured contract fingerprinted MIT (permissive) · c56b7ef16f309a45 · report fixture: signature window_size:int/0/int, sigma:float/0/float · returned Tensor · level recorded, date not recorded
gen_transf_mtx_from_vtransf model/modules.py ran MIT (permissive) · 412dda33006a6e27 · report fixture: signature vtransf:Tensor/4/float, bary_coords:Tensor/3/float, faces:Tensor/3/int, scaling:float/0/float · returned Tensor · level recorded 2026-09-24
gen_transf_mtx_full_uv model/modules.py ran; the contract check could not run (RAISES) MIT (permissive) · c661071dca6a8c5b · report fixture: signature verts:Tensor/3/float, faces:Tensor/3/int · returned Tensor · level recorded 2026-09-24
get_embedder in 88 papers model/modules.py ran · our draft was wrong MIT (permissive) · 94d79c473e827470 · report fixture: signature multires:int/0/int, i:int/0/int, input_dims:int/0/int · returned tuple · level recorded 2026-09-24
l1_loss_w utils/loss_utils.py ran fingerprinted MIT (permissive) · 8c3f087d9f30037e · report fixture: signature network_output:Tensor/2/float, gt:Tensor/2/float · returned Tensor · level recorded 2026-09-24
l2_loss in 136 papers utils/loss_utils.py ran · honoured contract fingerprinted MIT (permissive) · 8c3b0f873ba11813 · report fixture: signature network_output:Tensor/2/float, gt:Tensor/2/float · returned Tensor · level recorded 2026-09-24
rotate_camera_by_frame_idx scene/dataset_mono.py ran MIT (permissive) · 59b04ecdb5519178 · report fixture: signature extrinsics:ndarray/2/float, frame_idx:int/0/int, trans:ndarray/1/float, rotate_axis:str/0/str, period:int/0/int, inv_angle:bool/0/bool · returned ndarray · level recorded 2026-09-24
to_np in 63 papers
census: 8 implementations from 14 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float64
submodules/smplx/utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 43ebe3b786b2d59b · report fixture: returned ndarray · level recorded 2026-09-22
to_tensor in 92 papers
census: 8 implementations from 8 papers, 3 distinct outputs across 3 buckets, one shared input per bucket
submodules/smplx/utils.py ran · our draft was wrong MIT (permissive) · 9ad32763fbba1d53 · report fixture: signature array:ndarray/2/float, dtype:dtype/0/? · returned Tensor · level recorded 2026-09-24

Tasks

Motion Estimation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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