Hi Kai,
at least for this piece of output, the time step increase is below the precision used for the output. Please use a higher precision and double-check: https://cplusplus.com/reference/ios/ios_base/precision/ Kind regards Bernd -- _________________________________________________________________ Bernd Flemisch IWS, Universität Stuttgart phone: +49 711 685 69162 Pfaffenwaldring 61 email: [email protected] D-70569 Stuttgart url: www.iws.uni-stuttgart.de/en/lh2/<http://www.iws.uni-stuttgart.de/en/lh2/> _________________________________________________________________ ________________________________ Von: DuMux <[email protected]> im Auftrag von Kai Wendel <[email protected]> Gesendet: Dienstag, 2. August 2022 16:57:30 An: [email protected] Betreff: [DuMux] Fwd: Fwd: A weird bug in timeloop.hh The following part of the output seems most relevant regarding this problem: Set flowTimeLoops timeStepSize to firstHalfTimeStep+secondHalfTimeStep = 4.229e+00 This is flowTimeLoop->time() 1.440e+04 advanceTimeStep: timeStepSize_ = 4.229e+00 time_ = 1.440e+04 time_ = 1.440e+04 time_+timeStepSize_ = 1.440e+04What is with timeStepSize_: 4.229e+00 This is flowTimeLoop->time() now : 1.440e+04 More detailed: >>>>>>>>>>>>>>> Begin timestep #92 <<<<<<<<<<<<<<< Flow Problem Iteration 1/2 0 flowTimeLoop->time() = 1.440e+04 try to solve with totalTimeStepSize = 4.229e+00 energyTimeLoop->time() = 1.440e+04 Newton iteration 1 done, maximum relative shift = 3.0962e-07 Newton iteration 2 done, maximum relative shift = 3.5568e-11 Assemble/solve/update time: 0.45(84.76%)/0.069(13.06%)/0.011(2.17%) We called flowNonLinearSolver.solve(flowSolutionVector,*flowTimeLoop), this has effects? flowTimeLoop->time() = 1.440e+04 First halfed Time step size is 2.115e+00 341 Energy Problem Iteration 0 energyTimeLoop->time() = 1.440e+04 Now what happened? energyTimeLoop->maxTimeStepSize(): 4.229e+00 and Time step size energy before calling solve: 4.229e+00 Newton iteration 1 done, maximum relative shift = 9.0343e-08 Newton iteration 2 done, maximum relative shift = 8.0296e-16 Assemble/solve/update time: 0.1(97.43%)/0.0026(2.41%)/0.00017(0.16%) Checking if energy problem required a smaller time step size Total time step size flow: 4.229e+00 Time step size energy: 4.229e+00 Flow Problem Iteration 2/2 0 flowTimeLoop->time() = 1.440e+04 Newton iteration 1 done, maximum relative shift = 3.7548e-07 Newton iteration 2 done, maximum relative shift = 3.9240e-07 Newton iteration 3 done, maximum relative shift = 4.4968e-11 Assemble/solve/update time: 0.6(81.90%)/0.12(15.83%)/0.017(2.28%) Second halfed Time step size is 2.115e+00 timeStepSize of flowTimeLoop = 4.229e+00 whereas energyTimeLoop->timeStepSize() = 4.229e+00 Now what is this flowTimeLoop->time() = 1.440e+04 beginFlowTime = 1.440e+04 Set flowTimeLoops timeStepSize to firstHalfTimeStep+secondHalfTimeStep = 4.229e+00 This is flowTimeLoop->time() 1.440e+04 advanceTimeStep: timeStepSize_ = 4.229e+00 time_ = 1.440e+04 time_ = 1.440e+04 time_+timeStepSize_ = 1.440e+04What is with timeStepSize_: 4.229e+00 This is flowTimeLoop->time() now : 1.440e+04 [ 0%] Time step 93 done in 1.4 seconds. Wall clock time: 245.31, time: 14400, time step size: 4.229 What is now energyTimeLoop->timeStepSize(): 4.229e+00Next advnceTimeStep etc. comes advanceTimeStep: timeStepSize_ = 4.229e+00 time_ = 1.440e+04 time_ = 1.440e+04 time_+timeStepSize_ = 1.440e+04What is with timeStepSize_: 4.229e+00 [ 0%] Time step 93 done in 1.4 seconds. Wall clock time: 245.31, time: 14400, time step size: 4.229 What is now energyTimeLoop->timeStepSize(): 4.229e+00 calling suggestTimeStepSize() and targetSteps_ is 8 numSteps_ is 3 percent = 6.250e-01 Flow proposed time steps size: 2.766e-12 We have as input for : energyNonLinearSolver.suggestTimeStepSize(energyTimeLoop->timeStepSize()): 4.229e+00 calling suggestTimeStepSize() and targetSteps_ is 8 numSteps_ is 2 percent = 7.500e-01 Energy proposes time steps size: 6.872e+00 new time step size: 2.766e-12 <<<<<<<<<<<<<<< Finish timestep #92 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Begin timestep #93 <<<<<<<<<<<<<<< Flow Problem Iteration 1/2 0 flowTimeLoop->time() = 1.440e+04 try to solve with totalTimeStepSize = 1.819e-12 energyTimeLoop->time() = 1.440e+04 Newton iteration 1 done, maximum relative shift = 1.3553e-19 Newton iteration 2 done, maximum relative shift = 2.7105e-20 Assemble/solve/update time: 0.41(84.61%)/0.064(13.17%)/0.011(2.22%) We called flowNonLinearSolver.solve(flowSolutionVector,*flowTimeLoop), this has effects? flowTimeLoop->time() = 1.440e+04 First halfed Time step size is 9.095e-13 341 Energy Problem Iteration 0 energyTimeLoop->time() = 1.440e+04 Now what happened? energyTimeLoop->maxTimeStepSize(): 1.819e-12 and Time step size energy before calling solve: 1.819e-12 Newton iteration 1 done, maximum relative shift = 0.0000e+00 Newton iteration 2 done, maximum relative shift = 0.0000e+00 Assemble/solve/update time: 0.1(98.13%)/0.0018(1.71%)/0.00016(0.16%) Checking if energy problem required a smaller time step size Total time step size flow: 1.819e-12 Time step size energy: 1.819e-12 Flow Problem Iteration 2/2 0 flowTimeLoop->time() = 1.440e+04 You have set a very small timestep size (dt = 0). This might lead to numerical problems! UMFPACK V5.7.8 (Nov 9, 2018): WARNING: matrix is singular One can see in time step 92 at the end of the second flow iteration, that, despite that the time step size is 4.229 seconds, when the operation time_ += timestepsize_ is performed, then time_ is not changed. Best ---------- Forwarded message --------- Von: Holger Class <[email protected]<mailto:[email protected]>> Date: Di., 2. Aug. 2022 um 16:02 Uhr Subject: Fwd: [DuMux] Fwd: A weird bug in timeloop.hh To: Kai Wendel <[email protected]<mailto:[email protected]>> -------- Forwarded Message -------- Received: from EX12.ad1.uni-stuttgart.de<http://EX12.ad1.uni-stuttgart.de> (2001:7c0:2041:20e:d199:824f:acbd:c2f4) by EX22.ad1.uni-stuttgart.de<http://EX22.ad1.uni-stuttgart.de> (2001:7c0:2041:20f:99b8:abf3:6e85:a8f8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.18 via Mailbox Transport; Tue, 2 Aug 2022 14:58:53 +0200 Received: from mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> (129.69.192.20) by EX12.ad1.uni-stuttgart.de<http://EX12.ad1.uni-stuttgart.de> (129.69.193.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.18; Tue, 2 Aug 2022 14:58:52 +0200 Received: from localhost (localhost [127.0.0.1]) by mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> (Postfix) with ESMTP id D9DB560654; Tue, 2 Aug 2022 14:58:52 +0200 (CEST) X-Relay-Countries: ** DE X-Virus-Scanned: USTUTT mailrelay AV services at mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> X-Spam-Flag: NO X-Spam-Score: -3.397 X-Spam-Level: X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=uni-stuttgart.de<http://uni-stuttgart.de> Received: from mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> ([127.0.0.1]) by localhost (mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3nSHAxjXwwH; Tue, 2 Aug 2022 14:58:50 +0200 (CEST) Received: from mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> (mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> [IPv6:2001:7c0:2041:25::a:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de> (Postfix) with ESMTPS; Tue, 2 Aug 2022 14:58:50 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> (Postfix) with ESMTP id 738701F; Tue, 2 Aug 2022 14:58:50 +0200 (CEST) X-Virus-Scanned: USTUTT mailrelay AV services at mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> Received: from mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> ([127.0.0.1]) by localhost (mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmFHvLqx4QuK; Tue, 2 Aug 2022 14:58:48 +0200 (CEST) Received: from nflmailman3.rus.uni-stuttgart.de<http://nflmailman3.rus.uni-stuttgart.de> (nflmailman3.rus.uni-stuttgart.de<http://nflmailman3.rus.uni-stuttgart.de> [129.69.7.88]) by mx4.rus.uni-stuttgart.de<http://mx4.rus.uni-stuttgart.de> (Postfix) with ESMTP; Tue, 2 Aug 2022 14:58:48 +0200 (CEST) Received: from nflmailman3.rus.uni-stuttgart.de<http://nflmailman3.rus.uni-stuttgart.de> (localhost [IPv6:::1]) by nflmailman3.rus.uni-stuttgart.de<http://nflmailman3.rus.uni-stuttgart.de> (Postfix) with ESMTP id B5950C7DC3; Tue, 2 Aug 2022 14:58:45 +0200 (CEST) X-Original-To: [email protected]<mailto:[email protected]> Delivered-To: [email protected]<mailto:[email protected]> Received: from mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> (mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> [IPv6:2001:7c0:2041:25::a:3]) by nflmailman3.rus.uni-stuttgart.de<http://nflmailman3.rus.uni-stuttgart.de> (Postfix) with ESMTP id EB63FC7DB2 for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> (Postfix) with ESMTP id E8431202C1 for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:43 +0200 (CEST) X-Virus-Scanned: USTUTT mailrelay AV services at mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> X-Spam-Flag: NO X-Spam-Score: -3.007 X-Spam-Level: X-Spam-Status: No, score=-3.007 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> (amavisd-new); dkim=pass (2048-bit key) header.d=uni-stuttgart.de<http://uni-stuttgart.de> Received: from mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> ([127.0.0.1]) by localhost (mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQjeUv47iAry for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:39 +0200 (CEST) Received: from mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> (mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> [IPv6:2001:7c0:2041:24::a:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.rus.uni-stuttgart.de<http://mx3.rus.uni-stuttgart.de> (Postfix) with ESMTPS for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:39 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> (Postfix) with ESMTP id E72D2601AD for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=uni-stuttgart.de<http://uni-stuttgart.de>; h=mime-version:content-type:content-type:content-language :accept-language:in-reply-to:references:message-id:date:date :subject:subject:from:from:received:received:received:received; s=dkim; [email protected]<mailto:[email protected]>; t=1659445117; x=1661183918; bh=yAUGDeG3GcsFxZnY3/rsfdh6nF4l5dt2fuyFYllmrlo=; b=NAl6wK8IWZCp sS0n8sX1ht4fYxLSXnZpagYccRilyJtHi0YocapGZjTBZLNphcHtOM06H3xNKVv2 JRz4+wrCR9TmLCgW08fXp9Oc9JPa38TnZU6EyNrgfvYAJsb2p+3yB1JdwWkoT09z rIAwkEJ6oO/TNyTel5Nb2Dse/iQrP6SK8ztNF0P3idQi9YKjN0UjYP0jsnZJoaWf tp/VGIww0La4EHMEtyBQ2Ru52794hiZZ9vGX7x8vdYTTVbZ3McAW2/aHl+mVwRQ5 //qkI2/k7Ym0jhplRo65vIex3jncW7RdHUOCmni1tDk6Y+MyRwMS2JLoPdJdrJgI 8wGjC+dDHw== X-Virus-Scanned: USTUTT mailrelay AV services at mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> Received: from mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> ([127.0.0.1]) by localhost (mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rDj5COj7V9x5 for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:37 +0200 (CEST) Received: from EX21.ad1.uni-stuttgart.de<http://EX21.ad1.uni-stuttgart.de> (ex21.ad1.uni-stuttgart.de<http://ex21.ad1.uni-stuttgart.de> [IPv6:2001:7c0:2041:20f:9879:f38f:e4e0:34da]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client CN "EX21", Issuer "EX21" (not verified)) by mxex2.tik.uni-stuttgart.de<http://mxex2.tik.uni-stuttgart.de> (Postfix) with ESMTPS for <[email protected]><mailto:[email protected]>; Tue, 2 Aug 2022 14:58:37 +0200 (CEST) Received: from EX20.ad1.uni-stuttgart.de<http://EX20.ad1.uni-stuttgart.de> (2001:7c0:2041:20f:4d25:1eb5:5d9b:cfd0) by EX21.ad1.uni-stuttgart.de<http://EX21.ad1.uni-stuttgart.de> (2001:7c0:2041:20f:9879:f38f:e4e0:34da) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.18; Tue, 2 Aug 2022 14:58:37 +0200 Received: from EX20.ad1.uni-stuttgart.de<http://EX20.ad1.uni-stuttgart.de> ([fe80::6ce0:89ed:bb40:7d33]) by EX20.ad1.uni-stuttgart.de<http://EX20.ad1.uni-stuttgart.de> ([fe80::6ce0:89ed:bb40:7d33%13]) with mapi id 15.01.2375.018; Tue, 2 Aug 2022 14:58:37 +0200 From: Flemisch, Bernd <[email protected]><mailto:[email protected]> To: DuMux User Mailing List <[email protected]><mailto:[email protected]> Thread-Topic: [DuMux] Fwd: A weird bug in timeloop.hh Thread-Index: AQHYpm9BxvuHBxlwd0aHKXF7YXnpJ62bkik7 Date: Tue, 2 Aug 2022 12:58:37 +0000 Message-ID: <[email protected]><mailto:[email protected]> References: <CAKhkB6bn65MVEheM50R6YNVgAPzMzFoVn_N=luilaqemctn...@mail.gmail.com><mailto:CAKhkB6bn65MVEheM50R6YNVgAPzMzFoVn_N=luilaqemctn...@mail.gmail.com>, <CAKhkB6YgTn29Z70Krrv35h7yF1Q37fqN_euF+2=vpayw3gn...@mail.gmail.com><mailto:CAKhkB6YgTn29Z70Krrv35h7yF1Q37fqN_euF+2=vpayw3gn...@mail.gmail.com> In-Reply-To: <CAKhkB6YgTn29Z70Krrv35h7yF1Q37fqN_euF+2=vpayw3gn...@mail.gmail.com><mailto:CAKhkB6YgTn29Z70Krrv35h7yF1Q37fqN_euF+2=vpayw3gn...@mail.gmail.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.69.192.121] Subject: Re: [DuMux] Fwd: A weird bug in timeloop.hh X-BeenThere: [email protected]<mailto:[email protected]> X-Mailman-Version: 2.1.39 Precedence: list List-Id: DuMux User Mailing List <dumux.listserv.uni-stuttgart.de<http://dumux.listserv.uni-stuttgart.de>> List-Unsubscribe: <https://listserv.uni-stuttgart.de/mailman/options/dumux><https://listserv.uni-stuttgart.de/mailman/options/dumux>, <mailto:[email protected]?subject=unsubscribe><mailto:[email protected]?subject=unsubscribe> List-Archive: <http://listserv.uni-stuttgart.de/pipermail/dumux/><http://listserv.uni-stuttgart.de/pipermail/dumux/> List-Post: <mailto:[email protected]><mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help><mailto:[email protected]?subject=help> List-Subscribe: <https://listserv.uni-stuttgart.de/mailman/listinfo/dumux><https://listserv.uni-stuttgart.de/mailman/listinfo/dumux>, <mailto:[email protected]?subject=subscribe><mailto:[email protected]?subject=subscribe> Reply-To: DuMux User Mailing List <[email protected]><mailto:[email protected]> Content-Type: multipart/mixed; boundary="===============4345845473997986848==" Errors-To: [email protected]<mailto:[email protected]> Sender: DuMux <[email protected]><mailto:[email protected]> Return-Path: [email protected]<mailto:[email protected]> X-MS-Exchange-Organization-Network-Message-Id: 7492e4d2-d8d7-402f-5098-08da7486c051 X-MS-Exchange-Organization-PRD: listserv.uni-stuttgart.de<http://listserv.uni-stuttgart.de> X-MS-Exchange-Organization-SenderIdResult: Pass Received-SPF: Pass (EX12.ad1.uni-stuttgart.de<http://EX12.ad1.uni-stuttgart.de>: domain of [email protected]<mailto:[email protected]> designates 129.69.192.20 as permitted sender) receiver=EX12.ad1.uni-stuttgart.de<http://EX12.ad1.uni-stuttgart.de>; client-ip=129.69.192.20; helo=mxex1.tik.uni-stuttgart.de<http://mxex1.tik.uni-stuttgart.de>; X-MS-Exchange-ABP-GUID: 2dbe3a8c-5e9d-4d0b-bfde-7b18e84314ea X-MS-Exchange-Organization-AuthSource: EX12.ad1.uni-stuttgart.de<http://EX12.ad1.uni-stuttgart.de> X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Transport-EndToEndLatency: 00:00:00.4726743 X-MS-Exchange-Processed-By-BccFoldering: 15.01.2375.018 MIME-Version: 1.0 Hi Kai, can you please also post the output that you get? Kind regards Bernd -- _________________________________________________________________ Bernd Flemisch IWS, Universität Stuttgart phone: +49 711 685 69162 Pfaffenwaldring 61 email: [email protected]<mailto:[email protected]> D-70569 Stuttgart url: www.iws.uni-stuttgart.de/en/lh2/<http://www.iws.uni-stuttgart.de/en/lh2/> _________________________________________________________________ ________________________________ Von: DuMux <[email protected]><mailto:[email protected]> im Auftrag von Kai Wendel <[email protected]><mailto:[email protected]> Gesendet: Dienstag, 2. August 2022 14:55:48 An: [email protected]<mailto:[email protected]> Betreff: [DuMux] Fwd: A weird bug in timeloop.hh Hello, I am currently implementing a secondorder sequential (Strang sequential) scheme for freeflow models, which therefore has two timeloops, as there are two sequentially solved subproblems. It then happens after some time, that the function call advanceTimeStep() does not lead to an increase in the member varialbe time_, despite the expression time_ += timeStepSize_; is called and timeStepSize_ is definitely not zero. I checked this by writing the values out to the command line: void advanceTimeStep() override { std::cout << "advanceTimeStep: timeStepSize_ = " << timeStepSize_; timeStepIdx_++; std::cout << " time_ = " << time_ << std::endl; time_ += timeStepSize_; std::cout << "time_ = " << time_ << " time_+timeStepSize_ = " << time_+ timeStepSize_ << " What is with timeStepSize_: " << timeStepSize_ << std::endl; // NOTE: I receive the same value for time_ as before calling time_ += timeStepSize_; previousTimeStepSize_ = timeStepSize_; // compute how long the last time step took const auto cpuTime = wallClockTime(); timeStepWallClockTime_ = cpuTime - timeAfterLastTimeStep_; timeAfterLastTimeStep_ = cpuTime; // ensure that using current dt we don't exceed tEnd in next time step setTimeStepSize(timeStepSize_); } The dumux version used is commit 79d3057e3ee504ab40d3bc918931ca83fa008481 (HEAD) in the dumux master branch I have no idea, what could be the reason for this. Could this be connected to the use of the CheckpointTimeLoop class? Is there a possibility that the varialbe time_ has received some upper limit? How can this happen? Thanks for helping. Best Kai Wendel
_______________________________________________ DuMux mailing list [email protected] https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
