View the recipe
This is the file that runs. Not a description of the method, not pseudocode for it: the governed spec the embedding-analog report is computed from, reproduced here verbatim from the repository at build time. Every number on that page comes out of running it.
folia run registry/recipes/folia/reproductions/embedding-analog-gold-prospectivity --no-cache
That one command is the whole instruction. The AlphaEarth reads happen inside the run: a column-projected lookup in the published tile index over HTTPS range requests, a windowed read of each intersecting Cloud-Optimized GeoTIFF, int8 dequantisation per the dataset record's declared encoding, and a mosaic across UTM zones onto the analysis grid. No prefetch step, no Earth Engine, no credentials, nothing materialised on disk first.
What makes it a different site
Belt, site, reference set and every hyperparameter are parameters. Standing up
a second site is a --set list, not a fork of the recipe:
| Parameter | What it is |
|---|---|
belt_bbox |
The belt the model learns "deposit vs country rock" within, and where the background is drawn from. |
site_bbox |
The AOI you want a resemblance read on. It has to sit inside the belt. |
occurrences_uri |
Your belt's known-occurrence GeoJSON, travelling with the recipe (local://data/…) or fetched over http(s). |
positive_filter |
Which features count as positives. Non-matching features stay in the file and still push the background draw away from near-deposit ground. {} = every feature is a positive. |
background_seed, rf_*, reference_window_px |
The knobs the measured skill was measured under. Change them only with a reason, and re-measure. |
The fill-in-the-blanks form of that list, a template, and the launcher that writes
the command live in the repository at
research/mineral-prospecting/embedding-analog/sites/. A second site, the
Midlands (Kwekwe-Gweru) belt scoring Kwekwe block 4, is staged
there as the worked example.
The spec
Where the rest of it lives
The spec above cites three things by name, and all three are readable:
- The dataset record.
@google-deepmind/aef/v1/annualdeclares where the tile index sits, which columns it carries, and how int8 values dequantise. That record is the contract; swapping embedding products means swapping the reference, not editing the engine. - The operations.
raster_sample_points,point_classifier_train/_loo_validate/_predict, and theembedding_fieldsource arm. None of them knows anything about gold: the chain is "a multi-band raster plus labelled points, in; a classifier, its held-out skill, and a score map, out." - The validation record.
validations/comparison.yamlstates the floors first and then the measurements, and decomposes the 0.92-0.96 band by swapping one thing at a time (the classifier is worth ~0.001-0.01, the particular background draw ~0.02, the reprojected sampling grid ~0.015).