Comments (9)
See also the section in the manual that addresses this specific point.
from aspect.
Yes I vote for it. Actually I was involved in changing our earlier formulation (static pressure, but if I remember correctly it contained a bug) into the current form, but I agree that we should provide both possibilies. Maybe an input file parameter 'Use full pressure for adiabatic heating' could act as a switch. I would be fine in setting the default to static pressure as well, since this is what most people expect anyway.
from aspect.
Ok now we ran into the case in which we actually want to change the shear heating formulation as well (due to some complicated physics involving different deformation mechanism that contribute to viscosity). Therefore, we would like to use a different viscosity for the shear heating than for the stokes system. Currently, the only way would be to change the assembly. Maybe we can think about a formalism to allow for more flexible heating mechanisms at the hackathon?
from aspect.
It seems thermodynamically inconsistent to use different viscosities. Can you elaborate what these models attempt to achieve?
from aspect.
Well, I can try. The current implementation assumes that all of the deformation work that is done is converted to thermal energy in the form of shear heating. In the model we try to set up a part of this work is actually used to decrease the grain size (increasing the surface energy of the system). So what we actually want to do is multiply the shear heating by (1-surface_area_work_fraction), which changes in dependence of the solution. We can calculate this factor in the material model, but we need a way to use it for the shear heating (e.g. By modifying the current formulation or by providing a way to select a different heating term).
from aspect.
Hm, if I understand correctly then what is really happening here is that you convert mechanical energy (shear friction) into not just heat but in fact heat + chemical energy (in the form of crystal breakage)? If so, can't you just model this by first converting everything into heat, but then have another heat sink term coming from your material model that is proportional to the amount of energy that is converted into chemical energy? That would seem like a cleaner way to do it, given that we already have the ability to treat such terms (I believe).
from aspect.
Yes, you are correct, we want to convert a fraction of the mechanical energy into not just heat, but a different kind of energy (grain boundary energy - energy is minimised when the surface area of the grains is small, i.e. when there is one big crystal instead of several smaller ones).
A heat sink would be a way to implement this, but the way the heating model is implemented right now, it is not in the material model, but in a different plugin, and it does not even get the material model inputs and outputs. But it would be a great idea to either have the option to have such an additional heating term in the material model, or put all of the heating terms out of the assembly and into a separate heating model, which would then get the material model inputs and outputs.
from aspect.
Would what you want to do be possible now with your implementation in #416?
from aspect.
Yes. Closed by #416.
from aspect.
Related Issues (20)
- DOC: Move plugin info
- FIX or DOC: Consistent user-facing stress convention
- Bug : Strain Rheology in ASPECT 2.5 and deal.II 9.5.0 HOT 1
- ASPECT 3: Run full cookbooks for all complicated models
- Remove items from declare_parameters in diffusion_dislocation material model
- Read in functions only for fields that represent chemical compositions
- Compute a better alpha factor in the implementation of the SPD-ness of the Newton method. HOT 6
- Build deal.ii 9.5.1 with gcc 13.2.0, an error while building trillinos 13.2.0 HOT 6
- ASPECT 3: Update some of our default values HOT 1
- compiling and running ASPECT on TACC Stampede3 HOT 17
- Improve matrix-free performance marginally. HOT 1
- Make the Newton method compatible with the GMG solver HOT 1
- ASPECT cannot compile without WorldBuilder HOT 3
- Particles with free surface hang HOT 9
- Restart with free surface and latest deal.II is failing HOT 8
- Add support for different coordinate systems to more function plugins
- Particle deregistration error on ASPECT v2.6.0-pre with deal.II v9.5.1 HOT 3
- [CI] Jenkins tester is timing out / OOM / slow HOT 1
- CMake: consider removing `deal_ii_setup_target()` and using import targets directly (deal.II version 9.5 or later)
- velocity along the wall HOT 1
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 aspect.