Howdy Nek's, I have a couple questions regarding the ouput of files: 1. How can force, within the code (say in usrchk), some files to be output in 64 bits for high-accuracy checkpointing and other in regular 8 bits for simple visualisation? 2. Say, during the first 1000 iterations, the code outpost a file every single iteration so that I have blah0.f00001 to blah0.f01000. How can I then force the code to outpost my new files (from istep = 1001 to 2000 say) rewriting on blah0.f00001 to blah0.f01000? Thanks a lot. Regards, JC -- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
Hi JC, You should be able to control the outpost frequency and precision using the parameters parameter 15 (IOSTEP) and parameter 63, respectively. So, if you wanted the first 100 steps to output every step, you would set something like: if(istep.le.100) param(15)=1 To set the precision to 64bit, set param(63)=8, as well. Setting param(63) to anything else should default it to 8 byte precision. As far as overwriting previous fld files, you should be able to reset a parameter used in prepost.f that increments the file counter. I haven't had a chance to test this, but I can take a look at it last this weekend. hth. Katherine On Fri, Aug 15, 2014 at 3:34 AM, <[email protected]> wrote:
Howdy Nek's,
I have a couple questions regarding the ouput of files:
1. How can force, within the code (say in usrchk), some files to be output in 64 bits for high-accuracy checkpointing and other in regular 8 bits for simple visualisation? 2. Say, during the first 1000 iterations, the code outpost a file every single iteration so that I have blah0.f00001 to blah0.f01000. How can I then force the code to outpost my new files (from istep = 1001 to 2000 say) rewriting on blah0.f00001 to blah0.f01000?
Thanks a lot. Regards,
JC
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
Hi Katherine, Thanks for the answer. I knew about the parameter 15 and was not sure about the 64 bits precision. This is now more clear. Regarding the overwriting, I had guessed that prepost has a parameter that needs to be reset, but I haven't been able to figure out which one so far. That would be very helpful if you can take a quick look at it. Thanks a lot and enjoy the end of the summer ++ JC 2014-08-15 16:53 GMT+02:00 <[email protected]>:
Hi JC,
You should be able to control the outpost frequency and precision using the parameters parameter 15 (IOSTEP) and parameter 63, respectively.
So, if you wanted the first 100 steps to output every step, you would set something like:
if(istep.le.100) param(15)=1
To set the precision to 64bit, set param(63)=8, as well. Setting param(63) to anything else should default it to 8 byte precision.
As far as overwriting previous fld files, you should be able to reset a parameter used in prepost.f that increments the file counter. I haven't had a chance to test this, but I can take a look at it last this weekend.
hth. Katherine
On Fri, Aug 15, 2014 at 3:34 AM, <[email protected]> wrote:
Howdy Nek's,
I have a couple questions regarding the ouput of files:
1. How can force, within the code (say in usrchk), some files to be output in 64 bits for high-accuracy checkpointing and other in regular 8 bits for simple visualisation? 2. Say, during the first 1000 iterations, the code outpost a file every single iteration so that I have blah0.f00001 to blah0.f01000. How can I then force the code to outpost my new files (from istep = 1001 to 2000 say) rewriting on blah0.f00001 to blah0.f01000?
Thanks a lot. Regards,
JC
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
Hi Katherine, I was wondering if you had time to check on the parameter to be reset so that I can overwrite previous files? Bonne soirée, JC 2014-08-15 16:57 GMT+02:00 <[email protected]>:
Hi Katherine,
Thanks for the answer. I knew about the parameter 15 and was not sure about the 64 bits precision. This is now more clear. Regarding the overwriting, I had guessed that prepost has a parameter that needs to be reset, but I haven't been able to figure out which one so far. That would be very helpful if you can take a quick look at it.
Thanks a lot and enjoy the end of the summer ++
JC
2014-08-15 16:53 GMT+02:00 <[email protected]>:
Hi JC,
You should be able to control the outpost frequency and precision using the parameters parameter 15 (IOSTEP) and parameter 63, respectively.
So, if you wanted the first 100 steps to output every step, you would set something like:
if(istep.le.100) param(15)=1
To set the precision to 64bit, set param(63)=8, as well. Setting param(63) to anything else should default it to 8 byte precision.
As far as overwriting previous fld files, you should be able to reset a parameter used in prepost.f that increments the file counter. I haven't had a chance to test this, but I can take a look at it last this weekend.
hth. Katherine
On Fri, Aug 15, 2014 at 3:34 AM, <[email protected]> wrote:
Howdy Nek's,
I have a couple questions regarding the ouput of files:
1. How can force, within the code (say in usrchk), some files to be output in 64 bits for high-accuracy checkpointing and other in regular 8 bits for simple visualisation? 2. Say, during the first 1000 iterations, the code outpost a file every single iteration so that I have blah0.f00001 to blah0.f01000. How can I then force the code to outpost my new files (from istep = 1001 to 2000 say) rewriting on blah0.f00001 to blah0.f01000?
Thanks a lot. Regards,
JC
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
Hi JC, Sorry it took me awhile to get to this. For .fld files: In prepost.f, subroutine outfld(prefix), around line 333 (right before the call to file2 - If you reset nopen(iprefix), you should start writing to a file ending with 01 and incrementing from there. Something like: if(nopen(iprefix).gt.25) nopen(iprefix)=1 Note that nopen is a common variable and resetting this in prepost will carry over elsewhere in the code, essentially setting the number of open files to 1. If you want to preserve the open file count, just save the original nopen(iprefix) in a temp variable and restore it after the call to open the file. (~lines 344) For 0.f00000 files you can reset the variable nfld in prepost.f, subroutine mfo_open_files() before the "call mbyte_open(fname,fid0,ierr)" on line ~1703 Let me know if that doesn't work ok. Katherine On Sun, Aug 31, 2014 at 1:17 PM, <[email protected]> wrote:
Hi Katherine,
I was wondering if you had time to check on the parameter to be reset so that I can overwrite previous files?
Bonne soirée, JC
2014-08-15 16:57 GMT+02:00 <[email protected]>:
Hi Katherine,
Thanks for the answer. I knew about the parameter 15 and was not sure about the 64 bits precision. This is now more clear. Regarding the overwriting, I had guessed that prepost has a parameter that needs to be reset, but I haven't been able to figure out which one so far. That would be very helpful if you can take a quick look at it.
Thanks a lot and enjoy the end of the summer ++
JC
2014-08-15 16:53 GMT+02:00 <[email protected]>:
Hi JC,
You should be able to control the outpost frequency and precision using the parameters parameter 15 (IOSTEP) and parameter 63, respectively.
So, if you wanted the first 100 steps to output every step, you would set something like:
if(istep.le.100) param(15)=1
To set the precision to 64bit, set param(63)=8, as well. Setting param(63) to anything else should default it to 8 byte precision.
As far as overwriting previous fld files, you should be able to reset a parameter used in prepost.f that increments the file counter. I haven't had a chance to test this, but I can take a look at it last this weekend.
hth. Katherine
On Fri, Aug 15, 2014 at 3:34 AM, <[email protected]> wrote:
Howdy Nek's,
I have a couple questions regarding the ouput of files:
1. How can force, within the code (say in usrchk), some files to be output in 64 bits for high-accuracy checkpointing and other in regular 8 bits for simple visualisation? 2. Say, during the first 1000 iterations, the code outpost a file every single iteration so that I have blah0.f00001 to blah0.f01000. How can I then force the code to outpost my new files (from istep = 1001 to 2000 say) rewriting on blah0.f00001 to blah0.f01000?
Thanks a lot. Regards,
JC
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-- Jean-Christophe Loiseau Homepage <https://sites.google.com/site/loiseaujc/>
_______________________________________________ Nek5000-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Neks, I am interested in running multiple jobs sequentially in an automatic process. However I've noticed problems with .sch file (.sch file already exists. Use IFSCHCLOB=F to $disable this check BUT BEWARE!!!!!!). I have tried to remove it before and after a job, but I can still see problems for some of the jobs. Is there a way of disable this check? If so, how can I do it? The message says set IFSCHLOB=F, however I can see that IFSCHCLOB = .false. in connect2.f Any ideas? Regards, Luis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJT9IoKAAoJEIhcgrtekvd+pF8IAKtuI2drqlOJEAGVKguH4BT2 KMXQx2R7LLNkgSt/GGUbJvybI0oDnFIMO9cJk3r/qJP6m0UhixcWv0SIic+O+0ww e61lTuELcXSL03yVrWdlx3zUffbIvSG7NQ8yjjSXXa3YyWNnZ09HHduB/cQP9hE8 nYFkwHWbcFkqbWadLn328Qyx3VRUWwrPNB6wQsQep731i45FrC8J6jRuulh612jD B0dK0dPiAH0SA5smDl46xjYV6GPpShYyOiB+VtbstzeI6SRtpHe4xqMwE0pmoxZO pUKcHbqxv3CCwOp/Xww6+HTPgfoXeHRnYNefSh8/b4AWBYY7Z7cI39rTEnQmyms= =KPe0 -----END PGP SIGNATURE----- -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
participants (1)
-
nek5000-users＠lists.mcs.anl.gov