</> Code with Papers by Syntology

Methods › General › Interpretability › Monte Carlo Dropout › Papers, page 3

Monte Carlo Dropout

Papers archive 2025-07-28

archive papers tagged: 202 · with a code link: 60 · where Syntology ran a sample: 14 (11 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (14 of 202 tagged: 11 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument)

Page 3 of 3: papers 201 to 202 of 202, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.