Argus
BY MULTICOMIOT · VISUAL INTELLIGENCE
2026-07-23 13:56:52+00:00 UTC

Argus Operator's Guide

Full walk-through, training and support

Welcome to Argus

Argus is MulticomIOT's aerial plant & cannabis detection console. You fly a field with the DJI Matrice 4T, the imagery is analysed, and every finding - especially cannabis - is routed to a human for verification before it counts. The platform then tracks it on a map, alerts the right people, and produces compliance-grade reports.

Read this once: the detector is decision support, not proof. A cannabis detection is a candidate for human review, never an automatic accusation. The drone's sensor is RGB + thermal (no red-edge), so cannabis calls must be verified by a person. Nothing here replaces an agronomist or the law.

Quick start (5 minutes)

1. Sign in

Open the console URL, enter your operator name and passphrase. Sessions last 12 hours. If you fail the passphrase too many times the account is locked briefly - that is the brute-force protection, wait a few minutes.

2. Set your theme

Top-right sun/moon button cycles Auto → Light → Dark. Auto follows your device. Your choice is remembered.

3. Learn the three things you'll do most

  • Review Queue - verify flagged detections (Approve / Reject).
  • Live Map - see detections on satellite imagery, step through flights.
  • Alerts - the bell tells you when something needs attention.

What you can see and do depends on your role - see Roles below.

Roles & permissions

An admin assigns each person a role on the Team page. Higher roles include everything below them.

RoleCan do
viewerRead dashboards, the map, alerts and reports.
operator+ Log flights and manage field data.
reviewer+ Approve / reject review items; claim tasks.
manager+ Assign work, manage sites & devices, generate/schedule reports, see the team & audit log.
admin+ Full user management and settings.

Every login, review decision, assignment and user change is written to the append-only Audit Log - the chain-of-custody a regulator expects.

The daily workflow (field to report)

End to end, a mission flows like this:

#StepWhere
1Plan the survey grid (altitude/overlap for your target detail).argus mission / your DJI app
2Fly the field nadir (straight down) with the Matrice 4T.Field
3Media uploads to storage automatically as you capture.Field uploader (RC Plus / laptop)
4Your imagery is tiled, scanned, placed on the map and turned into a report.Automatic / argus agent
5Cannabis + low-confidence hits are routed to review.Review Queue
6A reviewer verifies each one (Approve / Reject).Review Queue / My Tasks
7Confirmed cannabis and change vs last flight raise alerts.Alert Center
8Findings appear on the map and in the trends.Live Map / Trends
9A compliance report is generated (or auto-scheduled).Reports

Page-by-page tour

Overview

Your home: counts of runs, pending review, open and critical alerts, and the list of field runs. Click a run to open its detailed dashboard.

Live Map

Georeferenced detections on satellite imagery, coloured by class (cannabis stands out). Pick a Field, switch View to Timeline to step through flights with the slider, and tick Compare vs previous to see what is new, removed or persistent between two flights.

Review Queue

The heart of the platform. Every cannabis call and every low-confidence detection lands here. Reviewers Approve or Reject. Managers assign items to people; reviewers can Claim an unassigned item. Filter tabs: All / Assigned to me / Unassigned.

My Tasks

Just the items assigned to you, with one-click Approve/Reject. Deciding an item clears it from your list.

Sites & Zones

Register the fields/blocks you monitor - client, region, crop type, licence number. Used for reports and to organise work.

Drones & Edge

Your Matrice 4T flight log, plus edge inference devices (Jetson) with live status, telemetry (GPU temp, disk, model version, detections) and their API keys. See Fleet & heartbeat below.

Trends & Change

Detections by class across flights, the cannabis trend, and a per-field flight-to-flight change table (new / removed / persistent).

Alerts

Every operational alert, severity-coded, with acknowledge. See Alerts below.

Reports

Generate compliance / per-field / period reports, and schedule recurring ones that auto-email and archive. See Reports below.

Team & Audit

(Managers/Admins) Manage operators and roles; read the append-only audit trail.

Field operations & uploading

Capturing good imagery

Fly nadir at 25–40 m for fine detail, 80/70 overlap, in even light. Full capture settings are in the Data Collection Protocol (docs/DATA_COLLECTION_PROTOCOL.md).

Getting media to the platform

Run the field uploader so photos/videos push to storage during the flight:

  • On the RC Plus controller - follow ingest/rc-plus-termux.md (Termux + rclone).
  • On a field laptop - argus ingest --source <album> --field F1 --watch.
Put only a scoped Spaces key on a field device (ingest/spaces-scoped-key.md) - never your master key.

Fleet & edge heartbeat

Register a device on Drones & Edge → Register edge device; it gets an API key (click show). Run the heartbeat agent on the Jetson so the console knows it is alive and healthy:

  • python -m argus.cli heartbeat --url https://your-console --key <KEY> --interval 30
  • or the always-on systemd unit in edge/.

The console shows live status (online/offline), last-seen, and telemetry: GPU temp, disk, memory, model version, and detections processed, with a GPU-temp sparkline. If a device stops checking in it flips offline and raises an alert; a hot GPU or full disk also alert. Tune the windows with EDGE_* env vars.

Alerts & notifications

The bell (top bar) shows unread alerts. Open the Alert Center to acknowledge them. What fires:

