Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Simultaneous localization and mapping (SLAM) tools in 3D
Currently implements particleFilterLoc
. Supports Python 3.6+.
Install the slam3d package from PyPi:
python3 -m pip install slam3d
Or use the source distribution or wheels in the latest release.
To install the latest unreleased code, download or clone this source repository and run the following to build and install:
python3 -m pip install .
import numpy as np
from particlefilter import ParticleFilterLoc, setSeed
# If deterministic tests are needed, call this before anything else
setSeed(123456789) # Argument is np.uint32
pf = ParticleFilterLoc()
pf.depositVio(t: np.float64, x: np.float32, y: np.float32, z: np.float32, dist: np.float32)
pf.depositRange(bx: np.float32, by: np.float32, bz: np.float32, range: np.float32, stdRange: np.float32)
pf.depositRssi(bx: np.float32, by: np.float32, bz: np.float32, rssi: np.int32)
pf.getTagLoc() # returns tuple: (status: np.int32, t: np.float64, x: np.float32, y: np.float32, z: np.float32, theta: np.float32)
To install for development, download or clone and run:
python3 -m pip install -e .
Source found in ./particlefilter/cython
.
Source found in ./particlefilter
. A bundled version of MUSL rand_r()
is included for Windows builds. Force it on other platforms with -DPF_FORCE_MUSL_RANDR=1
. Precompiled shared libraries can be found in the latest release.
gcc -fPIC -shared -o particlefilter.so -Iparticlefilter/include particlefilter/src/*.c -lm
Or on Windows with cl.exe
:
cl.exe particlefilter/src/*.c /Iparticlefilter/include /MT /link /DLL /OUT:build/particlefilter.dll
Compile tests with:
gcc -o build/test -Iparticlefilter/include particlefilter/src/*.c test/test.c -lm
On Windows cl.exe
also works (from Development Command Prompt):
cl.exe -o build/test -Iparticlefilter/include particlefilter/src/*.c test/test.c -lm
Compile and debug tests with:
gcc -o build/test -Iparticlefilter/include particlefilter/src/*.c test/test.c -lm -g
gdb ./build/test
Both test/test.c
and test/test.py
implement mostly the same test.
test [--nofail] <test folder> <output file> [expected file (required without --nofail)]
The currently provided test folder is ./test/data
. --nofail
will cause the test to always exit with status code 0 and allow omitting testing against an expected file (by not providing the last argument).
When running the C test, some expected files are provided in ./test/data
for various operating systems and compilers. When running the Python test, you should test against the output of running the C test on your system. The Python test will also for some floating point precision deviation. Since the Python test tests each value individually, it is impervious to CRLF/LF differences.
Copyright (c) 2021, Wireless Sensing and Embedded Systems Lab, Carnegie Mellon University All rights reserved.
This source code is licensed under the BSD-3-Clause license found in the LICENSE file in the root directory of this source tree.
FAQs
Simultaneous localization and mapping (SLAM) tools in 3D
We found that slam3d demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.