Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm

## [Unreleased]
### Added
- Added an option to read initial textures on grains from a ASCII file with has the format of a particle_cpo CPO.dat output from ASPECT. \[Yijun Wang; 2026-03-29; [#918](https://github.com/GeodynamicWorldBuilder/WorldBuilder/pull/918)\]

- Added Perlin noise models for composition and temperature across features, and gwb-dat coverage tests for Cartesian Perlin noise inputs. \[Tilman May; 2026-03-29; [#906](https://github.com/GeodynamicWorldBuilder/WorldBuilder/pull/906)\]

Expand Down
2 changes: 1 addition & 1 deletion doc/JOSS/1.0/paper.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ These principles are implemented in an object-oriented C++ code with interfaces

The GWB's world parameterization principles are built around the idea that a complex model region can be split into individual tectonic features. These tectonic features can be parameterized by defining their location and geometry in terms of points, lines, or areas in a map view. For example, a continental plate can be represented as an area on a map, and the GWB user defines this area. A fault is a linear feature on a map, so the user can define the fault trace as a line at the surface. Users can also provide additional information for a feature, such as a spatially variable thickness or dip angle. The GWB then uses these parameters to create the 3D geometry of the feature, defining its volume. Furthermore, users can attach one or many models to those volumes to define additional properties such as thermal or chemical structure. These can be very simple models, such as a uniform temperature distribution; or follow a more complex distribution, such as a half space cooling model, or a McKenzie model [@McKenzie_1970], or a mass conserving slab temperature model [@Billen_Fraters_AGU_2023].

All these tectonic features are bundled in a single input file in standard JSON format, which is human readable, writeable, and editable. The main idea behind this design of the GWB is that users can easily create, modify, and visualize complex parameterized geodynamic or tectonic settings.
All these tectonic features are bundled in a single input file in standard JSON format, which is human readable, writable, and editable. The main idea behind this design of the GWB is that users can easily create, modify, and visualize complex parameterized geodynamic or tectonic settings.

## Example
Below we show an example input file for a Cartesian model that contains a single feature, namely a subducting plate.
Expand Down
974 changes: 913 additions & 61 deletions doc/world_builder_declarations.schema.json

Large diffs are not rendered by default.

Loading
Loading