Volatile self-selective memristive neuron for millisecond-latency neuromorphic object detection at the edge.
Paper
Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
Markdown · 112 lines · 7.3 KB · no license
- # VisDrone-Dataset
- 
- Drones, or general UAVs, equipped with cameras have been fast deployed to a wide range of applications, including agricultural, aerial photography, fast delivery, and surveillance. Consequently, automatic understanding of visual data collected from these platforms become highly demanding, which brings computer vision to drones more and more closely. We are excited to present a large-scale benchmark with carefully annotated ground-truth for various important computer vision tasks, named VisDrone, to make vision meet drones. The VisDrone2019 dataset is collected by the AISKYEYE team at Lab of Machine Learning and Data Mining , Tianjin University, China. The benchmark dataset consists of 288 video clips formed by 261,908 frames and 10,209 static images, captured by various drone-mounted cameras, covering a wide range of aspects including location (taken from 14 different cities separated by thousands of kilometers in China), environment (urban and country), objects (pedestrian, vehicles, bicycles, etc.), and density (sparse and crowded scenes). Note that, the dataset was collected using various drone platforms (i.e., drones with different models), in different scenarios, and under various weather and lighting conditions. These frames are manually annotated with more than 2.6 million bounding boxes of targets of frequent interests, such as pedestrians, cars, bicycles, and tricycles. Some important attributes including scene visibility, object class and occlusion, are also provided for better data utilization.
- The challenge mainly focuses on four tasks:
- (1) Task 1: object detection in images challenge. The task aims to detect objects of predefined categories (e.g., cars and pedestrians) from individual images taken from drones.
- (2) Task 2: object detection in videos challenge. The task is similar to Task 1, except that objects are required to be detected from videos.
- (3) Task 3: single-object tracking challenge. The task aims to estimate the state of a target, indicated in the first frame, in the subsequent video frames.
- (4) Task 4: multi-object tracking challenge. The task aims to recover the trajectories of objects in each video frame.
- (5) Task 5: crowd counting challenge. The task aims to to count persons in each video frame.
- ## Download
- Note that the bounding box annotations of test-dev are avalialbe. Researchers can use test-dev to publish papers. testset-challenge is used for VisDrone2020 Challenge and the annotations is unavailable.
- ### Task 1: Object Detection in Images
- VisDrone-DET dataset
- * trainset (1.44 GB): [BaiduYun](https://pan.baidu.com/s/1K-JtLnlHw98UuBDrYJvw3A) | [GoogleDrive](https://drive.google.com/file/d/1a2oHjcEcwXP8oUF95qiwrqzACb2YlUhn/view?usp=sharing)
- * valset (0.07 GB): [BaiduYun](https://pan.baidu.com/s/1jdK_dAxRJeF2Xi50IoML1g) | [GoogleDrive](https://drive.google.com/file/d/1bxK5zgLn0_L8x276eKkuYA_FzwCIjb59/view?usp=sharing)
- * testset-dev (0.28 GB): [BaiduYun](https://pan.baidu.com/s/1RdRfSWV-1IFK7aWljLU_LQ) | [GoogleDrive](https://drive.google.com/open?id=1PFdW_VFSCfZ_sTSZAGjQdifF_Xd5mf0V) (GT avalialbe)
- * testset-challenge (0.28 GB): [BaiduYun](https://pan.baidu.com/s/1lvEkCgy1WWK4B7TLki4yBQ) | [GoogleDrive](https://drive.google.com/file/d/1KN8R3oioOvSXH492GEVk-Hx74nWHAcXT/view?usp=sharing)
- VisDrone-DET toolkit:
- * [Matlab beta](https://github.com/VisDrone/VisDrone2018-DET-toolkit)
- ### Task 2: Object Detection in Videos
- VisDrone-VID dataset
- * trainset (7.53 GB): [BaiduYun](https://pan.baidu.com/s/1kC3NTK6MPVv3D1CY9gXaCQ) | [GoogleDrive](https://drive.google.com/file/d/1NSNapZQHar22OYzQYuXCugA3QlMndzvw/view?usp=sharing)
- * valset (1.49 GB): [BaiduYun](https://pan.baidu.com/s/12-A6Mg1Gg7hyS4WwG27dDw) | [GoogleDrive](https://drive.google.com/file/d/1xuG7Z3IhVfGGKMe3Yj6RnrFHqo_d2a1B/view?usp=sharing)
- * testset-dev (2.14 GB): [BaiduYun](https://pan.baidu.com/s/1r1P5aJ1zOlQH_58LfYFzQQ) | [GoogleDrive](https://drive.google.com/open?id=1-BEq--FcjshTF1UwUabby_LHhYj41os5)(GT avalialbe)
- * testset-challenge (2.70 GB): [BaiduYun](https://pan.baidu.com/s/1ew6B-kvKV9yv__onnjA4dQ) | [GoogleDrive](https://drive.google.com/file/d/1Qwyp_cEpGyXGqJ8IbusEzuNHgbM403NP/view?usp=sharing)
- VisDrone-VID toolkit:
- * [Matlab beta](https://github.com/VisDrone/VisDrone2018-VID-toolkit)
- ### Task 3: Single-Object Tracking
- VisDrone-SOT dataset
- * trainset_part1 (7.78 GB): [BaiduYun](https://pan.baidu.com/s/1obWeT5DvBkTuBmO1NlSQ-Q) | [GoogleDrive](https://drive.google.com/file/d/1a-AmQjYATzj8seXLlEm9Sx8aQmClrJka/view?usp=sharing)
- * trainset_part2 (12.59 GB): [BaiduYun](https://pan.baidu.com/s/1c6iZeMJUXOIERxFJJ6B0jw) | [GoogleDrive](https://drive.google.com/file/d/16YPyhNDQrTgW8I2HaH_HNEO-KTRA-xso/view?usp=sharing)
- * valset (1.29 GB): [BaiduYun](https://pan.baidu.com/s/1WTWx4iyf33lnIyRu2uP_Hg) | [GoogleDrive](https://drive.google.com/file/d/18SNAOlCJtApnG2m45ud-1e_OtGYill0D/view?usp=sharing)
- * testset-dev (11.27 GB): [BaiduYun](https://pan.baidu.com/s/18j3umaWR_1fFy2ISOe9dGg) | [GoogleDrive](https://drive.google.com/open?id=1xCiHjU4JlR9QsYtiHYy2UUd3m6NthoBC)(GT avalialbe)
- * testset-challenge_part1 (17.40 GB): [BaiduYun](https://pan.baidu.com/s/14eWyaisDeciip-4_B14law) | [GoogleDrive](https://drive.google.com/file/d/1zxMLZrkkz4BkufbaDXQVMpDz-PRpPpxs/view?usp=sharing)
- * testset-challenge_part2 (17.31 GB): [BaiduYun](https://pan.baidu.com/s/1WDQ4JD5eLfRy-KVNyvKPig) | [GoogleDrive](https://drive.google.com/file/d/13J_9rwpf2TpVVsWgzMUv4uCxpOKDNbef/view?usp=sharing)
- * testset-challenge_initialization(12 KB): [BaiduYun](https://pan.baidu.com/s/1hvY0LXjTeuF8r-VVvVX1OQ) | [GoogleDrive](https://drive.google.com/file/d/1z7lQ0co8Dcu-ZojMN7dnIxn-i6QbGNL4/view?usp=sharing)
- VisDrone-SOT toolkit:
- * [Matlab beta](https://github.com/VisDrone/VisDrone2018-SOT-toolkit)
- ### Task 4: Multi-Object Tracking
- VisDrone-MOT dataset
- * trainset (7.53 GB): [BaiduYun](https://pan.baidu.com/s/16BtpKNWi0cEk8WUtfzpEHQ) | [GoogleDrive](https://drive.google.com/file/d/1-qX2d-P1Xr64ke6nTdlm33om1VxCUTSh/view?usp=sharing)
- * valset (1.48 GB): [BaiduYun](https://pan.baidu.com/s/1wTWFpHw4uLXPVCp1m5fQNQ) | [GoogleDrive](https://drive.google.com/file/d/1rqnKe9IgU_crMaxRoel9_nuUsMEBBVQu/view?usp=sharing)
- * testset-dev (2.14 GB): [BaiduYun](https://pan.baidu.com/s/1_gLvMxkMKb3RZjGyZv7btQ) | [GoogleDrive](https://drive.google.com/open?id=14z8Acxopj1d86-qhsF1NwS4Bv3KYa4Wu)(GT avalialbe)
- * testset-challenge (2.70 GB): [BaiduYun](https://pan.baidu.com/s/1xIloIRSj1FtcEoWI9esn7w) | [GoogleDrive](https://drive.google.com/file/d/1I0nn6dVKctzDE5YJ3q9qOlhKLiSIDAxF/view?usp=sharing)
- VisDrone-MOT toolkit:
- * [Matlab beta](https://github.com/VisDrone/VisDrone2018-MOT-toolkit)
- ### Task 5: Crowd Counting
- ECCV2020 Challenge
- DroneCrowd (1.03 GB): [BaiduYun](https://pan.baidu.com/share/init?surl=llJZJMi2L5oUQvj31iBlfg)(code: h0j8)|
- [GoogleDrive](https://drive.google.com/file/d/1HY3V4QObrVjzXUxL_J86oxn2bi7FMUgd/view?usp=sharing)
- ## Citation
- ```
- @article{zhu2021detection,
- title={Detection and tracking meet drones challenge},
- author={Zhu, Pengfei and Wen, Longyin and Du, Dawei and Bian, Xiao and Fan, Heng and Hu, Qinghua and Ling, Haibin},
- journal={IEEE Transactions on Pattern Analysis and Machine Intelligence},
- volume={44},
- number={11},
- pages={7380--7399},
- year={2021},
- publisher={IEEE}
- }
- ```
README.md at commit 4364e82, no license · at the source
Overview
- College of Integrated Circuits, Zhejiang University, ZJU-Hangzhou Global Scientific and Technological Innovation Center, Hangzhou, China
- Zhejiang ICsprout Semiconductor Co., Ltd, Hangzhou, China
- The State Key Laboratory of Integrated Services Networks, Xidian University, Xi’an, China
- Yongjiang Laboratory, Ningbo, China
- Guangdong Institute of Intelligence Science and Technology, Hengqin, Zhuhai, China
- School of Microelectronics, Nanjing University of Science and Technology, Nanjing, China
Abstract
The abstract is not reproduced here: the paper's license (CC BY-NC-ND) does not allow it. Read it in the paper, at the publisher or on Europe PMC.
Repository
Its files are read in the Code ↔ Paper reader above.
VisDrone/VisDrone-Dataset
4364e8265275dfa44fd8f767b5180af58580194d, 24 September 2023Availability: 2 checks, the latest on 27 October 2026: the link answers
- 27 October 2026: the link answers
- 27 September 2026: the link answers
1 file
- README.md, Text, 112 lines
Code availability statement
The paper has a code availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- it points to the authors' code: VisDrone/
VisDrone-Dataset - it says that the code is available on request
Read it in the paper: doi.org/10.1038/s41467-026-73825-3.
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 1 repository of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 0 scripts, each with its path and the digest of its content;
- no match between paragraphs and code yet;
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
No dataset and no data link were found in the paper.
Data availability statement
The paper has a data availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- no repository, dataset or request procedure was recognized in it
Read it in the paper: doi.org/10.1038/s41467-026-73825-3.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 28 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 16 authors, 2 keywords, 1 funder, 29 references.
Cite
This paper
Zhang, Z., Xu, J., Fan, X., Zhang, G., Wang, Z., Li, P., Luo, Q., Yu, H., Zhong, S., Zhang, Y., Fang, W., You, W., Sun, D., Ren, K., Wan, Q., & Zhang, Y. (2026). Volatile self-selective memristive neuron for millisecond-latency neuromorphic object detection at the edge. Nature communications, 17(1), 6951. https://
BibTeX
@article{zhang2026volati
author = {Zhang, Zhejia and Xu, Jiahua and Fan, Xuemeng and Zhang, Guobin and Wang, Zijian and Li, Pengtao and Luo, Qi and Yu, Haoxiang and Zhong, Shuai and Zhang, Yunyan and Fang, Wenzhang and You, Weidong and Sun, Daying and Ren, Kun and Wan, Qing and Zhang, Yishu},
title = {{Volatile self-selective memristive neuron for millisecond-latency neuromorphic object detection at the edge}},
journal = {Nature communications},
year = {2026},
month = may,
volume = {17},
number = {1},
pages = {6951},
publisher = {Nature Publishing Group},
issn = {2041-1723},
doi = {10.1038/
url = {https://
pmid = {42209522},
pmcid = {PMC13388706}
}
RIS
TY - JOUR
AU - Zhang, Zhejia
AU - Xu, Jiahua
AU - Fan, Xuemeng
AU - Zhang, Guobin
AU - Wang, Zijian
AU - Li, Pengtao
AU - Luo, Qi
AU - Yu, Haoxiang
AU - Zhong, Shuai
AU - Zhang, Yunyan
AU - Fang, Wenzhang
AU - You, Weidong
AU - Sun, Daying
AU - Ren, Kun
AU - Wan, Qing
AU - Zhang, Yishu
TI - Volatile self-selective memristive neuron for millisecond-latency neuromorphic object detection at the edge
T2 - Nature communications
J2 - Nat Commun
PY - 2026
DA - 2026/
VL - 17
IS - 1
SP - 6951
SN - 2041-1723
PB - Nature Publishing Group
DO - 10.1038/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1038/
"type": "article-journal",
"title": "Volatile self-selective memristive neuron for millisecond-latency neuromorphic object detection at the edge",
"container-title": "Nature communications",
"author": [
{
"family": "Zhang",
"given": "Zhejia"
},
{
"family": "Xu",
"given": "Jiahua"
},
{
"family": "Fan",
"given": "Xuemeng"
},
{
"family": "Zhang",
"given": "Guobin"
},
{
"family": "Wang",
"given": "Zijian"
},
{
"family": "Li",
"given": "Pengtao"
},
{
"family": "Luo",
"given": "Qi"
},
{
"family": "Yu",
"given": "Haoxiang"
},
{
"family": "Zhong",
"given": "Shuai"
},
{
"family": "Zhang",
"given": "Yunyan"
},
{
"family": "Fang",
"given": "Wenzhang"
},
{
"family": "You",
"given": "Weidong"
},
{
"family": "Sun",
"given": "Daying"
},
{
"family": "Ren",
"given": "Kun"
},
{
"family": "Wan",
"given": "Qing"
},
{
"family": "Zhang",
"given": "Yishu"
}
],
"container-title-short":
"volume": "17",
"issue": "1",
"page": "6951",
"DOI": "10.1038/
"PMID": "42209522",
"PMCID": "PMC13388706",
"ISSN": "2041-1723",
"publisher": "Nature Publishing Group",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
5,
28
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.1038/s41467-026-72428-2 [code]
- Artificial plateau neurons with in-situ spike-malleability for rhythmic quadrupedal locomotion.Journal: Nature communicationsIn common: 2 references, author Yishu Zhang
- [2] doi:10.1038/s41467-025-63831-2
- Wafer-scale fabrication of memristive passive crossbar circuits for brain-scale neuromorphic computing.Journal: Nature communicationsIn common: 4 references
- [3] doi:10.1002/advs.202407870
- All-Ferroelectric Spiking Neural Networks via Morphotropic Phase Boundary Neurons.Journal: Advanced science (Weinheim, Baden-Wurttemberg, Germany)In common: 4 references
- [4] doi:10.1038/s41467-022-34774-9
- Compact artificial neuron based on anti-ferroelectric transistor.Journal: Nature communicationsIn common: 4 references
- [5] doi:10.1021/acs.chemrev.5c00878
- Self-Oscillatory Neuron-like Devices for Unconventional Computing Applications.Journal: Chemical reviewsIn common: 3 references
- [6] doi:10.1038/s41586-025-08742-4 [code]
- Synaptic and neural behaviours in a standard silicon transistor.Journal: NatureIn common: 3 references
- [7] doi:10.1038/s41467-025-62151-9 [code]
- Artificial transneurons emulate neuronal activity in different areas of brain cortex.Journal: Nature communicationsIn common: 3 references
- [8] doi:10.1038/s41467-026-72900-z [code]
- Resistive memory-based neural differential equation solver for score-based diffusion model.Journal: Nature communicationsIn common: 3 references
- [9] doi:10.1038/s41467-022-35160-1
- Reconfigurable neuromorphic memristor network for ultralow-power smart textile electronics.Journal: Nature communicationsIn common: 3 references
- [10] doi:10.1126/sciadv.adv6603 [code]
- Neuromorphic ionic computing in droplet interface synapses.Journal: Science advancesIn common: 3 references
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 1 repository of the authors' code, each at its verified commit and with its license, 0 scripts, and 0 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:f23438f77f3a8a7f…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1038/s41467-026-73825-3)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41467-026-73825-3.svg
:target: https://openscicode.org/badge/doi/10.1038/s41467-026-73825-3
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41467-026-73825-3"><img src="https://openscicode.org/badge/doi/10.1038/s41467-026-73825-3.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".
If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
