> For the complete documentation index, see [llms.txt](https://anufrievroman.gitbook.io/freepaths/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anufrievroman.gitbook.io/freepaths/basic-tutorials/electrons-in-holey-membranes.md).

# Electrons in holey membranes

In this example, we use `examples/electrons_in_holey_membrane.py` file to compute the electrical conductivity and Seebeck coefficient of a holey membrane, similar to those measured in Ref. \[1]. The input file sets electron mean free paths at a constant value of 15 nm.

```
ELECTRON_MFP = 15e-9
```

Moreover, since the electrical conductivity depends on the energy of electrons, we need to set the Fermi level of the crystal. For example, in *n*-doped silicon with $$3 \times 10^{18} cm^{-3}$$ dopant concentration, we can estimate the Fermi level at about -50 meV from the conduction band. This value can be set in the input file to get values directly in the plots.

```python
from scipy.constants import electron_volt
MEDIA_FERMI_LEVEL = -50e-3 * electron_volt
```

To run the simulation for electrons, use the `-e` flag as follows:

```
freepaths -e electrons_in_holey_membrane.py
```

The simulation will trace the electrons in a 100-nm-thick porous silicon membrane:

<figure><img src="/files/3eu1dW0Cp7XA4fNpYmmd" alt="" width="257"><figcaption></figcaption></figure>

From the trajectories, the simulator calculates the spectra of mean travel time $$\tau\_s(E)$$ and transport distribution function $$\Xi (E)$$:

<div><figure><img src="/files/sWhk9RK7tGj6nkWVWGCu" alt=""><figcaption></figcaption></figure> <figure><img src="/files/VPHbOhQ5pLLhNzCbYpkK" alt=""><figcaption></figcaption></figure></div>

From the transport distribution function, the electrical conductivity $$\sigma$$ and Seebeck coefficient are evaluated as explained in [the Section of electrical conductivity](/freepaths/theory/electrical-conductivity.md) and Ref. \[2]. In practice, they are calculated and plotted as a function of Fermi energy:

<div><figure><img src="/files/cC2T1bfWz4P3BSIZxq5R" alt="" width="534"><figcaption></figcaption></figure> <figure><img src="/files/BikWjxUIowfdmXmIR4v6" alt="" width="563"><figcaption></figcaption></figure></div>

Thus, the values obtained for our specific Fermi level are about $$\sigma$$ = 85 kS/m and S = 0.3 mV/K, roughly in the range reported in the experiments \[1]. The uncertainty comes from the fact that the Fermi level in the experimental samples is usually not known and only roughly estimated from the doping level, which in turn is also approximated. Thus, these simulations work best to compare different structures on the same wafer with the same doping rather than to obtain absolute values.

#### References

1. Lim et al.,[ *ACS Nano* 10, 1, 124–132 (2016)](https://pubs.acs.org/doi/10.1021/acsnano.5b05385)
2. Priyadarshi and Neophytou, [J. Appl. Phys. 133, 054301 (2023)](https://doi.org/10.1063/5.0134466)


---

# 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 dynamically by asking a question.

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

```
GET https://anufrievroman.gitbook.io/freepaths/basic-tutorials/electrons-in-holey-membranes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
