SESAMI
Usage
from SESAMI.bet import fitbet
BET_dict, BET_ESW_dict = fitbet(csv_file="example.csv", columns=["Pressure","Loading"],
adsorbate="N2", p0=1e5, T=77,
R2_cutoff=0.9995, R2_min=0.998,
font_size=12, font_type="DejaVu Sans",
legend=True, dpi=600, save_fig=True, verbose=False)
print(BET_dict, BET_ESW_dict)
- csv_file: N2 isotherm csv file
- columns: [Pressure, Loading], 2 columns, one for rpessure (unit: Pa), one for uptake (unit: mmol/g)
- adsorbate: N2, Ar or other
- p0: if other
- T: test temperature if other
- R2_cutoff (default: 0.9995): The value of R2 beyond which we deem R2 ceases to have a bearing on the goodness of the linear region.
- R2_min (default: 0.998): R2 value a chosen region must have to be termed linear
- font_size: word size in figure
- font_type: word type in figure
- legend: with legend in figure or not
- dpi: dpi in figure
- save_fig: save png or not (local folder)
- verbose: print detail or not
from SESAMI.predict import betml
MLBET = betml(csv_file="example.csv", columns=["Pressure","Loading"], verbose=False)
print(MLBET)
- csv_file: N2 isotherm csv file, we recommend the columns name of pressure and uptake is Pressure and Loading, and the 1st column should be pressure with unit as Pa and 2nd column should be uptake with unit as mmol/g
- columns: [Pressure, Loading], 2 columns, one for rpessure (unit: Pa), one for uptake (unit: mmol/g)
- verbose: print detail or not
Website
Reference
SESAMI-APP: SESAMI APP: An Accessible Interface for Surface Area Calculation of Materials from Adsorption Isotherms
SESAMI 1.0: Surface Area Determination of Porous Materials Using the Brunauer-Emmett-Teller (BET) Method: Limitations and Improvements
SESAMI 2.0 (Machine Learning Model): Beyond the BET Analysis: The Surface Area Prediction of Nanoporous Materials Using a Machine Learning Method
Metadata
Release files for sesami 2.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sesami-2.9.tar.gz | 13.1 kB | Without provenance | Details for sesami-2.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sesami-2.9-py3-none-any.whl | Python 3 | none | any | Details for sesami-2.9-py3-none-any.whl |
Total release size: 25.2 kB
Release files / sesami-2.9.tar.gz
| Download URL | sesami-2.9.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b46b9c4e533295fcffd1a2ea675774f216668e948a59e74e921ee9ea7a11030
|
|
BLAKE2b-256 checksum How to use checksums |
25cc7c2fd5adcf32ea26b6a8131827e1da26fe9a2359cdb8e5c0b4ab5d9df69f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / sesami-2.9-py3-none-any.whl
| Download URL | sesami-2.9-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24a075578a21749eaaae9a5990e60b12ba629e533a8fc01d6d5c501d4358ae96
|
|
BLAKE2b-256 checksum How to use checksums |
61a280738d81edeaffaf46656ee40c9cc51732f49017ce7270230e2b9a0ce737
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for sesami 2.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.