Papers › Input Invex Neural Network

Input Invex Neural Network

16 Jun 2021arXiv:2106.08748archive 2025-07-28

Suman Sapkota, Binod Bhattarai

Connected decision boundaries are useful in several tasks like image segmentation, clustering, alpha-shape or defining a region in nD-space. However, the machine learning literature lacks methods for generating connected decision boundaries using neural networks. Thresholding an invex function, a generalization of a convex function, generates such decision boundaries. This paper presents two methods for constructing invex functions using neural networks. The first approach is based on constraining a neural network with Gradient Clipped-Gradient Penality (GCGP), where we clip and penalise the gradients. In contrast, the second one is based on the relationship of the invex function to the composition of invertible and convex functions. We employ connectedness as a basic interpretation method and create connected region-based classifiers. We show that multiple connected set based classifiers can approximate any classification function. In the experiments section, we use our methods for classification tasks using an ensemble of 1-vs-all models as well as using a single multiclass model on small-scale datasets. The experiments show that connected set-based classifiers do not pose any disadvantage over ordinary neural network classifiers, but rather, enhance their interpretability. We also did an extensive study on the properties of invex function and connected sets for interpretability and network morphism with experiments on toy and real-world data sets. Our study suggests that invex function is fundamental to understanding and applying locality and connectedness of input space which is useful for various downstream tasks.

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 12 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 12 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 9 samples that ran has no recorded date.

tsumansapkota/Input-Invex-Neural-Network officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 12 samples, 9 ran (0 instrument-failed) · 3 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

12 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures 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.

1ran · honoured contract
8ran
3unverified

Licence: 0 of the 12 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 tsumansapkota/Input-Invex-Neural-Network. “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.

tsumansapkota/Input-Invex-Neural-Network official repository 12 samples, 9 ran (0 instrument-failed) · 3 unverified
get_children classes.py ran Apache-2.0 (permissive) · e1a3bf8a0feda324 · report fixture: signature module:callable/0/? · returned list · level recorded 2026-09-25
jacobian in 21 papers nflib/res_flow.py ran Apache-2.0 (permissive) · 7bfb70b8bf7c94bb · report fixture: signature Y:Tensor/2/float, X:Tensor/2/float, create_graph:bool/0/bool · returned Tensor · level recorded 2026-09-25
line_search in 14 papers nflib/utils/broyden.py ran Apache-2.0 (permissive) · 2e551f7f67056cb3 · report fixture: signature update:Tensor/1/float, x0:Tensor/1/float, g0:Tensor/1/float, g:callable/0/?, nstep:int/0/int, on:bool/0/bool · returned tuple · level recorded 2026-09-25
normalize_u nflib/utils/mixed_lipschitz.py ran Apache-2.0 (permissive) · 51fae1159c4f5c74 · report fixture: signature u:Tensor/1/float, codomain:int/0/int, out:NoneType/0/? · returned Tensor · level recorded 2026-09-25
normalize_v nflib/utils/mixed_lipschitz.py ran Apache-2.0 (permissive) · a37b263718447216 · report fixture: signature v:Tensor/1/float, domain:int/0/int, out:NoneType/0/? · returned Tensor · level recorded 2026-09-25
projmax_ nflib/utils/mixed_lipschitz.py ran fingerprinted Apache-2.0 (permissive) · 4174ba4ef5147b9a · report fixture: signature v:Tensor/1/float · returned Tensor · level recorded 2026-09-25
rmatvec in 8 papers nflib/utils/broyden.py ran Apache-2.0 (permissive) · 54f0bd531896cb01 · report fixture: signature part_Us:Tensor/3/float, part_VTs:Tensor/3/float, x:Tensor/2/float · returned Tensor · level recorded 2026-09-25
scalar_search_armijo in 11 papers nflib/utils/broyden.py ran · honoured contract Apache-2.0 (permissive) · b2b5022f654ee4d3 · report fixture: signature phi:callable/0/?, phi0:float/0/float, derphi0:float/0/float, c1:float/0/float, alpha0:float/0/float, amin:float/0/float · returned tuple · level recorded, date not recorded
spectral_norm_fc in 5 papers nflib/utils/spectral_norm_fc.py ran Apache-2.0 (permissive) · c64ab1070035ae31 · report fixture: signature module:callable/0/?, coeff:float/0/float, name:str/0/str, n_power_iterations:int/0/int, eps:float/0/float, dim:int/0/int · returned SimpleModule · level recorded 2026-09-26
remove_spectral_norm in 10 papers nflib/utils/spectral_norm_fc.py unverified Apache-2.0 (permissive) · 40af90ae6f78dcfb · report
remove_spectral_norm_conv nflib/utils/spectral_norm_conv_inplace.py unverified Apache-2.0 (permissive) · 1ec532cf64021e4b · report
spectral_norm_conv nflib/utils/spectral_norm_conv_inplace.py unverified Apache-2.0 (permissive) · b52f59af0c419a22 · report

Tasks

Image ClassificationImage SegmentationSemantic Segmentation

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