Skip to content
#edge computing Open access

§23.32 · The Lookup Purity Restored, and Unified: n1 Alone Classifies All Three Vertex-Figure Classes

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Abstract§23.27 §6.4 found that, restricted to one defect per arm, grouping the holonomy angle by (transportclass, δ, (k1+k2) mod 5) gives a pure lookup for vertex-figure class T: 24 keys (6 per δ), each mapping to a single angle. §23.31 §6 tested the same grouping, using the same transport-class test, on classes M and A, and found it impure in both: the identical key can map to two different angles depending on which specific pair (a, b) is used.This note traces the impurity to its source directly, rather than guessing at a fix. For every impure key,the rows that disagree are printed side by side; in every single case, the two groups of rows are separated exactly by n1 — the ordinary wheel-closing power of edge e1 alone, already computed byfind_n in every script since §23.21, and never itself used as a grouping variable. Replacing the transport-class test with n1 directly — grouping by (n1, δ, (k1+k2 ) mod 5) — gives a pure lookup: 16 keys, 0 impure. This holds not only for M and A but for T as well, at every one of 4 hinges tested: 12 (hinge, class) combinations, all pure, all with exactly 16 keys.This is a stronger result than the one it replaces: a single classifier, n1∈ {1,4}, already available with no extra computation, produces a pure lookup uniformly across all three vertex-figure classes, superseding §23.27 §6.4’s class-T-specific transport-class test rather than merely patching it for M and A. Merging further over δ (grouping by (n1 , residue) alone) is checked too, and found impure for allthree classes alike (10 keys, 6 impure) — recorded for completeness, not claimed to work; δ is needed.Keywords600-cell · lookup purity · wheel-closing power n1· vertex figure · classes T/M/A · exhaustive verification

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54

Related blog posts

Microsoft Research Blog Oct 6, 2026

What AI gets wrong and what failure teaches us

Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity.  The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.