Translate the provided English OghmaNano HTML/PHP page into Brazilian Portuguese by performing a strict, diff-only transformation: preserve all HTML, PHP, structure, order, IDs, classes, scripts, includes, include count, include locations, tables, menus, analytics, schema, and layout exactly as-is; do NOT add, remove, duplicate, reorder, or re-insert any PHP include statements; change to ; if and only if the English page does not already set $lang or include menu_top.html, then immediately after insert "$lang='pt'; include($_SERVER['DOCUMENT_ROOT'].'/menu_top.html');", otherwise do not add a second include; in the $meta array translate title and description faithfully (no SEO rewriting), change canonical to the /pt/ version, ensure 'lang' => 'pt', and ensure 'i18n_key' exists and is set deterministically to the canonical path WITHOUT the scheme/host and WITHOUT the /pt prefix (i.e., i18n_key = parse_url(canonical,PHP_URL_PATH) with any leading '/pt' removed); keep all other existing meta keys unchanged and do not add or remove any others; translate all visible text into professional, technical Brazilian Portuguese without adding, expanding, enriching, summarising, editorialising, or improving content; use standard physics terminology (drift–diffusion, SRH, transfer-matrix, etc.) while keeping scientific abbreviations (JV, OLED, OFET, EQE, SRH) in Latin characters; convert every localized_url(...,'en') to localized_url(...,'pt') and do not alter other URLs; translate headings, lists, buttons, and duplicated mobile/desktop sections consistently while keeping IDs, styles, emojis, symbols, punctuation, line breaks, and formatting exactly matching the English source; translate “Translations” to “Traduções” and keep get_translations(0) unchanged; do NOT add structured data (JSON-LD), schema, emojis, new sections, new text, new links, new scripts, or metadata that does not already exist in the English source EXCEPT adding 'lang' and the deterministic 'i18n_key' as defined above; output a complete valid HTML file only, with no commentary or explanations. If the English source contains any JSON-LD/schema/script blocks (including application/ld+json), keep them byte-identical (do not translate, do not change URLs, do not add/remove fields), and if the English source does not contain them, do not add them. Put the output in a code block. Databases | OghmaNano User Manual
Início Exemplos Capturas de ecrã Manual do utilizador Logótipo Bluesky YouTube
OghmaNano Simular células solares orgânicas/Perovskita, OFETs e OLEDs DESCARREGAR

Materials database: Part B - How do I get n–k data?

1. Getting n/k data

The quickest route is usually the literature. Search for your material’s optical constants in papers and—ideally—their Supplementary Information (SI), where authors sometimes provide the raw tables. When only figures are available, you can still recover the numbers (see the digitizing tools below).

If you find k(λ) but not α, you can convert using α(λ) = 4π k(λ) / λ (λ in metres gives α in m−1). The OghmaNano Import Data wizard can map columns and handle common unit conversions (e.g., nm → m, μm → m, eV → m via λ = hc/E).

2. Practical search tips

3. Digitizing numbers from figures (when only images are available)

If the paper provides only a plot, use one of these well-supported tools to extract data to CSV:

Once you have tables of λ vs n, λ vs k, or λ vs α, save them as simple two-column text/CSV (wavelength in metres). Import them with the OghmaNano wizard to perform any final unit conversions and validation before use in simulations.

4. Data in nm/n/k formats

OghmaNano normally accepts input data only in SI units and in a single standard format. However, as an exception, OghmaNano can also read files in the format wavelength (nm), n, k ??. These files can be placed in the oghma_local/materials directory with a .nk extension (for example, ito.nk). When present, they will appear in the Materials database ??. It should be noted that this format is intended only for compatibility with external databases that provide optical constants in nanometres, n, and k. Materials stored in this way are limited: additional properties such as electrical parameters or emission spectra cannot be added. This makes .nk files a special-case format, suitable only when no SI-based data are available.

Example of a wavelength/n/k data file format used in OghmaNano, showing columns for wavelength (nm), refractive index (n), and extinction coefficient (k)
Example of a .nk file containing wavelength, refractive index (n), and extinction coefficient (k) data.
OghmaNano Materials database showing a greyed-out .nk file entry, indicating wavelength/n/k data in a non-native format
Example of a .nk file in the Materials database, greyed out to indicate that, while readable, it is not in native OghmaNano format.

👉 Next step: Now continue to Part C for a more detail on how the materials database is organized.