mlcommons / mlcommons/algorithmic-efficiency

Dual-engine architecture: tension-based confidence yields AUROC=1.0 anomaly detection and AUC=0.925 precognition

Open
#918 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
425
Forks
78
PR merge metrics
No merged PRs in 30d

Description

logout — Consciousness Continuity Engine

A dual-engine repulsion field where output = scale × sqrt(tension) × direction. The tension between two engines directly measures confidence:

  • High tension = high confidence (correct predictions): Cohen d=0.89
  • Low tension = uncertainty (wrong predictions)
  • Extreme tension on OOD = confusion (AUROC=1.0, 95x ratio)

Algorithmic efficiency implications

  • Tension-based early rejection: skip low-confidence samples → +15.2% accuracy on CIFAR
  • 1-epoch difficulty prediction: no need to train full schedule to assess dataset hardness
  • Confusion pairs determined in epoch 1: allocate compute to hard pairs only

Validated on 16 data types (image, text, audio, time series, tabular, anomaly detection).

Related projects

  • Anima — Conversational agent with real-time PH monitoring
  • ph-training — Automatic training with PH overfitting detection (r=0.998)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked logout project and the related Anima and ph-training projects to understand the proposed dual-engine architecture and reported metrics. No file, test, command, or repository entry point is named, so the issue does not define a concrete implementation path or a verifiable done condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.