User Forum of Software BASEMENT

Matthias

Advanced_User

Registered: 2014-12-16

Posts: 29

Sediment Restart File

Hi guys
I would like to start my sediment transport simulation with "washed in" (Einwaschung) grain classes for each cross section. With Basement V2.4 R1808 there is a new block MORPHOLOGY/INITIAL which needs an input file. The help-text for the "type" states: b)'continue'. The simulation is restarted from a restart-file obtained by a previous run ('hot-start'). The restart file contains the final topography from the former simulation with its layers and soil compositions.

Now I tried to add various output-files from previous runs as Sediment input files but none of them were "accepted" in the run, meaning that they had no effect to the simulation and the simulation always started with the initially set grain classes.

Which output-file has to be added here? I tried: *Sed.txt file (Only taking the last time step and setting the time to 0.00), *SedRestart.txt, *_topo_restart.bmg.
Does it need to be in the .CGNS format? Do you maybe have an example file?

The reason behind it is that I want to implement an already armoured active layer due to very large erosion processes which are happening at some cross sections in the very first time steps of the simulation.

Best regards
Matthias

Matthias

Advanced_User

Registered: 2014-12-16

Posts: 29

Re: Sediment Restart File

Quick Answer:
I found the solution to the problem. The Version I am using (R1808) is unable to run with a SedRestart file because the parameter block has been changed from being internally in the Morphology/Parameter to being a separate block in Morphology/Initial. I think that SedRestart ist not implemented yet with this new block-form. If anyone needs to use a washed in model, please use the official version R1692.

Best regards
Matthias

Christian Volz

User

Registered: 2014-09-04

Posts: 31

Re: Sediment Restart File

Thanks for this info Matthias!

This seems to be a bug, caused by moving the INITIAL block to another  location. This problem therefore only occurs with "intermediate" versions, but not with the official release versions. It should be fixed in the next release.