Papers › CrysXPP:An Explainable Property Predictor for Crystalline Materials

CrysXPP:An Explainable Property Predictor for Crystalline Materials

22 Apr 2021arXiv:2104.10869links table onlyarchive 2025-07-28

Kishalay Das, Bidisha Samanta, Pawan Goyal, Seung-Cheol Lee, Satadeep Bhattacharjee, Niloy Ganguly

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

We present a deep-learning framework, CrysXPP, to allow rapid prediction of electronic, magnetic and elastic properties of a wide range of materials with reasonable precision. Although our work is consistent with several recent attempts to build deep learning-based property predictors, it overcomes some of their limitations. CrysXPP lowers the need for a large volume of tagged data to train a deep learning model by intelligently designing an autoencoder CrysAE and passing the structural information to the property prediction process. The autoencoder in turn is trained on a huge volume of untagged crystal graphs, the designed loss function helps in capturing all their important structural and chemical information. Moreover, CrysXPP uses only a small amount of tagged data for property prediction, and also trains a feature selector that provides interpretability to the results obtained. We demonstrate that CrysXPP convincingly performs better than all the competing and recent baseline algorithms across seven diverse set of properties. Most notably, when given a small amount of experimental data, CrysXPP is consistently able to outperform conventional DFT. We release the large pretrained model CrysAE so that it could be fine-tuned using small amount of tagged data by the research community on various applications with restricted data source.

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

By repository: official repository: 9 samples from 1 repository, 8 ran (8 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 2 samples from 1 repository, 2 ran (2 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

iitkgpaiforscience/crysxpp officialmentioned in paperpytorchMITSyntology: 9 samples, 8 ran (0 instrument-failed) · 1 unverified report
kdmsit/CrysXPP mentioned on GitHubpytorchMITSyntology: 2 samples, 2 ran (0 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

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 1 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.

10ran
1unverified

Licence: 0 of the 11 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. 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.

iitkgpaiforscience/crysxpp official repository 9 samples, 8 ran (0 instrument-failed) · 1 unverified
disc_edge_feature src/data.py ran MIT (permissive) · 6fa60cc510c79ce4 · report fixture: signature edge:ndarray/2/float, data:ndarray/2/int · returned ndarray · level recorded 2026-09-25
disc_edge_feature src/data_prop.py ran fingerprinted MIT (permissive) · 754129e77312b15b · report fixture: signature edge:ndarray/2/float · returned ndarray · level recorded 2026-09-25
getActivation in 5 papers src/model.py ran MIT (permissive) · 80cc71b697292968 · report fixture: signature activation:str/0/str · returned ReLU · level recorded 2026-09-25
get_data_loader in 44 papers src/data.py ran MIT (permissive) · 3564cd5a3000945a · report fixture: signature dataset:SimpleDataset/0/?, collate_fn:callable/0/?, train_size:int/0/int, batch_size:int/0/int, num_workers:int/0/int, pin_memory:bool/0/bool · returned DataLoader · level recorded 2026-09-25
get_molecular_adj src/data.py ran MIT (permissive) · 747b83a5ce897be4 · report fixture: signature nbr_fea_idx:list/1/list, N:int/0/int · returned ndarray · level recorded 2026-09-25
get_molecular_multigraph_adj src/data_prop.py ran MIT (permissive) · bf02b65c4f9c1778 · report fixture: signature data:list/1/list · returned ndarray · level recorded 2026-09-25
sanitize in 12 papers src/prop.py ran MIT (permissive) · f997a9a7c06ccbbf · report fixture: signature input_var:Tensor/1/float, reference:Tensor/1/float, return_diff:bool/0/bool · returned tuple · level recorded 2026-09-25
sparse_loss src/prop.py ran MIT (permissive) · f2b4c1cbe71051af · report fixture: signature prop_model:callable/0/?, input:Tensor/2/float · returned Tensor · level recorded 2026-09-25
kdmsit/CrysXPP community (archive-listed) 2 samples, 2 ran (0 instrument-failed) · 0 unverified
collate_pool src/data_prop.py ran MIT (permissive) · 3f6dd8d427414044 · report fixture: signature dataset_list:list/1/tuple · returned tuple · level recorded 2026-09-24
get_train_val_test_loader src/data_prop.py ran MIT (permissive) · 9673d28023c7d8d8 · report fixture: signature dataset:SimpleDataset/0/?, collate_fn:callable/0/?, batch_size:int/0/int, train_ratio:float/0/float, val_ratio:float/0/float, test_ratio:float/0/float, return_test:bool/0/bool, num_workers:int/0/int, pin_memory:bool/0/bool, train_size:NoneType/0/?, test_size:NoneType/0/? · returned tuple · level recorded 2026-09-24

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