Skip to content

290 as default resources monitoring - #292

Merged
guillaume-byte merged 4 commits into
288-data-tags-export-to-labelling-integrationfrom
290-as-default-resources-monitoring
Aug 14, 2026
Merged

290 as default resources monitoring#292
guillaume-byte merged 4 commits into
288-data-tags-export-to-labelling-integrationfrom
290-as-default-resources-monitoring

Conversation

@guillaume-byte

Copy link
Copy Markdown
Member

Mix of resources monitoring and data export with tags feature.

guillaume-byte and others added 4 commits August 11, 2026 17:23
Background daemon thread, started alongside the watchdog in grpc_serve(),
samples system and process resource usage on a wall-clock interval and
logs each metric through the existing signal pipeline so it shows up in
Weights Studio like any other loss/metric curve. GPU metrics use NVML
(nvidia-ml-py) and degrade gracefully with no NVIDIA driver present.

Enabled by default; configurable/disableable via env vars or a new
resource_monitoring.yaml (per-category toggles), documented in
docs/resource_monitoring.rst and docs/configuration.rst.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
New weightslab.export package collects bounding boxes and segmentation
masks (converted to polygons via OpenCV, optional weightslab[export]
extra) from the registered dataframe into a format-agnostic
representation, then encodes it to one of three relabeling-tool formats.
Bounding-box export needs no extra dependency.

Wired through three equally-weighted entry points sharing the same core
logic:
- Python API: wl.export_annotations(fmt, path=None, origin=None, ...)
- CLI: `weightslab export --format {cvat,label_studio,v7} [OUTPUT]`,
  connecting over gRPC like `weightslab cli`
- gRPC: new ExportAnnotations RPC (experiment_service.proto), delegated
  to DataService -- this backs the Weights Studio "Export" button
  (frontend change tracked separately in weights_studio)

Class names and image paths/dimensions have no dedicated registry in the
current data model, so both are resolved best-effort (explicit override,
then dataset.class_names / common path attributes, then a synthetic
filename) -- documented explicitly in docs/export.rst so silent
mismatches aren't a surprise.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@guillaume-byte
guillaume-byte merged commit 091a4df into 288-data-tags-export-to-labelling-integration Aug 14, 2026
9 checks passed
@guillaume-byte
guillaume-byte deleted the 290-as-default-resources-monitoring branch August 14, 2026 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant