The twelve Processor modules, in practice
Processor modules turn acquired material into inspectable candidates and derived assets. Their outputs have different evidential roles; none should be treated as a general-purpose authority on an instrument.
Follow the input, output and review boundary
The current module guide describes twelve modules in Processor 0.2.0, an unpublished development candidate. The following map explains those documented responsibilities. It is not an assertion that each module is independently released, broadly benchmarked or available through a public service. Choose a module by the material it accepts and the evidence it returns, then preserve the review decision that connects its result to the research record.
| Module | Input → output | Interpretation and review |
|---|---|---|
| Ingestor | Registered transfer records → source-preserving staging records. | Schema-valid staging establishes an intake contract; it does not make the content an accepted canonical fact. |
| Normalizer | Staged source records → deterministic normalized candidates with original evidence. | Review and projection remain explicit. Exact replay preserves existing decisions instead of silently replacing them. |
| Bootstrap | Versioned policies, observations and decisions → governed projection receipts. | Projection depends on the authorized policy and its prerequisites; it is not unrestricted automatic acceptance. |
| Document evidence | Identified document bytes → pages, assets, exact selectors and candidate assertions. | A quotation must resolve to its source. Silence or an absent value must not become an invented numerical fact. |
| Localizer | Place mentions and provider evidence → ranked geographic candidates. | Retain ambiguity, temporal context and unknown positional accuracy. A high-ranked candidate is not automatically the historical location. |
| Language detection | Source text → language-identification evidence for quality review. | Short or ambiguous text can justify abstention. Uncalibrated scores are not probabilities of correctness. |
| Litparser | Citation strings → literature candidates with literal field evidence. | Conflicting years and indefinite page continuations remain uncertain; parsing does not authorize a canonical bibliographic write. |
| Enrichment | An authorized page or workflow → retained institution or virtual-instrument facts. | Fetching is opt-in and source-bound. Replaying retained evidence is distinct from obtaining a new page snapshot. |
| PLENUM | Claim-scoped evidence → versioned suitability and source-dependence assessments. | The result is a policy-based assessment for a claim, not permanent trust in a publisher or a truth probability. |
| Ambitus | MusicXML, compressed MXL or MIDI → nominal pitch-range evidence. | Instrument identity remains a separate question. MIDI pitch-control information is flagged rather than silently treated as measured acoustic pitch. |
| Imageseg | Image and SAM 2 configuration → aligned masks and annotations. | Masks are class-agnostic. A selected region needs interpretation and review before it becomes an organological component label. |
| Modelgenerator | Photographic bundle and pinned DA3 configuration → checked point clouds and camera paths. | These are not automatically textured meshes. Registration, visibility and transport verification are separate concerns. |
Example: a historical account becomes a candidate
Consider a supplied document naming a workshop, place and construction year. Intake preserves the source identity. Document evidence identifies the relevant page and passage. Language detection and Litparser can assist interpretation or bibliography; Localizer can propose geographic matches. Normalizer organizes candidate values without discarding the literal account. PLENUM evaluates how suitable that account is for the particular proposition and whether other accounts depend on it.
The editorial question is then precise: does the passage support construction by this workshop for this instrument state and date? A page mentioning a workshop nearby, or a contract that did not lead to completion, requires a different relation. The accepted projection should retain the reviewed claim and its grounds. If the evidence is insufficient, preserving an unresolved candidate is more informative than forcing a clean but unsupported value.
Example: images and scores support different claims
Imageseg can isolate a visible region for inspection; Modelgenerator can estimate spatial structure from a photographic bundle. Neither establishes the identity or date of the object pictured. Ambitus can describe the nominal range of a score or MIDI file; it does not establish that a particular surviving instrument can produce every encoded pitch under its current configuration. Connect each derived asset to its source and the domain question it actually addresses.
Use diagnostics to answer a bounded question
Processor source checkout · documented local inspection commands
modavis-processor modules --check-imports
modavis-processor exampleIn the documented development package, the first command inspects the module inventory and imports; the second runs an authored, deterministic PLENUM example without requiring a database, model or service. It reports the modavis.plenum.v1 policy with automatic promotion disabled. These checks help establish that a local installation and example behave as described. They do not evaluate extraction accuracy over a historical corpus or validate an external provider.
For a meaningful module evaluation, retain the diagnostic input, expected task, actual output and failure cases. Separate transport success from semantic correctness, model availability from useful output, and a small authored fixture from a representative benchmark. The module guide’s boundaries are especially useful here: they show where an automated result stops and a research judgment begins.
Sources & further reading
- MODAVIS Processor · module guide and package README
Project documentation inspected on 26 September 2026; package 0.2.0, an unpublished development candidate. Used for current module responsibilities and limitations, not as a claim of public package availability.
- MODAVIS Framework · component registry
Project component documentation inspected on 26 September 2026. Used for the division of responsibilities among Initiator, Aggregator, Processor, Navigator, Prospector, Persistor and supporting services.
- Research workflow demonstrations 0.1.1
A separately archived demonstration resource; not a substitute for the current unpublished Processor package.
- Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)
Dissertation submitted to Universität Leipzig, 11 September 2026. Chapter 4 on source processing and provenance; §8.3.4.1 on claim-scoped assessment. Page numbers refer to the printed manuscript pagination. The manuscript is not distributed by this website.
Page editions 2026-09-r4 ↓
Read a fixed snapshot of this chapter, or return to the current notebook.
Edition 2026-09-r4 · SHA-256
1db01f30a1ecPage metadata ↗