Source
Synthetic
Generated controls; no telescope exposure is added.
Evidence dossier / EXP-002
Injection & recovery
The record behind it.
Recovery depends strongly on drift and injected strength in this configuration. No tested strength recovered every trial across ±3 Hz/s. This is a synthetic detector check, not telescope survey completeness.
What has actually been checked
Separate assessments keep missing evidence visible. No combined confidence percentage is assigned.
Repeatability
Recorded
Parameters, seed and recovery decisions preserved.
Sensitivity
Limited
Five trials per cell in one tested configuration.
External review
Not recorded
No independent acceptance or submission is claimed.
Chain of evidence
01 / Input0 source referencesArchive or generated control
02 / ProcessingEXP-002Code e9db4be
03 / Outputrecovery_grid_completed2026-10-12 19:08 UTC
Run identifier: 20261012T190848550861Z-exp-002-floor. The code reference is the one recorded by the experiment, not the current website build.
Source material
Radio-input hashes identify the local frequency slices described in the notes. They are not checksums of the complete remote archive files.
Outputs you can inspect
recovery_grid.json273,572 bytes
SHA-256: 77f84624867ed5e1a2bf9e1e2409270284254f090162ee9b25474a8e4804a234
sweep.csv2,352 bytes
SHA-256: 54a99746a0e208541ccf6ec8dd72c8fd4e5e4fab9f90504fd62b984a2a8ab343
manifest.json
SHA-256: Manifest is the checksum index; it does not hash itself.
Reproduce the recorded processing
Use the project installation guide and the code revision recorded above. Source access and optional scientific dependencies are required. The website itself does not execute this command.
xenia live floor --mode full --seed 20261012 --experiment-id EXP-002Original run notes
- Synthetic setigen calibration; not telescope observations.
- Trials use deterministic seeds and one-to-one frequency/drift hit matching.
- sweep.csv is row-major; recovered_seeds is encoded as a compact JSON array.
- turboSETI 2.3.2 raised its known NumPy-array formatting TypeError during final candidate-count logging after writing parseable .dat hit rows; those rows were retained and validated.
- turboSETI 2.3.2 raised its known NumPy-array formatting TypeError during final candidate-count logging after writing parseable .dat hit rows; those rows were retained and validated.
- turboSETI 2.3.2 raised its known NumPy-array formatting TypeError during final candidate-count logging after writing parseable .dat hit rows; those rows were retained and validated.
- turboSETI 2.3.2 raised its known NumPy-array formatting TypeError during final candidate-count logging after writing parseable .dat hit rows; those rows were retained and validated.
- turboSETI 2.3.2 raised its known NumPy-array formatting TypeError during final candidate-count logging after writing parseable .dat hit rows; those rows were retained and validated.
This dossier makes our processing inspectable. A publication, DOI, or external review will be linked only after it exists. How the work can contribute →