Menu

#27 mysterious influence of oldtime output

1.0
open
nobody
2019-02-15
2019-02-15
Pfiffikus
No

During check of our selfmade time step control we see an influence of
Info << "OLD TIME: \n" << field.second.oldTime().internalField() << endl; Info << "CURRENT: \n" << field.second.internalField() << endl; Info << "OLD TIME 2: \n" << field.second.oldTime().internalField() << endl;
being compiled or not: For the next output of current and old time state (the same way ...!) we get the same values for both states ...
But when the aforementioned code lines are missing, the printed state values are different!

What happens implicitly by the call of .oldTime()?
Could it be caused by the warning mentioned in a former ticket?

What are the correct lines to
1. redo the last time step
2. after decreasing the time step size?

Many thanks for any hint in advance

Discussion


Log in to post a comment.

MongoDB Logo MongoDB
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.