Hi It seems to work now, but I found 2 typos in iolib_no_graph.f causing pretex crashes: 1) line 153; WRITE(S,'(3G113.9)',ERR=1) changed to WRITE(S,'(3G13.9)',ERR=1) 2) line 184; WRITE(SS(NC+1:NC+5), '(I13)', changed to WRITE(SS(NC+1:NC+13),'(I13)', Thank you for help. Best regards Adam On 24/04/13 13:05, [email protected] wrote:

Hi Adam,

My apologies - I didn't realize that anyone was using sc. (Glad to hear that it _is_ being used!)

I think I've now restored the old functionality --- It was hardwired with a particular resolution just until it gets a bit more usage and we understand the typical use cases for the feature. Since prenek/postnek do not have standard .usr interfaces, it's often easiest just to modify the code for the application at hand, as the number of free parameters is otherwise innumerable.

Please let me know if this revision works for you.

Best, Paul

On Wed, 24 Apr 2013, [email protected] wrote:

...

Hi Neks.

I have a question about prenek. I use it to insert a cap in the mesh connecting pipe with the box, but there is an exit (call prexit) in the new version of subroutine sc_make_sphere_cap. Why is it so? Is the new version incomplete? Moreover the resolution is changed by increasing the number of radii to 7, while I'm using 3. Are you going to add additional switch to choose resolution? Regards Adam _______________________________________________ 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

Dear Neks, As part of a strategic planning exercise, I'd like to get a survey of performance profiles over a broad range of applications. I'm particularly interested in production runs involving lots of compute cycles, since these would be the most important for future optimization (i.e., cases where you are running 100s of simulations of more or less the same type). I'm wonder if I could ask each of you to send one or at most two logfiles directly to me - [email protected] with a very brief description giving a ballpark estimate of utilization, i.e., something like: We have run 100 of these cases, typically 6 hours each, or whatever suits. I don't really need to know anything about the app. The one thing I do need, however, is that your logfile contain the statistics that are printed at the end when the job terminates with nek's standard termination criterion (i.e., it does not stop because your run time expired). When you grep time logfile you should see something like: 163.0805685520172 7.9530425400815632E-002 eslv time 121259 153.8100430965424 7.5009415695555526E-002 pres time 121259 433.6815834045410 0.2114959564030525 crsl time 122729 0.7530927658081055 3.6726501852911642E-004 hmhz time 363777 469.4056932926178 0.2289177355990086 spro time 121260 14.56137013435364 7.1012259246232062E-003 usbc time 606294 54.14203882217407 2.6403755014022586E-002 axhm time 2070607 497.7768969535828 0.2427536813301520 advc time 363777 252.1085748672485 0.1229472179574250 vdss time 486498 7.609275102615356 3.7108583277339125E-003 dsum time 2438769 18.98749208450317 9.2597379085877490E-003 dadd time 0 1.966142654418945 9.5883993472067994E-004 ddsl time 122729 49.81083679199219 2.4291533165547920E-002 solv time 122729 22.48464226722717 1.0965212964212575E-002 prep time 121259 10.51901149749756 5.1298659712803868E-003 total elapsed time : 2.05059E+03 sec total solver time incl. I/O : 2.05054E+03 sec time/timestep : 1.69104E-02 sec CPU seconds/timestep/gridpt : 4.23184E-06 sec Preferably, the case in question should be 3D and have run for at least 100 timesteps (the more the better), so that the statistics have more significance. My plan is to build a histogram with pts/core on the x-axis, time spent where on the y axis, etc. --- something like this... By gathering this on a variety of platforms we'll be able to make more informed decisions. Thank you all! Paul