Comments (7)
The mesh size affects the strain rate, and because plasticity (and maybe dislocation creep) is considered in your model, the result is expected to depend on the resolution. However, I doubt that mesh resolution alone can cause such a significant difference in the model’s evolution. Maybe the initial weak seed or other physical parameters depend on the mesh resolution in your model? Also, is the dimensional time the same between these two models?
from underworld2.
Hi @tingyang2004 , thanks for the reply.
Ok, that makes sense but the difference remains substantial.
The initial weak seed is a velocity discontinuity located in the bottom center of the model. Yes, the dimensional time is the same in both models.
from underworld2.
Are you saying that the horizontal velocity of the base boundary is imposed as a Dirichlet boundary condition, and that the imposed velocity is discontinuous at the horizontal center? In this case, the physical model of the weak seed setup does not depend on resolution, but maybe the inhomogeneity introduced by your initial weak seed may have effects lower than or comparable to that of the random error (e.g., introduced by the swarm whose initial position is usually randomly assigned). In this case, rerun the model at the same resolution may also make a noticeable difference.
from underworld2.
@jlikermanUPC it would be good to see the high res. "regular" results, ie, 1024 x 256, 2048x512, ....
Perhaps the model was initially underesolved in the vertical direction with 128.
Also solver tolerances could impact the results of fine (and finer) shear banding.
Maybe decrease (tighten) the tolerances for high resolution if you still observe different outcomes at difference resolutions.
from underworld2.
@tingyang2004, indeed, the issue we are facing does not seem to originate from the generation of the weakness seed itself, but rather from the overall result of the model. In fact, failure occurs consistently in the seed's location in all runs. On the other hand, we have run several models keeping the resolution (either the same or varying it minimally) and there are not substantial changes.
Thanks @julesghub, we will carry out the suggested tests. Currently, we are running mumps solver with a tolerance of 1e-2. Would you recommend reducing it to 1e-3?
from underworld2.
I agree with @tingyang2004 initial comment and @julesghub comment on the model being under resolved in the vertical direction.
To me, this looks similar to the 'wide' and 'narrow' rift phenomenon, which is dictated by the viscosity at the base of the crust. As your resolution increases it looks like the viscosity at the base of the crust appears to decrease. This is probably due to the higher resolution capturing the change from strong plastic crust to weak viscous crust below the brittle-ductile transition. The weaker the lower crust the more spread out (or wider) the deformation becomes. This may be why you see it after a certain resolution, I assume the models before this critical resolution look like fig 1 and all modes after look like fig 2.
from underworld2.
Thanks to all, we conducted the test and found the best mesh resolution.
from underworld2.
Related Issues (20)
- RuntimeError: There were left over keyword arguments. kwargs = [{'_fn_fssa': None}]
- communication between the UW2 model and the Badlands surface processes model
- UWGeodynamics velocitySurface_2D Bug HOT 1
- Coupled Evolution of Deformation, Pore Fluid Pressure, and Fluid Flow in the thrust-fold mountain belt ? HOT 4
- Uncoupled temperature and compositional field in UW Geodynamics HOT 2
- Adding two plasticities to one material HOT 3
- SystemError: <built-in function SystemLinearEquations_UpdateSolutionOntoNodes> returned a result with an exception set HOT 1
- Parallel computing and An installation problem (MpiRun) HOT 4
- 'surface' integration HOT 2
- Model.mesh.deform_mesh() error with mpirun. Possibly two nodes are in an identical location.
- Installation error HOT 11
- Compressible mantle convection with tala approximation HOT 1
- A question about strata results from coupled model HOT 3
- May I ask how is the second-order invariant of strain rate(function: fn.tensor.second_invariant)in underworld2.13 calculated?
- Question about using mesh.specialSets['MinI_VertexSet'] as a boundary index with parallel run
- Converging issue for 3D subduction model with oblique trench shape. HOT 1
- May I ask how to use Underworld2 modeling the melt-related process?
- An issue when using trapezoid mesh HOT 1
- issue with surface processes
- To find the example to generate collision_wedge.gif HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from underworld2.