qamule-trajectory
Python trajectory toolkit for QAMule VLM and agent training datasets.
Install
uv sync
CLI
Start the local viewer for the current directory and open the browser:
uv run qamule-trajectory
Start the viewer quietly without opening the browser:
uv run qamule-trajectory -q
Quiet mode still prints the local viewer URL.
Create a session:
uv run qamule-trajectory init dataset/open_wifi_20260626_120000 \
--instruction "Open Wi-Fi in Settings" \
--app com.android.settings \
--device-model "Pixel 8" \
--resolution 1080 2400 \
--android 14
Append a step after saving step_001.jpg in the session directory:
uv run qamule-trajectory append dataset/open_wifi_20260626_120000 \
--screenshot step_001.jpg \
--current-app com.android.settings/.Settings \
--thought "I can see the Settings home screen." \
--action '{"type":"click","x":540,"y":620}'
Validate a dataset, session, or trajectory.json:
uv run qamule-trajectory validate dataset/
Browse trajectories locally:
uv run qamule-trajectory view dataset/ --port 8932
-q and --quiet are accepted for quiet viewer mode.
Trajectory Layout
Each session is a directory named {task_slug}_YYYYMMDD_HHMMSS containing trajectory.json and sequential screenshots named step_001.jpg, step_002.jpg, and so on.
Metadata
Release files for qamule-trajectory 0.1.0
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 | |
|---|---|---|---|---|
| qamule_trajectory-0.1.0.tar.gz | 493.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qamule_trajectory-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 988.6 kB
Release files / qamule_trajectory-0.1.0.tar.gz
| Download URL | qamule_trajectory-0.1.0.tar.gz |
|---|---|
| Size | 493.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86a2bb7205c1dba5e22bce61f55a5e7a6f47d402e630d40aaabd8e6eebf26222
|
|
BLAKE2b-256 checksum How to use checksums |
396bb0521ca9aee477e6a99c70753da77a2ff042a4585217f75bfcc2ae0aad6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / qamule_trajectory-0.1.0-py3-none-any.whl
| Download URL | qamule_trajectory-0.1.0-py3-none-any.whl |
|---|---|
| Size | 495.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3635af4d4d974ae7e22ff8175dd5111d013b36b023665080a35eb25adb1caff4
|
|
BLAKE2b-256 checksum How to use checksums |
3f3c3720c2a2faa608e80f6c5bbf1743bdf3c4a18fe3af2144300b8c460f7602
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.24 {"installer":{"name":"uv","version":"0.11.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for qamule-trajectory 0.1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.