PyPI - pyoomph - Versions diffs - 0.2.0__tar.gz → 0.2.1__tar.gz - Mend

pyoomph 0.2.0tar.gz → 0.2.1tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1126) hide show

{pyoomph-0.2.0 → pyoomph-0.2.1}/.github/workflows/wheels.yml RENAMED Viewed

@@ -19,6 +19,15 @@ on:
         type: choice
         default: auto
         options: [auto, force, skip]
+      upload_from_run_id:
+        description: >-
+          Publish the wheels and sdist that an EARLIER run of this workflow already built, instead of
+          building anything: give that run's id. Nothing is compiled, no prerequisite is checked, and
+          the artifacts are taken as they are. For the case where the build was green and only the
+          upload did not happen - artifacts live 90 days, so the run has to be recent enough.
+        required: false
+        type: string
+        default: ""
   workflow_run:
     workflows:
       - Prebuild static CLN/GiNaC
@@ -85,8 +94,12 @@ jobs:
   prereqs:
     name: Check release prerequisites
     # Nothing here needs to run for the prebuild-completed trigger; the wheel jobs keep their own
-    # copy of that condition.
-    if: github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success'
+    # copy of that condition. Nor for an upload-only dispatch, which certifies nothing and builds
+    # nothing - the run it takes its artifacts from is what was gated.
+    if: >-
+      ${{ inputs.upload_from_run_id == ''
+          && (github.event_name != 'workflow_run'
+              || github.event.workflow_run.conclusion == 'success') }}
     runs-on: ubuntu-latest
     permissions:
       contents: read
@@ -243,6 +256,7 @@ jobs:
     if: >-
       ${{ !cancelled()
           && !contains(needs.*.result, 'failure')
+          && inputs.upload_from_run_id == ''
           && (github.event_name != 'workflow_run'
               || github.event.workflow_run.conclusion == 'success') }}
     name: ${{ matrix.label }}
@@ -654,6 +668,7 @@ jobs:
     if: >-
       ${{ !cancelled()
           && !contains(needs.*.result, 'failure')
+          && inputs.upload_from_run_id == ''
           && (github.event_name != 'workflow_run'
               || github.event.workflow_run.conclusion == 'success') }}
     name: sdist
@@ -698,23 +713,60 @@ jobs:
   upload_pypi:
     name: Upload to PyPI
     needs: [build_wheels, build_sdist]
-    if: github.event_name == 'release' && github.event.action == 'published'
+    # Two ways in, and !cancelled() rather than success() because the second one SKIPS both build
+    # jobs deliberately:
+    #
+    #   * a release, which is the normal path;
+    #   * a manual dispatch naming an earlier run of this workflow in upload_from_run_id, for the
+    #     case where that run built and tested everything and only the upload did not happen. This
+    #     stays in wheels.yml rather than becoming a workflow of its own on purpose: PyPI's trusted
+    #     publisher is bound to a workflow FILENAME, so a second file would be rejected until it was
+    #     registered on PyPI as well.
+    #
+    # The release half deliberately does NOT also test github.event.action == 'published'. That term
+    # was here, it was redundant - `on.release.types` below is [published], so a release-triggered
+    # run IS a publish and nothing else can reach this job - and on the 0.2.0 release it evaluated
+    # false anyway. Every wheel and the sdist built and passed, and the upload was then skipped;
+    # re-running the job alone against the same payload skipped it again, so the payload did not
+    # carry the action the term asked for. Why is unexplained: a probe workflow confirms that both a
+    # fresh non-draft create and the publishing of a draft emit `published` (alongside `released`
+    # and, for a create, `created`), and no GitHub changelog entry describes a payload whose action
+    # differs from the type that matched it. Rather than keep a redundant check that is capable of
+    # withholding a release, the types filter is left to do the one job it already does.
+    if: >-
+      ${{ !cancelled()
+          && !contains(needs.*.result, 'failure')
+          && (github.event_name == 'release'
+              || (github.event_name == 'workflow_dispatch'
+                  && inputs.upload_from_run_id != '')) }}
     runs-on: ubuntu-latest
     environment: release
     permissions:
       id-token: write  # mandatory for trusted publishing
+      # Reading another run's artifacts, for the upload_from_run_id path.
+      actions: read
     steps:
