.pdbqt

0 claimants 0 primary 0 secondary

SWH popularity

From the SWH-MSR-ARV dataset (Desmazières, Di Cosmo, Lorentz, MSR 2025; file nb_extensions_alphanum.csv) — one row per (ext, year) in the full SWH archive. Case-aggregated. citation.

931.3K
total occurrences
449.3K
since 2019 (48.2%)
2007–2023
years active

Help label this extension

No PL in our taxonomy claims this extension. If you know what it's used for, fill the form below. Vocabulary reference: docs/extension_labels.md.

— or, if the button is blocked, use the link just below:
(fill the form to enable this link)
What happens after I submit?
  1. A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
  2. A curator script (tools/process_extension_labels.py) fetches all ext-review issues and writes their parsed contents into data/derived/extension_labels.csv with curator_status="new". Until this script runs, your submission lives only as the GitHub issue.
  3. Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
  4. For pl/<id> labels, build_pl_taxonomy.py promotes accepted labels into ext_claim.csv with source="manual_review:<your-login>" and strength="proposed". The next site rebuild then shows your claim on this extension's page and on the language's page.
  5. Friendly-name + reference-URL labels (e.g. binary:image for .png) are not promoted into ext_claim.csv (they aren't PL claims) but are surfaced on this page's "Prior labels" table so anyone landing here sees them next to the auto-detected category.

In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.

SWH-mined examples (2)

Real archived programs with this extension, byte-verified against the SWH archive. Useful for deciding what this extension actually is when the attribution is uncertain.
pdbqt_inputpdbqt.pdbqt · 144456 B · seen 610× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:12b31a3ded4e50a6f897beba3d6be472e1ee86ba;origin=https://github.com/MDAnalysis/mdanalysis;anchor=swh:1:rev:30e21da161dcbb2ad43f0b459279f1519e8bd623;path=/testsuite/MDAnalysisTests/data/pdbqt_inputpdbqt.pdbqt
Open in SWH · Raw bytes
hsg1.pdbqt · 147416 B · seen 97× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:39e41641f9b5de8ca694ab966b8e9ff427f3a6dc;origin=https://github.com/ccsb-scripps/AutoGrid;anchor=swh:1:rev:2b7c32c87ff472cb44cc1ddf64e81dfdd3dfba08;path=/Tests/hsg1.pdbqt
Open in SWH · Raw bytes
Request more SWH-mined examples
If the examples above don't disambiguate what .pdbqt is, request a fresh mining run.
(or open the pre-filled issue directly)