Lachlan Grose

**Describe the bug** Interface constraints are implemented incorrectly and produce weird solutions. The interface constraint should try to minimise the difference in the interpolated scalar field value for all pairs...

**Describe the bug** Progress bar only gets updated when the fault frame is built, not per coordinate.

[BUG] if a data point is outside of the model support no warning is shown

2

Adding data that falls outside of the interpolation support can result in unexpected geometries (the data isn't used for interpolation). This should either warn or automatically resize the interpolation support.

**Describe the bug** When using the rescale flag for building the model, the faults seem to be cropped. Only an issue since the support is resized on the fly. The...

**Describe the bug** If unconformities are added into the model the time taken to evaluate the model increases by about double. Map2loop example 130 seconds without unconformities 260 seconds with...

another request from @markdlindsay and @markjessell **Is your feature request related to a problem? Please describe.** Calculate isopach map from a geological model

Request from @markdlindsay and @markjessell **Is your feature request related to a problem? Please describe.** Calculate the depth to the top of a unit - May need to improve how...

**Describe the bug** Using PLI if you try and evaluate the mesh outside of the model area it has an indexing problem. Seems to occur when modelling faults. packages/LoopStructural/interpolators/structured_tetra.py", line...

**Is your feature request related to a problem? Please describe.** Add in a digital elevation model to the model area either: 1. interpolate a scalar field where underground < 0...

**Describe the bug** When using process_map2loop the scalar values assigned to the series are in assending order. This means that the unconformity is added to the top of the youngest...