ARCTIC SYSTEMSTECHNICAL DOCUMENTATION / SCOPE
Available physics.
Explicit boundaries.
Implemented numerical features, local interface features and future public access are separate release decisions.
On small screens, scroll the table sideways to compare all columns.
| Capability | Numerical implementation | Local interface / public access |
|---|---|---|
| 1D / 2D / 3D conduction | Implemented and tested on selected synthetic tasks. | Simple domains supported locally. Public compute pilot planned. |
| Freezing and thawing | Enthalpy balance with a smooth synthetic equilibrium phase law. | Phase parameters available locally; no calibrated soil database. |
| Temperature, flux, Robin BC | Implemented; analytical / manufactured tests. | Six independent constant face conditions for the 3D box. |
| Layered materials | Cell material IDs and ideal-contact interface fluxes. | Horizontal layers aligned to cell faces. No arbitrary stratigraphic CAD. |
| Uniform Cartesian grid | 1D/2D/3D; cell masks in applicable native paths. | Simple sections and 3D boxes, with XZ / YZ / XY result slices. |
| Static nonuniform grid | Experimental 1D/2D rectilinear API; separate verification. | Not yet integrated into the workbench or portable pilot release. |
| Thin-pipe exchange | Separate experimental constant-property, non-phase model. Early transient and phase behaviour remain unqualified. | Excluded from this first public module. No cooling-circuit or heat-pump simulation. |
| Adaptive / unstructured mesh | Not implemented. | No automatic mesh accuracy guarantee or arbitrary CAD meshing. |
| Water flow / mechanics | Not implemented. | No groundwater advection, water migration, frost heave or stress analysis. |
What completion means
A completed run solves its discrete problem within the chosen tolerances. It does not by itself establish mesh independence, physical validity or engineering suitability. Check the quantity you will use: temperature, flux, integrated heat or phase extent.
Conservation, nonlinear convergence, discretization accuracy and agreement with measurements are distinct checks. The public examples here establish numerical evidence only.
Opening the solver to visitors
The local interface already bounds runs at 6,400 cells, an estimated work budget and 90 seconds. Those local guards are not a multi-user service.
A public pilot needs a shared queue, per-user and total quotas, memory/time/storage caps, isolated workers and recovery. Hosting tests must set the actual public limits. No public calculation endpoint is enabled by this documentation.