Papers › Block Neural Autoregressive Flow

Block Neural Autoregressive Flow

9 Apr 2019arXiv:1904.04676archive 2025-07-28

Nicola De Cao, Ivan Titov, Wilker Aziz

Normalising flows (NFS) map two density functions via a differentiable bijection whose Jacobian determinant can be computed efficiently. Recently, as an alternative to hand-crafted bijections, Huang et al. (2018) proposed neural autoregressive flow (NAF) which is a universal approximator for density functions. Their flow is a neural network (NN) whose parameters are predicted by another NN. The latter grows quadratically with the size of the former and thus an efficient technique for parametrization is needed. We propose block neural autoregressive flow (B-NAF), a much more compact universal approximator of density functions, where we model a bijection directly using a single feed-forward network. Invertibility is ensured by carefully designing each affine transformation with block matrices that make the flow autoregressive and (strictly) monotone. We compare B-NAF to NAF and other established flows on density estimation and approximate inference for latent variable models. Our proposed flow is competitive across datasets while using orders of magnitude fewer parameters.

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

By repository: official repository: 4 samples from 1 repository, 2 ran (0 with no instrument failure; 2 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.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

nicola-decao/BNAF officialmentioned in papermentioned on GitHubpytorchSyntology: 4 samples, 2 ran (2 instrument-failed) · 2 unverified report
Naagar/Glow_NormalizingFlow_implimentation mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Glow: Generative Flow with Invertible 1x1 Convolutions (arXiv:1807.03039; that paper's own run record: 85 ran (of which 47 constructed an object rather than computing a result; 73 with no instrument failure: 3 honoured, 0 violated, 70 with no contract checked; 12 where Syntology's instrument failed) · 44 unverified); nothing checks that they implement this paper's method. report
metachenyiyan/BreezeForest mentioned on GitHubpytorchSyntology: not harvested report
sshish/NF mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Density estimation using Real NVP (arXiv:1605.08803; that paper's own run record: 48 ran (of which 26 constructed an object rather than computing a result; 38 with no instrument failure: 2 honoured, 0 violated, 36 with no contract checked; 10 where Syntology's instrument failed) · 22 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

4 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

2ran · our draft was wrong
2unverified

Licence: 0 of the 4 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 nicola-decao/BNAF. “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.

nicola-decao/BNAF official repository 4 samples, 2 ran (2 instrument-failed) · 2 unverified
compute_log_p_x toy2d.py ran · our draft was wrong MIT (permissive) · 1e3e1419bbf70774 · report fixture: signature model:callable/0/?, x_mb:Tensor/2/float · returned Tensor · level recorded 2026-09-22
save_model in 19 papers density_estimation.py ran · our draft was wrong MIT (permissive) · c7c2cd135ec55792 · report fixture: signature model:callable/0/?, optimizer:SGD/0/?, epoch:int/0/int, args:Args/0/? · returned function · level recorded 2026-09-22
create_model in 163 papers toy2d.py unverified MIT (permissive) · f2977965fe47a3fe · report
create_model in 163 papers density_estimation.py unverified MIT (permissive) · 87c781818f839148 · report

Tasks

Density EstimationNormalising Flows

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Density Estimation BSDS300 B-NAF Log-likelihood 157.36 #3 of 5 Archive leaderboard report
Density Estimation Caltech-101 B-NAF NLL 105.42 #1 of 3 Archive leaderboard report
Density Estimation Caltech-101 B-NAF Negative ELBO 94.91 #1 of 3 Archive leaderboard report
Density Estimation Freyfaces B-NAF NLL 4.42 #1 of 3 Archive leaderboard report
Density Estimation Freyfaces B-NAF Negative ELBO 4.33 #1 of 3 Archive leaderboard report
Density Estimation OMNIGLOT B-NAF NLL 100.08 #1 of 4 Archive leaderboard report
Density Estimation OMNIGLOT B-NAF Negative ELBO 94.83 #1 of 4 Archive leaderboard report
Density Estimation UCI GAS B-NAF Log-likelihood 12.06 #1 of 5 Archive leaderboard report
Density Estimation UCI HEPMASS B-NAF Log-likelihood -14.71 #3 of 5 Archive leaderboard report
Density Estimation UCI MINIBOONE B-NAF Log-likelihood -8.95 #4 of 5 Archive leaderboard report
Density Estimation UCI POWER B-NAF Log-likelihood 0.61 #3 of 6 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.

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