> For the complete documentation index, see [llms.txt](https://docs.haposan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.haposan.com/chc/interpreting-characterisation-results.md).

# Interpreting characterisation results

## Welcome

**Welcome to the guide of interpreting characterization results!** :wave: This guidebook records some notes on interpreting characterization results of materials. The goal is to provide a comprehensive and collective documentation of interpreting characterisation results that are tied to publications I have participated in. Contents may vary, but in general, each page contains something in this format:

1. A checklist of pre-requisite understanding;
2. General reference of the principles and working mechanism of the measurement technique;
3. How to verify and analyse your results (with softwares, if available);
4. How to write the interpretation of the analysis; and
5. Some know-how or case-specific explanations related to published works.

I hope this collective will be useful for your work! :man\_scientist::woman\_scientist:

## Navigation

You can quickly navigate through the sections using the navigation bar on the left side. There is also a search box to help you find any content in this course swiftly.

## Contact

Feel free to contact me through email: <kb@haposan.com> or <haposan@u.nus.edu> if you have inquiries and/ or suggestions. Looking forward to hearing from you!


---

# 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://docs.haposan.com/chc/interpreting-characterisation-results.md?ask=<question>&goal=<user_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.