+      # run-id defaults to this run, so the release path is unchanged; with upload_from_run_id set
+      # the artifacts come from that run instead. github-token is required whenever run-id is given,
+      # even for a run in the same repository.
       - uses: actions/download-artifact@v4
         with:
           pattern: wheels-*
           path: dist
           merge-multiple: true
+          run-id: ${{ inputs.upload_from_run_id || github.run_id }}
+          github-token: ${{ github.token }}
       - uses: actions/download-artifact@v4
         with:
           name: sdist
           path: dist
+          run-id: ${{ inputs.upload_from_run_id || github.run_id }}
+          github-token: ${{ github.token }}
+      - name: Show what is about to be uploaded
+        run: ls -la dist
       - uses: pypa/gh-action-pypi-publish@release/v1

{pyoomph-0.2.0 → pyoomph-0.2.1}/CHANGELOG.md RENAMED Viewed

@@ -1,5 +1,15 @@
 # Changelog
+## [0.2.1]
+Released as urgent patch of 0.2.0.
+### Fixed
+- **A two-sided interface could exhaust the machine's memory during the first assembly.** The pruned sparsity pattern (`prune_structural_zeros_by_field_coupling`, on by
+  default since 0.2.0) let the two sides of a coupled interface ask each other for an answer each was
+  still computing, which recursed without bound.
 ## [0.2.0] - 2026-08-30
 About six weeks and 940+ commits since 0.1.9. Four themes: h-adaptivity generalised from quads and

{pyoomph-0.2.0 → pyoomph-0.2.1}/INSTALL.md RENAMED Viewed

@@ -16,46 +16,7 @@ Verify whether everything runs fine by
 > python -m pyoomph check all
