From nek5000-users at lists.mcs.anl.gov Tue Dec 6 08:23:37 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Tue, 06 Dec 2011 15:23:37 +0100 Subject: [Nek5000-users] Restart problem Message-ID: <1323181417.5193.13.camel@skagsnebb.mech.kth.se> Hi I simulate jet in crossflow problem with nek5000 and I've got serius problems with restarting the simulation. It causes strong spurious velocity oscillation and I cannot get rid of them. I've implemented restarting procedure described in prepost.f, but it doesn't help much. Playing with file format (parameters p66, p67) and projection (p94, p95) I can only decrease oscillations amplitude, but they are still there. Surprisingly saving output files in double precision (p63=8) makes everything worse. Has anybody got similar problems? Best regards Adam From nek5000-users at lists.mcs.anl.gov Wed Dec 7 07:53:58 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 07 Dec 2011 14:53:58 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) Message-ID: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> Dear All, I have been conducting a direct numerical simulation of turbulent pipe flow using nek5000 at a moderately high Reynolds number (at present Re_tau=550). For this, I have to use a very fine grid in order to capture the flow physics accurately (for a length of 25R, I am using a total of 450 million grid points when assuming a polynomial order 7). However, I have been having problems with the stability of the code when using TORDER = 3, i.e. parameter 027. The way I conducted my simulation was as follows: - I started with polynomial order 3, TORDER set to 3, and run for 4 flow through times, starting from random noise. At this point I had the projection parameters, i.e. P094 and P095 set to non-zero values. - Afterwards, I increased the polynomial order to 5, with TORDER kept at 3, and ran for another 2 flow through times. Here, I set the projection parameters P094 and P095 to zero. - Now, starting from the last field of the previous run, I changed to my target polynomial order 7, and keeping TORDER = 3. However, the codes explodes shortly after restarting. The error is: "failed in HMHOLTZ." I also tried a considerably lower time-step, but the problem persisted. Meanwhile, when I change TORDER to 2, the code runs fine and does not explode. The "physical" results are absolutely fine, and the statistics I get are in perfect agreement to our expectations. I did not get the same problem while running a turbulent pipe flow at a lower Reynolds number (Re_tau=180) and with less grid points. Probably also of importance, I did test with various ways of restarting, i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing multiple consecutive fields for the multi-step time scheme. None of these changes made significant impact. Also, I am using overintegration and filtering (0.01 in parameter P103); increasing the filtering (by a factor of 5) did also not help. I am wondering if any faced a similar issue before, and if would have an insight on how to tackle it. Could my problem maybe be related to the restart-issue that Adam brought up recently? Best regards George ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From nek5000-users at lists.mcs.anl.gov Wed Dec 7 08:11:36 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 07 Dec 2011 15:11:36 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> Message-ID: <4EDF7418.6040807@mech.kth.se> BDF2 is more robust than BDF3. I used it successfully for my diffuser. Johan nek5000-users at lists.mcs.anl.gov wrote: > > Dear All, > > I have been conducting a direct numerical simulation of turbulent pipe > flow > using nek5000 at a moderately high Reynolds number (at present > Re_tau=550). > For this, I have to use a very fine grid in order to capture the flow > physics accurately (for a length of 25R, I am using a total of 450 > million > grid points when assuming a polynomial order 7). However, I have been > having > problems with the stability of the code when using TORDER = 3, i.e. > parameter 027. The way I conducted my simulation was as follows: > > - I started with polynomial order 3, TORDER set to 3, and run for 4 flow > through times, starting from random noise. At this point I had the > projection parameters, i.e. P094 and P095 set to non-zero values. > > - Afterwards, I increased the polynomial order to 5, with TORDER kept > at 3, > and ran for another 2 flow through times. Here, I set the projection > parameters P094 and P095 to zero. > > - Now, starting from the last field of the previous run, I changed to my > target polynomial order 7, and keeping TORDER = 3. However, the codes > explodes shortly after restarting. The error is: "failed in HMHOLTZ." > I also tried a considerably lower time-step, but the problem persisted. > Meanwhile, when I change TORDER to 2, the code runs fine and does not > explode. The "physical" results are absolutely fine, and the statistics I > get are in perfect agreement to our expectations. > > I did not get the same problem while running a turbulent pipe flow at a > lower Reynolds number (Re_tau=180) and with less grid points. > > Probably also of importance, I did test with various ways of restarting, > i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing > multiple consecutive fields for the multi-step time scheme. None of these > changes made significant impact. Also, I am using overintegration and > filtering (0.01 in parameter P103); increasing the filtering (by a > factor of > 5) did also not help. > > I am wondering if any faced a similar issue before, and if would have an > insight on how to tackle it. Could my problem maybe be related to the > restart-issue that Adam brought up recently? > > Best regards > George > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users -- Johan Malm Department of Mechanics, KTH SE-100 44, Stockholm, Sweden Phone: +46 8 7906876 E-mail: johan at mech.kth.se From nek5000-users at lists.mcs.anl.gov Wed Dec 7 09:12:27 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 7 Dec 2011 09:12:27 -0600 (CST) Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> Message-ID: Hi George, Is your timestep size variable? or fixed? You can fix it (highly recommended) by setting it to the value you want, but negative (e.g., param 12 = -.001 in the .rea file would imply that DT=.001 for all timesteps). >From what you describe, I am guessing that this is the issue. In particular, variable timestepping + projection has some difficulties. With dealiasing and filtering, I never have problems with Torder=3, and I would recommend using this. I concur, however, with Johan that Torder=2 is more stable. (See the CRAS article with J. Mullen in 2001.) I hope this helps - please let us know if problems persist. Paul On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > > Dear All, > > I have been conducting a direct numerical simulation of turbulent pipe flow > using nek5000 at a moderately high Reynolds number (at present Re_tau=550). > For this, I have to use a very fine grid in order to capture the flow > physics accurately (for a length of 25R, I am using a total of 450 million > grid points when assuming a polynomial order 7). However, I have been having > problems with the stability of the code when using TORDER = 3, i.e. > parameter 027. The way I conducted my simulation was as follows: > > - I started with polynomial order 3, TORDER set to 3, and run for 4 flow > through times, starting from random noise. At this point I had the > projection parameters, i.e. P094 and P095 set to non-zero values. > > - Afterwards, I increased the polynomial order to 5, with TORDER kept at 3, > and ran for another 2 flow through times. Here, I set the projection > parameters P094 and P095 to zero. > > - Now, starting from the last field of the previous run, I changed to my > target polynomial order 7, and keeping TORDER = 3. However, the codes > explodes shortly after restarting. The error is: "failed in HMHOLTZ." > I also tried a considerably lower time-step, but the problem persisted. > Meanwhile, when I change TORDER to 2, the code runs fine and does not > explode. The "physical" results are absolutely fine, and the statistics I > get are in perfect agreement to our expectations. > > I did not get the same problem while running a turbulent pipe flow at a > lower Reynolds number (Re_tau=180) and with less grid points. > > Probably also of importance, I did test with various ways of restarting, > i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing > multiple consecutive fields for the multi-step time scheme. None of these > changes made significant impact. Also, I am using overintegration and > filtering (0.01 in parameter P103); increasing the filtering (by a factor of > 5) did also not help. > > I am wondering if any faced a similar issue before, and if would have an > insight on how to tackle it. Could my problem maybe be related to the > restart-issue that Adam brought up recently? > > Best regards > George > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Wed Dec 7 09:38:05 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 07 Dec 2011 16:38:05 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> Message-ID: <20111207163805.11226tijj6k67nfh@www.mech.kth.se> Hi Paul, Thanks for the quick answer. I have been using a fixed time-step. After a suggestion from Johan, I will try to overintegrate with lxd \approx 2*lx1, since I use a curved geometry. In addition, it might be useful to try with an even polynomial order? (Since my problems start as I change from N=5 to N=7, maybe N=8 is better?) George Quoting nek5000-users at lists.mcs.anl.gov: > > Hi George, > > Is your timestep size variable? or fixed? > > You can fix it (highly recommended) by setting it to the value > you want, but negative (e.g., param 12 = -.001 in the .rea file > would imply that DT=.001 for all timesteps). > >> From what you describe, I am guessing that this is the issue. > In particular, variable timestepping + projection has some difficulties. > > With dealiasing and filtering, I never have problems with Torder=3, > and I would recommend using this. I concur, however, with Johan > that Torder=2 is more stable. (See the CRAS article with J. Mullen > in 2001.) > > I hope this helps - please let us know if problems persist. > > Paul > > > On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > >> >> Dear All, >> >> I have been conducting a direct numerical simulation of turbulent pipe flow >> using nek5000 at a moderately high Reynolds number (at present Re_tau=550). >> For this, I have to use a very fine grid in order to capture the flow >> physics accurately (for a length of 25R, I am using a total of 450 million >> grid points when assuming a polynomial order 7). However, I have been having >> problems with the stability of the code when using TORDER = 3, i.e. >> parameter 027. The way I conducted my simulation was as follows: >> >> - I started with polynomial order 3, TORDER set to 3, and run for 4 flow >> through times, starting from random noise. At this point I had the >> projection parameters, i.e. P094 and P095 set to non-zero values. >> >> - Afterwards, I increased the polynomial order to 5, with TORDER kept at 3, >> and ran for another 2 flow through times. Here, I set the projection >> parameters P094 and P095 to zero. >> >> - Now, starting from the last field of the previous run, I changed to my >> target polynomial order 7, and keeping TORDER = 3. However, the codes >> explodes shortly after restarting. The error is: "failed in HMHOLTZ." >> I also tried a considerably lower time-step, but the problem persisted. >> Meanwhile, when I change TORDER to 2, the code runs fine and does not >> explode. The "physical" results are absolutely fine, and the statistics I >> get are in perfect agreement to our expectations. >> >> I did not get the same problem while running a turbulent pipe flow at a >> lower Reynolds number (Re_tau=180) and with less grid points. >> >> Probably also of importance, I did test with various ways of restarting, >> i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing >> multiple consecutive fields for the multi-step time scheme. None of these >> changes made significant impact. Also, I am using overintegration and >> filtering (0.01 in parameter P103); increasing the filtering (by a factor of >> 5) did also not help. >> >> I am wondering if any faced a similar issue before, and if would have an >> insight on how to tackle it. Could my problem maybe be related to the >> restart-issue that Adam brought up recently? >> >> Best regards >> George >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From nek5000-users at lists.mcs.anl.gov Wed Dec 7 09:44:37 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 7 Dec 2011 09:44:37 -0600 (CST) Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: <20111207163805.11226tijj6k67nfh@www.mech.kth.se> References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> <20111207163805.11226tijj6k67nfh@www.mech.kth.se> Message-ID: Hi George, That would seem unnecessary... It could simply be the case that you are facing lack of resolution. Also, have you already experienced transition to a fully turbulent state? The transition phase normally takes more resolution to get through because of the intense vortex stretching. Additional filtering usually cures this, however. Given that you've already tried this, perhaps this is something we need to look at. If you want me to look in detail at the case that blows up, contact me off list and we can arrange a file transfer. Regards, Paul On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > > Hi Paul, > > Thanks for the quick answer. I have been using a fixed time-step. After a > suggestion from Johan, I will try to overintegrate with lxd \approx 2*lx1, > since I use a curved geometry. In addition, it might be useful to try with an > even polynomial order? (Since my problems start as I change from N=5 to N=7, > maybe N=8 is better?) > > George > > Quoting nek5000-users at lists.mcs.anl.gov: > >> >> Hi George, >> >> Is your timestep size variable? or fixed? >> >> You can fix it (highly recommended) by setting it to the value >> you want, but negative (e.g., param 12 = -.001 in the .rea file >> would imply that DT=.001 for all timesteps). >> >>> From what you describe, I am guessing that this is the issue. >> In particular, variable timestepping + projection has some difficulties. >> >> With dealiasing and filtering, I never have problems with Torder=3, >> and I would recommend using this. I concur, however, with Johan >> that Torder=2 is more stable. (See the CRAS article with J. Mullen >> in 2001.) >> >> I hope this helps - please let us know if problems persist. >> >> Paul >> >> >> On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >> >>> >>> Dear All, >>> >>> I have been conducting a direct numerical simulation of turbulent pipe >>> flow >>> using nek5000 at a moderately high Reynolds number (at present >>> Re_tau=550). >>> For this, I have to use a very fine grid in order to capture the flow >>> physics accurately (for a length of 25R, I am using a total of 450 million >>> grid points when assuming a polynomial order 7). However, I have been >>> having >>> problems with the stability of the code when using TORDER = 3, i.e. >>> parameter 027. The way I conducted my simulation was as follows: >>> >>> - I started with polynomial order 3, TORDER set to 3, and run for 4 flow >>> through times, starting from random noise. At this point I had the >>> projection parameters, i.e. P094 and P095 set to non-zero values. >>> >>> - Afterwards, I increased the polynomial order to 5, with TORDER kept at >>> 3, >>> and ran for another 2 flow through times. Here, I set the projection >>> parameters P094 and P095 to zero. >>> >>> - Now, starting from the last field of the previous run, I changed to my >>> target polynomial order 7, and keeping TORDER = 3. However, the codes >>> explodes shortly after restarting. The error is: "failed in HMHOLTZ." >>> I also tried a considerably lower time-step, but the problem persisted. >>> Meanwhile, when I change TORDER to 2, the code runs fine and does not >>> explode. The "physical" results are absolutely fine, and the statistics I >>> get are in perfect agreement to our expectations. >>> >>> I did not get the same problem while running a turbulent pipe flow at a >>> lower Reynolds number (Re_tau=180) and with less grid points. >>> >>> Probably also of importance, I did test with various ways of restarting, >>> i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing >>> multiple consecutive fields for the multi-step time scheme. None of these >>> changes made significant impact. Also, I am using overintegration and >>> filtering (0.01 in parameter P103); increasing the filtering (by a factor >>> of >>> 5) did also not help. >>> >>> I am wondering if any faced a similar issue before, and if would have an >>> insight on how to tackle it. Could my problem maybe be related to the >>> restart-issue that Adam brought up recently? >>> >>> Best regards >>> George >>> >>> ---------------------------------------------------------------- >>> This message was sent using IMP, the Internet Messaging Program. >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Wed Dec 7 11:01:32 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 7 Dec 2011 11:01:32 -0600 (CST) Subject: [Nek5000-users] Restart problem In-Reply-To: <1323181417.5193.13.camel@skagsnebb.mech.kth.se> Message-ID: <780895814.41294.1323277292362.JavaMail.root@zimbra.anl.gov> Hi Adam, Have you tried the full restart option described in email https://lists.mcs.anl.gov/mailman/htdig/nek5000-users/2010-August/000900.html There was an earlier email about some problems with it -- I can check it once I came back from travel. Best. Aleks ----- Original Message ----- From: nek5000-users at lists.mcs.anl.gov To: nek5000-users at lists.mcs.anl.gov Sent: Tuesday, December 6, 2011 8:23:37 AM Subject: [Nek5000-users] Restart problem Hi I simulate jet in crossflow problem with nek5000 and I've got serius problems with restarting the simulation. It causes strong spurious velocity oscillation and I cannot get rid of them. I've implemented restarting procedure described in prepost.f, but it doesn't help much. Playing with file format (parameters p66, p67) and projection (p94, p95) I can only decrease oscillations amplitude, but they are still there. Surprisingly saving output files in double precision (p63=8) makes everything worse. Has anybody got similar problems? Best regards Adam _______________________________________________ Nek5000-users mailing list Nek5000-users at lists.mcs.anl.gov https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Thu Dec 8 01:45:16 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 08 Dec 2011 08:45:16 +0100 Subject: [Nek5000-users] Restart problem In-Reply-To: <780895814.41294.1323277292362.JavaMail.root@zimbra.anl.gov> References: <780895814.41294.1323277292362.JavaMail.root@zimbra.anl.gov> Message-ID: <1323330316.26784.6.camel@skagsnebb.mech.kth.se> Hi Aleks Yes, I did. It's described in prepost.f and I implemented it in my usr file. Unfortunately my case so sensitive it doesn't help. Regards Adam On Wed, 2011-12-07 at 11:01 -0600, nek5000-users at lists.mcs.anl.gov wrote: > Hi Adam, > > Have you tried the full restart option described in email > > https://lists.mcs.anl.gov/mailman/htdig/nek5000-users/2010-August/000900.html > > There was an earlier email about some problems with it -- I can check it once I came back from travel. > > Best. > Aleks > > > ----- Original Message ----- > From: nek5000-users at lists.mcs.anl.gov > To: nek5000-users at lists.mcs.anl.gov > Sent: Tuesday, December 6, 2011 8:23:37 AM > Subject: [Nek5000-users] Restart problem > > Hi > > I simulate jet in crossflow problem with nek5000 and I've got serious > problems with restarting the simulation. It causes strong spurious > velocity oscillation and I cannot get rid of them. I've implemented > restarting procedure described in prepost.f, but it doesn't help much. > Playing with file format (parameters p66, p67) and projection (p94, p95) > I can only decrease oscillations amplitude, but they are still there. > Surprisingly saving output files in double precision (p63=8) makes > everything worse. Has anybody got similar problems? > Best regards > > Adam > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Thu Dec 8 04:52:14 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 8 Dec 2011 04:52:14 -0600 (CST) Subject: [Nek5000-users] Restart problem In-Reply-To: <1323330316.26784.6.camel@skagsnebb.mech.kth.se> References: <780895814.41294.1323277292362.JavaMail.root@zimbra.anl.gov> <1323330316.26784.6.camel@skagsnebb.mech.kth.se> Message-ID: Hi Adam, Are you using pn/pn ? or pn/pn-2 ? (I'm guessing the latter?) I've not yet got this thing fully resolved, but one issue appears to be an inaccuracy when mapping back and forth from N-2 to N. This is only used for restart and should not be an issue since the information originates on N-2 --- there should be very little loss, save for the conditioning of the interpolation matrices. I'm presently seeing more, and will fix this issue. Also, I think we'll go to a loss-less conversion for the particular case of restarting with 8 bit precision. That being said, there is something else that remains to be tracked down given that pn/pn restart also has issues. Still digging... Paul On Thu, 8 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > Hi Aleks > > Yes, I did. It's described in prepost.f and I implemented it in my usr > file. Unfortunately my case so sensitive it doesn't help. > Regards > > Adam > > On Wed, 2011-12-07 at 11:01 -0600, nek5000-users at lists.mcs.anl.gov > wrote: >> Hi Adam, >> >> Have you tried the full restart option described in email >> >> https://lists.mcs.anl.gov/mailman/htdig/nek5000-users/2010-August/000900.html >> >> There was an earlier email about some problems with it -- I can check it once I came back from travel. >> >> Best. >> Aleks >> >> >> ----- Original Message ----- >> From: nek5000-users at lists.mcs.anl.gov >> To: nek5000-users at lists.mcs.anl.gov >> Sent: Tuesday, December 6, 2011 8:23:37 AM >> Subject: [Nek5000-users] Restart problem >> >> Hi >> >> I simulate jet in crossflow problem with nek5000 and I've got serious >> problems with restarting the simulation. It causes strong spurious >> velocity oscillation and I cannot get rid of them. I've implemented >> restarting procedure described in prepost.f, but it doesn't help much. >> Playing with file format (parameters p66, p67) and projection (p94, p95) >> I can only decrease oscillations amplitude, but they are still there. >> Surprisingly saving output files in double precision (p63=8) makes >> everything worse. Has anybody got similar problems? >> Best regards >> >> Adam >> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Fri Dec 9 04:32:55 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 9 Dec 2011 11:32:55 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> <20111207163805.11226tijj6k67nfh@www.mech.kth.se> Message-ID: Geroge, Can you provide more details. A logfile would be helpful. Cheers, Stefan On 12/7/11, nek5000-users at lists.mcs.anl.gov wrote: > > Hi George, > > That would seem unnecessary... It could simply be the case > that you are facing lack of resolution. > > Also, have you already experienced transition to a fully > turbulent state? The transition phase normally takes more > resolution to get through because of the intense vortex > stretching. Additional filtering usually cures this, however. > > Given that you've already tried this, perhaps this is something > we need to look at. If you want me to look in detail at the > case that blows up, contact me off list and we can arrange a > file transfer. > > Regards, > > Paul > > > > > On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > >> >> Hi Paul, >> >> Thanks for the quick answer. I have been using a fixed time-step. After a >> suggestion from Johan, I will try to overintegrate with lxd \approx 2*lx1, >> >> since I use a curved geometry. In addition, it might be useful to try with >> an >> even polynomial order? (Since my problems start as I change from N=5 to >> N=7, >> maybe N=8 is better?) >> >> George >> >> Quoting nek5000-users at lists.mcs.anl.gov: >> >>> >>> Hi George, >>> >>> Is your timestep size variable? or fixed? >>> >>> You can fix it (highly recommended) by setting it to the value >>> you want, but negative (e.g., param 12 = -.001 in the .rea file >>> would imply that DT=.001 for all timesteps). >>> >>>> From what you describe, I am guessing that this is the issue. >>> In particular, variable timestepping + projection has some difficulties. >>> >>> With dealiasing and filtering, I never have problems with Torder=3, >>> and I would recommend using this. I concur, however, with Johan >>> that Torder=2 is more stable. (See the CRAS article with J. Mullen >>> in 2001.) >>> >>> I hope this helps - please let us know if problems persist. >>> >>> Paul >>> >>> >>> On Wed, 7 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >>> >>>> >>>> Dear All, >>>> >>>> I have been conducting a direct numerical simulation of turbulent pipe >>>> flow >>>> using nek5000 at a moderately high Reynolds number (at present >>>> Re_tau=550). >>>> For this, I have to use a very fine grid in order to capture the flow >>>> physics accurately (for a length of 25R, I am using a total of 450 >>>> million >>>> grid points when assuming a polynomial order 7). However, I have been >>>> having >>>> problems with the stability of the code when using TORDER = 3, i.e. >>>> parameter 027. The way I conducted my simulation was as follows: >>>> >>>> - I started with polynomial order 3, TORDER set to 3, and run for 4 flow >>>> through times, starting from random noise. At this point I had the >>>> projection parameters, i.e. P094 and P095 set to non-zero values. >>>> >>>> - Afterwards, I increased the polynomial order to 5, with TORDER kept at >>>> >>>> 3, >>>> and ran for another 2 flow through times. Here, I set the projection >>>> parameters P094 and P095 to zero. >>>> >>>> - Now, starting from the last field of the previous run, I changed to my >>>> target polynomial order 7, and keeping TORDER = 3. However, the codes >>>> explodes shortly after restarting. The error is: "failed in HMHOLTZ." >>>> I also tried a considerably lower time-step, but the problem persisted. >>>> Meanwhile, when I change TORDER to 2, the code runs fine and does not >>>> explode. The "physical" results are absolutely fine, and the statistics >>>> I >>>> get are in perfect agreement to our expectations. >>>> >>>> I did not get the same problem while running a turbulent pipe flow at a >>>> lower Reynolds number (Re_tau=180) and with less grid points. >>>> >>>> Probably also of importance, I did test with various ways of restarting, >>>> i.e. storing in fld or f files, using 4 or 8 byte accuracy, and storing >>>> multiple consecutive fields for the multi-step time scheme. None of >>>> these >>>> changes made significant impact. Also, I am using overintegration and >>>> filtering (0.01 in parameter P103); increasing the filtering (by a >>>> factor >>>> of >>>> 5) did also not help. >>>> >>>> I am wondering if any faced a similar issue before, and if would have an >>>> insight on how to tackle it. Could my problem maybe be related to the >>>> restart-issue that Adam brought up recently? >>>> >>>> Best regards >>>> George >>>> >>>> ---------------------------------------------------------------- >>>> This message was sent using IMP, the Internet Messaging Program. >>>> _______________________________________________ >>>> Nek5000-users mailing list >>>> Nek5000-users at lists.mcs.anl.gov >>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>> >> >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Fri Dec 9 08:07:22 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 09 Dec 2011 15:07:22 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> <20111207163805.11226tijj6k67nfh@www.mech.kth.se> Message-ID: <20111209150722.80955p873qx25fyy@www.mech.kth.se> Hi Stefan, Here is a part of a file I obtained from a run that failed with TORDER = 3. Regards George ------------------------------------------------------------------------------- 118 Parameters from file:/ 1 1.00000 P001: DENSITY 2 -9500. P002: VISCOS 7 1.00000 P007: RHOCP 8 1.00000 P008: CONDUCT 11 500.0 P011: NSTEPS 12 -5.000E-04 P012: DT 15 500.00 P015: IOSTEP 17 1.00000 P017: 18 0.500000E-01 P018: GRID < 0 --> # cells on screen 19 -1.00000 P019: INTYPE 20 10.0000 P020: NORDER 21 0.100000E-05 P021: DIVERGENCE 22 9.920000E-08 P022: HELMHOLTZ 24 0.100000E-01 P024: TOLREL 25 0.100000E-01 P025: TOLABS 26 1.00000 P026: COURANT/NTAU 27 3.00000 P027: TORDER 28 0.00000 P028: TORDER: mesh velocity (0: p28=p27) 54 -3.00000 P054: fixed flow rate dir: |p54|=1,2,3=x,y,z 55 1.00000 P055: vol.flow rate (p54>0) or Ubar (p54<0) 63 8.00000 P063: =8 --> force 8-byte output 65 6.00000 P065: #iofiles (eg, 0 or 64); <0 --> sep. dirs 66 6.00000 P066: output : <0=ascii, else binary 67 6.00000 P067: restart: <0=ascii, else binary 68 500.00 P068: iastep: freq for avg_all (0=iostep) 69 50000.0 P069: : : frequency of srf dump 93 20.0000 P093: Number of previous pressure solns saved 99 3.00000 P099: dealiasing: <0--> off/3--> old/4--> new 102 1.00000 P102: Dump out divergence at each time step 103 0.05000 P103: weight of stabilizing filter (.01) IFTRAN = T IFFLOW = T IFHEAT = F IFSPLIT = F IFLOMACH = F IFUSERVP = F IFUSERMV = F IFSTRS = F IFCHAR = T IFCYCLIC = F IFAXIS = F IFMVBD = F IFMELT = F IFMODEL = F IFKEPS = F IFMOAB = F IFNEKNEK = F IFSYNC = T IFVCOR = T IFINTQ = F IFCWUZ = F IFSWALL = F IFGEOM = F IFSURT = F IFWCNO = F IFTMSH for field 1 = F IFADVC for field 1 = T IFNONL for field 1 = F Dealiasing enabled, lxd= 12 Estimated eigenvalues EIGAA = 1.650197855862139 EIGGA = 71694413.86227663 EIGAE = 1.5791367041742943E-002 EIGAS = 7.9744816586921753E-004 EIGGE = 71694413.86227663 EIGGS = 2.000000000000000 verify mesh topology -1.000000000000000 1.000000000000000 Xrange -1.000000000000000 1.000000000000000 Yrange 0.000000000000000 25.00000000000002 Zrange done :: verify mesh topology E-solver strategy: 1 itr mg_nx: 1 5 7 mg_ny: 1 5 7 mg_nz: 1 5 7 call usrsetvert done :: usrsetvert gs_setup: 277536 unique labels shared pairwise times (avg, min, max): 0.000236133 0.000198293 0.000261211 crystal router : 0.000244021 0.000238085 0.00025022 used all_to_all method: crystal router setupds time 2.1331E-02 seconds 1 2 875808 853632 setvert3d: 4 16416864 23245920 16416864 16416864 call usrsetvert done :: usrsetvert gs_setup: 2635744 unique labels shared pairwise times (avg, min, max): 0.0004331 0.000362206 0.000494504 crystal router : 0.001126 0.0011049 0.00114682 used all_to_all method: pairwise setupds time 1.9091E-01 seconds 2 4 16416864 853632 setvert3d: 6 52620192 107252640 52620192 52620192 call usrsetvert done :: usrsetvert gs_setup: 7399328 unique labels shared pairwise times (avg, min, max): 0.000524018 0.000427318 0.000591493 crystal router : 0.00345075 0.0033884 0.0035347 used all_to_all method: pairwise setupds time 5.6218E-01 seconds 3 6 52620192 853632 setvert3d: 8 109485792 293870304 109485792 109485792 call usrsetvert done :: usrsetvert gs_setup: 14568288 unique labels shared pairwise times (avg, min, max): 0.00098448 0.000790119 0.00117922 crystal router : 0.00694697 0.00683801 0.00708301 used all_to_all method: pairwise setupds time 1.4705E+00 seconds 4 8 109485792 853632 setup h1 coarse grid, nx_crs= 2 call usrsetvert done :: usrsetvert gs_setup: 277536 unique labels shared pairwise times (avg, min, max): 0.000271898 0.000193095 0.000345087 crystal router : 0.000370127 0.000366497 0.000374007 used all_to_all method: pairwise done :: setup h1 coarse grid 562.8824191093445 sec call usrdat3 done :: usrdat3 set initial conditions Checking restart options: pipe?.f00001 Reading checkpoint data 0 0 OPEN: pipe0.f00001 byte swap: F 6.543210 -2.9312772E+35 850 0 OPEN: pipe5.f00001 510 0 OPEN: pipe3.f00001 170 0 OPEN: pipe1.f00001 1020 0 OPEN: pipe6.f00001 680 0 OPEN: pipe4.f00001 340 0 OPEN: pipe2.f00001 0 1.6225E+02 done :: Read checkpoint data avg data-throughput = -65.6MBps io-nodes = 6 xyz min -1.0000 -1.0000 0.0000 uvwpt min -0.43349 -0.45564 -0.77820E-01 0.69058E+08 0.0000 xyz max 1.0000 1.0000 25.000 uvwpt max 0.44557 0.38210 1.4216 0.69058E+08 0.0000 Restart: recompute geom. factors. regenerate geomerty data 1 vol_t,vol_v: 78.53976641971477 78.53976641971477 done :: regenerate geomerty data 1 done :: set initial conditions call userchk done :: userchk gridpoints unique/tot: 293870304 437059584 dofs: 291725280 184384512 Initial time: 0.1622500E+03 Initialization successfully completed 616.10 sec Starting time loop ... DT/DTCFL/DTFS/DTINIT 0.500E-03 0.494-323 0.299-316 0.500E-03 Step 1, t= 1.6225050E+02, DT= 5.0000000E-04, C= 0.251 0.0000E+00 0.0000E+00 Solving for fluid 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELX F: 1.0654E+00 9.9200E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELX F: 1.5163E-02 9.9200E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELX F: 1.6029E-03 9.9200E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELX F: 3.9700E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELX F: 1.4559E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELX F: 4.8307E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELX F: 1.5822E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELX F: 4.7557E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELX F: 1.4659E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELX F: 5.6372E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELX F: 1.6238E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELX F: 4.9454E-08 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELX: 11 4.9454E-08 1.0654E+00 9.9200E-08 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELY F: 1.0592E+00 9.9200E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELY F: 1.5106E-02 9.9200E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELY F: 1.6168E-03 9.9200E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELY F: 3.9446E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELY F: 1.4562E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELY F: 4.9132E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELY F: 1.5898E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELY F: 4.7011E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELY F: 1.4592E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELY F: 5.6658E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELY F: 1.6209E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELY F: 4.8705E-08 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELY: 11 4.8705E-08 1.0592E+00 9.9200E-08 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELZ F: 9.0867E-01 9.9200E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELZ F: 1.5203E-02 9.9200E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELZ F: 2.3594E-03 9.9200E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELZ F: 5.4341E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELZ F: 1.9420E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELZ F: 6.9938E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELZ F: 2.1336E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELZ F: 6.4972E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELZ F: 2.1068E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELZ F: 7.2366E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELZ F: 2.2873E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELZ F: 6.6523E-08 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELZ: 11 6.6523E-08 9.0867E-01 9.9200E-08 1 1.00000E-06 8.15804E-04 1.72021E-03 4.74246E-01 1 Divergence 2 1.00000E-06 4.25351E-04 1.72021E-03 2.47267E-01 1 Divergence 3 1.00000E-06 2.20250E-04 1.72021E-03 1.28037E-01 1 Divergence 4 1.00000E-06 1.10200E-04 1.72021E-03 6.40617E-02 1 Divergence 5 1.00000E-06 6.66356E-05 1.72021E-03 3.87369E-02 1 Divergence 6 1.00000E-06 4.55137E-05 1.72021E-03 2.64582E-02 1 Divergence 7 1.00000E-06 3.45979E-05 1.72021E-03 2.01126E-02 1 Divergence 8 1.00000E-06 2.74987E-05 1.72021E-03 1.59856E-02 1 Divergence 9 1.00000E-06 2.25703E-05 1.72021E-03 1.31207E-02 1 Divergence 10 1.00000E-06 1.84355E-05 1.72021E-03 1.07170E-02 1 Divergence 11 1.00000E-06 1.51102E-05 1.72021E-03 8.78394E-03 1 Divergence 12 1.00000E-06 1.23753E-05 1.72021E-03 7.19407E-03 1 Divergence 13 1.00000E-06 9.99015E-06 1.72021E-03 5.80751E-03 1 Divergence 14 1.00000E-06 7.91532E-06 1.72021E-03 4.60136E-03 1 Divergence 15 1.00000E-06 6.25368E-06 1.72021E-03 3.63541E-03 1 Divergence 16 1.00000E-06 4.91692E-06 1.72021E-03 2.85832E-03 1 Divergence 17 1.00000E-06 3.87115E-06 1.72021E-03 2.25039E-03 1 Divergence 18 1.00000E-06 3.04686E-06 1.72021E-03 1.77121E-03 1 Divergence 19 1.00000E-06 2.41971E-06 1.72021E-03 1.40663E-03 1 Divergence 20 1.00000E-06 1.93080E-06 1.72021E-03 1.12242E-03 1 Divergence 21 1.00000E-06 1.69768E-06 1.72021E-03 9.86902E-04 1 Divergence 22 1.00000E-06 1.48272E-06 1.72021E-03 8.61940E-04 1 Divergence 23 1.00000E-06 1.31245E-06 1.72021E-03 7.62959E-04 1 Divergence 24 1.00000E-06 1.15596E-06 1.72021E-03 6.71990E-04 1 Divergence 25 1.00000E-06 9.86100E-07 1.72021E-03 5.73243E-04 1 Divergence 1 U-PRES gmres: 25 9.8610E-07 1.0000E-06 1.7202E-03 9.0149E+00 1.6742E+01 1 DNORM, DIVEX 9.8609999662049055E-007 9.8609999670093433E-007 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELX F: 0.0000E+00 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELY F: 0.0000E+00 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 1 1 1 1 Helmholtz VELZ F: 9.9993E-01 9.9200E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELZ F: 3.4255E-02 9.9200E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELZ F: 8.5689E-03 9.9200E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELZ F: 2.0449E-03 9.9200E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELZ F: 8.2452E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELZ F: 2.5912E-04 9.9200E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELZ F: 8.5857E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELZ F: 2.4937E-05 9.9200E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELZ F: 8.7854E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELZ F: 3.0249E-06 9.9200E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELZ F: 9.2479E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELZ F: 3.0301E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 13 Helmholtz VELZ F: 1.0306E-07 9.9200E-08 1.0526E-04 2.0000E+03 1 14 Helmholtz VELZ F: 3.4387E-08 9.9200E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELZ: 13 3.4387E-08 9.9993E-01 9.9200E-08 1 1.00000E-04 8.48221E-11 1.31021E-10 6.47394E-01 0 Divergence 0 U-PRES gmres: 1 8.4822E-11 1.0000E-04 1.3102E-10 3.6466E-01 6.1275E-01 1 1.57007E-03 2.50000E+01 1.00000E+00 basflow Z 1 0.1622505E+03 6.74973E-03 1.05976E-05 3.14158E+00 3.14159E+00 volflow Z 1 1.6225E+02 2.5581E+01 Fluid done filt amp 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 filt trn 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 0.9500 schfile: /cfs/klemming/nobackup/g/georgeek/Pipe_550/pipe.sch Step 2, t= 1.6225100E+02, DT= 5.0000000E-04, C= 0.252 2.9590E+01 2.9590E+01 Solving for fluid 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELX: 10 2.6583E-08 1.5981E+00 9.9200E-08 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELY: 10 2.6270E-08 1.5887E+00 9.9200E-08 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELZ: 10 3.7961E-08 1.3628E+00 9.9200E-08 2 U-PRES gmres: 26 8.8941E-07 1.0000E-06 8.7570E-04 9.3625E+00 1.7342E+01 2 DNORM, DIVEX 8.8940552367860238E-007 8.8940552232510758E-007 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 2 1 2 Hmholtz VELZ: 11 2.9548E-08 9.9993E-01 9.9200E-08 0 U-PRES gmres: 1 5.0819E-11 1.0000E-04 7.6670E-11 3.6476E-01 6.1121E-01 2 1.04680E-03 2.50000E+01 1.00000E+00 basflow Z 2 0.1622510E+03 6.74912E-03 7.06497E-06 3.14158E+00 3.14159E+00 volflow Z 2 1.6225E+02 2.5493E+01 Fluid done Step 3, t= 1.6225150E+02, DT= 5.0000000E-04, C= 0.253 6.2005E+01 3.2415E+01 Solving for fluid 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELX: 9 5.9973E-08 1.9551E+00 9.9200E-08 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELY: 9 5.9734E-08 1.9436E+00 9.9200E-08 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELZ: 9 6.7060E-08 1.6769E+00 9.9200E-08 3 U-PRES gmres: 43 9.7341E-07 1.0000E-06 5.8253E-03 1.5480E+01 2.9163E+01 3 DNORM, DIVEX 9.7340773053122238E-007 9.7340773046898007E-007 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 9.9200000000000002E-008 p22 3 1 3 Hmholtz VELZ: 10 3.2545E-08 9.9993E-01 9.9200E-08 0 U-PRES gmres: 1 3.1707E-11 1.0000E-04 3.8884E-11 3.6436E-01 6.1134E-01 3 8.56501E-04 2.50000E+01 1.00000E+00 basflow Z 3 0.1622515E+03 6.74739E-03 5.77915E-06 3.14158E+00 3.14159E+00 volflow Z 3 1.6225E+02 3.6833E+01 Fluid done Step 4, t= 1.6225200E+02, DT= 5.0000000E-04, C= 0.253 1.0909E+02 4.7088E+01 Solving for fluid 9.9200000000000002E-008 p22 4 1 4 Hmholtz VELX: 9 5.1382E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 4 1 4 Hmholtz VELY: 9 5.1245E-08 1.9419E+00 9.9200E-08 9.9200000000000002E-008 p22 4 1 4 Hmholtz VELZ: 9 5.8121E-08 1.6656E+00 9.9200E-08 4 U-PRES gmres: 20 9.8736E-07 1.0000E-06 5.8401E-04 7.2002E+00 1.3507E+01 4 DNORM, DIVEX 9.8735913161531008E-007 9.8735912866392627E-007 4 0.1622520E+03 6.74462E-03 5.77677E-06 3.14158E+00 3.14159E+00 volflow Z 4 1.6225E+02 1.8072E+01 Fluid done Step 5, t= 1.6225250E+02, DT= 5.0000000E-04, C= 0.254 1.3731E+02 2.8220E+01 Solving for fluid 9.9200000000000002E-008 p22 5 1 5 Hmholtz VELX: 9 5.5907E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 5 1 5 Hmholtz VELY: 9 5.5659E-08 1.9419E+00 9.9200E-08 9.9200000000000002E-008 p22 5 1 5 Hmholtz VELZ: 9 5.9684E-08 1.6655E+00 9.9200E-08 5 U-PRES gmres: 16 9.2427E-07 1.0000E-06 1.5556E-04 5.7643E+00 1.0499E+01 5 DNORM, DIVEX 9.2426901539348950E-007 9.2426901307669303E-007 5 0.1622525E+03 6.74218E-03 5.77469E-06 3.14158E+00 3.14159E+00 volflow Z 5 1.6225E+02 1.5064E+01 Fluid done Step 6, t= 1.6225300E+02, DT= 5.0000000E-04, C= 0.255 1.6256E+02 2.5244E+01 Solving for fluid 9.9200000000000002E-008 p22 6 1 6 Hmholtz VELX: 9 6.0915E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 6 1 6 Hmholtz VELY: 9 6.0642E-08 1.9418E+00 9.9200E-08 9.9200000000000002E-008 p22 6 1 6 Hmholtz VELZ: 9 5.9861E-08 1.6655E+00 9.9200E-08 6 U-PRES gmres: 14 8.6298E-07 1.0000E-06 1.2403E-04 5.0438E+00 9.0451E+00 6 DNORM, DIVEX 8.6297683366363408E-007 8.6297681628504936E-007 6 0.1622530E+03 6.73975E-03 5.77261E-06 3.14158E+00 3.14159E+00 volflow Z 6 1.6225E+02 1.3610E+01 Fluid done Step 7, t= 1.6225350E+02, DT= 5.0000000E-04, C= 0.255 1.8632E+02 2.3767E+01 Solving for fluid 9.9200000000000002E-008 p22 7 1 7 Hmholtz VELX: 9 7.2389E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 7 1 7 Hmholtz VELY: 9 7.1978E-08 1.9418E+00 9.9200E-08 9.9200000000000002E-008 p22 7 1 7 Hmholtz VELZ: 9 6.0336E-08 1.6654E+00 9.9200E-08 7 U-PRES gmres: 14 7.8284E-07 1.0000E-06 1.2790E-04 5.0456E+00 9.0568E+00 7 DNORM, DIVEX 7.8284171959673956E-007 7.8284171260985997E-007 7 0.1622535E+03 6.73731E-03 5.77052E-06 3.14158E+00 3.14159E+00 volflow Z 7 1.6225E+02 1.3620E+01 Fluid done Step 8, t= 1.6225400E+02, DT= 5.0000000E-04, C= 0.256 2.1010E+02 2.3780E+01 Solving for fluid 9.9200000000000002E-008 p22 8 1 8 Hmholtz VELX: 9 8.0530E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 8 1 8 Hmholtz VELY: 9 8.0474E-08 1.9418E+00 9.9200E-08 9.9200000000000002E-008 p22 8 1 8 Hmholtz VELZ: 9 6.1838E-08 1.6654E+00 9.9200E-08 8 U-PRES gmres: 13 9.3871E-07 1.0000E-06 8.2637E-05 4.6862E+00 8.3450E+00 8 DNORM, DIVEX 9.3870751505892285E-007 9.3870750972531774E-007 8 0.1622540E+03 6.73487E-03 5.76843E-06 3.14158E+00 3.14159E+00 volflow Z 8 1.6225E+02 1.2911E+01 Fluid done Step 9, t= 1.6225450E+02, DT= 5.0000000E-04, C= 0.257 2.3318E+02 2.3081E+01 Solving for fluid 9.9200000000000002E-008 p22 9 1 9 Hmholtz VELX: 9 8.5197E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 9 1 9 Hmholtz VELY: 9 8.4881E-08 1.9418E+00 9.9200E-08 9.9200000000000002E-008 p22 9 1 9 Hmholtz VELZ: 9 6.3849E-08 1.6654E+00 9.9200E-08 9 U-PRES gmres: 10 8.0419E-07 1.0000E-06 5.5243E-05 3.6054E+00 6.2748E+00 9 DNORM, DIVEX 8.0418938467388352E-007 8.0418939044644440E-007 9 0.1622545E+03 6.73242E-03 5.76633E-06 3.14158E+00 3.14159E+00 volflow Z 9 1.6225E+02 1.0838E+01 Fluid done Step 10, t= 1.6225500E+02, DT= 5.0000000E-04, C= 0.257 2.5418E+02 2.0995E+01 Solving for fluid 9.9200000000000002E-008 p22 10 1 10 Hmholtz VELX: 9 8.7316E-08 1.9533E+00 9.9200E-08 9.9200000000000002E-008 p22 10 1 10 Hmholtz VELY: 9 8.7257E-08 1.9418E+00 9.9200E-08 9.9200000000000002E-008 p22 10 1 10 Hmholtz VELZ: 9 6.5276E-08 1.6654E+00 9.9200E-08 10 U-PRES gmres: 14 7.9070E-07 1.0000E-06 5.7631E-05 5.0451E+00 9.0540E+00 10 DNORM, DIVEX 7.9069874056473697E-007 7.9069875187583686E-007 10 0.1622550E+03 6.72998E-03 5.76424E-06 3.14158E+00 3.14159E+00 volflow Z 10 1.6225E+02 1.3620E+01 Fluid done Step 11, t= 1.6225550E+02, DT= 5.0000000E-04, C= 0.258 2.7885E+02 2.4675E+01 Solving for fluid 11 100 **ERROR**: Failed in HMHOLTZ: VELX 7.9521E+07 1.9533E+00 9.9200E-08 11 100 **ERROR**: Failed in HMHOLTZ: VELY 2.8223E+03 1.9418E+00 9.9200E-08 11 Hmholtz VELZ: 9 6.6283E-08 1.6654E+00 9.9200E-08 11 U-PRES gmres: 100 1.6296E+02 1.0000E-06 2.6253E+12 3.6002E+01 6.8265E+01 11 DNORM, DIVEX 54998323.86255041 162.9642641112922 11 0.1622555E+03 4.32525E-03 3.70458E-06 3.14159E+00 3.14159E+00 volflow Z 11 1.6226E+02 9.4526E+01 Fluid done CFL, Ctarg! 11083557069312.66 1.000000000000000 call outfld: ifpsco: F 12 1.6226E+02 Write checkpoint: call outfld: ifpsco: F 12 1.6226E+02 Write checkpoint: 0 12 OPEN: pipe0.f00001 850 12 OPEN: pipe5.f00001 510 12 OPEN: pipe3.f00001 170 12 OPEN: pipe1.f00001 1020 12 OPEN: pipe6.f00001 680 12 OPEN: pipe4.f00001 340 12 OPEN: pipe2.f00001 12 1.6226E+02 done :: Write checkpoint file size = 234.E+02MB 899 Emergency exit: 12 time = 162.2554999999999 512 Emergency exit: 12 time = 162.2554999999999 459 Emergency exit: 12 time = 162.2554999999999 Latest solution and data are dumped for post-processing. *** STOP *** 461 Emergency exit: 12 time = 162.2554999999999 Latest solution and data are dumped for post-processing. *** STOP *** ------------------------------------------------------------------------------- Quoting nek5000-users at lists.mcs.anl.gov: > Geroge, > > Can you provide more details. A logfile would be helpful. > > Cheers, > Stefan ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From nek5000-users at lists.mcs.anl.gov Fri Dec 9 10:28:32 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 9 Dec 2011 17:28:32 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: <20111209150722.80955p873qx25fyy@www.mech.kth.se> References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> <20111207163805.11226tijj6k67nfh@www.mech.kth.se> <20111209150722.80955p873qx25fyy@www.mech.kth.se> Message-ID: George, Can you do a run using single 4 byte .fXXXXX file using just one IO-node. Also, turn off the characteristics scheme (IFCHAR). Then try to do a restart again. Cheers, Stefan On 12/9/11, nek5000-users at lists.mcs.anl.gov wrote: > > Hi Stefan, > > Here is a part of a file I obtained from a run that failed with TORDER = 3. > > Regards > George > > ------------------------------------------------------------------------------- > 118 Parameters from file:/ > 1 1.00000 P001: DENSITY > 2 -9500. P002: VISCOS > 7 1.00000 P007: RHOCP > 8 1.00000 P008: CONDUCT > 11 500.0 P011: NSTEPS > 12 -5.000E-04 P012: DT > 15 500.00 P015: IOSTEP > 17 1.00000 P017: > 18 0.500000E-01 P018: GRID < 0 --> # cells on screen > 19 -1.00000 P019: INTYPE > 20 10.0000 P020: NORDER > 21 0.100000E-05 P021: DIVERGENCE > 22 9.920000E-08 P022: HELMHOLTZ > 24 0.100000E-01 P024: TOLREL > 25 0.100000E-01 P025: TOLABS > 26 1.00000 P026: COURANT/NTAU > 27 3.00000 P027: TORDER > 28 0.00000 P028: TORDER: mesh velocity (0: p28=p27) > 54 -3.00000 P054: fixed flow rate dir: |p54|=1,2,3=x,y,z > 55 1.00000 P055: vol.flow rate (p54>0) or Ubar (p54<0) > 63 8.00000 P063: =8 --> force 8-byte output > 65 6.00000 P065: #iofiles (eg, 0 or 64); <0 --> sep. dirs > 66 6.00000 P066: output : <0=ascii, else binary > 67 6.00000 P067: restart: <0=ascii, else binary > 68 500.00 P068: iastep: freq for avg_all (0=iostep) > 69 50000.0 P069: : : frequency of srf dump > 93 20.0000 P093: Number of previous pressure solns saved > 99 3.00000 P099: dealiasing: <0--> off/3--> old/4--> new > 102 1.00000 P102: Dump out divergence at each time step > 103 0.05000 P103: weight of stabilizing filter (.01) > > IFTRAN = T > IFFLOW = T > IFHEAT = F > IFSPLIT = F > IFLOMACH = F > IFUSERVP = F > IFUSERMV = F > IFSTRS = F > IFCHAR = T > IFCYCLIC = F > IFAXIS = F > IFMVBD = F > IFMELT = F > IFMODEL = F > IFKEPS = F > IFMOAB = F > IFNEKNEK = F > IFSYNC = T > > IFVCOR = T > IFINTQ = F > IFCWUZ = F > IFSWALL = F > IFGEOM = F > IFSURT = F > IFWCNO = F > > IFTMSH for field 1 = F > IFADVC for field 1 = T > IFNONL for field 1 = F > > Dealiasing enabled, lxd= 12 > > Estimated eigenvalues > EIGAA = 1.650197855862139 > EIGGA = 71694413.86227663 > EIGAE = 1.5791367041742943E-002 > EIGAS = 7.9744816586921753E-004 > EIGGE = 71694413.86227663 > EIGGS = 2.000000000000000 > > verify mesh topology > -1.000000000000000 1.000000000000000 Xrange > -1.000000000000000 1.000000000000000 Yrange > 0.000000000000000 25.00000000000002 Zrange > done :: verify mesh topology > > E-solver strategy: 1 itr > mg_nx: 1 5 7 > mg_ny: 1 5 7 > mg_nz: 1 5 7 > call usrsetvert > done :: usrsetvert > > gs_setup: 277536 unique labels shared > pairwise times (avg, min, max): 0.000236133 0.000198293 0.000261211 > crystal router : 0.000244021 0.000238085 0.00025022 > used all_to_all method: crystal router > setupds time 2.1331E-02 seconds 1 2 875808 853632 > setvert3d: 4 16416864 23245920 16416864 16416864 > call usrsetvert > done :: usrsetvert > > gs_setup: 2635744 unique labels shared > pairwise times (avg, min, max): 0.0004331 0.000362206 0.000494504 > crystal router : 0.001126 0.0011049 0.00114682 > used all_to_all method: pairwise > setupds time 1.9091E-01 seconds 2 4 16416864 853632 > setvert3d: 6 52620192 107252640 52620192 52620192 > call usrsetvert > done :: usrsetvert > > gs_setup: 7399328 unique labels shared > pairwise times (avg, min, max): 0.000524018 0.000427318 0.000591493 > crystal router : 0.00345075 0.0033884 0.0035347 > used all_to_all method: pairwise > setupds time 5.6218E-01 seconds 3 6 52620192 853632 > setvert3d: 8 109485792 293870304 109485792 109485792 > call usrsetvert > done :: usrsetvert > > gs_setup: 14568288 unique labels shared > pairwise times (avg, min, max): 0.00098448 0.000790119 0.00117922 > crystal router : 0.00694697 0.00683801 0.00708301 > used all_to_all method: pairwise > setupds time 1.4705E+00 seconds 4 8 109485792 853632 > setup h1 coarse grid, nx_crs= 2 > call usrsetvert > done :: usrsetvert > > gs_setup: 277536 unique labels shared > pairwise times (avg, min, max): 0.000271898 0.000193095 0.000345087 > crystal router : 0.000370127 0.000366497 0.000374007 > used all_to_all method: pairwise > done :: setup h1 coarse grid 562.8824191093445 sec > > call usrdat3 > done :: usrdat3 > > set initial conditions > Checking restart options: pipe?.f00001 > Reading checkpoint data > 0 0 OPEN: pipe0.f00001 > byte swap: F 6.543210 -2.9312772E+35 > 850 0 OPEN: pipe5.f00001 > 510 0 OPEN: pipe3.f00001 > 170 0 OPEN: pipe1.f00001 > 1020 0 OPEN: pipe6.f00001 > 680 0 OPEN: pipe4.f00001 > 340 0 OPEN: pipe2.f00001 > > 0 1.6225E+02 done :: Read checkpoint data > avg data-throughput = -65.6MBps > io-nodes = 6 > > xyz min -1.0000 -1.0000 0.0000 > uvwpt min -0.43349 -0.45564 -0.77820E-01 0.69058E+08 0.0000 > xyz max 1.0000 1.0000 25.000 > uvwpt max 0.44557 0.38210 1.4216 0.69058E+08 0.0000 > Restart: recompute geom. factors. > regenerate geomerty data 1 > vol_t,vol_v: 78.53976641971477 78.53976641971477 > done :: regenerate geomerty data 1 > > done :: set initial conditions > > call userchk > done :: userchk > > gridpoints unique/tot: 293870304 437059584 > dofs: 291725280 184384512 > > Initial time: 0.1622500E+03 > Initialization successfully completed 616.10 sec > > Starting time loop ... > > DT/DTCFL/DTFS/DTINIT 0.500E-03 0.494-323 0.299-316 0.500E-03 > Step 1, t= 1.6225050E+02, DT= 5.0000000E-04, C= 0.251 0.0000E+00 > 0.0000E+00 > Solving for fluid > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELX F: 1.0654E+00 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 2 Helmholtz VELX F: 1.5163E-02 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 3 Helmholtz VELX F: 1.6029E-03 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 4 Helmholtz VELX F: 3.9700E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 5 Helmholtz VELX F: 1.4559E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 6 Helmholtz VELX F: 4.8307E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 7 Helmholtz VELX F: 1.5822E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 8 Helmholtz VELX F: 4.7557E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 9 Helmholtz VELX F: 1.4659E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 10 Helmholtz VELX F: 5.6372E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 11 Helmholtz VELX F: 1.6238E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 12 Helmholtz VELX F: 4.9454E-08 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELX: 11 4.9454E-08 1.0654E+00 9.9200E-08 > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELY F: 1.0592E+00 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 2 Helmholtz VELY F: 1.5106E-02 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 3 Helmholtz VELY F: 1.6168E-03 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 4 Helmholtz VELY F: 3.9446E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 5 Helmholtz VELY F: 1.4562E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 6 Helmholtz VELY F: 4.9132E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 7 Helmholtz VELY F: 1.5898E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 8 Helmholtz VELY F: 4.7011E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 9 Helmholtz VELY F: 1.4592E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 10 Helmholtz VELY F: 5.6658E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 11 Helmholtz VELY F: 1.6209E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 12 Helmholtz VELY F: 4.8705E-08 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELY: 11 4.8705E-08 1.0592E+00 9.9200E-08 > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELZ F: 9.0867E-01 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 2 Helmholtz VELZ F: 1.5203E-02 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 3 Helmholtz VELZ F: 2.3594E-03 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 4 Helmholtz VELZ F: 5.4341E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 5 Helmholtz VELZ F: 1.9420E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 6 Helmholtz VELZ F: 6.9938E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 7 Helmholtz VELZ F: 2.1336E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 8 Helmholtz VELZ F: 6.4972E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 9 Helmholtz VELZ F: 2.1068E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 10 Helmholtz VELZ F: 7.2366E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 11 Helmholtz VELZ F: 2.2873E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 12 Helmholtz VELZ F: 6.6523E-08 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELZ: 11 6.6523E-08 9.0867E-01 9.9200E-08 > 1 1.00000E-06 8.15804E-04 1.72021E-03 4.74246E-01 1 Divergence > 2 1.00000E-06 4.25351E-04 1.72021E-03 2.47267E-01 1 Divergence > 3 1.00000E-06 2.20250E-04 1.72021E-03 1.28037E-01 1 Divergence > 4 1.00000E-06 1.10200E-04 1.72021E-03 6.40617E-02 1 Divergence > 5 1.00000E-06 6.66356E-05 1.72021E-03 3.87369E-02 1 Divergence > 6 1.00000E-06 4.55137E-05 1.72021E-03 2.64582E-02 1 Divergence > 7 1.00000E-06 3.45979E-05 1.72021E-03 2.01126E-02 1 Divergence > 8 1.00000E-06 2.74987E-05 1.72021E-03 1.59856E-02 1 Divergence > 9 1.00000E-06 2.25703E-05 1.72021E-03 1.31207E-02 1 Divergence > 10 1.00000E-06 1.84355E-05 1.72021E-03 1.07170E-02 1 Divergence > 11 1.00000E-06 1.51102E-05 1.72021E-03 8.78394E-03 1 Divergence > 12 1.00000E-06 1.23753E-05 1.72021E-03 7.19407E-03 1 Divergence > 13 1.00000E-06 9.99015E-06 1.72021E-03 5.80751E-03 1 Divergence > 14 1.00000E-06 7.91532E-06 1.72021E-03 4.60136E-03 1 Divergence > 15 1.00000E-06 6.25368E-06 1.72021E-03 3.63541E-03 1 Divergence > 16 1.00000E-06 4.91692E-06 1.72021E-03 2.85832E-03 1 Divergence > 17 1.00000E-06 3.87115E-06 1.72021E-03 2.25039E-03 1 Divergence > 18 1.00000E-06 3.04686E-06 1.72021E-03 1.77121E-03 1 Divergence > 19 1.00000E-06 2.41971E-06 1.72021E-03 1.40663E-03 1 Divergence > 20 1.00000E-06 1.93080E-06 1.72021E-03 1.12242E-03 1 Divergence > 21 1.00000E-06 1.69768E-06 1.72021E-03 9.86902E-04 1 Divergence > 22 1.00000E-06 1.48272E-06 1.72021E-03 8.61940E-04 1 Divergence > 23 1.00000E-06 1.31245E-06 1.72021E-03 7.62959E-04 1 Divergence > 24 1.00000E-06 1.15596E-06 1.72021E-03 6.71990E-04 1 Divergence > 25 1.00000E-06 9.86100E-07 1.72021E-03 5.73243E-04 1 Divergence > 1 U-PRES gmres: 25 9.8610E-07 1.0000E-06 1.7202E-03 > 9.0149E+00 1.6742E+01 > 1 DNORM, DIVEX 9.8609999662049055E-007 > 9.8609999670093433E-007 > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELX F: 0.0000E+00 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELY F: 0.0000E+00 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 1 1 > 1 1 Helmholtz VELZ F: 9.9993E-01 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 2 Helmholtz VELZ F: 3.4255E-02 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 3 Helmholtz VELZ F: 8.5689E-03 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 4 Helmholtz VELZ F: 2.0449E-03 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 5 Helmholtz VELZ F: 8.2452E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 6 Helmholtz VELZ F: 2.5912E-04 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 7 Helmholtz VELZ F: 8.5857E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 8 Helmholtz VELZ F: 2.4937E-05 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 9 Helmholtz VELZ F: 8.7854E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 10 Helmholtz VELZ F: 3.0249E-06 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 11 Helmholtz VELZ F: 9.2479E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 12 Helmholtz VELZ F: 3.0301E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 13 Helmholtz VELZ F: 1.0306E-07 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 14 Helmholtz VELZ F: 3.4387E-08 9.9200E-08 1.0526E-04 > 2.0000E+03 > 1 Hmholtz VELZ: 13 3.4387E-08 9.9993E-01 9.9200E-08 > 1 1.00000E-04 8.48221E-11 1.31021E-10 6.47394E-01 0 Divergence > 0 U-PRES gmres: 1 8.4822E-11 1.0000E-04 1.3102E-10 > 3.6466E-01 6.1275E-01 > 1 1.57007E-03 2.50000E+01 1.00000E+00 basflow Z > 1 0.1622505E+03 6.74973E-03 1.05976E-05 3.14158E+00 > 3.14159E+00 volflow Z > 1 1.6225E+02 2.5581E+01 Fluid done > filt amp 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 > filt trn 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 0.9500 > schfile: > /cfs/klemming/nobackup/g/georgeek/Pipe_550/pipe.sch > Step 2, t= 1.6225100E+02, DT= 5.0000000E-04, C= 0.252 2.9590E+01 > 2.9590E+01 > Solving for fluid > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELX: 10 2.6583E-08 1.5981E+00 9.9200E-08 > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELY: 10 2.6270E-08 1.5887E+00 9.9200E-08 > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELZ: 10 3.7961E-08 1.3628E+00 9.9200E-08 > 2 U-PRES gmres: 26 8.8941E-07 1.0000E-06 8.7570E-04 > 9.3625E+00 1.7342E+01 > 2 DNORM, DIVEX 8.8940552367860238E-007 > 8.8940552232510758E-007 > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 2 1 > 2 Hmholtz VELZ: 11 2.9548E-08 9.9993E-01 9.9200E-08 > 0 U-PRES gmres: 1 5.0819E-11 1.0000E-04 7.6670E-11 > 3.6476E-01 6.1121E-01 > 2 1.04680E-03 2.50000E+01 1.00000E+00 basflow Z > 2 0.1622510E+03 6.74912E-03 7.06497E-06 3.14158E+00 > 3.14159E+00 volflow Z > 2 1.6225E+02 2.5493E+01 Fluid done > Step 3, t= 1.6225150E+02, DT= 5.0000000E-04, C= 0.253 6.2005E+01 > 3.2415E+01 > Solving for fluid > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELX: 9 5.9973E-08 1.9551E+00 9.9200E-08 > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELY: 9 5.9734E-08 1.9436E+00 9.9200E-08 > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELZ: 9 6.7060E-08 1.6769E+00 9.9200E-08 > 3 U-PRES gmres: 43 9.7341E-07 1.0000E-06 5.8253E-03 > 1.5480E+01 2.9163E+01 > 3 DNORM, DIVEX 9.7340773053122238E-007 > 9.7340773046898007E-007 > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 > 9.9200000000000002E-008 p22 3 1 > 3 Hmholtz VELZ: 10 3.2545E-08 9.9993E-01 9.9200E-08 > 0 U-PRES gmres: 1 3.1707E-11 1.0000E-04 3.8884E-11 > 3.6436E-01 6.1134E-01 > 3 8.56501E-04 2.50000E+01 1.00000E+00 basflow Z > 3 0.1622515E+03 6.74739E-03 5.77915E-06 3.14158E+00 > 3.14159E+00 volflow Z > 3 1.6225E+02 3.6833E+01 Fluid done > Step 4, t= 1.6225200E+02, DT= 5.0000000E-04, C= 0.253 1.0909E+02 > 4.7088E+01 > Solving for fluid > 9.9200000000000002E-008 p22 4 1 > 4 Hmholtz VELX: 9 5.1382E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 4 1 > 4 Hmholtz VELY: 9 5.1245E-08 1.9419E+00 9.9200E-08 > 9.9200000000000002E-008 p22 4 1 > 4 Hmholtz VELZ: 9 5.8121E-08 1.6656E+00 9.9200E-08 > 4 U-PRES gmres: 20 9.8736E-07 1.0000E-06 5.8401E-04 > 7.2002E+00 1.3507E+01 > 4 DNORM, DIVEX 9.8735913161531008E-007 > 9.8735912866392627E-007 > 4 0.1622520E+03 6.74462E-03 5.77677E-06 3.14158E+00 > 3.14159E+00 volflow Z > 4 1.6225E+02 1.8072E+01 Fluid done > Step 5, t= 1.6225250E+02, DT= 5.0000000E-04, C= 0.254 1.3731E+02 > 2.8220E+01 > Solving for fluid > 9.9200000000000002E-008 p22 5 1 > 5 Hmholtz VELX: 9 5.5907E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 5 1 > 5 Hmholtz VELY: 9 5.5659E-08 1.9419E+00 9.9200E-08 > 9.9200000000000002E-008 p22 5 1 > 5 Hmholtz VELZ: 9 5.9684E-08 1.6655E+00 9.9200E-08 > 5 U-PRES gmres: 16 9.2427E-07 1.0000E-06 1.5556E-04 > 5.7643E+00 1.0499E+01 > 5 DNORM, DIVEX 9.2426901539348950E-007 > 9.2426901307669303E-007 > 5 0.1622525E+03 6.74218E-03 5.77469E-06 3.14158E+00 > 3.14159E+00 volflow Z > 5 1.6225E+02 1.5064E+01 Fluid done > Step 6, t= 1.6225300E+02, DT= 5.0000000E-04, C= 0.255 1.6256E+02 > 2.5244E+01 > Solving for fluid > 9.9200000000000002E-008 p22 6 1 > 6 Hmholtz VELX: 9 6.0915E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 6 1 > 6 Hmholtz VELY: 9 6.0642E-08 1.9418E+00 9.9200E-08 > 9.9200000000000002E-008 p22 6 1 > 6 Hmholtz VELZ: 9 5.9861E-08 1.6655E+00 9.9200E-08 > 6 U-PRES gmres: 14 8.6298E-07 1.0000E-06 1.2403E-04 > 5.0438E+00 9.0451E+00 > 6 DNORM, DIVEX 8.6297683366363408E-007 > 8.6297681628504936E-007 > 6 0.1622530E+03 6.73975E-03 5.77261E-06 3.14158E+00 > 3.14159E+00 volflow Z > 6 1.6225E+02 1.3610E+01 Fluid done > Step 7, t= 1.6225350E+02, DT= 5.0000000E-04, C= 0.255 1.8632E+02 > 2.3767E+01 > Solving for fluid > 9.9200000000000002E-008 p22 7 1 > 7 Hmholtz VELX: 9 7.2389E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 7 1 > 7 Hmholtz VELY: 9 7.1978E-08 1.9418E+00 9.9200E-08 > 9.9200000000000002E-008 p22 7 1 > 7 Hmholtz VELZ: 9 6.0336E-08 1.6654E+00 9.9200E-08 > 7 U-PRES gmres: 14 7.8284E-07 1.0000E-06 1.2790E-04 > 5.0456E+00 9.0568E+00 > 7 DNORM, DIVEX 7.8284171959673956E-007 > 7.8284171260985997E-007 > 7 0.1622535E+03 6.73731E-03 5.77052E-06 3.14158E+00 > 3.14159E+00 volflow Z > 7 1.6225E+02 1.3620E+01 Fluid done > Step 8, t= 1.6225400E+02, DT= 5.0000000E-04, C= 0.256 2.1010E+02 > 2.3780E+01 > Solving for fluid > 9.9200000000000002E-008 p22 8 1 > 8 Hmholtz VELX: 9 8.0530E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 8 1 > 8 Hmholtz VELY: 9 8.0474E-08 1.9418E+00 9.9200E-08 > 9.9200000000000002E-008 p22 8 1 > 8 Hmholtz VELZ: 9 6.1838E-08 1.6654E+00 9.9200E-08 > 8 U-PRES gmres: 13 9.3871E-07 1.0000E-06 8.2637E-05 > 4.6862E+00 8.3450E+00 > 8 DNORM, DIVEX 9.3870751505892285E-007 > 9.3870750972531774E-007 > 8 0.1622540E+03 6.73487E-03 5.76843E-06 3.14158E+00 > 3.14159E+00 volflow Z > 8 1.6225E+02 1.2911E+01 Fluid done > Step 9, t= 1.6225450E+02, DT= 5.0000000E-04, C= 0.257 2.3318E+02 > 2.3081E+01 > Solving for fluid > 9.9200000000000002E-008 p22 9 1 > 9 Hmholtz VELX: 9 8.5197E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 9 1 > 9 Hmholtz VELY: 9 8.4881E-08 1.9418E+00 9.9200E-08 > 9.9200000000000002E-008 p22 9 1 > 9 Hmholtz VELZ: 9 6.3849E-08 1.6654E+00 9.9200E-08 > 9 U-PRES gmres: 10 8.0419E-07 1.0000E-06 5.5243E-05 > 3.6054E+00 6.2748E+00 > 9 DNORM, DIVEX 8.0418938467388352E-007 > 8.0418939044644440E-007 > 9 0.1622545E+03 6.73242E-03 5.76633E-06 3.14158E+00 > 3.14159E+00 volflow Z > 9 1.6225E+02 1.0838E+01 Fluid done > Step 10, t= 1.6225500E+02, DT= 5.0000000E-04, C= 0.257 2.5418E+02 > 2.0995E+01 > Solving for fluid > 9.9200000000000002E-008 p22 10 1 > 10 Hmholtz VELX: 9 8.7316E-08 1.9533E+00 9.9200E-08 > 9.9200000000000002E-008 p22 10 1 > 10 Hmholtz VELY: 9 8.7257E-08 1.9418E+00 9.9200E-08 > 9.9200000000000002E-008 p22 10 1 > 10 Hmholtz VELZ: 9 6.5276E-08 1.6654E+00 9.9200E-08 > 10 U-PRES gmres: 14 7.9070E-07 1.0000E-06 5.7631E-05 > 5.0451E+00 9.0540E+00 > 10 DNORM, DIVEX 7.9069874056473697E-007 > 7.9069875187583686E-007 > 10 0.1622550E+03 6.72998E-03 5.76424E-06 3.14158E+00 > 3.14159E+00 volflow Z > 10 1.6225E+02 1.3620E+01 Fluid done > Step 11, t= 1.6225550E+02, DT= 5.0000000E-04, C= 0.258 2.7885E+02 > 2.4675E+01 > Solving for fluid > 11 100 **ERROR**: Failed in HMHOLTZ: VELX 7.9521E+07 > 1.9533E+00 9.9200E-08 > 11 100 **ERROR**: Failed in HMHOLTZ: VELY 2.8223E+03 > 1.9418E+00 9.9200E-08 > 11 Hmholtz VELZ: 9 6.6283E-08 1.6654E+00 9.9200E-08 > 11 U-PRES gmres: 100 1.6296E+02 1.0000E-06 2.6253E+12 > 3.6002E+01 6.8265E+01 > 11 DNORM, DIVEX 54998323.86255041 162.9642641112922 > 11 0.1622555E+03 4.32525E-03 3.70458E-06 3.14159E+00 > 3.14159E+00 volflow Z > 11 1.6226E+02 9.4526E+01 Fluid done > CFL, Ctarg! 11083557069312.66 1.000000000000000 > call outfld: ifpsco: F > > 12 1.6226E+02 Write checkpoint: > > call outfld: ifpsco: F > > 12 1.6226E+02 Write checkpoint: > 0 12 OPEN: pipe0.f00001 > 850 12 OPEN: pipe5.f00001 > 510 12 OPEN: pipe3.f00001 > 170 12 OPEN: pipe1.f00001 > 1020 12 OPEN: pipe6.f00001 > 680 12 OPEN: pipe4.f00001 > 340 12 OPEN: pipe2.f00001 > > 12 1.6226E+02 done :: Write checkpoint > file size = 234.E+02MB > > 899 Emergency exit: 12 time = 162.2554999999999 > > 512 Emergency exit: 12 time = 162.2554999999999 > > 459 Emergency exit: 12 time = 162.2554999999999 > Latest solution and data are dumped for post-processing. > *** STOP *** > 461 Emergency exit: 12 time = 162.2554999999999 > Latest solution and data are dumped for post-processing. > *** STOP *** > > ------------------------------------------------------------------------------- > > Quoting nek5000-users at lists.mcs.anl.gov: > >> Geroge, >> >> Can you provide more details. A logfile would be helpful. >> >> Cheers, >> Stefan > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Fri Dec 9 12:11:27 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 09 Dec 2011 19:11:27 +0100 Subject: [Nek5000-users] Failure with TORDER = 3 (P027) In-Reply-To: References: <20111207145358.57299dpe5pezsqgm@www.mech.kth.se> <20111207163805.11226tijj6k67nfh@www.mech.kth.se> <20111209150722.80955p873qx25fyy@www.mech.kth.se> Message-ID: <20111209191127.3153737fhe1lddn3@www.mech.kth.se> Hi Stefan, I did runs before with single 4byte (this included both types of restart files, the .fldXX and the .fXXXXX) and they failed. I tried a simulation with IFCHAR = F, but it didn't help. Regards George 118 Parameters from file:/cfs 1 1.00000 P001: DENSITY 2 -9500. P002: VISCOS 7 1.00000 P007: RHOCP 8 1.00000 P008: CONDUCT 11 500.0 P011: NSTEPS 12 -5.000E-04 P012: DT 15 500.00 P015: IOSTEP 17 1.00000 P017: 18 0.500000E-01 P018: GRID < 0 --> # cells on screen 19 -1.00000 P019: INTYPE 20 10.0000 P020: NORDER 21 6.97000E-07 P021: DIVERGENCE 22 3.91000E-08 P022: HELMHOLTZ 24 0.100000E-01 P024: TOLREL 25 0.100000E-01 P025: TOLABS 26 1.00000 P026: COURANT/NTAU 27 3.00000 P027: TORDER 28 0.00000 P028: TORDER: mesh velocity (0: p28=p27) 54 -3.00000 P054: fixed flow rate dir: |p54|=1,2,3=x,y,z 55 1.00000 P055: vol.flow rate (p54>0) or Ubar (p54<0) 63 8.00000 P063: =8 --> force 8-byte output 65 1.00000 P065: #iofiles (eg, 0 or 64); <0 --> sep. dirs 66 4.00000 P066: output : <0=ascii, else binary 67 4.00000 P067: restart: <0=ascii, else binary 68 500.00 P068: iastep: freq for avg_all (0=iostep) 69 50000.0 P069: : : frequency of srf dump 93 20.0000 P093: Number of previous pressure solns saved 99 3.00000 P099: dealiasing: <0--> off/3--> old/4--> new 102 1.00000 P102: Dump out divergence at each time step 103 0.05000 P103: weight of stabilizing filter (.01) IFTRAN = T IFFLOW = T IFHEAT = F IFSPLIT = F IFLOMACH = F IFUSERVP = F IFUSERMV = F IFSTRS = F IFCHAR = F IFCYCLIC = F IFAXIS = F IFMVBD = F IFMELT = F IFMODEL = F IFKEPS = F IFMOAB = F IFNEKNEK = F IFSYNC = T IFVCOR = T IFINTQ = F IFCWUZ = F IFSWALL = F IFGEOM = F IFSURT = F IFWCNO = F IFTMSH for field 1 = F IFADVC for field 1 = T IFNONL for field 1 = F Dealiasing enabled, lxd= 12 Estimated eigenvalues EIGAA = 1.650197855862139 EIGGA = 71694413.86227663 EIGAE = 1.5791367041742943E-002 EIGAS = 7.9744816586921753E-004 EIGGE = 71694413.86227663 EIGGS = 2.000000000000000 verify mesh topology -1.000000000000000 1.000000000000000 Xrange -1.000000000000000 1.000000000000000 Yrange 0.000000000000000 25.00000000000002 Zrange done :: verify mesh topology E-solver strategy: 1 itr mg_nx: 1 5 7 mg_ny: 1 5 7 mg_nz: 1 5 7 call usrsetvert done :: usrsetvert gs_setup: 277536 unique labels shared pairwise times (avg, min, max): 0.000217676 0.000179911 0.000260091 crystal router : 0.000397386 0.000384593 0.000415206 used all_to_all method: pairwise setupds time 2.3977E-02 seconds 1 2 875808 853632 setvert3d: 4 16416864 23245920 16416864 16416864 call usrsetvert done :: usrsetvert gs_setup: 2635744 unique labels shared pairwise times (avg, min, max): 0.000402858 0.000331998 0.000490713 crystal router : 0.00114883 0.00112629 0.00117478 used all_to_all method: pairwise setupds time 1.7600E-01 seconds 2 4 16416864 853632 setvert3d: 6 52620192 107252640 52620192 52620192 call usrsetvert done :: usrsetvert gs_setup: 7399328 unique labels shared pairwise times (avg, min, max): 0.000520725 0.000422287 0.000607514 crystal router : 0.00361464 0.00353529 0.0037215 used all_to_all method: pairwise setupds time 5.4703E-01 seconds 3 6 52620192 853632 setvert3d: 8 109485792 293870304 109485792 109485792 call usrsetvert done :: usrsetvert gs_setup: 14568288 unique labels shared pairwise times (avg, min, max): 0.000940861 0.000729108 0.00109351 crystal router : 0.0069962 0.006883 0.007128 used all_to_all method: pairwise setupds time 1.4284E+00 seconds 4 8 109485792 853632 setup h1 coarse grid, nx_crs= 2 call usrsetvert done :: usrsetvert gs_setup: 277536 unique labels shared pairwise times (avg, min, max): 0.000215451 0.000180602 0.0002491 crystal router : 0.000217089 0.000212789 0.000222802 used all_to_all method: crystal router done :: setup h1 coarse grid 564.0989270210266 sec call usrdat3 done :: usrdat3 set initial conditions Checking restart options: pipe.fld00 Reading checkpoint data byte swap: F 6.543210 -2.9312772E+35 Read mode: 4.000000000000000 neltr,nxr,nyr,nzr: 853632 8 8 8 Restarting from file pipe.fld00 Columns for restart data U,V,W,P,T,S,N: 4 5 6 7 0 0 7 Reading 1 Reading 10001 Reading 20001 Reading 30001 Reading 40001 Reading 50001 Reading 60001 Reading 70001 Reading 80001 Reading 90001 Reading 100001 Reading 110001 Reading 120001 Reading 130001 Reading 140001 Reading 150001 Reading 160001 Reading 170001 Reading 180001 Reading 190001 Reading 200001 Reading 210001 Reading 220001 Reading 230001 Reading 240001 Reading 250001 Reading 260001 Reading 270001 Reading 280001 Reading 290001 Reading 300001 Reading 310001 Reading 320001 Reading 330001 Reading 340001 Reading 350001 Reading 360001 Reading 370001 Reading 380001 Reading 390001 Reading 400001 Reading 410001 Reading 420001 Reading 430001 Reading 440001 Reading 450001 Reading 460001 Reading 470001 Reading 480001 Reading 490001 Reading 500001 Reading 510001 Reading 520001 Reading 530001 Reading 540001 Reading 550001 Reading 560001 Reading 570001 Reading 580001 Reading 590001 Reading 600001 Reading 610001 Reading 620001 Reading 630001 Reading 640001 Reading 650001 Reading 660001 Reading 670001 Reading 680001 Reading 690001 Reading 700001 Reading 710001 Reading 720001 Reading 730001 Reading 740001 Reading 750001 Reading 760001 Reading 770001 Reading 780001 Reading 790001 Reading 800001 Reading 810001 Reading 820001 Reading 830001 Reading 840001 Reading 850001 Successfully read data from dump number 1. xyz min -1.0000 -1.0000 0.0000 uvwpt min -0.47295 -0.47385 -0.70747E-01 0.69058E+08 0.0000 xyz max 1.0000 1.0000 25.000 uvwpt max 0.41327 0.43558 1.4154 0.69058E+08 0.0000 Restart: recompute geom. factors. regenerate geomerty data 1 vol_t,vol_v: 78.53976645402923 78.53976645402923 done :: regenerate geomerty data 1 done :: set initial conditions call userchk done :: userchk gridpoints unique/tot: 293870304 437059584 dofs: 291725280 184384512 Initial time: 0.1630000E+03 Initialization successfully completed 744.39 sec Starting time loop ... DT/DTCFL/DTFS/DTINIT 0.500E-03 0.494-323 0.299-316 0.500E-03 Step 1, t= 1.6300050E+02, DT= 5.0000000E-04, C= 0.265 0.0000E+00 0.0000E+00 Solving for fluid 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELX F: 1.0764E+00 3.9100E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELX F: 1.5181E-02 3.9100E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELX F: 1.2884E-03 3.9100E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELX F: 3.3662E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELX F: 1.1417E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELX F: 4.1989E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELX F: 1.2416E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELX F: 4.3828E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELX F: 1.2547E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELX F: 4.4060E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELX F: 1.5341E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELX F: 4.5290E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 13 Helmholtz VELX F: 1.7132E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELX: 12 1.7132E-08 1.0764E+00 3.9100E-08 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELY F: 1.0734E+00 3.9100E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELY F: 1.5151E-02 3.9100E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELY F: 1.2884E-03 3.9100E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELY F: 3.3554E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELY F: 1.1416E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELY F: 4.2265E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELY F: 1.2415E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELY F: 4.3557E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELY F: 1.2475E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELY F: 4.4262E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELY F: 1.5405E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELY F: 4.5188E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 13 Helmholtz VELY F: 1.7139E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELY: 12 1.7139E-08 1.0734E+00 3.9100E-08 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELZ F: 9.1190E-01 3.9100E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELZ F: 1.5421E-02 3.9100E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELZ F: 2.3950E-03 3.9100E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELZ F: 5.6307E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELZ F: 2.0207E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELZ F: 7.3327E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELZ F: 2.2459E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELZ F: 7.0171E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELZ F: 2.2581E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELZ F: 7.6724E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELZ F: 2.5555E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELZ F: 7.3426E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 13 Helmholtz VELZ F: 2.6479E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELZ: 12 2.6479E-08 9.1190E-01 3.9100E-08 1 6.97000E-07 9.38347E-03 1.07416E-02 8.73561E-01 1 Divergence 2 6.97000E-07 6.99275E-03 1.07416E-02 6.50995E-01 1 Divergence 3 6.97000E-07 5.35367E-03 1.07416E-02 4.98405E-01 1 Divergence 4 6.97000E-07 4.17851E-03 1.07416E-02 3.89002E-01 1 Divergence 5 6.97000E-07 3.58459E-03 1.07416E-02 3.33711E-01 1 Divergence 6 6.97000E-07 3.11414E-03 1.07416E-02 2.89913E-01 1 Divergence 7 6.97000E-07 2.61270E-03 1.07416E-02 2.43231E-01 1 Divergence 8 6.97000E-07 2.10346E-03 1.07416E-02 1.95824E-01 1 Divergence 9 6.97000E-07 1.68746E-03 1.07416E-02 1.57096E-01 1 Divergence 10 6.97000E-07 1.36517E-03 1.07416E-02 1.27092E-01 1 Divergence 11 6.97000E-07 1.09952E-03 1.07416E-02 1.02360E-01 1 Divergence 12 6.97000E-07 8.82762E-04 1.07416E-02 8.21815E-02 1 Divergence 13 6.97000E-07 6.90225E-04 1.07416E-02 6.42571E-02 1 Divergence 14 6.97000E-07 5.44279E-04 1.07416E-02 5.06701E-02 1 Divergence 15 6.97000E-07 4.32713E-04 1.07416E-02 4.02837E-02 1 Divergence 16 6.97000E-07 3.43981E-04 1.07416E-02 3.20232E-02 1 Divergence 17 6.97000E-07 2.71675E-04 1.07416E-02 2.52918E-02 1 Divergence 18 6.97000E-07 2.22506E-04 1.07416E-02 2.07144E-02 1 Divergence 19 6.97000E-07 1.83569E-04 1.07416E-02 1.70895E-02 1 Divergence 20 6.97000E-07 1.50434E-04 1.07416E-02 1.40048E-02 1 Divergence 21 6.97000E-07 1.33491E-04 1.07416E-02 1.24275E-02 1 Divergence 22 6.97000E-07 1.17538E-04 1.07416E-02 1.09423E-02 1 Divergence 23 6.97000E-07 1.03720E-04 1.07416E-02 9.65593E-03 1 Divergence 24 6.97000E-07 9.06332E-05 1.07416E-02 8.43757E-03 1 Divergence 25 6.97000E-07 7.81647E-05 1.07416E-02 7.27680E-03 1 Divergence 26 6.97000E-07 6.48416E-05 1.07416E-02 6.03649E-03 1 Divergence 27 6.97000E-07 5.41612E-05 1.07416E-02 5.04218E-03 1 Divergence 28 6.97000E-07 4.51610E-05 1.07416E-02 4.20430E-03 1 Divergence 29 6.97000E-07 3.72104E-05 1.07416E-02 3.46413E-03 1 Divergence 30 6.97000E-07 2.96862E-05 1.07416E-02 2.76366E-03 1 Divergence 31 6.97000E-07 2.37038E-05 1.07416E-02 2.20673E-03 1 Divergence 32 6.97000E-07 1.90892E-05 1.07416E-02 1.77713E-03 1 Divergence 33 6.97000E-07 1.53081E-05 1.07416E-02 1.42512E-03 1 Divergence 34 6.97000E-07 1.19893E-05 1.07416E-02 1.11615E-03 1 Divergence 35 6.97000E-07 9.22878E-06 1.07416E-02 8.59161E-04 1 Divergence 36 6.97000E-07 7.21590E-06 1.07416E-02 6.71770E-04 1 Divergence 37 6.97000E-07 5.57207E-06 1.07416E-02 5.18736E-04 1 Divergence 38 6.97000E-07 4.24959E-06 1.07416E-02 3.95620E-04 1 Divergence 39 6.97000E-07 3.35840E-06 1.07416E-02 3.12653E-04 1 Divergence 40 6.97000E-07 2.75992E-06 1.07416E-02 2.56937E-04 1 Divergence 41 6.97000E-07 2.48393E-06 1.07416E-02 2.31244E-04 1 Divergence 42 6.97000E-07 2.21978E-06 1.07416E-02 2.06652E-04 1 Divergence 43 6.97000E-07 1.92655E-06 1.07416E-02 1.79354E-04 1 Divergence 44 6.97000E-07 1.64569E-06 1.07416E-02 1.53207E-04 1 Divergence 45 6.97000E-07 1.39375E-06 1.07416E-02 1.29752E-04 1 Divergence 46 6.97000E-07 1.13485E-06 1.07416E-02 1.05649E-04 1 Divergence 47 6.97000E-07 9.31679E-07 1.07416E-02 8.67354E-05 1 Divergence 48 6.97000E-07 7.70014E-07 1.07416E-02 7.16851E-05 1 Divergence 49 6.97000E-07 6.32830E-07 1.07416E-02 5.89138E-05 1 Divergence 1 U-PRES gmres: 49 6.3283E-07 6.9700E-07 1.0742E-02 1.7663E+01 3.2017E+01 1 DNORM, DIVEX 6.3283009986342846E-007 6.3283009983826269E-007 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELX F: 0.0000E+00 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELY F: 0.0000E+00 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 1 1 1 1 Helmholtz VELZ F: 9.9993E-01 3.9100E-08 1.0526E-04 2.0000E+03 1 2 Helmholtz VELZ F: 3.4256E-02 3.9100E-08 1.0526E-04 2.0000E+03 1 3 Helmholtz VELZ F: 8.5689E-03 3.9100E-08 1.0526E-04 2.0000E+03 1 4 Helmholtz VELZ F: 2.0449E-03 3.9100E-08 1.0526E-04 2.0000E+03 1 5 Helmholtz VELZ F: 8.2452E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 6 Helmholtz VELZ F: 2.5912E-04 3.9100E-08 1.0526E-04 2.0000E+03 1 7 Helmholtz VELZ F: 8.5855E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 8 Helmholtz VELZ F: 2.4936E-05 3.9100E-08 1.0526E-04 2.0000E+03 1 9 Helmholtz VELZ F: 8.7849E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 10 Helmholtz VELZ F: 3.0247E-06 3.9100E-08 1.0526E-04 2.0000E+03 1 11 Helmholtz VELZ F: 9.2473E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 12 Helmholtz VELZ F: 3.0298E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 13 Helmholtz VELZ F: 1.0305E-07 3.9100E-08 1.0526E-04 2.0000E+03 1 14 Helmholtz VELZ F: 3.4384E-08 3.9100E-08 1.0526E-04 2.0000E+03 1 Hmholtz VELZ: 13 3.4384E-08 9.9993E-01 3.9100E-08 1 1.00000E-04 8.48170E-11 1.31016E-10 6.47379E-01 0 Divergence 0 U-PRES gmres: 1 8.4817E-11 1.0000E-04 1.3102E-10 3.6395E-01 6.0687E-01 1 1.57007E-03 2.50000E+01 1.00000E+00 basflow Z 1 0.1630005E+03 6.76646E-03 1.06238E-05 3.14158E+00 3.14159E+00 volflow Z 1 1.6300E+02 4.2939E+01 Fluid done filt amp 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 filt trn 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 0.9500 schfile: /cfs/klemming/nobackup/g/georgeek/Pipe_550/pipe.sch Step 2, t= 1.6300100E+02, DT= 5.0000000E-04, C= 0.266 4.6703E+01 4.6703E+01 Solving for fluid 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELX: 10 2.7917E-08 1.5986E+00 3.9100E-08 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELY: 10 2.7685E-08 1.5941E+00 3.9100E-08 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELZ: 11 1.1825E-08 1.3662E+00 3.9100E-08 2 U-PRES gmres: 30 5.8658E-07 6.9700E-07 9.6007E-04 1.0743E+01 1.8863E+01 2 DNORM, DIVEX 5.8657654334453548E-007 5.8657654183056372E-007 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 2 1 2 Hmholtz VELZ: 11 2.9546E-08 9.9993E-01 3.9100E-08 0 U-PRES gmres: 1 5.0816E-11 1.0000E-04 7.6665E-11 3.6302E-01 6.0612E-01 2 1.04680E-03 2.50000E+01 1.00000E+00 basflow Z 2 0.1630010E+03 6.76588E-03 7.08253E-06 3.14158E+00 3.14159E+00 volflow Z 2 1.6300E+02 2.8100E+01 Fluid done Step 3, t= 1.6300150E+02, DT= 5.0000000E-04, C= 0.267 7.7150E+01 3.0447E+01 Solving for fluid 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELX: 10 2.2287E-08 1.9558E+00 3.9100E-08 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELY: 10 2.2187E-08 1.9504E+00 3.9100E-08 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELZ: 10 1.9504E-08 1.6812E+00 3.9100E-08 3 U-PRES gmres: 46 6.2075E-07 6.9700E-07 5.9016E-03 1.6469E+01 2.9191E+01 3 DNORM, DIVEX 6.2074611064574755E-007 6.2074610903560854E-007 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 3.9100E-08 3.9099999999999999E-008 p22 3 1 3 Hmholtz VELZ: 10 3.2542E-08 9.9993E-01 3.9100E-08 0 U-PRES gmres: 1 3.1706E-11 1.0000E-04 3.8883E-11 3.6437E-01 6.0709E-01 3 8.56501E-04 2.50000E+01 1.00000E+00 basflow Z 3 0.1630015E+03 6.76414E-03 5.79350E-06 3.14158E+00 3.14159E+00 volflow Z 3 1.6300E+02 3.8096E+01 Fluid done Step 4, t= 1.6300200E+02, DT= 5.0000000E-04, C= 0.267 1.1723E+02 4.0079E+01 Solving for fluid 3.9099999999999999E-008 p22 4 1 4 Hmholtz VELX: 10 3.4704E-08 1.9540E+00 3.9100E-08 3.9099999999999999E-008 p22 4 1 4 Hmholtz VELY: 10 3.4346E-08 1.9485E+00 3.9100E-08 3.9099999999999999E-008 p22 4 1 4 Hmholtz VELZ: 10 1.7982E-08 1.6695E+00 3.9100E-08 4 U-PRES gmres: 23 6.5944E-07 6.9700E-07 5.4153E-04 8.2398E+00 1.4582E+01 4 DNORM, DIVEX 6.5944402063993297E-007 6.5944402093381349E-007 4 0.1630020E+03 6.76139E-03 5.79114E-06 3.14158E+00 3.14159E+00 volflow Z 4 1.6300E+02 2.0115E+01 Fluid done Step 5, t= 1.6300250E+02, DT= 5.0000000E-04, C= 0.268 1.3936E+02 2.2129E+01 Solving for fluid 3.9099999999999999E-008 p22 5 1 5 100 **ERROR**: Failed in HMHOLTZ: VELX 4.6165E+07 1.9538E+00 3.9100E-08 3.9099999999999999E-008 p22 5 1 5 100 **ERROR**: Failed in HMHOLTZ: VELY 1.5363E+06 1.9483E+00 3.9100E-08 3.9099999999999999E-008 p22 5 1 5 Hmholtz VELZ: 10 2.1234E-08 1.6693E+00 3.9100E-08 5 U-PRES gmres: 100 1.6287E+02 6.9700E-07 2.8049E+12 3.5805E+01 6.3973E+01 5 DNORM, DIVEX 90256688.76909679 162.8677243951093 5 0.1630025E+03 5.97476E-03 5.11739E-06 3.14159E+00 3.14159E+00 volflow Z 5 1.6300E+02 9.3713E+01 Fluid done CFL, Ctarg! 10694544583364.97 0.5000000000000000 Quoting nek5000-users at lists.mcs.anl.gov: > George, > > Can you do a run using single 4 byte .fXXXXX file using just one > IO-node. Also, turn off the characteristics scheme (IFCHAR). Then try > to do a restart again. > > Cheers, > Stefan > > On 12/9/11, nek5000-users at lists.mcs.anl.gov > wrote: >> >> Hi Stefan, >> >> Here is a part of a file I obtained from a run that failed with TORDER = 3. >> >> Regards >> George >> >> ------------------------------------------------------------------------------- >> 118 Parameters from file:/ >> 1 1.00000 P001: DENSITY >> 2 -9500. P002: VISCOS >> 7 1.00000 P007: RHOCP >> 8 1.00000 P008: CONDUCT >> 11 500.0 P011: NSTEPS >> 12 -5.000E-04 P012: DT >> 15 500.00 P015: IOSTEP >> 17 1.00000 P017: >> 18 0.500000E-01 P018: GRID < 0 --> # cells on screen >> 19 -1.00000 P019: INTYPE >> 20 10.0000 P020: NORDER >> 21 0.100000E-05 P021: DIVERGENCE >> 22 9.920000E-08 P022: HELMHOLTZ >> 24 0.100000E-01 P024: TOLREL >> 25 0.100000E-01 P025: TOLABS >> 26 1.00000 P026: COURANT/NTAU >> 27 3.00000 P027: TORDER >> 28 0.00000 P028: TORDER: mesh velocity (0: p28=p27) >> 54 -3.00000 P054: fixed flow rate dir: |p54|=1,2,3=x,y,z >> 55 1.00000 P055: vol.flow rate (p54>0) or Ubar (p54<0) >> 63 8.00000 P063: =8 --> force 8-byte output >> 65 6.00000 P065: #iofiles (eg, 0 or 64); <0 --> sep. dirs >> 66 6.00000 P066: output : <0=ascii, else binary >> 67 6.00000 P067: restart: <0=ascii, else binary >> 68 500.00 P068: iastep: freq for avg_all (0=iostep) >> 69 50000.0 P069: : : frequency of srf dump >> 93 20.0000 P093: Number of previous pressure solns saved >> 99 3.00000 P099: dealiasing: <0--> off/3--> old/4--> new >> 102 1.00000 P102: Dump out divergence at each time step >> 103 0.05000 P103: weight of stabilizing filter (.01) >> >> IFTRAN = T >> IFFLOW = T >> IFHEAT = F >> IFSPLIT = F >> IFLOMACH = F >> IFUSERVP = F >> IFUSERMV = F >> IFSTRS = F >> IFCHAR = T >> IFCYCLIC = F >> IFAXIS = F >> IFMVBD = F >> IFMELT = F >> IFMODEL = F >> IFKEPS = F >> IFMOAB = F >> IFNEKNEK = F >> IFSYNC = T >> >> IFVCOR = T >> IFINTQ = F >> IFCWUZ = F >> IFSWALL = F >> IFGEOM = F >> IFSURT = F >> IFWCNO = F >> >> IFTMSH for field 1 = F >> IFADVC for field 1 = T >> IFNONL for field 1 = F >> >> Dealiasing enabled, lxd= 12 >> >> Estimated eigenvalues >> EIGAA = 1.650197855862139 >> EIGGA = 71694413.86227663 >> EIGAE = 1.5791367041742943E-002 >> EIGAS = 7.9744816586921753E-004 >> EIGGE = 71694413.86227663 >> EIGGS = 2.000000000000000 >> >> verify mesh topology >> -1.000000000000000 1.000000000000000 Xrange >> -1.000000000000000 1.000000000000000 Yrange >> 0.000000000000000 25.00000000000002 Zrange >> done :: verify mesh topology >> >> E-solver strategy: 1 itr >> mg_nx: 1 5 7 >> mg_ny: 1 5 7 >> mg_nz: 1 5 7 >> call usrsetvert >> done :: usrsetvert >> >> gs_setup: 277536 unique labels shared >> pairwise times (avg, min, max): 0.000236133 0.000198293 0.000261211 >> crystal router : 0.000244021 0.000238085 0.00025022 >> used all_to_all method: crystal router >> setupds time 2.1331E-02 seconds 1 2 875808 853632 >> setvert3d: 4 16416864 23245920 16416864 16416864 >> call usrsetvert >> done :: usrsetvert >> >> gs_setup: 2635744 unique labels shared >> pairwise times (avg, min, max): 0.0004331 0.000362206 0.000494504 >> crystal router : 0.001126 0.0011049 0.00114682 >> used all_to_all method: pairwise >> setupds time 1.9091E-01 seconds 2 4 16416864 853632 >> setvert3d: 6 52620192 107252640 52620192 52620192 >> call usrsetvert >> done :: usrsetvert >> >> gs_setup: 7399328 unique labels shared >> pairwise times (avg, min, max): 0.000524018 0.000427318 0.000591493 >> crystal router : 0.00345075 0.0033884 0.0035347 >> used all_to_all method: pairwise >> setupds time 5.6218E-01 seconds 3 6 52620192 853632 >> setvert3d: 8 109485792 293870304 109485792 109485792 >> call usrsetvert >> done :: usrsetvert >> >> gs_setup: 14568288 unique labels shared >> pairwise times (avg, min, max): 0.00098448 0.000790119 0.00117922 >> crystal router : 0.00694697 0.00683801 0.00708301 >> used all_to_all method: pairwise >> setupds time 1.4705E+00 seconds 4 8 109485792 853632 >> setup h1 coarse grid, nx_crs= 2 >> call usrsetvert >> done :: usrsetvert >> >> gs_setup: 277536 unique labels shared >> pairwise times (avg, min, max): 0.000271898 0.000193095 0.000345087 >> crystal router : 0.000370127 0.000366497 0.000374007 >> used all_to_all method: pairwise >> done :: setup h1 coarse grid 562.8824191093445 sec >> >> call usrdat3 >> done :: usrdat3 >> >> set initial conditions >> Checking restart options: pipe?.f00001 >> Reading checkpoint data >> 0 0 OPEN: pipe0.f00001 >> byte swap: F 6.543210 -2.9312772E+35 >> 850 0 OPEN: pipe5.f00001 >> 510 0 OPEN: pipe3.f00001 >> 170 0 OPEN: pipe1.f00001 >> 1020 0 OPEN: pipe6.f00001 >> 680 0 OPEN: pipe4.f00001 >> 340 0 OPEN: pipe2.f00001 >> >> 0 1.6225E+02 done :: Read checkpoint data >> avg data-throughput = -65.6MBps >> io-nodes = 6 >> >> xyz min -1.0000 -1.0000 0.0000 >> uvwpt min -0.43349 -0.45564 -0.77820E-01 0.69058E+08 0.0000 >> xyz max 1.0000 1.0000 25.000 >> uvwpt max 0.44557 0.38210 1.4216 0.69058E+08 0.0000 >> Restart: recompute geom. factors. >> regenerate geomerty data 1 >> vol_t,vol_v: 78.53976641971477 78.53976641971477 >> done :: regenerate geomerty data 1 >> >> done :: set initial conditions >> >> call userchk >> done :: userchk >> >> gridpoints unique/tot: 293870304 437059584 >> dofs: 291725280 184384512 >> >> Initial time: 0.1622500E+03 >> Initialization successfully completed 616.10 sec >> >> Starting time loop ... >> >> DT/DTCFL/DTFS/DTINIT 0.500E-03 0.494-323 0.299-316 0.500E-03 >> Step 1, t= 1.6225050E+02, DT= 5.0000000E-04, C= 0.251 0.0000E+00 >> 0.0000E+00 >> Solving for fluid >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELX F: 1.0654E+00 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 2 Helmholtz VELX F: 1.5163E-02 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 3 Helmholtz VELX F: 1.6029E-03 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 4 Helmholtz VELX F: 3.9700E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 5 Helmholtz VELX F: 1.4559E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 6 Helmholtz VELX F: 4.8307E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 7 Helmholtz VELX F: 1.5822E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 8 Helmholtz VELX F: 4.7557E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 9 Helmholtz VELX F: 1.4659E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 10 Helmholtz VELX F: 5.6372E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 11 Helmholtz VELX F: 1.6238E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 12 Helmholtz VELX F: 4.9454E-08 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELX: 11 4.9454E-08 1.0654E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELY F: 1.0592E+00 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 2 Helmholtz VELY F: 1.5106E-02 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 3 Helmholtz VELY F: 1.6168E-03 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 4 Helmholtz VELY F: 3.9446E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 5 Helmholtz VELY F: 1.4562E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 6 Helmholtz VELY F: 4.9132E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 7 Helmholtz VELY F: 1.5898E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 8 Helmholtz VELY F: 4.7011E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 9 Helmholtz VELY F: 1.4592E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 10 Helmholtz VELY F: 5.6658E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 11 Helmholtz VELY F: 1.6209E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 12 Helmholtz VELY F: 4.8705E-08 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELY: 11 4.8705E-08 1.0592E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELZ F: 9.0867E-01 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 2 Helmholtz VELZ F: 1.5203E-02 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 3 Helmholtz VELZ F: 2.3594E-03 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 4 Helmholtz VELZ F: 5.4341E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 5 Helmholtz VELZ F: 1.9420E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 6 Helmholtz VELZ F: 6.9938E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 7 Helmholtz VELZ F: 2.1336E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 8 Helmholtz VELZ F: 6.4972E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 9 Helmholtz VELZ F: 2.1068E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 10 Helmholtz VELZ F: 7.2366E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 11 Helmholtz VELZ F: 2.2873E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 12 Helmholtz VELZ F: 6.6523E-08 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELZ: 11 6.6523E-08 9.0867E-01 9.9200E-08 >> 1 1.00000E-06 8.15804E-04 1.72021E-03 4.74246E-01 1 Divergence >> 2 1.00000E-06 4.25351E-04 1.72021E-03 2.47267E-01 1 Divergence >> 3 1.00000E-06 2.20250E-04 1.72021E-03 1.28037E-01 1 Divergence >> 4 1.00000E-06 1.10200E-04 1.72021E-03 6.40617E-02 1 Divergence >> 5 1.00000E-06 6.66356E-05 1.72021E-03 3.87369E-02 1 Divergence >> 6 1.00000E-06 4.55137E-05 1.72021E-03 2.64582E-02 1 Divergence >> 7 1.00000E-06 3.45979E-05 1.72021E-03 2.01126E-02 1 Divergence >> 8 1.00000E-06 2.74987E-05 1.72021E-03 1.59856E-02 1 Divergence >> 9 1.00000E-06 2.25703E-05 1.72021E-03 1.31207E-02 1 Divergence >> 10 1.00000E-06 1.84355E-05 1.72021E-03 1.07170E-02 1 Divergence >> 11 1.00000E-06 1.51102E-05 1.72021E-03 8.78394E-03 1 Divergence >> 12 1.00000E-06 1.23753E-05 1.72021E-03 7.19407E-03 1 Divergence >> 13 1.00000E-06 9.99015E-06 1.72021E-03 5.80751E-03 1 Divergence >> 14 1.00000E-06 7.91532E-06 1.72021E-03 4.60136E-03 1 Divergence >> 15 1.00000E-06 6.25368E-06 1.72021E-03 3.63541E-03 1 Divergence >> 16 1.00000E-06 4.91692E-06 1.72021E-03 2.85832E-03 1 Divergence >> 17 1.00000E-06 3.87115E-06 1.72021E-03 2.25039E-03 1 Divergence >> 18 1.00000E-06 3.04686E-06 1.72021E-03 1.77121E-03 1 Divergence >> 19 1.00000E-06 2.41971E-06 1.72021E-03 1.40663E-03 1 Divergence >> 20 1.00000E-06 1.93080E-06 1.72021E-03 1.12242E-03 1 Divergence >> 21 1.00000E-06 1.69768E-06 1.72021E-03 9.86902E-04 1 Divergence >> 22 1.00000E-06 1.48272E-06 1.72021E-03 8.61940E-04 1 Divergence >> 23 1.00000E-06 1.31245E-06 1.72021E-03 7.62959E-04 1 Divergence >> 24 1.00000E-06 1.15596E-06 1.72021E-03 6.71990E-04 1 Divergence >> 25 1.00000E-06 9.86100E-07 1.72021E-03 5.73243E-04 1 Divergence >> 1 U-PRES gmres: 25 9.8610E-07 1.0000E-06 1.7202E-03 >> 9.0149E+00 1.6742E+01 >> 1 DNORM, DIVEX 9.8609999662049055E-007 >> 9.8609999670093433E-007 >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELX F: 0.0000E+00 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELY F: 0.0000E+00 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 1 1 >> 1 1 Helmholtz VELZ F: 9.9993E-01 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 2 Helmholtz VELZ F: 3.4255E-02 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 3 Helmholtz VELZ F: 8.5689E-03 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 4 Helmholtz VELZ F: 2.0449E-03 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 5 Helmholtz VELZ F: 8.2452E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 6 Helmholtz VELZ F: 2.5912E-04 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 7 Helmholtz VELZ F: 8.5857E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 8 Helmholtz VELZ F: 2.4937E-05 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 9 Helmholtz VELZ F: 8.7854E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 10 Helmholtz VELZ F: 3.0249E-06 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 11 Helmholtz VELZ F: 9.2479E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 12 Helmholtz VELZ F: 3.0301E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 13 Helmholtz VELZ F: 1.0306E-07 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 14 Helmholtz VELZ F: 3.4387E-08 9.9200E-08 1.0526E-04 >> 2.0000E+03 >> 1 Hmholtz VELZ: 13 3.4387E-08 9.9993E-01 9.9200E-08 >> 1 1.00000E-04 8.48221E-11 1.31021E-10 6.47394E-01 0 Divergence >> 0 U-PRES gmres: 1 8.4822E-11 1.0000E-04 1.3102E-10 >> 3.6466E-01 6.1275E-01 >> 1 1.57007E-03 2.50000E+01 1.00000E+00 basflow Z >> 1 0.1622505E+03 6.74973E-03 1.05976E-05 3.14158E+00 >> 3.14159E+00 volflow Z >> 1 1.6225E+02 2.5581E+01 Fluid done >> filt amp 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 >> filt trn 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 0.9500 >> schfile: >> /cfs/klemming/nobackup/g/georgeek/Pipe_550/pipe.sch >> Step 2, t= 1.6225100E+02, DT= 5.0000000E-04, C= 0.252 2.9590E+01 >> 2.9590E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELX: 10 2.6583E-08 1.5981E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELY: 10 2.6270E-08 1.5887E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELZ: 10 3.7961E-08 1.3628E+00 9.9200E-08 >> 2 U-PRES gmres: 26 8.8941E-07 1.0000E-06 8.7570E-04 >> 9.3625E+00 1.7342E+01 >> 2 DNORM, DIVEX 8.8940552367860238E-007 >> 8.8940552232510758E-007 >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 2 1 >> 2 Hmholtz VELZ: 11 2.9548E-08 9.9993E-01 9.9200E-08 >> 0 U-PRES gmres: 1 5.0819E-11 1.0000E-04 7.6670E-11 >> 3.6476E-01 6.1121E-01 >> 2 1.04680E-03 2.50000E+01 1.00000E+00 basflow Z >> 2 0.1622510E+03 6.74912E-03 7.06497E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 2 1.6225E+02 2.5493E+01 Fluid done >> Step 3, t= 1.6225150E+02, DT= 5.0000000E-04, C= 0.253 6.2005E+01 >> 3.2415E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELX: 9 5.9973E-08 1.9551E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELY: 9 5.9734E-08 1.9436E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELZ: 9 6.7060E-08 1.6769E+00 9.9200E-08 >> 3 U-PRES gmres: 43 9.7341E-07 1.0000E-06 5.8253E-03 >> 1.5480E+01 2.9163E+01 >> 3 DNORM, DIVEX 9.7340773053122238E-007 >> 9.7340773046898007E-007 >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELX: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELY: 0 0.0000E+00 0.0000E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 3 1 >> 3 Hmholtz VELZ: 10 3.2545E-08 9.9993E-01 9.9200E-08 >> 0 U-PRES gmres: 1 3.1707E-11 1.0000E-04 3.8884E-11 >> 3.6436E-01 6.1134E-01 >> 3 8.56501E-04 2.50000E+01 1.00000E+00 basflow Z >> 3 0.1622515E+03 6.74739E-03 5.77915E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 3 1.6225E+02 3.6833E+01 Fluid done >> Step 4, t= 1.6225200E+02, DT= 5.0000000E-04, C= 0.253 1.0909E+02 >> 4.7088E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 4 1 >> 4 Hmholtz VELX: 9 5.1382E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 4 1 >> 4 Hmholtz VELY: 9 5.1245E-08 1.9419E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 4 1 >> 4 Hmholtz VELZ: 9 5.8121E-08 1.6656E+00 9.9200E-08 >> 4 U-PRES gmres: 20 9.8736E-07 1.0000E-06 5.8401E-04 >> 7.2002E+00 1.3507E+01 >> 4 DNORM, DIVEX 9.8735913161531008E-007 >> 9.8735912866392627E-007 >> 4 0.1622520E+03 6.74462E-03 5.77677E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 4 1.6225E+02 1.8072E+01 Fluid done >> Step 5, t= 1.6225250E+02, DT= 5.0000000E-04, C= 0.254 1.3731E+02 >> 2.8220E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 5 1 >> 5 Hmholtz VELX: 9 5.5907E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 5 1 >> 5 Hmholtz VELY: 9 5.5659E-08 1.9419E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 5 1 >> 5 Hmholtz VELZ: 9 5.9684E-08 1.6655E+00 9.9200E-08 >> 5 U-PRES gmres: 16 9.2427E-07 1.0000E-06 1.5556E-04 >> 5.7643E+00 1.0499E+01 >> 5 DNORM, DIVEX 9.2426901539348950E-007 >> 9.2426901307669303E-007 >> 5 0.1622525E+03 6.74218E-03 5.77469E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 5 1.6225E+02 1.5064E+01 Fluid done >> Step 6, t= 1.6225300E+02, DT= 5.0000000E-04, C= 0.255 1.6256E+02 >> 2.5244E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 6 1 >> 6 Hmholtz VELX: 9 6.0915E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 6 1 >> 6 Hmholtz VELY: 9 6.0642E-08 1.9418E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 6 1 >> 6 Hmholtz VELZ: 9 5.9861E-08 1.6655E+00 9.9200E-08 >> 6 U-PRES gmres: 14 8.6298E-07 1.0000E-06 1.2403E-04 >> 5.0438E+00 9.0451E+00 >> 6 DNORM, DIVEX 8.6297683366363408E-007 >> 8.6297681628504936E-007 >> 6 0.1622530E+03 6.73975E-03 5.77261E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 6 1.6225E+02 1.3610E+01 Fluid done >> Step 7, t= 1.6225350E+02, DT= 5.0000000E-04, C= 0.255 1.8632E+02 >> 2.3767E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 7 1 >> 7 Hmholtz VELX: 9 7.2389E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 7 1 >> 7 Hmholtz VELY: 9 7.1978E-08 1.9418E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 7 1 >> 7 Hmholtz VELZ: 9 6.0336E-08 1.6654E+00 9.9200E-08 >> 7 U-PRES gmres: 14 7.8284E-07 1.0000E-06 1.2790E-04 >> 5.0456E+00 9.0568E+00 >> 7 DNORM, DIVEX 7.8284171959673956E-007 >> 7.8284171260985997E-007 >> 7 0.1622535E+03 6.73731E-03 5.77052E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 7 1.6225E+02 1.3620E+01 Fluid done >> Step 8, t= 1.6225400E+02, DT= 5.0000000E-04, C= 0.256 2.1010E+02 >> 2.3780E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 8 1 >> 8 Hmholtz VELX: 9 8.0530E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 8 1 >> 8 Hmholtz VELY: 9 8.0474E-08 1.9418E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 8 1 >> 8 Hmholtz VELZ: 9 6.1838E-08 1.6654E+00 9.9200E-08 >> 8 U-PRES gmres: 13 9.3871E-07 1.0000E-06 8.2637E-05 >> 4.6862E+00 8.3450E+00 >> 8 DNORM, DIVEX 9.3870751505892285E-007 >> 9.3870750972531774E-007 >> 8 0.1622540E+03 6.73487E-03 5.76843E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 8 1.6225E+02 1.2911E+01 Fluid done >> Step 9, t= 1.6225450E+02, DT= 5.0000000E-04, C= 0.257 2.3318E+02 >> 2.3081E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 9 1 >> 9 Hmholtz VELX: 9 8.5197E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 9 1 >> 9 Hmholtz VELY: 9 8.4881E-08 1.9418E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 9 1 >> 9 Hmholtz VELZ: 9 6.3849E-08 1.6654E+00 9.9200E-08 >> 9 U-PRES gmres: 10 8.0419E-07 1.0000E-06 5.5243E-05 >> 3.6054E+00 6.2748E+00 >> 9 DNORM, DIVEX 8.0418938467388352E-007 >> 8.0418939044644440E-007 >> 9 0.1622545E+03 6.73242E-03 5.76633E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 9 1.6225E+02 1.0838E+01 Fluid done >> Step 10, t= 1.6225500E+02, DT= 5.0000000E-04, C= 0.257 2.5418E+02 >> 2.0995E+01 >> Solving for fluid >> 9.9200000000000002E-008 p22 10 1 >> 10 Hmholtz VELX: 9 8.7316E-08 1.9533E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 10 1 >> 10 Hmholtz VELY: 9 8.7257E-08 1.9418E+00 9.9200E-08 >> 9.9200000000000002E-008 p22 10 1 >> 10 Hmholtz VELZ: 9 6.5276E-08 1.6654E+00 9.9200E-08 >> 10 U-PRES gmres: 14 7.9070E-07 1.0000E-06 5.7631E-05 >> 5.0451E+00 9.0540E+00 >> 10 DNORM, DIVEX 7.9069874056473697E-007 >> 7.9069875187583686E-007 >> 10 0.1622550E+03 6.72998E-03 5.76424E-06 3.14158E+00 >> 3.14159E+00 volflow Z >> 10 1.6225E+02 1.3620E+01 Fluid done >> Step 11, t= 1.6225550E+02, DT= 5.0000000E-04, C= 0.258 2.7885E+02 >> 2.4675E+01 >> Solving for fluid >> 11 100 **ERROR**: Failed in HMHOLTZ: VELX 7.9521E+07 >> 1.9533E+00 9.9200E-08 >> 11 100 **ERROR**: Failed in HMHOLTZ: VELY 2.8223E+03 >> 1.9418E+00 9.9200E-08 >> 11 Hmholtz VELZ: 9 6.6283E-08 1.6654E+00 9.9200E-08 >> 11 U-PRES gmres: 100 1.6296E+02 1.0000E-06 2.6253E+12 >> 3.6002E+01 6.8265E+01 >> 11 DNORM, DIVEX 54998323.86255041 162.9642641112922 >> 11 0.1622555E+03 4.32525E-03 3.70458E-06 3.14159E+00 >> 3.14159E+00 volflow Z >> 11 1.6226E+02 9.4526E+01 Fluid done >> CFL, Ctarg! 11083557069312.66 1.000000000000000 >> call outfld: ifpsco: F >> >> 12 1.6226E+02 Write checkpoint: >> >> call outfld: ifpsco: F >> >> 12 1.6226E+02 Write checkpoint: >> 0 12 OPEN: pipe0.f00001 >> 850 12 OPEN: pipe5.f00001 >> 510 12 OPEN: pipe3.f00001 >> 170 12 OPEN: pipe1.f00001 >> 1020 12 OPEN: pipe6.f00001 >> 680 12 OPEN: pipe4.f00001 >> 340 12 OPEN: pipe2.f00001 >> >> 12 1.6226E+02 done :: Write checkpoint >> file size = 234.E+02MB >> >> 899 Emergency exit: 12 time = 162.2554999999999 >> >> 512 Emergency exit: 12 time = 162.2554999999999 >> >> 459 Emergency exit: 12 time = 162.2554999999999 >> Latest solution and data are dumped for post-processing. >> *** STOP *** >> 461 Emergency exit: 12 time = 162.2554999999999 >> Latest solution and data are dumped for post-processing. >> *** STOP *** >> >> ------------------------------------------------------------------------------- >> >> Quoting nek5000-users at lists.mcs.anl.gov: >> >>> Geroge, >>> >>> Can you provide more details. A logfile would be helpful. >>> >>> Cheers, >>> Stefan >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From nek5000-users at lists.mcs.anl.gov Fri Dec 16 12:24:59 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 16 Dec 2011 18:24:59 +0000 Subject: [Nek5000-users] Problem using gradm1 Message-ID: Dear nek developers, I am running a very simple Conjugate Heat Transfer case. It is a 2D channel with a solid wall. The inlet temperature of the fluid is 1 and I initialize the temperature in the entire domain to 1. I set a boundary condition 't' on the outer surface of the wall and I impose TEMP = 1.1. I run nek in order to solve the transient prolem (using cvode) and at the interface between solid and fluid I check the energy balance: lambda*gradT]solid = lambda*gradT]fluid I have already checked many cases and, after the changes implemented by Stefan (thanks again Stefan!) it seems that the energy balance is fine. This time (and also other times) the error in the energy balance is quite big compared to the fluxes but, what is strange, is that the fluxes have different sign. In order to compute the fluxes I put in userchk the following lines of code: call gradm1(g1,g2,g3,t) call col2(g2,vdiff(1,1,1,1,2),ntot) I don't use opgrad because it works only on the fluid mesh, isn't it? I checked the temperature and, as expected, it grows from the fluid to the solid, going towards the outer surface of the wall (I checked the t array at every grid point in debug mode). In order to be sure that I was taking the right points, I checked also ym1 of the same points. I took two contiguous elements in y-direction, one on the fluid side and one on the solid side. I varied iy from 1 to ny1. In the fluid, the gradient is always positive, as expected. In the solid, the gradient is negative for iy = 1 (interface with the fluid), but then it becomes positive for iy = 2 to ny1. I also tried to compute a rough estimation of the gradient between two grid points as dt/dym1 and the values are not very different from those computed by gradm1 but for the first point of the solid gradm1 is completely wrong. Is there any other subroutine to compute the gradient in the solid? Thanks a lot in advance. Regards, Andrea. From nek5000-users at lists.mcs.anl.gov Mon Dec 19 10:46:00 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 19 Dec 2011 17:46:00 +0100 Subject: [Nek5000-users] stokes flow with time-dependent boundary Message-ID: <4EEF6A48.9090601@mech.kth.se> Hello, guys, i am a new guy to Nek5000, i saw the manual of nek5000 that it can solve the steady stokes flow. i guess when i solve such a flow, do i need to set it as a transient simulation with time-derivative term included to get a steady-state solution? or, i can solve it by a direct solver method to get the solution immediately? since i want to add some time-dependent boundary condition for the steady stokes flow, so it will be pretty nice if i can solve it using the direct solver, for each time step, i solve one stokes flow; if nek5000 cannot solve it in such a way, i guess i have to use the first way; then for each time step i have to solve a transient problem to approach the steady state with some artificial time step used. i am not sure if i have stated my problem clearly. hopefully you guys have some experience on the feasibility of the two ways mentioned above. Thank you in advance. lailai From nek5000-users at lists.mcs.anl.gov Mon Dec 19 11:17:38 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 19 Dec 2011 11:17:38 -0600 (CST) Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: <4EEF6A48.9090601@mech.kth.se> References: <4EEF6A48.9090601@mech.kth.se> Message-ID: Hi Lailai, I have used the approach you proposed for solving multiple steady stokes problems... you use an artificially large timestep. That works. If you really have a time-dependent boundary condition, there is no reason you can't just use the unsteady Stokes solver with whatever timestep is required to accurately resolve your temporal bcs. Note that, in this case, you would indeed have the inertial term rho du/dt present in the physics. Paul On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > Hello, guys, > > i am a new guy to Nek5000, i saw the manual of nek5000 that it can solve the > steady stokes flow. > i guess when i solve such a flow, do i need to set it as a transient > simulation with time-derivative term included to get a steady-state > solution? or, i can solve it by a direct solver method to get the solution > immediately? > > since i want to add some time-dependent boundary condition for the steady > stokes flow, so it will be pretty nice if i can solve it using the direct > solver, for each time step, i solve one stokes flow; if nek5000 cannot solve > it in such a way, i guess i have to use the first way; then for each time > step i have to solve a transient problem to approach the steady state with > some artificial time step used. > > i am not sure if i have stated my problem clearly. hopefully you guys have > some experience on the feasibility of the two ways mentioned above. Thank you > in advance. > > lailai > > > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Wed Dec 21 08:30:40 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 21 Dec 2011 15:30:40 +0100 Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: References: <4EEF6A48.9090601@mech.kth.se> Message-ID: <4EF1ED90.702@mech.kth.se> On 12/19/2011 06:17 PM, nek5000-users at lists.mcs.anl.gov wrote: > > Hi Lailai, > > I have used the approach you proposed for solving multiple > steady stokes problems... you use an artificially large > timestep. That works. > thank for your reply, if understand correctly, here you are talking about the second approach i proposed. For each time step, we solve a transient problem with very large internal timestep to quickly get to the steady-state solution. since i am very new to nek5000, thus i am not sure how to implement this method which seems not trivial. On the other hand, i started from the first example of the Kovasznay problem. I remove the time-derivative and convection term by setting the density in .rea file to zero, the numerical results agree very well with the analytical solution with zero Re number. I guess here the solver is just inverting a matrix which seems feasible for a 2D problem but might be too expensive or inefficient for a 3D problem. > If you really have a time-dependent boundary condition, there > is no reason you can't just use the unsteady Stokes solver > with whatever timestep is required to accurately resolve your > temporal bcs. Note that, in this case, you would indeed have > the inertial term rho du/dt present in the physics. > > Paul > > > On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > >> Hello, guys, >> >> i am a new guy to Nek5000, i saw the manual of nek5000 that it can >> solve the steady stokes flow. >> i guess when i solve such a flow, do i need to set it as a transient >> simulation with time-derivative term included to get a steady-state >> solution? or, i can solve it by a direct solver method to get the >> solution immediately? >> >> since i want to add some time-dependent boundary condition for the >> steady stokes flow, so it will be pretty nice if i can solve it using >> the direct solver, for each time step, i solve one stokes flow; if >> nek5000 cannot solve it in such a way, i guess i have to use the >> first way; then for each time step i have to solve a transient >> problem to approach the steady state with some artificial time step >> used. >> >> i am not sure if i have stated my problem clearly. hopefully you guys >> have some experience on the feasibility of the two ways mentioned >> above. Thank you in advance. >> >> lailai >> >> >> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Wed Dec 21 11:47:26 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 21 Dec 2011 11:47:26 -0600 (CST) Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: <4EF1ED90.702@mech.kth.se> References: <4EEF6A48.9090601@mech.kth.se> <4EF1ED90.702@mech.kth.se> Message-ID: Hi Lailai, To switch to unsteady Stokes, you simply set the flag IFNAV to "F" in the .rea file, which turns off the convective term and simultaneously eliminates the CFL timestep constraint. [ Set: T F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) to F F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) .] It's still not clear to me if you are solving an unsteady Stokes problem, or a series of steady Stokes problems. (There is a difference...) Nek can handle either case with equal ease. I hope this helps. Paul On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > On 12/19/2011 06:17 PM, nek5000-users at lists.mcs.anl.gov wrote: >> >> Hi Lailai, >> >> I have used the approach you proposed for solving multiple >> steady stokes problems... you use an artificially large >> timestep. That works. >> > > thank for your reply, if understand correctly, here you are talking about the > second approach i proposed. For each time step, we solve a transient problem > with very large internal timestep to quickly get to the steady-state > solution. > since i am very new to nek5000, thus i am not sure how to implement this > method which seems not trivial. > > On the other hand, i started from the first example of the Kovasznay problem. > I remove the time-derivative and convection term by setting the density in > .rea file to zero, the numerical results agree very well with the analytical > solution with zero Re number. I guess here the solver is just inverting a > matrix which seems feasible for a 2D problem but might be too expensive or > inefficient for a 3D problem. > > >> If you really have a time-dependent boundary condition, there >> is no reason you can't just use the unsteady Stokes solver >> with whatever timestep is required to accurately resolve your >> temporal bcs. Note that, in this case, you would indeed have >> the inertial term rho du/dt present in the physics. >> > > >> Paul >> >> >> On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >> >>> Hello, guys, >>> >>> i am a new guy to Nek5000, i saw the manual of nek5000 that it can solve >>> the steady stokes flow. >>> i guess when i solve such a flow, do i need to set it as a transient >>> simulation with time-derivative term included to get a steady-state >>> solution? or, i can solve it by a direct solver method to get the solution >>> immediately? >>> >>> since i want to add some time-dependent boundary condition for the steady >>> stokes flow, so it will be pretty nice if i can solve it using the direct >>> solver, for each time step, i solve one stokes flow; if nek5000 cannot >>> solve it in such a way, i guess i have to use the first way; then for each >>> time step i have to solve a transient problem to approach the steady state >>> with some artificial time step used. >>> >>> i am not sure if i have stated my problem clearly. hopefully you guys have >>> some experience on the feasibility of the two ways mentioned above. Thank >>> you in advance. >>> >>> lailai >>> >>> >>> >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Wed Dec 21 15:12:40 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 21 Dec 2011 22:12:40 +0100 Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: References: <4EEF6A48.9090601@mech.kth.se> <4EF1ED90.702@mech.kth.se> Message-ID: <4EF24BC8.8030302@mech.kth.se> thank you for your tip, Paul. i think we are solving a series of Stokes problems linked by a time-dependent boundary condition. The time-derivative term is zero and we are not solving an unsteady Stokes problem. I think we are not clear how to solve a series of Stokes problems. lailai On 12/21/2011 06:47 PM, nek5000-users at lists.mcs.anl.gov wrote: > Hi Lailai, > > To switch to unsteady Stokes, you simply set the flag > IFNAV to "F" in the .rea file, which turns off the convective > term and simultaneously eliminates the CFL timestep constraint. > > [ Set: > > T F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) > > to > > F F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) > > .] > > It's still not clear to me if you are solving an unsteady > Stokes problem, or a series of steady Stokes problems. > (There is a difference...) > > Nek can handle either case with equal ease. > > I hope this helps. > > Paul > > > On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > >> On 12/19/2011 06:17 PM, nek5000-users at lists.mcs.anl.gov wrote: >>> >>> Hi Lailai, >>> >>> I have used the approach you proposed for solving multiple >>> steady stokes problems... you use an artificially large >>> timestep. That works. >>> >> >> thank for your reply, if understand correctly, here you are talking >> about the second approach i proposed. For each time step, we solve a >> transient problem with very large internal timestep to quickly get to >> the steady-state solution. >> since i am very new to nek5000, thus i am not sure how to implement >> this method which seems not trivial. >> >> On the other hand, i started from the first example of the Kovasznay >> problem. I remove the time-derivative and convection term by setting >> the density in .rea file to zero, the numerical results agree very >> well with the analytical solution with zero Re number. I guess here >> the solver is just inverting a matrix which seems feasible for a 2D >> problem but might be too expensive or inefficient for a 3D problem. >> >> >>> If you really have a time-dependent boundary condition, there >>> is no reason you can't just use the unsteady Stokes solver >>> with whatever timestep is required to accurately resolve your >>> temporal bcs. Note that, in this case, you would indeed have >>> the inertial term rho du/dt present in the physics. >>> >> >> >>> Paul >>> >>> >>> On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >>> >>>> Hello, guys, >>>> >>>> i am a new guy to Nek5000, i saw the manual of nek5000 that it can >>>> solve the steady stokes flow. >>>> i guess when i solve such a flow, do i need to set it as a >>>> transient simulation with time-derivative term included to get a >>>> steady-state solution? or, i can solve it by a direct solver method >>>> to get the solution immediately? >>>> >>>> since i want to add some time-dependent boundary condition for the >>>> steady stokes flow, so it will be pretty nice if i can solve it >>>> using the direct solver, for each time step, i solve one stokes >>>> flow; if nek5000 cannot solve it in such a way, i guess i have to >>>> use the first way; then for each time step i have to solve a >>>> transient problem to approach the steady state with some artificial >>>> time step used. >>>> >>>> i am not sure if i have stated my problem clearly. hopefully you >>>> guys have some experience on the feasibility of the two ways >>>> mentioned above. Thank you in advance. >>>> >>>> lailai >>>> >>>> >>>> >>>> _______________________________________________ >>>> Nek5000-users mailing list >>>> Nek5000-users at lists.mcs.anl.gov >>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>>> >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Wed Dec 21 15:17:39 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 21 Dec 2011 15:17:39 -0600 (CST) Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: <4EF24BC8.8030302@mech.kth.se> References: <4EEF6A48.9090601@mech.kth.se> <4EF1ED90.702@mech.kth.se> <4EF24BC8.8030302@mech.kth.se> Message-ID: Hi Lailai, I suggest initially starting with a single run, using steady Stokes. (Note, steady Stokes works only for Pn-Pn-2, so set lx2,ly2 = lx1-2, etc.) Paul On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > thank you for your tip, Paul. > > i think we are solving a series of Stokes problems linked by a time-dependent > boundary condition. > The time-derivative term is zero and we are not solving an unsteady Stokes > problem. I think we are not clear how to solve a series of Stokes problems. > > lailai > > > > > > On 12/21/2011 06:47 PM, nek5000-users at lists.mcs.anl.gov wrote: >> Hi Lailai, >> >> To switch to unsteady Stokes, you simply set the flag >> IFNAV to "F" in the .rea file, which turns off the convective >> term and simultaneously eliminates the CFL timestep constraint. >> >> [ Set: >> >> T F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) >> >> to >> >> F F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) >> >> .] >> >> It's still not clear to me if you are solving an unsteady >> Stokes problem, or a series of steady Stokes problems. >> (There is a difference...) >> >> Nek can handle either case with equal ease. >> >> I hope this helps. >> >> Paul >> >> >> On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >> >>> On 12/19/2011 06:17 PM, nek5000-users at lists.mcs.anl.gov wrote: >>>> >>>> Hi Lailai, >>>> >>>> I have used the approach you proposed for solving multiple >>>> steady stokes problems... you use an artificially large >>>> timestep. That works. >>>> >>> >>> thank for your reply, if understand correctly, here you are talking about >>> the second approach i proposed. For each time step, we solve a transient >>> problem with very large internal timestep to quickly get to the >>> steady-state solution. >>> since i am very new to nek5000, thus i am not sure how to implement this >>> method which seems not trivial. >>> >>> On the other hand, i started from the first example of the Kovasznay >>> problem. I remove the time-derivative and convection term by setting the >>> density in .rea file to zero, the numerical results agree very well with >>> the analytical solution with zero Re number. I guess here the solver is >>> just inverting a matrix which seems feasible for a 2D problem but might be >>> too expensive or inefficient for a 3D problem. >>> >>> >>>> If you really have a time-dependent boundary condition, there >>>> is no reason you can't just use the unsteady Stokes solver >>>> with whatever timestep is required to accurately resolve your >>>> temporal bcs. Note that, in this case, you would indeed have >>>> the inertial term rho du/dt present in the physics. >>>> >>> >>> >>>> Paul >>>> >>>> >>>> On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >>>> >>>>> Hello, guys, >>>>> >>>>> i am a new guy to Nek5000, i saw the manual of nek5000 that it can solve >>>>> the steady stokes flow. >>>>> i guess when i solve such a flow, do i need to set it as a transient >>>>> simulation with time-derivative term included to get a steady-state >>>>> solution? or, i can solve it by a direct solver method to get the >>>>> solution immediately? >>>>> >>>>> since i want to add some time-dependent boundary condition for the >>>>> steady stokes flow, so it will be pretty nice if i can solve it using >>>>> the direct solver, for each time step, i solve one stokes flow; if >>>>> nek5000 cannot solve it in such a way, i guess i have to use the first >>>>> way; then for each time step i have to solve a transient problem to >>>>> approach the steady state with some artificial time step used. >>>>> >>>>> i am not sure if i have stated my problem clearly. hopefully you guys >>>>> have some experience on the feasibility of the two ways mentioned above. >>>>> Thank you in advance. >>>>> >>>>> lailai >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Nek5000-users mailing list >>>>> Nek5000-users at lists.mcs.anl.gov >>>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>>>> >>>> _______________________________________________ >>>> Nek5000-users mailing list >>>> Nek5000-users at lists.mcs.anl.gov >>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>> >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > From nek5000-users at lists.mcs.anl.gov Wed Dec 21 15:29:27 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 21 Dec 2011 22:29:27 +0100 Subject: [Nek5000-users] stokes flow with time-dependent boundary In-Reply-To: References: <4EEF6A48.9090601@mech.kth.se> <4EF1ED90.702@mech.kth.se> <4EF24BC8.8030302@mech.kth.se> Message-ID: <4EF24FB7.8010406@mech.kth.se> On 12/21/2011 10:17 PM, nek5000-users at lists.mcs.anl.gov wrote: > > Hi Lailai, > > I suggest initially starting with a single run, using steady Stokes. > (Note, steady Stokes works only for Pn-Pn-2, so set lx2,ly2 = lx1-2, > etc.) > yes, this is what i did before, solving the Kovasznay problem in the tutorial using steady Stokes. The way i used is simply setting DENSITY to be zero in the .rea file, is this the right way to solve the steady Stokes problem? it seems work out for me, as the numerical results agreed very well with the analytical ones. lailai > Paul > > > On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: > >> thank you for your tip, Paul. >> >> i think we are solving a series of Stokes problems linked by a >> time-dependent boundary condition. >> The time-derivative term is zero and we are not solving an unsteady >> Stokes problem. I think we are not clear how to solve a series of >> Stokes problems. >> >> lailai >> >> >> >> >> >> On 12/21/2011 06:47 PM, nek5000-users at lists.mcs.anl.gov wrote: >>> Hi Lailai, >>> >>> To switch to unsteady Stokes, you simply set the flag >>> IFNAV to "F" in the .rea file, which turns off the convective >>> term and simultaneously eliminates the CFL timestep constraint. >>> >>> [ Set: >>> >>> T F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) >>> >>> to >>> >>> F F F F F F F F F F F IFNAV & IFADVC (convection in P.S. fields) >>> >>> .] >>> >>> It's still not clear to me if you are solving an unsteady >>> Stokes problem, or a series of steady Stokes problems. >>> (There is a difference...) >>> >>> Nek can handle either case with equal ease. >>> >>> I hope this helps. >>> >>> Paul >>> >>> >>> On Wed, 21 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >>> >>>> On 12/19/2011 06:17 PM, nek5000-users at lists.mcs.anl.gov wrote: >>>>> >>>>> Hi Lailai, >>>>> >>>>> I have used the approach you proposed for solving multiple >>>>> steady stokes problems... you use an artificially large >>>>> timestep. That works. >>>>> >>>> >>>> thank for your reply, if understand correctly, here you are talking >>>> about the second approach i proposed. For each time step, we solve >>>> a transient problem with very large internal timestep to quickly >>>> get to the steady-state solution. >>>> since i am very new to nek5000, thus i am not sure how to >>>> implement this method which seems not trivial. >>>> >>>> On the other hand, i started from the first example of the >>>> Kovasznay problem. I remove the time-derivative and convection term >>>> by setting the density in .rea file to zero, the numerical results >>>> agree very well with the analytical solution with zero Re number. I >>>> guess here the solver is just inverting a matrix which seems >>>> feasible for a 2D problem but might be too expensive or inefficient >>>> for a 3D problem. >>>> >>>> >>>>> If you really have a time-dependent boundary condition, there >>>>> is no reason you can't just use the unsteady Stokes solver >>>>> with whatever timestep is required to accurately resolve your >>>>> temporal bcs. Note that, in this case, you would indeed have >>>>> the inertial term rho du/dt present in the physics. >>>>> >>>> >>>> >>>>> Paul >>>>> >>>>> >>>>> On Mon, 19 Dec 2011, nek5000-users at lists.mcs.anl.gov wrote: >>>>> >>>>>> Hello, guys, >>>>>> >>>>>> i am a new guy to Nek5000, i saw the manual of nek5000 that it >>>>>> can solve the steady stokes flow. >>>>>> i guess when i solve such a flow, do i need to set it as a >>>>>> transient simulation with time-derivative term included to get a >>>>>> steady-state solution? or, i can solve it by a direct solver >>>>>> method to get the solution immediately? >>>>>> >>>>>> since i want to add some time-dependent boundary condition for >>>>>> the steady stokes flow, so it will be pretty nice if i can solve >>>>>> it using the direct solver, for each time step, i solve one >>>>>> stokes flow; if nek5000 cannot solve it in such a way, i guess i >>>>>> have to use the first way; then for each time step i have to >>>>>> solve a transient problem to approach the steady state with some >>>>>> artificial time step used. >>>>>> >>>>>> i am not sure if i have stated my problem clearly. hopefully you >>>>>> guys have some experience on the feasibility of the two ways >>>>>> mentioned above. Thank you in advance. >>>>>> >>>>>> lailai >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Nek5000-users mailing list >>>>>> Nek5000-users at lists.mcs.anl.gov >>>>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>>>>> >>>>> _______________________________________________ >>>>> Nek5000-users mailing list >>>>> Nek5000-users at lists.mcs.anl.gov >>>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>>> >>>> _______________________________________________ >>>> Nek5000-users mailing list >>>> Nek5000-users at lists.mcs.anl.gov >>>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >>>> >>> _______________________________________________ >>> Nek5000-users mailing list >>> Nek5000-users at lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> >> _______________________________________________ >> Nek5000-users mailing list >> Nek5000-users at lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users >> > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users From nek5000-users at lists.mcs.anl.gov Thu Dec 22 12:58:15 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 22 Dec 2011 12:58:15 -0600 Subject: [Nek5000-users] Nek/MOAB documented, fixed Message-ID: <4EF37DC7.2070909@mcs.anl.gov> Hi everyone, I've written new documentation, and fixed various bugs, in the Nek/MOAB integration. This should enable running Nek on CUBIT-generated meshes. The process for building and running Nek/MOAB is described on the Nek wiki pages, at https://nek5000.mcs.anl.gov/index.php/Building_and_Using_Nek_/_MOAB. If you run into any problems, please email this list, or me directly. If you run any cool-looking problems enabled by this, we'd also love to hear about that! Thanks to Katie Heisey and the rest of the Nek team for their help along the way. - tim -- ================================================================ "You will keep in perfect peace him whose mind is steadfast, because he trusts in you." Isaiah 26:3 Tim Tautges Argonne National Laboratory (tautges at mcs.anl.gov) (telecommuting from UW-Madison) phone (gvoice): (608) 354-1459 1500 Engineering Dr. fax: (608) 263-4499 Madison, WI 53706 From nek5000-users at lists.mcs.anl.gov Thu Dec 22 22:22:55 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 22 Dec 2011 22:22:55 -0600 (CST) Subject: [Nek5000-users] Restart problem In-Reply-To: <1323181417.5193.13.camel@skagsnebb.mech.kth.se> References: <1323181417.5193.13.camel@skagsnebb.mech.kth.se> Message-ID: > Hi > > I simulate jet in crossflow problem with nek5000 and I've got serius > problems with restarting the simulation. It causes strong spurious > velocity oscillation and I cannot get rid of them. I've implemented > restarting procedure described in prepost.f, but it doesn't help much. > Playing with file format (parameters p66, p67) and projection (p94, p95) > I can only decrease oscillations amplitude, but they are still there. > Surprisingly saving output files in double precision (p63=8) makes > everything worse. Has anybody got similar problems? > Best regards > > Adam Hi, I think that the full restart capability should now work with the current version of the source. There is a 2D example in the repo, with a README that I also provide below. Basically, you will now save 4 files each time you wish to checkpoint. The files come in two sets, A and B, and the A set is then overwritten by the 3rd checkpoint, etc. so that you have at most 8 checkpoint files on hand at any one time. The files are 64 bit and thus cannot be used by VisIt --- thus, they are truly designated as checkpoint/restart files and not analysis files. More information in the README below. Please let me know if you have comments or questions. Best regards, Paul ------------------------------------------------------------------------- >From the examples/cyl_restart directory: SET UP: ======= This directory contains an example of full restart capabilities for Nek5000. The model flow is a von Karman street in the wake of a 2D cylinder. The quantity of interest is taken to be the lift, which is monitored via "grep agy logfile" in the run_test script. A matlab file, doit.m, can be used to analyze the output files containing the lift history of the four cases. The cases are: ca - initial run (no projection) cb - restart run for ca case pa - initial run (with projection) pb - restart run for pa case BACKGROUND: =========== Timestepping in Nek5000 is based on BDFk/EXTk (k=3, typ.), which uses kth-order backward-difference formulae (BDFk) to evaluate velocity time derivatives and kth-order extrapolation (EXTk) for explicit evaluation of the nonlinear and pressure boundary terms. Under normal conditions, the velocity and pressure for preceding timesteps are required to advance the the solution at each step. At startup, the timestepper is typically bootstrapped using a lower-order BDF/EXT formula that, given the artificiality of most initial conditions, is typically adequate. The velocity field often has enough inertia and sufficient signature such that the same bootstrap procedure also works when restarting from an existing solution (i.e., a .fnnnnn or .fldnn file, stored in 32-bit precision). For some cases, it is important to have reproducibility of the time history to the working precision (14 digits, typ.) of the code. The full restart feature is designed to provide this capability. The main features of full restart are: .Preserve alternating sets of snapshots (4 per set) in 64-bit precision. (Alternating sets are saved in case the job fails in the middle of saving a set.) .Use the most recent set to restart the computation by overwriting the solution for the first steps, 0 through 3, with the preserved snapshots. Full restart is triggered through the .usr file. In the given example cases, "ca" and "cb" the restart-save is illustrated in ca.usr and the actual restart, plus the save, is illustrated in cb.usr. For these cases, the restart is encapsulated in the user-provided routine "my_full_restart" shown below, along with the calling format in userchk: c----------------------------------------------------------------------- subroutine userchk include 'SIZE' include 'TOTAL' logical if_drag_out,if_torq_out call my_full_restart scale = 1. if_drag_out = .true. if_torq_out = .false. call torque_calc(scale,x0,if_drag_out,if_torq_out) return end c----------------------------------------------------------------------- subroutine my_full_restart character*80 s80(4) call blank(s80,4*80) s80(1) ='rs8ca0.f00005' s80(2) ='rs8ca0.f00006' s80(3) ='rs8ca0.f00007' s80(4) ='rs8ca0.f00008' call full_restart(s80,4) ! Will overload 5-8 onto steps 0-3 iosave = iostep ! Trigger save based on iostep call full_restart_save(iosave) return end c----------------------------------------------------------------------- Note that in the example above, the set enumerated 5--8 is used to restart the computation. This set is generated by first running the "ca" case. Note that the frequency of the restart output is coincident with the standard output frequency of field files (snapshots). This might be too frequent if one is, say, making a movie where snapshots are typically dumped every 10 steps. It would make more sense in this case to set iosave=1000, say. Note also that if one is initiating a computation from something other than the full restart mode then the full_restart() call should be commented out. COMMENTS: ========= Full reproducibility of the solution is predicated on having sufficient history information to replicate the state of "a" when running "b". While such replication is possible, it does preclude acceleration of the iterative solvers by projection onto prior solution spaces [1,2], since these projections typically retain relatively long sequences of information (e.g., spanning tens of steps) to maximally extract all the regularity in the solution history. Consequently, _full_ reproducibility is not retained with projection turned on. In this case, the solution is reproduced only to the tolerance of the iterative solvers, which is in any case the maximum level of accuracy attainable in the solution. To illustrate the difference, we provide a test case pairing, "pa" and "pb", which is essentially the same as the ca/cb pair save that projection is turned on for pa/pb. From nek5000-users at lists.mcs.anl.gov Thu Dec 29 06:24:45 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 29 Dec 2011 13:24:45 +0100 Subject: [Nek5000-users] Nek5000 YouTube Channel Message-ID: Dear Nek users, We believe our YouTube channel is a great way to demonstrate the capabilities of Nek5000 to a broad audience. Just check it out: http://nek5000.mcs.anl.gov/index.php/Visualization_Gallery Let us know if you want to share your favorite Nek5000 visualization on our channel. -Stefan From nek5000-users at lists.mcs.anl.gov Thu Dec 29 06:45:53 2011 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 29 Dec 2011 13:45:53 +0100 Subject: [Nek5000-users] Help us to write a tutorial Message-ID: Dear Nek users, We are looking for help from the community to provide a tutorial (from users to users) to get new Nek users started. The tutorial will be published on our Wiki. A good starting point is the Lid-driven cavity flow tutorial of OpenFOAM: http://www.openfoam.org/docs/user/tutorials.php You can get yourself a Wiki account to setup the tutorial: http://nek5000.mcs.anl.gov/index.php?title=LidDrivenCavity&action=edit&redlink=1 Thank you very much for your support! Stefan