1. Settings & configuration reference
This page lists defaults and explicit overrides. LatticeMind still requires an AI provider configuration and the LatticeMind license described in The LatticeMind license. A solver command, its own license, and its licensed data are required only when that solver executes.
1.1. Where settings come from
LatticeMind reads configuration from several places, in order of precedence (later sources override earlier ones):
Defaults built into LatticeMind.
Config file —
~/.latticemind/config.json(or a file named byLATTICEMIND_CONFIG_FILE).Your saved settings —
~/.latticemind/.env(or the file named byLATTICEMIND_USER_ENV_FILE), written bylatticemind setup,/modeland the browser setup screen.The folder’s
.env— in the folder you start in, or the nearest one in a folder above it.Environment variables.
Choices made in a session, such as
/model,/remoteandlatticemind-webflags.
A conversation keeps the model and execution settings it began with; changing a default affects new conversations.
Tip
When /model or the browser saves a value, it writes to the folder’s own
.env if there is one, otherwise to ~/.latticemind/.env. For servers
and reproducibility, prefer .env or real environment variables.
1.2. AI provider & models
Variable |
Purpose |
|---|---|
|
|
|
The model a research conversation uses with that provider, e.g.
|
|
A different file for your saved settings instead of
|
|
OpenAI API key. |
|
|
|
Only if your account uses org/project scoping. |
|
Anthropic Claude key. |
|
|
|
Google Gemini key. |
|
|
|
Qwen (DashScope) key. |
|
|
|
Local Ollama endpoint (default |
|
|
|
Spending caps on metered providers, in estimated USD (defaults |
1.3. Reports & output location
Variable |
Purpose |
|---|---|
|
Overrides the project folder. By default a conversation works in the
folder you start it in, and |
|
|
|
|
|
|
1.4. Release update notice
Variable or file |
Purpose |
|---|---|
|
|
|
The last check’s result. A successful check is reused for 24 hours; an
unavailable index is retried after one hour. When
|
1.5. Web UI
Variable |
Purpose |
|---|---|
|
Bind host (default |
|
Bind port (default |
|
|
|
Explicit proxy prefix (e.g. |
|
|
|
|
|
|
1.6. Solver commands, license & pseudopotentials
LatticeMind stores one launch command per solver. latticemind setup and the
browser’s Save path write them to ~/.latticemind/.env; environment
variables override them.
Variable |
Purpose |
|---|---|
|
RESCU launch command (default: |
|
NanoDCAL launch command. |
|
Extracted NeutralAtomDatabase root. LatticeMind searches it recursively
for the |
|
VASP launch command (e.g. |
|
Exact LatticeMind license file used at startup. If unset, LatticeMind
expects exactly one |
|
Pseudopotential database folder (containing |
|
VASP POTCAR library directory. |
|
Comma-separated calc types forced to run serially (default covers
|
The classic dashboard (/classic) keeps its own choices in
~/.latticemind/dashboard_settings.json; a research conversation does not
read that file.
1.7. Parallel execution
Control local and remote parallel launches for latticemind quick (also set
from the classic dashboard’s settings), mapped to Slurm resources for remote
jobs. In a conversation, the thread count is set on the browser setup card or
with latticemind research chat --solver-threads.
Variable |
Purpose |
|---|---|
|
|
|
|
|
Custom launcher prefix, e.g. |
|
MPI rank count (also Slurm |
|
OpenMP/BLAS threads per rank (also Slurm |
|
Optional VASP INCAR parallelization overrides. |
1.8. Remote / HPC execution
Remote targets are defined in ~/.latticemind/remote_profiles.toml (see
Step 2 — Describe the target). In a conversation, /remote chooses one. These
variables select and describe the target for latticemind quick:
Variable |
Purpose |
|---|---|
|
|
|
Default remote profile name. |
|
Per-solver remote profile override (e.g.
|
|
|
|
Set |
|
Named runtime/deployment profile. |
|
Advisory deployment context used when planning run scripts and reports. |
|
File of advisory operator instructions (deployment context only). |
1.9. Documentation retrieval
The RESCU documentation is built in and works offline — no configuration required. Optional overrides:
Variable |
Purpose |
|---|---|
|
Read the RESCU docs from a different local folder. |
|
Set to |
|
Your vector store ID ( |
1.10. Structure sourcing
Variable |
Purpose |
|---|---|
|
Enables seeding structures from the Materials Project database. |
1.11. A complete .env example
# --- AI provider ---
RESCU_LLM_PROVIDER=openai
OPENAI_API_KEY=your_key_here
LATTICEMIND_OPENAI_MODEL=gpt-5.6-sol
# --- Optional: a fixed project folder for automation ---
# LATTICEMIND_ARTIFACTS_DIR=/data/latticemind_outputs
Continue in the same .env file with the license and solver paths:
# --- LatticeMind license ---
LATTICEMIND_LICENSE_FILE=/opt/licenses/latticemind.lic
# --- RESCU solver ---
LATTICEMIND_RESCU_CMD=/opt/esapp/rescu
# --- NanoDCAL solver (when selected) ---
LATTICEMIND_NANODCAL_CMD=/opt/nanodcal/bin/nanodcal
LATTICEMIND_NANODCAL_DATA_PATH=/opt/nanodcal/NeutralAtomDatabase
# --- Optional: Materials Project structure sourcing ---
MATERIALS_PROJECT_API_KEY=your_key_here