-If you encounter segmentation faults during solving, please try to downgrade your MKL package, e.g. via *python -m pip install mkl==2024.1.0*.
-### PETSc/SLEPc via WSL
-PETSc/SLEPc (used for a much more stable eigensolver, see the [tutorial](https://pyoomph.readthedocs.io/)) cannot be built natively on Windows. If you need it, install pyoomph inside the [Windows Subsystem for Linux (WSL)](https://learn.microsoft.com/windows/wsl/) instead, where it can be built exactly as on native Linux.
-From an elevated PowerShell:
-```powershell
-wsl --install -d Ubuntu
-```
-Reboot if prompted, open the "Ubuntu" app, then inside it install pyoomph as on Linux (see below), keeping the source trees on the Linux filesystem (e.g. `~/...`, not `/mnt/c/...`):
-```bash
-sudo apt update
-sudo apt install gcc libopenmpi-dev flex bison
-python3 -m pip install --upgrade pyoomph
-```
-Then build PETSc/SLEPc as on Linux:
-```bash
-cd A_FOLDER_OF_YOUR_CHOICE
-git clone -b release https://gitlab.com/petsc/petsc.git petsc
-cd petsc
-export PETSC_DIR=$(pwd)
-export PETSC_ARCH=pyoomph_petsc_arch
-./configure --with-mpi --with-petsc4py --download-mumps=yes --download-hypre=yes --download-parmetis=yes --download-ptscotch=yes --download-slepc=yes --download-superlu=yes --download-superlu_dist=yes --download-suitesparse=yes --download-metis=yes --download-scalapack --with-scalar-type=complex
-```
-`configure` prints the exact `make` command to run next. Afterwards, add to `~/.bashrc`:
-```bash
-export PETSC_DIR=A_FOLDER_OF_YOUR_CHOICE/petsc
-export PETSC_ARCH=pyoomph_petsc_arch
-export PYTHONPATH=$PYTHONPATH:$PETSC_DIR/$PETSC_ARCH/lib
-```
-If `make` is killed for running out of memory, raise the memory available to WSL2 via `C:\Users\<you>\.wslconfig` (`[wsl2]` section, `memory=8GB`), then `wsl --shutdown` and reopen. If you use VS Code, install the "WSL" remote extension and open the project from within WSL so the editor picks up the environment variables above. Full details, including how to select the SLEPc/MUMPS eigensolver, are in the [tutorial](https://pyoomph.readthedocs.io/en/latest/tutorial/installation/wsl.html).
+If you encounter segmentation faults during solving, please try to upgrade or downgrade your MKL package, e.g. via *python -m pip install mkl==2024.1.0*.
 ## On Linux
@@ -67,11 +28,14 @@ If you encounter segmentation faults during solving, please try to downgrade you
 ## On Mac
-The fast `MKL Pardiso` solver from `mkl` is not available on `arm64` Macs. If you want to use it, install pyoomph in a `Rosetta 2 terminal`, see [here](https://www.courier.com/blog/tips-and-tricks-to-setup-your-apple-m1-for-development/) how to set it up (**note**: recent systems must be handled differently, see [here](https://developer.apple.com/forums/thread/718666)).
+The fast `MKL Pardiso` solver from `mkl` is not available on `arm64` Macs. Since the default solver on `arm64` Macs (`Accelerate`) is unable to tackle larger problems at reasonable times, you definitely either want to use `MKL Pardiso` with a workaround or use `MUMPS` via `PETSc`.
+To use `MKL Pardiso`, install pyoomph in a `Rosetta 2 terminal`, see [here](https://www.courier.com/blog/tips-and-tricks-to-setup-your-apple-m1-for-development/) how to set it up (**note**: recent systems must be handled differently, see [here](https://developer.apple.com/forums/thread/718666)).
 Also, please downgrade `mkl` by
 > python3 -m pip install mkl==2021.4.0
+The alternative, solving with `PETSc/MUMPS`, runs natively on `arm64`, but requires the installation of `PETSc/MUMPS`. See [here](https://pyoomph.readthedocs.io/en/latest/tutorial/installation/petscslepc.html) for details.
 Make sure to have the `Xcode` developer tools, e.g. by installing them via
 > xcode-select --install
@@ -80,8 +44,6 @@ and test pyoomph via
 > python -m pyoomph check all
-Alternatively, if you do not want to use the `Rosetta 2 terminal` detour, you can also install it directly on arm64 systems. This will use the `Accelerate Framework` as default solver.
 ## Compilation from source (including MPI)

{pyoomph-0.2.0 → pyoomph-0.2.1}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pyoomph
-Version: 0.2.0
+Version: 0.2.1
 Summary: pyoomph - a multi-physics finite element framework based on oomph-lib and GiNaC
 Author-Email: Christian Diddens <c.diddens@utwente.nl>, Duarte Rocha <d.rocha@utwente.nl>, Maxim de Wildt <m.dewildt@utwente.nl>
 License: GNU GENERAL PUBLIC LICENSE Version 3

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/_static/css/custom.css RENAMED Viewed

@@ -8,12 +8,13 @@
 .downloadbutton {
   margin: auto;
-  margin-bottom: 20px;
-  width: 50%;
+  margin-bottom: 20px;
+  width: fit-content;
+  max-width: 100%;
   border: 2px solid rgb(165, 149, 224);
   background-color: rgb(225, 221, 235);
   text-align: center;
-  padding: 5px;
+  padding: 5px 20px;
   border-radius: 7px;
 }

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/conf.py RENAMED Viewed

@@ -111,6 +111,14 @@ autodoc_inherit_docstrings=False
 # name pyoomph.equations.navier_stokes pulls in from pyoomph.expressions. Keep the previous behaviour.
 autodoc_default_options = {"ignore-module-all": True}
+# preCICE is a heavy installation and is deliberately not a documentation requirement, so
+# pyoomph/solvers/precice_adapter.py's top-level "import precice" fails when the docs are built
+# (on Read the Docs, for instance) and its API page would come out empty. Mocking it keeps the
+# adapter documented. Note that the import would otherwise still succeed by accident:
+# build_tutorial_zip() below puts source/tutorial on sys.path, and the tutorial chapter directory
+# source/tutorial/precice is then picked up as an (empty) namespace package.
+autodoc_mock_imports = ["precice"]
 # sphinx_autodoc_typehints resolves "if TYPE_CHECKING:" blocks by actually executing them, to
 # make forward-referenced types resolvable. pyoomph/meshes/mesh.py deliberately has TYPE_CHECKING-
 # only classes (_MeshFromTemplate1dTypingBase, _InterfaceMeshTypingBase, ...) that combine a

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/azimuthal/rbconvect.rst RENAMED Viewed

@@ -82,6 +82,8 @@ Finally, we trace out the critical curve :math:`\operatorname{Ra}_\text{c}(\Gamm
 	.. container:: downloadbutton
-		:download:`Download this example <rayleigh_benard_azimuthal_stability.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/rayleigh_benard_azimuthal_stability.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/azimuthal/rising_bubble.rst RENAMED Viewed

@@ -82,7 +82,9 @@ We can also generate a movie of the instability. Please refer to :numref:`secplo
 	.. container:: downloadbutton
-		:download:`Download this example <rising_bubble.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/rising_bubble.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/bifgui/example.rst RENAMED Viewed

@@ -101,7 +101,9 @@ The orbit handler is installed afterwards, i.e. the problem solves for the entir
 	.. container:: downloadbutton
-		:download:`Download this example <thin_film_bifurcation_gui.py>`
+		Full code available in the
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/thin_film_bifurcation_gui.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/cartesiannormal/rivulet.rst RENAMED Viewed

@@ -72,6 +72,8 @@ Here :py:class:`~pyoomph.meshes.meshdatacache.MeshDataCombineWithEigenfunction`
 	.. container:: downloadbutton
-		:download:`Download this example <rivulet.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/rivulet.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/cartesiannormal/turingdispersion.rst RENAMED Viewed

@@ -53,6 +53,8 @@ In particular, we can quickly get a good guess for the dominant wavenumber, here
 	.. container:: downloadbutton
-		:download:`Download this example <turing_dispersion.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/turing_dispersion.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/eigenconti.rst RENAMED Viewed

@@ -40,9 +40,11 @@ Once set up, we can use this problem and solve for the stationary state at the m
 	.. container:: downloadbutton
-		:download:`Download this example <eigenbranch_continuation.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/eigenbranch_continuation.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/movmesh/dropdetach.rst RENAMED Viewed

@@ -76,6 +76,8 @@ Of course, the choice to nondimensionalize the system by the contact line radius
 	.. container:: downloadbutton
-		:download:`Download this example <hanging_droplet.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/hanging_droplet.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/response/dampedho.rst RENAMED Viewed

@@ -55,7 +55,9 @@ Before the problem is initialized, we must create a :py:class:`~pyoomph.utils.pe
 	.. container:: downloadbutton
-		:download:`Download this example <linear_response_oscillator.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/linear_response_oscillator.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/advstab/response/drums.rst RENAMED Viewed

@@ -46,6 +46,8 @@ To obtain the full response data, we can access the eigenvector of the problem.
 	.. container:: downloadbutton
-		:download:`Download this example <linear_response_drum.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Advanced_Linear_Dynamics/linear_response_drum.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/aledt.rst RENAMED Viewed

@@ -80,7 +80,9 @@ The field :math:`c` is now not following the oscillatory motion of the mesh, but
 	.. container:: downloadbutton
-		:download:`Download this example <ALE_correction.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/ALE_correction.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/beadsonstring.rst RENAMED Viewed

@@ -92,6 +92,8 @@ The finer mesh is not optional -- the reference notes the same requirement -- an
 	.. container:: downloadbutton
-		:download:`Download this example <beads_on_string.py>`
+		Full code available in the
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/beads_on_string.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/freesurf.rst RENAMED Viewed

@@ -126,7 +126,9 @@ As opposed to the lubrication example in :numref:`eqpdelubric_relax`, we use a :
 	.. container:: downloadbutton
-		:download:`Download this example <free_surface.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/free_surface.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/gmshfields.rst RENAMED Viewed

@@ -90,7 +90,9 @@ The results in figure :numref:`figrayleighplateauinstab` show how the remeshing
 	.. container:: downloadbutton
-		:download:`Download this example <rayleigh_plateau.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/rayleigh_plateau.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/laplsmooth.rst RENAMED Viewed

@@ -46,7 +46,9 @@ Finally, the :py:class:`~pyoomph.equations.generic.SpatialErrorEstimator` will r
 	.. container:: downloadbutton
-		:download:`Download this example <laplace_smoothed_mesh.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/laplace_smoothed_mesh.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/pinchoff.rst RENAMED Viewed

@@ -117,6 +117,8 @@ i.e. the break-up costs about what remeshing the same mesh costs anyway, and bot
 	.. container:: downloadbutton
-		:download:`Download this example <rayleigh_plateau_pinchoff.py>`
+		Full code available in the
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/rayleigh_plateau_pinchoff.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/remesh.rst RENAMED Viewed

@@ -58,7 +58,9 @@ One additional option is to add an instance of the class :py:class:`~pyoomph.equ
 	.. container:: downloadbutton
-		:download:`Download this example <remeshing.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Moving_Mesh/remeshing.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/solid/cantilever.rst RENAMED Viewed

@@ -49,7 +49,9 @@ Finally, we can just run the problem by gradually increasing the pressure load,
 	.. container:: downloadbutton
-		:download:`Download this example <cantilever.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/cantilever.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/solid/compressed_disc.rst RENAMED Viewed

@@ -45,7 +45,9 @@ In the driver code, we just iterate over the imposed pressure (starting with a n
 	.. container:: downloadbutton
-		:download:`Download this example <compressed_disc.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/compressed_disc.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/solid/solid_oscillations.rst RENAMED Viewed

@@ -30,7 +30,9 @@ For the torsion, we use the original undeformed beam by accessing the Lagrangian
 	.. container:: downloadbutton
-		:download:`Download this example <solid_oscillations.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/solid_oscillations.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/spread/free.rst RENAMED Viewed

@@ -39,7 +39,9 @@ Important differences are the mesh, which is now the north-east (``"NE"``) quart
 	.. container:: downloadbutton
-		:download:`Download this example <droplet_spread_free_slip.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/droplet_spread_free_slip.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/spread/hyperelastic.rst RENAMED Viewed

@@ -42,8 +42,10 @@ The issue without shifting the tangent node positions is shown in the left part
 	.. container:: downloadbutton
-		:download:`Download this example <droplet_spread_hyperelastic_tangential_shift.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/droplet_spread_hyperelastic_tangential_shift.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/spread/maraandgrav.rst RENAMED Viewed

@@ -84,9 +84,11 @@ The method :py:meth:`~pyoomph.generic.problem.Problem.go_to_param` will graduall
 	.. container:: downloadbutton
-		:download:`Download this example <droplet_spread_marangoni_and_gravity.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/droplet_spread_marangoni_and_gravity.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/spread/navier.rst RENAMED Viewed

@@ -37,7 +37,9 @@ A comparison of results without and with slip length can be seen on the right si
 	.. container:: downloadbutton
-		:download:`Download this example <droplet_spread_sliplength.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/droplet_spread_sliplength.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/ale/spread/threedim.rst RENAMED Viewed

@@ -43,7 +43,9 @@ Since we are mostly interested in the final state of the droplet, we have not co
 	.. container:: downloadbutton
-		:download:`Download this example <droplet_spread_3d.py>`
-		:download:`Download all examples <../../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../../tutorial_example_scripts.zip>`
+		``Moving_Mesh/droplet_spread_3d.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/dg/advdiffu.rst RENAMED Viewed

@@ -141,9 +141,11 @@ The discontinuous output is plotted in :numref:`figdgconvdiffu`.
 	.. container:: downloadbutton
-		:download:`Download this example <convection_diffusion.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Discontinuous_Galerkin/convection_diffusion.py``
 .. note::

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/dg/facetfields.rst RENAMED Viewed

@@ -146,6 +146,8 @@ An unknown on the facets also changes what the *bulk* unknowns are coupled to. W
 	.. container:: downloadbutton
-		:download:`Download this example <hybrid_poisson.py>`
+		Full code available in the
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Discontinuous_Galerkin/hybrid_poisson.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/dg/hdg.rst RENAMED Viewed

@@ -106,6 +106,8 @@ The elimination is exact, so the accuracy is that of the unreduced scheme. Refin
 	.. container:: downloadbutton
-		:download:`Download this example <hdg_poisson.py>`
+		Full code available in the
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Discontinuous_Galerkin/hdg_poisson.py``

{pyoomph-0.2.0 → pyoomph-0.2.1}/docs/source/tutorial/dg/weakdirichlet.rst RENAMED Viewed

@@ -42,9 +42,11 @@ By default, :py:class:`~pyoomph.equations.generic.DirichletBC` will impose the c
 	.. container:: downloadbutton
-		:download:`Download this example <poisson_weak_dirichlet.py>`
-		:download:`Download all examples <../tutorial_example_scripts.zip>`
+		Full code available in the
+		:download:`pyoomph example bundle <../tutorial_example_scripts.zip>`
+		``Discontinuous_Galerkin/poisson_weak_dirichlet.py``
 Finally, we want to address that the discontinuous Galerkin implementation can easily be switched to a *finite volume method*. In such methods, quantities are usually element-wise constant, i.e. approximated on the space ``"D0"``. If setting ``space="D0"``, all terms involving ``grad(u)`` and ``grad(v)`` will vanish, since the gradients are zero in the element-wise constant space. The weak formulation will hence only read

pyoomph 0.2.0__tar.gz → 0.2.1__tar.gz

pyoomph 0.2.0tar.gz → 0.2.1tar.gz