User Forum of Software BASEMENT

Ueli

User

Registered: 2017-02-03

Posts: 2

different output timesteps from same special_output

Hello to all
the following output command delivers different amount of timesteps. depth.sol delivers 117 timesteps, this is what i can expect with a total runtime of 14000s. velocity.sol delivers only 76 timesteps.
       
        OUTPUT {
            console_time_step = 600
            reference_time    = 12-12-2016-15-00-00
            restart_time_step = 1E32
            SPECIAL_OUTPUT {
                type             = node_centered
                output_time_step = 120
                values           = (depth velocity )
                format           = sms

thanks for any hints
Ueli

Lukas Vonwiller

Developer

Registered: 2014-09-04

Posts: 127

Re: different output timesteps from same special_output

Dear Ueli
Is this the only Special_Ouput Block you defined?
If so there must be something wrong when writing the output.
Please send us a minimal running example to reproduce this bug to basement@ethz.ch

Br, Lukas

Ueli

User

Registered: 2017-02-03

Posts: 2

Re: different output timesteps from same special_output

Hi Lukas
it is the only Special_Output defined. i send you all the files.
Ueli

Lukas Vonwiller

Developer

Registered: 2014-09-04

Posts: 127

Re: different output timesteps from same special_output

Dear Ueli,
I tested your input files using shorter simulation time and output time steps and I was not able to reproduce this behaviour.
Basement writes the right amount of time steps into the defined output files.

Your mesh is quite large (750k elements), might be that you run into trouble on your computer system?
Furthermore, there are several warnings for ambiguous quadrilateral elements and other warnings: check in file 'Area Property Mesh Grid.err'

Hope this helps!
Best, Lukas