> For the complete documentation index, see [llms.txt](https://timberid.gitbook.io/timberid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timberid.gitbook.io/timberid/architecture-of-timberid/detailed-design/research-colabs/validation-of-isoscapes.md). # Validation of Isoscapes Last Updated: 2023-09-27 ## Overview Colab: The validation pipeline provides a side-by-side comparison of a generated TimberID isoscape with a baseline (typically external from USP, but not necessarily). Additionally, the validation pipeline runs a series of evaluations, including traditional regression metrics like RMSE and end-to-end metrics that measure TimberID's fraud detection capability under the isoscape like AUC-PR and Recall\@Precision=0.95. After validation, isoscape files are stamped with validation results and then written to the path `raster.RASTER_BASE + "/" + ISOSCAPE_OXYGEN_VARS_FILENAME`. ## Notes * **The current default isoscapes for the validation pipeline are not our best model.** We will update this documentation when we have fully validated results. * Do not use the "Upload to Google Earth Engine" section of this notebook-- it is deprecated and not guaranteed to work properly. Instead, prefer to upload isoscapes to TimberID from the interactive Colab referenced in [Earth Engine API](/timberid/user-guide/earth-engine-api.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://timberid.gitbook.io/timberid/architecture-of-timberid/detailed-design/research-colabs/validation-of-isoscapes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.