avalanche issueshttps://develop.openfoam.com/Community/avalanche/-/issues2023-06-14T19:55:49Zhttps://develop.openfoam.com/Community/avalanche/-/issues/7Avalanche tutorials are not working in V2006 and V20122023-06-14T19:55:49ZGebray HabtuAvalanche tutorials are not working in V2006 and V2012I tried running Avalanche tutorial cases in V2006 og V2012 (both simple slope and wolfsgrube) and I am getting the following errors:
`// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mes...I tried running Avalanche tutorial cases in V2006 og V2012 (both simple slope and wolfsgrube) and I am getting the following errors:
`// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mesh for time = 0
Reading g
Reading field h
--> FOAM FATAL IO ERROR:
unexpected class name volScalarField expected areaScalarField
while reading object h
file: /mnt/d/gebray/OpenFOAM/simpleslope/0/h at line 15.
From Foam::Istream& Foam::regIOobject::readStream(const Foam::word&, bool)
in file db/regIOobject/regIOobjectRead.C at line 170.
FOAM exiting`
I tried to run all utilities one by and it seems the "releaseAreaMapping" utility is modifying the 0 directory by changing the areaScalarField to volScalarField.Matti RauterMatti Rauterhttps://develop.openfoam.com/Community/avalanche/-/issues/6Incorrect gravitational vector in the friction models2023-07-05T05:10:18ZBas NieuwboerIncorrect gravitational vector in the friction modelsIn the friction models, for instance the manninStrikcler, the vertical component of the gravitational vector is used. This is incorrect, since it is the component normal to the bed which will induce the friction. A thought experiment is ...In the friction models, for instance the manninStrikcler, the vertical component of the gravitational vector is used. This is incorrect, since it is the component normal to the bed which will induce the friction. A thought experiment is to think about a very steep (nearly vertical) slope. For this slope, the friction should be near zero. The normal component of the gravitation vector would be nearly zero and is the right component to use.
In my application I only needed the manningStrickler friction and adapted these files together with the frictionModel to include the normal component of the gravity. I've included the changes I made to these files. Obviously, also the call to the friction constructor should be updated in the solver.
I've also read in the dimensionless manning coefficient and changed the units in the class so the input file becomes less cluttered. I can imagine that incorporating this is somewhat more difficult.
[frictionModel.H](/uploads/bfd22a04eb3a3feb6294e7c5f9eca36d/frictionModel.H)
[frictionModelNew.C](/uploads/224cd548cf5a4445e359b18dbfef9141/frictionModelNew.C)
[frictionModel.C](/uploads/c5e7987046c35159e95f68cf0aed4da0/frictionModel.C)
[ManningStrickler.C](/uploads/e677c95a8d8c0035401b802585c2cc63/ManningStrickler.C)
[ManningStrickler.H](/uploads/71974f7543978f892918cc8f0ce91c96/ManningStrickler.H)Matti RauterMatti Rauterhttps://develop.openfoam.com/Community/avalanche/-/issues/5Various regex failures (older GCC)2023-06-20T13:38:28ZPraveenJagnathan_01Various regex failures (older GCC)The GIS tools use std::regex, but these are flakey (really bad) on older versions of gcc.The GIS tools use std::regex, but these are flakey (really bad) on older versions of gcc.https://develop.openfoam.com/Community/avalanche/-/issues/4Geodata for tutorial wolfsgrube takes up too much space2018-06-28T11:02:20ZMatti RauterGeodata for tutorial wolfsgrube takes up too much spaceGeodata for tutorial wolfsgrube takes up too much space (40 MB at least).
Reduce Geodata (DEM) size if possible.Geodata for tutorial wolfsgrube takes up too much space (40 MB at least).
Reduce Geodata (DEM) size if possible.Matti RauterMatti Rauterhttps://develop.openfoam.com/Community/avalanche/-/issues/3adjust release area mapping format2020-06-16T20:30:48ZMark OLESENadjust release area mapping formatJust a suggestion. You are using PtrList of entries (https://develop.openfoam.com/Community/avalanche/blob/module-1712/applications/utilities/releaseAreaMapping/releaseAreaMapping.C#L65).
If `fields` were a plain dictionary entry instea...Just a suggestion. You are using PtrList of entries (https://develop.openfoam.com/Community/avalanche/blob/module-1712/applications/utilities/releaseAreaMapping/releaseAreaMapping.C#L65).
If `fields` were a plain dictionary entry instead, you could walk easily and also benefit from using other dictionary expansions. For example,
base { ... }
releaseArea1 { ... }
releaseArea2 { ... }
and then later
fields
{
hentrain
{
regions
{
$base;
$releaseArea1;
}
}
h
{
default h0 [0 1 0 0 0 0 0] 1e-5;
regions
{
$releaseArea1;
}
}
}
Or place the information in a separate file and use and `#include` within each `regions` dictionary.Matti RauterMatti Rauterhttps://develop.openfoam.com/Community/avalanche/-/issues/2friction and deposition models missing publication references2020-06-16T20:31:07ZMark OLESENfriction and deposition models missing publication references- useful for cross-referencing and later debugging.- useful for cross-referencing and later debugging.Matti RauterMatti Rauterhttps://develop.openfoam.com/Community/avalanche/-/issues/1releaseAreaMapping blocks in parallel2017-12-20T12:53:31ZMark OLESENreleaseAreaMapping blocks in parallelv1712Matti RauterMatti Rauter