Elmer Discussion Forum

Hi, unfortunately, I am not able to reproduce your error. Could you try to go into the subdirectory of this test and run it manually and send the output. To that end, you have to declare the following variables (provided you are running bash) export ELMER_GRID="ElmerGrid" export FORT="...

Hi Rupert,
I send you the setup scripts of MUMPS on taito - although they might not be of particular help, as system differs. If I interpret them right, we use parmetis there.

Cheers,

Thomas

Hi Rupert, Checking the commit history of the SVN repository, the most likely changes after revision 6798 that could influence your simulation where actually committed by you (Grid2DInterpolator.f90 and FlowDepth,f90). I don't know if those influence something set for your Stokes solver. Else, my la...

Hi Christian, I apparently missed a few potential issues in your setup: !! bedrock: Boundary Condition 3 Name = "bedrock" Height = Real 0.0 Bottom Surface = Equals bedrockDEM Normal-Tangential Velocity = Logical True Flow Force BC = Logical True Flow Solution 1 = Real 0.0 Flow Solution 1 C...

Christian, I didn't realise that you use Block Pre-Conditioner (BPC). As you apparently were able to run with no-slip condition (Dirichlet) the issue is not directly connected to your Mesh or Solver rather than the boundary condition. Solver settings for ParStokes are well documented here: http://el...

Hi Christian, I made an approach with a mountain glacier using Weertman law. I didn't switch between a Dirichlet condition and the sliding law, but simply, depending on the depth, switched from one to another sliding coefficient. Something like that: $ function depthwise(D) {\ if (D > 10.0) {\ _dept...

Hi, if I might add one comment to the presented solution. The DummySolver was just run on the body for which you want to have the volume computed in order to create a variable (DummyVar) that has the needed permutations (only existing on that very body). If you have such a variable already at hand, ...

I think, by keeping the geometry constant in c), you also should omit any ALE related corrections, i.e., keep Mesh Velocity at zero.

-Thomas

Martina, if you anyhow do not need the Mesh Velocity, why don't you set: Compute Mesh Velocity = Logical False ? Why does it produce non-sense?: In the code it reads as follows: MeshVelocity = ( MeshUpdate - Solver % Variable % PrevValues(:,1) ) / dt My suspicion is, that you have dt=0 in case of st...

Hi Denis, with the help of Joe we found a bug in USF_GetFrictionHeat.f90 that might explain your problems. We have a new version and we are testing it at the moment. I will send a message to the list once things are completely fixed and a test-case has been set up. Sorry for the inconvenience, Thomas