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. Backing Up Simulations | OghmaNano User Manual

Início Exemplos Capturas de ecrã Manual do utilizador

OghmaNano Simular células solares orgânicas/Perovskita, OFETs e OLEDs DESCARREGAR

Backups of simulations

When running a simulation, it is often useful to make a copy before changing parameters. To do this, click the Backup simulation button in the Database ribbon (see ??). This opens the backup window (??). Clicking the New backup icon in the top-right corner creates a copy of your current simulation, and an icon representing that backup will appear in the window. To restore a backup, simply double-click its icon. Note that backups are stored only in your local simulation directory, so they act as convenient checkpoints rather than long-term storage. If your simulation is important, make sure you also keep external copies.

OghmaNano Databases ribbon with the Backup Simulation button highlighted. — The Databases ribbon in OghmaNano, with the Backup Simulation button highlighted.

OghmaNano window showing how to back up an OghmaNano simulation midway through the simulation procedure. — Backing up an OghmaNano simulation midway through the simulation procedure.

Web Analytics