# Instructions for entering data into the template file

> **Template file download.** [(template\_input.xlsx)](https://github.com/KRICT-DATA/solarcell/raw/main/template_input.xlsx)

* The information below was written based on the 240228 version of the template Excel file.
* The order of columns in the Excel file can be written in the order of stacking layers of a Perovskite Solar Cell.
* Each column contains information about the coating and post-processing used to form a stacking layer.
* Each column is divided into blocks, which contain a single procedure for building a stacking layer.
* If various materials or solvents, etc. are used for each procedure, you can add blocks to enter the additional data.
* The first two rows contain the experimental environment (coating condition) during each column process.
* Each data is described with the following items.

&#x20;       Description:

&#x20;       Format:

&#x20;       Default:

&#x20;       Examples: (Examples are separated by semicolons.)

* The columns of each layer are organized in the following order. The order of columns can be changed depending on the solar cell type, such as n-i-p or p-i-n.&#x20;

1. TCO
2. Blocking/buffer layer
3. Surface Treatment1
4. ETL
5. ETL Treatment
6. Surface Treatment2
7. Perovskite\*
8. Perovskite Treatment
9. HTL
10. HTL Treatment
11. Anode metal
12. Note

* &#x20;The pre-registered multiple JV curve files, UV-visible light absorption spectra, X-ray diffraction (XRD), scanning electron microscopy (SEM), and stability (JV, MPPT) data can be uploaded with the device recipes.

&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://krict-data.gitbook.io/perovskite-solar-cell-docs/recipes-template/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
