sim-bug-tools
sim_bug_tools is a python toolkit for exploring bugs in software simulations. This module consists of python classes for describing, navigating, and interacting with software simulations to find bugs or other scenario outcomes based on geometric analysis of known information.
This module is developed for research in scenario-based testing for the validation and verification (V&V) of autonomous vehicles (AV). We were frustrated by the limitations imposed by time and resource cost of the AV V&V testing process given the many configurations of parameters for AV Testing. This module contains the tools we use to understand and navigate these high-dimensional spaces.
Research Team
This research is conducted by Embry-Riddle Aeronautical University of Daytona Beach, Florida. Dept. of Electrical Engineering and Computer Science.
Faculty Team Lead
Dr. Mustafa İlhan Akbaş akbasm@erau.edu
PhD Students
Quentin Goss gossq@my.erau.edu
John Thompson thomj130@my.erau.edu
Undergraduate Students
Annamaria Summer summera@my.erau.edu
Citing This Work
If you would like to cite this work. Please cite our latest paper about the topic:
J. M. Thompson, Q. Goss, and M. I. Akbas, “A Strategy for Boundary Adherence and Exploration in Black-Box Testing of Autonomous Vehicles,” in 2023 IEEE International Conference on Mobility, Operations, Services and Technologies (MOST), pp. 17–19, IEEE.
@incollection{Thompson2023Strategy,
author = {Thompson, John M. and Goss, Quentin and Akba{\ifmmode\mbox{\c{s}}\else\c{s}\fi}, Mustafa {\ifmmode\dot{I}\else\.{I}\fi}lhan},
title = {{A Strategy for Boundary Adherence and Exploration in Black-Box Testing of Autonomous Vehicles}},
booktitle = {{2023 IEEE International Conference on Mobility, Operations, Services and Technologies (MOST)}},
journal = {Published in: 2023 IEEE International Conference on Mobility, Operations, Services and Technologies (MOST)},
pages = {17--19},
publisher = {IEEE},
doi = {10.1109/MOST57249.2023.00028}
}
Metadata
Release files for sim-bug-tools 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sim-bug-tools-1.0.1.tar.gz | 47.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sim_bug_tools-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.8 kB
Release files / sim-bug-tools-1.0.1.tar.gz
| Download URL | sim-bug-tools-1.0.1.tar.gz |
|---|---|
| Size | 47.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f3c978498bea4bde3e4bc9556421e6bd261e1f7e43aa20ac2fa71dee4df5582
|
|
BLAKE2b-256 checksum How to use checksums |
e2e566d2471a0f4610e4b108f5b58b5934a332930e1d156cf27597096cab21a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.18
|
Release files / sim_bug_tools-1.0.1-py3-none-any.whl
| Download URL | sim_bug_tools-1.0.1-py3-none-any.whl |
|---|---|
| Size | 55.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00f2063d9b086384651dd5fc44ea1009f77c22ffe426f4b7db707bbdd5526d2c
|
|
BLAKE2b-256 checksum How to use checksums |
c5bdf84152bb1e250122b7e6a6e2ba80e8004944d81166710df89a78c9fd94f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.18
|
Security for sim-bug-tools 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.