Clean up docs

srosenbu · srosenbu · commit f36961d38bd0 · 2025-07-14T12:21:23.000+02:00
diff --git a/docs/benchmarks/index.md b/docs/benchmarks/index.md
@@ -1,19 +1,3 @@
 # Introduction to the benchmarks
 
-## TODO
-
-* [ ] What format should the benchmark data be stored in? 
-    * Full fields? -> VMAP or scripting interfaces to solvers ([Abaqus scripting](https://classes.engineering.wustl.edu/2009/spring/mase5513/abaqus/docs/v6.5/books/cmd/default.htm?startat=pt02ch04s05.html), [PyAnsys postprocessing](https://post.docs.pyansys.com/version/stable/), [pybaqus](https://github.com/cristobaltapia/pybaqus/tree/master))
-    * Only scalar values from sensors?
-    * Ontology for benchmark results? [NFDI4Ing Metadata Profile service](https://profiles.nfdi4ing.de/#/editor)
-* [ ] How do we deal with quadrature values like stresses?
-    * Mapping to nodes? -> [Discussion on fenics forum](https://fenicsproject.discourse.group/t/comparative-analysis-ansys-vs-fenicsx-displacement-in-linear-elasticity/13398)
-    * Can we export quadrature values and do the mapping ourselves?
-* [ ] What is a good result?
-    * Should we always do mesh-convergence? Cauchy series, if analytical solution is not known?
-* [ ] Which element types? Linear, quadratic? underintegrated? 
-* [ ] What is a sufficient format do describe an algorithm? 
-    * Are algorithm boxes with noting more complicated than a matrix-vector product enough?
-    * Do we always need a reference implementation?
-* [x] Is it _easy_ to link a umat/usermat?
-    * We think so. Both Abaqus and Ansys can link dynamically at runtime. You can also compile a new `ansys.exe`, but it is not required and mainly recommended for shipping the model.   
+**todo**
diff --git a/docs/benchmarks/linear elasticity/mms_elasticity.ipynb b/docs/benchmarks/linear elasticity/mms_elasticity.ipynb
@@ -255,7 +255,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.12.4"
+   "version": "3.13.1"
   },
   "orig_nbformat": 4
  },
diff --git a/docs/benchmarks/linear elasticity/one-element-tests.md b/docs/benchmarks/linear elasticity/one-element-tests.md
diff --git a/docs/benchmarks/linear elasticity/patch-test.md b/docs/benchmarks/linear elasticity/patch-test.md
diff --git a/docs/benchmarks/linear elasticity/plate_with_hole_Kratos.ipynb b/docs/benchmarks/linear elasticity/plate_with_hole_Kratos.ipynb
@@ -1,5 +1,15 @@
 {
  "cells": [
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "\n",
+    "# Postprocessing for Kratos example\n",
+    "\n",
+    "[![Jupyter4NFDI](https://nfdi-jupyter.de/images/jupyter4nfdi_badge.svg)](https://hub.nfdi-jupyter.de/v2/gh/BAMresearch/NFDI4IngModelValidationPlatform/HEAD?labpath=docs%2Fbenchmarks%2Flinear%20elasticity%2Fplate_with_hole_Kratos.ipynb)"
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": 1,
diff --git a/docs/benchmarks/plasticity/mms_plasticity.ipynb b/docs/benchmarks/plasticity/mms_plasticity.ipynb
@@ -202,7 +202,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.12.4"
+   "version": "3.13.1"
   },
   "orig_nbformat": 4
  },
diff --git a/docs/index.md b/docs/index.md
@@ -1,21 +1,3 @@
-# Welcome the NFDI4Ing Model Validation Platform
-
-This platform aims to validate implementations of mechanical constitutive models.
-
-## Current goals (Wonderpill)
-
-1. Create a generalized interface design for user-defined material model (e.g. UMATs in Abaqus) such that
-    1. you can easily convert a constitutive model from any commercial or non-commercial FEM solver to this interface such that interoperability between solvers is possible,
-    2. the implemented models can be any small-strain, large-deformation model.
-2. Establish a comprehensive set of numerical benchmarks for:
-    1. Linear elasticity
-        * Critical factors include element order, mapping stresses to nodes, combined rotation and stretch
-    2. Mises plasticity with linear isotropinc hardening
-        * Critical factors include loading, unloading, reloading
-    3. Dynamic test case for linear elasticity (some form of wave propagation)
-3. Parts of the platform
-    1. A website for the visualization of benchmark results in the form of interactive jupyter notebooks
-    2. GitHub repository with the validation workflows
-    3. Excecution platform for the workflows (optional goal because of licensing issues)
-    4. Database platform for benchmark results
+# Welcome the NFDI4Ing Model Validation/Verification Platform
 
+**todo**
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -34,12 +34,12 @@ markdown_extensions:
 
 nav:
   - index.md
-  - conventions.md
-  - data.md
-  - interface.md
+  #- conventions.md
+  #- data.md
+  #- interface.md
   - Benchmarks:
      - Introduction: "benchmarks/index.md"
      - Linear Elasticity: "benchmarks/linear elasticity"
-     - Plasticity: benchmarks/plasticity
+     #- Plasticity: benchmarks/plasticity
   - "zz_bibliography.md"
 
