Papers › LAN-HDR: Luminance-based Alignment Network for High Dynamic Range Video Reconstruction
LAN-HDR: Luminance-based Alignment Network for High Dynamic Range Video Reconstruction
Haesoo Chung, Nam Ik Cho
As demands for high-quality videos continue to rise, high-resolution and high-dynamic range (HDR) imaging techniques are drawing attention. To generate an HDR video from low dynamic range (LDR) images, one of the critical steps is the motion compensation between LDR frames, for which most existing works employed the optical flow algorithm. However, these methods suffer from flow estimation errors when saturation or complicated motions exist. In this paper, we propose an end-to-end HDR video composition framework, which aligns LDR frames in the feature space and then merges aligned features into an HDR frame, without relying on pixel-domain optical flow. Specifically, we propose a luminance-based alignment network for HDR (LAN-HDR) consisting of an alignment module and a hallucination module. The alignment module aligns a frame to the adjacent reference by evaluating luminance-based attention, excluding color information. The hallucination module generates sharp details, especially for washed-out areas due to saturation. The aligned and hallucinated features are then blended adaptively to complement each other. Finally, we merge the features to generate a final HDR frame. In training, we adopt a temporal loss, in addition to frame reconstruction losses, to enhance temporal consistency and thus reduce flickering. Extensive experiments demonstrate that our method performs better or comparable to state-of-the-art methods on several benchmarks.
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):
get_harvested_code_for_paper(arxiv_id="2308.11116")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2308.11116", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2308.11116")
Code
Syntology 18 code samples harvested from 1 repository linked to this paper: 12 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 3 where Syntology's instrument failed) · 6 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: 18 samples from 1 repository, 12 ran (9 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.
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
18 samples harvested: 12 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 3 where Syntology's instrument failed) · 6 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.
Licence: 18 of the 18 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 haesoochung/lan-hdr. “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.
f1b5901af26dbfca · report
fixture: returned Transformer_swap_once · level recorded 2026-09-22 aa6da43d05cfaf65 · report
fixture: signature data:dict/0/? · returned list · level recorded 2026-09-24 e1a1e65065bdcfd2 · report
fixture: signature array:ndarray/3/float · returned Tensor · level recorded 2026-09-24 3f82133185c8bcb4 · report
fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-24 029ef88513e67c12 · report
fixture: signature in_channels:int/0/int, out_channels:int/0/int, stride:int/0/int · returned Conv2d · level recorded 2026-09-24 ef02d64125a1bf3d · report
fixture: signature in_channels:int/0/int, out_channels:int/0/int, stride:int/0/int · returned Conv2d · level recorded 2026-09-24 0a8669330777872f · report
fixture: signature img:ndarray/3/float, k:int/0/int · returned ndarray · level recorded 2026-09-24 881643cfd2f34bc0 · report
fixture: signature LOAD_ROOT:str/0/str, _args:Namespace/0/? · returned Namespace · level recorded 2026-09-24 70578ea79958d42a · report
fixture: signature d_model:int/0/int, x:Tensor/4/float · returned Tensor · level recorded 2026-09-24 a35918ebf7e71a85 · report
fixture: signature inputs:ndarray/3/float, size:tuple/1/int, margin:int/0/int · returned ndarray · level recorded 2026-09-24 05992505df9ef0cd · report
fixture: signature input_dict:dict/0/?, average:bool/0/bool · returned dict · level recorded 2026-09-24 2c64396daab7bab1 · report
fixture: signature affix:str/0/str · returned tuple · level recorded 2026-09-24 77a000f198ad51c9 · report
19a2e11b07ea832f · report
afe4804b0b959fd3 · report
8f61e1a91f2ea02d · report
224a1a3b3ac9ca1b · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for LAN-HDR (graph method: LAN-HDR). 7 bricks; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
- Align_sup_00 entry · level 0 · unverified ·
77a000f198ad51c9 - FE_res_fft helper · level 0 · unverified ·
19a2e11b07ea832f - FE_res_fft_gc helper · level 0 · unverified ·
afe4804b0b959fd3 - Fuser model · level 0 · unverified ·
80f0b733f364ebd3 - Recon_swap_once helper · level 0 · unverified ·
8f61e1a91f2ea02d - Transformer_swap_once helper · level 1 · ran ·
f1b5901af26dbfca - Single_sup_T_wo_se helper · level 0 · unverified ·
224a1a3b3ac9ca1b
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2308.11116") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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