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. User Manual | OghmaNano - Organic & Hybrid Material Nano Simulation Tool
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

Introduction to Databases in OghmaNano

There are a series of databases used to define material parameters, shapes and solar spectra etc... These are described within this section. From the graphical user interface they can be accessed from the database ribbon, see figure 15.1.

OghmaNano interface showing the Databases ribbon with icons for Materials, Optical, Emission, User data, Shape, Filters, and Backup simulations
The Databases ribbon in OghmaNano, showing quick access to the Materials, Optical, Emission, User data, Shape, Filters, and Backup simulation databases.

There are two copies of these databases, one copy in the install directory of OghmaNano C:\(\backslash\)Program Files\(\backslash\)OghmaNano\(\backslash\) and one in your home directory in a folder called oghma_local. When the model starts for the first time it copies the read only materials database from, to the oghma_local folder in your home directory. If you delete the copy of the materials database in the oghma_local folder it will get copied back next time you start the model, this way you can always revert to the original databases if you damage the copy in oghma_local.

The structure of the databases are simple, they are a series of directories with one directory dedicated to each material or spectra etc.. E.g. there will be one directory called Ag in the optical database which defines silver, and another directory in the spectra database called am1.5g which defines the solar spectrum. Within each directory there is a data.json file which defines basic material properties of the material such as what it is and what icon to use for it. There may be a couple of .bib files that contain reference information for the object in bibtex format. The rest of the key information will be stored in human readable .csv files. These files can be opend in notepad or any text editor. The one exception is that in the shape database some large files are stored in a binary format.