AlertSeverityMeaning
Cannabis confirmedcriticalA reviewer approved a cannabis detection.
New cannabis (change)criticalCannabis appeared vs the previous flight - a possible new grow.
Cannabis candidatewarningCannabis is waiting in the review queue.
Review backlog highwarningToo many items pending - assign reviewers.
Edge device offline / hot / disk fullwarningA field device needs attention.
Report readyinfoA scheduled report was generated/emailed/archived.
Backup failedcriticalThe system of record was not backed up - fix immediately.

Alerts always show in-app; set ALERT_CHANNELS + credentials to also push to email / WhatsApp / Telegram / Slack.

Reports & compliance

On Reports (managers), generate three kinds:

  • Compliance / regulator - sites inspected, confirmed cannabis with GPS, and the full review chain-of-custody.
  • Per-field summary - runs, detections by class, review outcomes for a field.
  • Period analytics - a rollup across all fields.

Each opens in a new tab (print to PDF). Add a Schedule to auto-generate on a cadence - it emails recipients (SMTP) and archives a copy to your Spaces bucket. Run now fires one immediately.

Change detection

When a field is flown again, the platform compares the two flights and labels each detection added (new), removed (gone), or persistent (still there). New cannabis triggers a critical alert. See it visually on the Live Map (Compare vs previous) and summarised on Trends & Change. This is how you spot a new grow between surveys and how you confirm a cleared site stayed cleared.

Model training & validation

Detection accuracy is earned with data, not assumed. The honest state: until a model is trained on real, labelled Ghanaian field imagery and validated, cannabis detection is unproven - which is exactly why human review is mandatory.

The path, once you have imagery:

StepHow
CollectFly per docs/DATA_COLLECTION_PROTOCOL.md (stages, sites, oversample cannabis).
LabelAuto-label then human-verify per docs/LABELING_PROTOCOL.md; agronomist signs off cannabis.
SplitLeakage-free spatial split (hold out whole fields).
Trainargus train --data dataset.yaml (GPU droplet).
Validateargus evaluate --preds preds.json --gt gt.json → report + model card.
Sign offModel passes acceptance gates; card + human sign-off recorded (docs/MODEL_VALIDATION_PLAN.md).
The validation report chooses the cannabis threshold for a target precision (default 90%), not a guessed 0.50 - because a false accusation is not recoverable. Do not deploy a model that fails its gates.

Administration & deployment

(Admins) The platform runs from Docker on a droplet behind Caddy. Key .env settings and the full runbook are in deploy/README.md. The essentials:

  • Accounts - first admin from PORTAL_USER/PORTAL_PASSWORD; add the team on the Team page.
  • HTTPS - set a domain in SITE_ADDRESS, then PORTAL_SECURE_COOKIE=1 and PORTAL_FORCE_HTTPS=1.
  • Backups - set SPACES_* so the DB + review queue snapshot off-site automatically. Do not skip this.
  • Uptime - point a monitor at /healthz, and set HEALTHCHECK_PING_URL so downtime is noticed.
  • Map - set MAPBOX_TOKEN for the satellite basemap.

Troubleshooting & FAQ

SymptomFix
Locked out at loginToo many wrong tries - wait ~5 minutes, then use the correct passphrase. An admin can reset it on the Team page.
Map is blank / 'add token'The console has no MAPBOX_TOKEN set, or there are no georeferenced detections yet. Add the token; fly a mapped (nadir+GPS) mission.
No detections on the mapThe run had no GPS/georeferencing, or it hasn't finished processing. Confirm the mission was nadir with GPS.
Alerts not arriving by email/WhatsAppIn-app always works; external channels need ALERT_CHANNELS + the channel credentials in .env. Check the Alert Center's channel line.
Device shows offlineThe heartbeat agent isn't running or lost network. Restart it (systemd) and check the device key matches.
'Backup OFF' warningSet the SPACES_* keys so the system of record is protected off-site.
Report email didn't sendSMTP not configured, or recipients empty. Fill the SMTP_* block; 'Run now' to test.
Cross-origin request blockedA security protection - use the console directly, not embedded in another site.

Glossary

TermMeaning
NadirCamera pointing straight down (−90°) - the angle used for mapping.
GSDGround sample distance - cm per pixel. Lower = more detail.
OrthomosaicA single stitched, geometrically-corrected map image from many photos.
GeoreferencedEach detection has a real-world lon/lat.
RTK / PPKCentimetre-accurate GPS correction - needed for enforcement-grade coordinates.
PrecisionOf the things flagged cannabis, how many really were (few false accusations).
RecallOf the real cannabis, how much was found (few misses).
mAP@0.5Mean average precision - overall detection quality across classes.
Chain-of-custodyThe audit record of who verified what and when.
Edge deviceA field computer (Jetson) that can run detection near the drone.

Getting help & support

Still stuck? Contact MulticomIOT support:

  • Email: info@multicomgh.com
  • Docs in the repo: deploy/README.md (ops), ingest/, edge/README.md, and the docs/ protocols (collection, labeling, validation).
  • Health check: /healthz and /health show system status.

When reporting an issue, include what page you were on, what you clicked, what you expected, and anything from the Alert Center or /health.

Developed by MulticomIOT.

Argus compliance-grade report · Developed by MulticomIOT