From nek5000-users at lists.mcs.anl.gov Sun Mar 1 05:25:44 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 1 Mar 2015 11:25:44 +0000 Subject: [Nek5000-users] Solving mesh Laplace equation (Re: Mesh morphing) In-Reply-To: References: <20150217195418.Horde.kBfYvzXQjnLW9MGGXpBSXg6@www.mech.kth.se> <, > Message-ID: Dear Paul, Thank you for this script!! It works very nicely to morph the mesh for the cylinder example. I modified it to deform the mesh in both x- and y-direction, and made the cylinder into an ellipse (attached picture). (If someone is interested in the code, I am happy to share it after tidy-up.) Now I am experimenting with other meshes and blending functions. Best regards, Outi > On 21 Feb 2015, at 00:34, nek5000-users at lists.mcs.anl.gov wrote: > > > Hi Outi, > > It's ok... it just means that the solver did not converge all the way... but the > resulting field is nonetheless sufficiently smooth. > > Paul > > ________________________________________ > From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > Sent: Friday, February 20, 2015 5:11 PM > To: nek5000-users at lists.mcs.anl.gov > Subject: Re: [Nek5000-users] Solving mesh Laplace equation (Re: Mesh morphing) > > Dear Paul, > > Thank you very much, the idea seems exactly like what I would like to > do. However, there is an error appearing in the Helmholtz solver. From > logfile: > > call userchk > 1.000000000000000E-006 p22 0 1 > 0 200 **ERROR**: Failed in HMHOLTZ: mshv 1.3206E-02 > 2.7147E+03 1.0000E-06 > done :: userchk > > Best regards, > Outi > > Quoting nek5000-users at lists.mcs.anl.gov: > >> Dear Outi, >> >> I have just added "ocyl2" to the ocyl example directory. >> >> I think it addresses the question you raise. Please advise and let >> us know if you have any difficulties. >> >> Paul >> >> ________________________________________ >> From: nek5000-users-bounces at lists.mcs.anl.gov >> [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of >> nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] >> Sent: Friday, February 20, 2015 11:39 AM >> To: nek5000-users at lists.mcs.anl.gov >> Subject: [Nek5000-users] Solving mesh Laplace equation (Re: Mesh morphing) >> >> Dear Neks, >> >> What I actually would like to accomplish is to solve the Laplace >> equation for the mesh (with the boundary deformation as a BC). I saw >> that this has been done already at least by Paul (a thread 2009) and >> Matt (for smoothing of a wing mesh, with zero deformation). >> Could any of you please give me a hint on how to solve the Laplace >> equation for the mesh like this? Matt? Paul? >> I would be very grateful. >> >> Best regards, >> Outi >> >> Quoting Outi Tammisola : >> >>> Dear Neks, >>> >>> I thought this question might be of interest for someone else as >>> well, so posting it here: >>> >>> I have been looking at the oscillating cylinder example. I would >>> like to do something similar, but instead of a prescribed boundary >>> velocity, would like to prescribe a given displacement of one >>> boundary, and morph my mesh smoothly everywhere to match this >>> displacement. For example, if one were to describe a deformation of >>> the cylinder rather than a velocity (but without altering the other >>> boundaries and without scaling the mesh). This just needs to be done >>> once, not at every time step. >>> >>> Is there an easy way to do this? Can I arrive there somehow by minor >>> modifications of the elasticity solver? What equation exactly is the >>> elasticity solver solving at every time step? >>> (When I outputted the files after every time step for the >>> oscillating cylinder, the mesh deformation seemed to match the >>> prescribed one only after 2 time steps. Is there a reason for this, >>> or did I do something wrong?) >>> >>> Best regards, >>> Outi >> >> >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cylinder_to_ellipse_small.jpg Type: image/jpeg Size: 37675 bytes Desc: not available URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 1 09:32:00 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 1 Mar 2015 10:32:00 -0500 Subject: [Nek5000-users] Metadata files Message-ID: Hi all, Would someone be able to help me create a Metadata file, so I can upload my results into VisIt? I'm under the impression that you have to create a new file, is that correct? Thanks. David H. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 1 09:48:01 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 1 Mar 2015 15:48:01 +0000 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Hi David, Which files are you referring to? Your own output files or nek outpost generated ones? The easiest would be to just make a call to outpost and overwrite the velocity fields and pressure, and use a different name than your current SESSION, instead of writing out your own data file. In this way you can still use the script 'visnek' to create a Visit readable file (the format visit has for nek is .nek5000 which looks very simple to tweak if needed). Hope I understood your problem correctly, Oana ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Sunday, March 01, 2015 9:32 AM To: Nek Mailing List Subject: [Nek5000-users] Metadata files Hi all, Would someone be able to help me create a Metadata file, so I can upload my results into VisIt? I'm under the impression that you have to create a new file, is that correct? Thanks. David H. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Thu Mar 5 02:00:04 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 5 Mar 2015 02:00:04 -0600 Subject: [Nek5000-users] Cylinder geometry for Rayleigh Benard flow Message-ID: Dear all, Hi everyone. I am a new user and I want to define a cylinder with insulated side wall. However, I find that Genbox only provides generation of annulus mesh, according to a website manaul . Would anyone tell me how to do it? Thank you. Regards, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Thu Mar 5 15:16:04 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 5 Mar 2015 16:16:04 -0500 Subject: [Nek5000-users] calculating friction velocity/wall shear stress Message-ID: Hello, I want to calculate friction velocity or wall shear stress along seveal lines, like lines around circle, my question is what would be the easiest way to do?! defining a line in set_obj and calling torque_calc in userchk or finding the velocity derivatives in userchck and then calculating wall shear stress or even using post processing tool like VisIt or postnek?! Thanks, Ami -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Thu Mar 5 17:37:05 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 5 Mar 2015 16:37:05 -0700 Subject: [Nek5000-users] calculating friction velocity/wall shear stress In-Reply-To: References: Message-ID: Hi Ami, I believe, developing a set_obj() routine followed by tourque_calc() is the easiest thing to do. Then calculate drag(obj) and eventually you can calculate the surface area, and divide it by the drag, to obtain wall shear stress Best Regards, Tanmoy On Thu, Mar 5, 2015 at 2:16 PM, wrote: > Hello, > > I want to calculate friction velocity or wall shear stress along seveal > lines, like lines around circle, my question is what would be the easiest > way to do?! defining a line in set_obj and calling torque_calc in userchk > or finding the velocity derivatives in userchck and then calculating wall > shear stress or even using post processing tool like VisIt or postnek?! > > Thanks, > Ami > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 7 12:37:10 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 7 Mar 2015 12:37:10 -0600 Subject: [Nek5000-users] Fail to load prexnek and postnek Message-ID: Dear all, Previously I tried to load prenek and postnek by typing command 'prex' and 'postx'. After entering the session name, it seems the windows didn't give further instructions, but frozen in black without any words. As I know, there should be request to input parameters (prenek). Has anyone who have experienced the same thing before? How did you solve that? Thank you. Regards, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 8 09:17:40 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 8 Mar 2015 10:17:40 -0400 Subject: [Nek5000-users] Linear Advection Equation In-Reply-To: References: Message-ID: Thank You, Paul. Why does the conductivity/diffusivity (i.e. param(08)) have to be small and non-zero positive? Can nek5k solve the linear advection equation without the discrete diffusion term? On Sat, Feb 28, 2015 at 10:31 AM, wrote: > > > > Set ifflow to false and ifheat to T and ifadvc = F T F F F F... > > in the .rea file. > > Then, supply your velocity field in useric (ux, uy, uz), or, if you > want time-varying velocity, > do so in usrchk by over-writing the velocity field arrays, vx(), vy(), and > vz() at each step. > > > Paul > ------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > *Sent:* Saturday, February 28, 2015 9:24 AM > *To:* nek5000-users at lists.mcs.anl.gov > *Subject:* [Nek5000-users] Linear Advection Equation > > Dear Users, > > Is there a way to solve a linear advection equation in nek5k without > computing the Navier-Stokes equations? I am simply interested in advecting > a profile according to the following: > > D(phi)/Dt = d (phi) /dt + v*.*grad(phi)= 0 > > where v*.*grad(phi) = u.d(phi)/dx + v.d(phi)/dy + w.d(phi)/dz > > and v is a prescribed velocity (for example v = (1,1) in 2D) > > Best, > > Saumil > > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > -- Saumil S. Patel Ph.D. Candidate Department of Mechanical Engineering Computational Multiphase Fluid Dynamics Group The City College of New York Telephone: 1 (212) 650-7134 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 8 16:17:23 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 8 Mar 2015 21:17:23 +0000 Subject: [Nek5000-users] Linear Advection Equation In-Reply-To: References: , Message-ID: Technically Nek solves convection-diffusion (CD). CD with nu=0 is invalid because it's a singular perturbation --- the number of boundary conditions is different for the 1st-order convection eqn than for the 2nd-order CD equation, so Nek checks to make certain nu \ge 0. I usually set nu=1.e-31.... it won't show up in the calculation (assuming your other quantities are O(1)). Best, Paul ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Sunday, March 08, 2015 9:17 AM To: nek5000-users at lists.mcs.anl.gov Subject: Re: [Nek5000-users] Linear Advection Equation Thank You, Paul. Why does the conductivity/diffusivity (i.e. param(08)) have to be small and non-zero positive? Can nek5k solve the linear advection equation without the discrete diffusion term? On Sat, Feb 28, 2015 at 10:31 AM, > wrote: Set ifflow to false and ifheat to T and ifadvc = F T F F F F... in the .rea file. Then, supply your velocity field in useric (ux, uy, uz), or, if you want time-varying velocity, do so in usrchk by over-writing the velocity field arrays, vx(), vy(), and vz() at each step. Paul ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Saturday, February 28, 2015 9:24 AM To: nek5000-users at lists.mcs.anl.gov Subject: [Nek5000-users] Linear Advection Equation Dear Users, Is there a way to solve a linear advection equation in nek5k without computing the Navier-Stokes equations? I am simply interested in advecting a profile according to the following: D(phi)/Dt = d (phi) /dt + v.grad(phi)= 0 where v.grad(phi) = u.d(phi)/dx + v.d(phi)/dy + w.d(phi)/dz and v is a prescribed velocity (for example v = (1,1) in 2D) Best, Saumil _______________________________________________ Nek5000-users mailing list Nek5000-users at lists.mcs.anl.gov https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users -- Saumil S. Patel Ph.D. Candidate Department of Mechanical Engineering Computational Multiphase Fluid Dynamics Group The City College of New York Telephone: 1 (212) 650-7134 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 8 19:08:06 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 8 Mar 2015 19:08:06 -0500 Subject: [Nek5000-users] Fail to load prexnek and postnek In-Reply-To: References: Message-ID: I tried to reinstall nek5000. There is a large error list which I faced in my previous installation as well. The error is attached in the email as a reference. I ran the prenek again. Stuck in the same problem. I remove the prenek in ~/bin/ and did a "./maketools prenek" back in /home/kchu10/nek5_svn/trunk/tools. Same. Here is the return for "prex" [kchu10 at golubh1 ~]$ prex -Adobe-Helvetica-Medium-R-Normal--12-120-75-75-P-67-ISO8859-1 I/O Error: No String Terminator sent to PRS NEKTON Version 2.6 cp: cannot stat `/home/kchu10/.nekdefaults': No such file or directory (6144,6144,6144) (61440,61440,61440) (61440, 0, 0) (61440,61440, 0) (30720,30720,30720) ( 0, 0,61440) (61440, 0,43008) (61440,61440, 0) (43008,61440, 0) (12288,61440,12288) ( 0,61440,61440) ( 0,18432,61440) (61440, 0,61440) (61440, 0,12288) (36864,36864,36864) (30720,30720,43008) Choose a Name for This Session: test (Stuck in blank page) I hope there is anyone who got the same problem as I do and solve it out already. Again thanks for help. Regards, Simon 2015-03-07 12:37 GMT-06:00 : > Dear all, > > Previously I tried to load prenek and postnek by typing command 'prex' and > 'postx'. After entering the session name, it seems the windows didn't give > further instructions, but frozen in black without any words. > > As I know, there should be request to input parameters (prenek). Has > anyone who have experienced the same thing before? How did you solve that? > > Thank you. > > Regards, > Simon > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- [kchu10 at golubh4 tools]$ ./maketools all ---------------------- Make genbox... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/genbox' gfortran -mcmodel=medium -c -fdefault-real-8 genbox.f genbox.f:1615.28: if (indx1(string,comment,1).ne.1) then 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (1/132) at (1) genbox.f:1625.32: i1 = indx1(string,comment,1) 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (1/132) at (1) genbox.f:1490.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) genbox.f:2888.25: if (indx1(temps,'IFFLOW',6).ne.0) then 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (6/132) at (1) genbox.f:2895.29: elseif (indx1(temps,'IFHEAT',6).ne.0) then 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (6/132) at (1) genbox.f:2925.25: if (indx1(temps,'MESH DATA',9).ne.0) return 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (9/132) at (1) genbox.f:2104.30: call out_tens_bcs (cbc,nelx,nely,nelz,1,nfld,if3d,ifflow) 1 Warning: Rank mismatch in argument 'nlx' at (1) (rank-1 and scalar) genbox.f:1510.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) genbox.f:895.29: call icopy(buf(1),ie,1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:896.29: call icopy(buf(2),iedge,1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:902.30: call chcopy(buf(8),'C',1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:920.30: call chcopy(buf2(8),'C',1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1129.30: call blank(buf(1),30*4) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1132.32: call icopy(buf(1),ie,1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1134.34: call icopy(buf(2),eface(3),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1136.35: call chcopy(buf(8),cbc3,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1137.53: if(nel.ge.1000000) call icopy(buf(3),ibc(3),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1142.34: call icopy(buf(2),eface(2),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1144.35: call chcopy(buf(8),cbc2,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1145.53: if(nel.ge.1000000) call icopy(buf(3),ibc(2),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1150.34: call icopy(buf(2),eface(4),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1152.35: call chcopy(buf(8),cbc4,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1153.53: if(nel.ge.1000000) call icopy(buf(3),ibc(4),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1158.34: call icopy(buf(2),eface(1),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1160.35: call chcopy(buf(8),cbc1,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1161.53: if(nel.ge.1000000) call icopy(buf(3),ibc(1),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1166.33: call icopy(buf(2),eface(5),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1168.34: call chcopy(buf(8),cbc5,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1169.52: if(nel.ge.1000000) call icopy(buf(3),ibc(5),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1174.33: call icopy(buf(2),eface(6),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1176.34: call chcopy(buf(8),cbc6,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1177.52: if(nel.ge.1000000) call icopy(buf(3),ibc(6),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1186.35: call chcopy(buf2(8),cbc3,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1194.36: call chcopy(buf2(8),cbc2,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1202.35: call chcopy(buf2(8),cbc4,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1210.35: call chcopy(buf2(8),cbc1,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1218.34: call chcopy(buf2(8),cbc5,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1226.34: call chcopy(buf2(8),cbc6,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1358.30: call blank(buf(1),30*4) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1360.32: call icopy(buf(1),ie,1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1363.34: call icopy(buf(2),eface(3),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1365.35: call chcopy(buf(8),cbc3,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1366.53: if(nel.ge.1000000) call icopy(buf(3),ibc(3),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1371.34: call icopy(buf(2),eface(2),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1373.35: call chcopy(buf(8),cbc2,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1374.53: if(nel.ge.1000000) call icopy(buf(3),ibc(2),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1379.34: call icopy(buf(2),eface(4),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1381.35: call chcopy(buf(8),cbc4,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1382.53: if(nel.ge.1000000) call icopy(buf(3),ibc(4),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1387.34: call icopy(buf(2),eface(1),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1389.35: call chcopy(buf(8),cbc1,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to CHARACTER(1) genbox.f:1390.53: if(nel.ge.1000000) call icopy(buf(3),ibc(1),1) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) genbox.f:1399.35: call chcopy(buf2(8),cbc3,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1407.35: call chcopy(buf2(8),cbc2,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1415.35: call chcopy(buf2(8),cbc4,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:1423.35: call chcopy(buf2(8),cbc1,3) 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to CHARACTER(1) genbox.f:100.20: common /genbc/ cbc 1 Warning: Named COMMON block 'genbc' at (1) shall be of the same size as elsewhere (7200 vs 1080 bytes) gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -fdefault-real-8 -o /home/kchu10/bin/genbox genbox.o byte.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/genbox' ---------------------- Make int_tp... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/int_tp' gfortran -mcmodel=medium -c int_tp.f int_tp.f:274.49: call get_bin_data2(x,nx,ny,nz,nel,nfld,if_byte_sw,if3d) 1 Warning: Type mismatch in argument 'if_byte_sw' at (1); passed INTEGER(4) to LOGICAL(4) int_tp.f:276.49: call get_bin_data (x,nx,ny,nz,nel,nfld,if_byte_sw,if3d) 1 Warning: Type mismatch in argument 'if_byte_sw' at (1); passed INTEGER(4) to LOGICAL(4) int_tp.f:281.42: call get_data(x,nx,ny,nz,nel,nfld,if3d) 1 Warning: Type mismatch in argument 'if3d' at (1); passed INTEGER(4) to LOGICAL(4) int_tp.f:55.49: call get_old_data(uin,nx,ny,nz,nel,nfld,if_byte_sw,if3d,fname, 1 Warning: Type mismatch in argument 'if_byte_sw' at (1); passed LOGICAL(4) to INTEGER(4) int_tp.f:57.44: call xyz_chk(uin,nx,ny,nz,nel,nfld,if3d) 1 Warning: Type mismatch in argument 'if3d' at (1); passed LOGICAL(4) to INTEGER(4) int_tp.f:512.19: common /c132/ s132 1 Warning: Named COMMON block 'c132' at (1) shall be of the same size as elsewhere (80 vs 132 bytes) gfortran -mcmodel=medium -c ../../nek/speclib.f ../../nek/speclib.f:147.27: CALL ZWGJD (ZD,WD,NP,ALPHAD,BETAD) 1 Warning: Type mismatch in argument 'alpha' at (1); passed REAL(4) to REAL(8) gfortran -mcmodel=medium -c mxm44f2.f gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -c int_tp_gbox.f int_tp_gbox.f:574.28: if (indx1(string,comment,1).ne.1) then 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (1/80) at (1) int_tp_gbox.f:581.32: i1 = indx1(string,comment,1) 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (1/80) at (1) gfortran -mcmodel=medium -o /home/kchu10/bin/int_tp int_tp.o speclib.o mxm44f2.o byte.o int_tp_gbox.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/int_tp' ---------------------- Make nekmerge... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/nekmerge' gfortran -mcmodel=medium -c nekmerge.f gfortran -mcmodel=medium -c reader.f gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -c strings.f strings.f:18.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) strings.f:45.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) strings.f:227.22: call int_write(s(1),2) 1 Warning: Type mismatch in argument 's' at (1); passed REAL(4) to INTEGER(4) strings.f:229.22: call strg_write(s(8),1) 1 Warning: Type mismatch in argument 's' at (1); passed REAL(4) to CHARACTER(1) gfortran -mcmodel=medium -c tsort.f gfortran -mcmodel=medium -o /home/kchu10/bin/nekmerge nekmerge.o reader.o byte.o strings.o tsort.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/nekmerge' ---------------------- Make prenek... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/prenek' gfortran -mcmodel=medium -c prenek.f gfortran -mcmodel=medium -c curve.f gfortran -mcmodel=medium -c edit.f gfortran -mcmodel=medium -c build.f build.f:1143.20: call readscan('DIMENSION',9,47) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) build.f:1155.20: call readscan('MESH DATA',9,47) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) build.f:2937.53: call unique_vertex2(cell,dx,ndim,nel,q,i_n,j_n,j_o,wk) 1 Warning: Type mismatch in argument 'ifseg' at (1); passed INTEGER(4) to LOGICAL(4) gfortran -mcmodel=medium -c build1.f gfortran -mcmodel=medium -c build2.f build2.f:77.19: call add3s2 (p,x0,v,lp,3) ! p = x0 + lp*v 1 Warning: Rank mismatch in argument 'x' at (1) (rank-1 and scalar) build2.f:1807.47: call build_dia_saddle (v(1,1,nt),q,d,rad,if_sph_ctr) 1 Warning: Type mismatch in argument 'if_sph_ctr' at (1); passed INTEGER(4) to LOGICAL(4) gfortran -mcmodel=medium -c bound.f bound.f:581.31: call letbc(jside,je,ifld,bclab) 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) bound.f:582.31: call letbc(iside,ie,ifld,bclab) 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) bound.f:2158.35: call letbc(js,je,if,bclab) 1 Warning: Type mismatch in argument 'bclab' at (1); passed REAL(4) to CHARACTER(1) bound.f:2159.35: call letbc(is,ie,if,bclab) 1 Warning: Type mismatch in argument 'bclab' at (1); passed REAL(4) to CHARACTER(1) bound.f:1899.46: call letbc(jside,jel,ifld,bclab) 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) bound.f:1900.40: call letbc(f,e,ifld,bclab) 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) bound.f:1977.37: call letbc(fp,ep,ifld,bclab) 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) bound.f:1430.26: call letbc(f,e,ifld,bclab) ! Label Boundary Side 1 Warning: Rank mismatch in argument 'bclab' at (1) (scalar and rank-1) gfortran -mcmodel=medium -c plot.f plot.f:365.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) plot.f:378.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) plot.f:1727.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) gfortran -mcmodel=medium -c xinterface.f xinterface.f:317.19: COMMON /CLIP/ XMOVEC,YMOVEC,WT,WB,WL,WR 1 Warning: Named COMMON block 'clip' at (1) shall be of the same size as elsewhere (24 vs 28 bytes) gfortran -mcmodel=medium -c glomod.f glomod.f:1535.38: call get_gxyz(nv,cell,nvc,ncell,ww(n1),ww,ierr) 1 Warning: Type mismatch in argument 'ww' at (1); passed REAL(4) to INTEGER(4) glomod.f:1721.9: ja(2) = w(2,1) 1 Warning: Array reference at (1) is out of bounds (2 > 1) in dimension 1 glomod.f:1558.54: call build_adj (ja,ia,n,cell,nvc,ncell,edge,ne,ww,ww(n1),ww(n2)) 1 Warning: Type mismatch in argument 'w' at (1); passed REAL(4) to INTEGER(4) glomod.f:2192.13: $ (rxm1,nvc,wv1,wkv1,sdump(1,4),sdump(1,5),jacm1 1 Warning: Type mismatch in argument 'cell' at (1); passed REAL(4) to INTEGER(4) glomod.f:1438.20: common /ctmp0/ idel(nelm),edel(nelm) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (4000000 vs 660 bytes) gfortran -mcmodel=medium -c legend.f legend.f:21.17: call zwgll(zpts,wght,n) 1 Warning: Rank mismatch in argument 'z' at (1) (rank-1 and scalar) gfortran -mcmodel=medium -c vprops.f gfortran -mcmodel=medium -c iolib.f gfortran -mcmodel=medium -c subs.f gfortran -mcmodel=medium -c zipper2.f zipper2.f:3679.20: ie = ie_click('Click on element to refine:$') 1 Warning: Character length of actual argument shorter than of dummy argument 'prompt' (28/80) at (1) zipper2.f:3732.38: rrz(k) = get_ratio(k,nzsp,razi) 1 Warning: Rank mismatch in argument 'ratio' at (1) (scalar and rank-1) zipper2.f:3708.40: call msplite(ie,nxsp,nysp,nzsp,rax,ray,raz) 1 Warning: Rank mismatch in argument 'raxi' at (1) (rank-1 and scalar) zipper2.f:3712.43: call msplite(ie,nxsp,nysp,nzsp,rax,ray,raz) 1 Warning: Rank mismatch in argument 'raxi' at (1) (rank-1 and scalar) zipper2.f:5186.37: call msplite(ie,nxsp,nysp,nzsp,rax,ray,raz) 1 Warning: Rank mismatch in argument 'raxi' at (1) (rank-1 and scalar) zipper2.f:78.30: call octsplitn(ie,liste) ! New oct/quad split 1 Warning: Rank mismatch in argument 'liste' at (1) (scalar and rank-1) zipper2.f:1187.20: COMMON /CTMP2/ XP(NXM3),YP(NXM3),ZP(NXM3) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (4116 vs 4128 bytes) zipper2.f:2878.20: COMMON /CTMP2/ XP(NXM3),YP(NXM3),ZP(NXM3),RRL(3) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (4452 vs 4128 bytes) zipper2.f:3465.20: common /ctmp2/ xp(nxm3),yp(nxm3),zp(nxm3),rrl(3) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (4128 vs 4452 bytes) zipper2.f:3580.20: common /ctmp2/ xp(nxm3),yp(nxm3),zp(nxm3),rrl(3) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (4128 vs 4452 bytes) zipper2.f:4482.20: common /ctmp2/ xp(nxm3),yp(nxm3),zp(nxm3),wk(ldw) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (6860 vs 4452 bytes) zipper2.f:699.20: common /ctmp0/ xcv(3,2,2),vn1(3),vn2(3) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (1164 vs 1824 bytes) zipper2.f:4630.20: common /ctmp0/ xcb(2,2,2),ycb(2,2,2),zcb(2,2,2),w(ldw) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (2840 vs 1824 bytes) zipper2.f:4687.20: common /ctmp0/ w(ldw,2),zg(3) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (2756 vs 2840 bytes) zipper2.f:2241.20: common /ctmp0/ xcv(3,2,2),vn1(3),vn2(3) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (1164 vs 2840 bytes) zipper2.f:4961.20: COMMON /CTMP2/ XP(NXM3),YP(NXM3),ZP(NXM3),RRL(3) 1 Warning: Named COMMON block 'ctmp2' at (1) shall be of the same size as elsewhere (4452 vs 6860 bytes) gfortran -mcmodel=medium -c postnek6.f gfortran -mcmodel=medium -c screen.f screen.f:440.19: COMMON /CLIP/ XMOVEC,YMOVEC,WT,WB,WL,WR 1 Warning: Named COMMON block 'clip' at (1) shall be of the same size as elsewhere (24 vs 28 bytes) screen.f:1454.20: common /ctmp0/ xbz(0:mm),ybz(0:mm) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (808 vs 408 bytes) gcc -mcmodel=medium -c -DUNDERSCORE -Dr8 revert.c gfortran -mcmodel=medium -c crs.f gfortran -mcmodel=medium -c mxm.f gcc -mcmodel=medium -c -DUNDERSCORE -Dr8 xdriver.c gfortran -mcmodel=medium -o /home/kchu10/bin/prex prenek.o curve.o edit.o build.o build1.o build2.o bound.o plot.o xinterface.o glomod.o legend.o vprops.o iolib.o subs.o zipper2.o postnek6.o screen.o revert.o crs.o mxm.o xdriver.o -L/usr/lib/X11 -lX11 -lm Linux gfortran -mcmodel=medium -c iolib_no_graph.f iolib_no_graph.f:509.22: CALL GETSOLD(S) 1 Warning: Rank mismatch in argument 's' at (1) (scalar and rank-1) gfortran -mcmodel=medium -o /home/kchu10/bin/pretex prenek.o curve.o edit.o build.o build1.o build2.o bound.o plot.o xinterface.o glomod.o legend.o vprops.o iolib_no_graph.o subs.o zipper2.o postnek6.o screen.o revert.o crs.o mxm.o xdriver.o -L/usr/lib/X11 -lX11 -lm make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/prenek' ---------------------- Make genmap... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/genmap' gfortran -mcmodel=medium -c -fdefault-real-8 genmap.f genmap.f:896.18: len = indx1(prompt,'$',1) - 1 1 Warning: Rank mismatch in argument 's1' at (1) (scalar and rank-1) genmap.f:909.22: lsf = indx1 (suffix,'$',1) - 1 1 Warning: Rank mismatch in argument 's1' at (1) (scalar and rank-1) genmap.f:238.24: call linearmsh(cell,nelv,nelt,ndim) 1 Warning: Actual argument contains too few elements for dummy argument 'cell' (1/2) at (1) genmap.f:387.24: call cscan(string,'MESH DATA',9) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) genmap.f:3362.9: $ ('Error opening file in open_bin_file ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (36/40) at (1) genmap.f:3365.9: $ ('Error reading header in open_bin_file ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (38/40) at (1) genmap.f:3281.10: $ ('Error byte_reverse in buf_to_xy ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (32/40) at (1) genmap.f:3284.21: call copyi4(igroup,buf(0),1) !0-1 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) genmap.f:3286.27: call copy (xc,buf( 2),8) !2 --17 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3287.27: call copy (yc,buf(18),8) !18--33 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3288.27: call copy (zc,buf(34),8) !34--49 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3290.27: call copy (xc,buf( 2),4) !2 --9 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3291.27: call copy (yc,buf(10),4) !10--17 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3296.27: call copy4r(xc,buf( 1),8) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:3297.27: call copy4r(yc,buf( 9),8) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:3298.27: call copy4r(zc,buf(17),8) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:3300.27: call copy4r(xc,buf( 1),4) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:3301.27: call copy4r(yc,buf( 5),4) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:259.16: $ ('Error reading ncurve in makemesh ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (33/40) at (1) genmap.f:263.16: $ ('Error reading curve data in makemesh ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (37/40) at (1) genmap.f:269.16: $ ('Error reading ncurve in makemesh ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (33/40) at (1) genmap.f:273.16: $ ('Error reading curve data in makemesh ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (37/40) at (1) genmap.f:3204.21: & ('Error reading byte bcs ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (23/40) at (1) genmap.f:3238.21: call copyi4(e,buf(1),1) !1-2 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) genmap.f:3239.21: call copyi4(f,buf(3),1) !3-4 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) genmap.f:3240.31: call copy (bl(1,f,e),buf(5),5) !5--14 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to REAL(8) genmap.f:3241.31: call chcopy(cbl( f,e),buf(15),3)!15-16 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to CHARACTER(1) genmap.f:3243.21: $ call copyi4(bl(1,f,e),buf(5),1) !Integer assign connecting P el 1 Warning: Type mismatch in argument 'a' at (1); passed REAL(8) to INTEGER(4) genmap.f:3247.34: call copy48r ( bl(1,f,e),buf(3),5) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) genmap.f:3248.34: call chcopy (cbl( f,e),buf(8),3) 1 Warning: Type mismatch in argument 'y' at (1); passed INTEGER(4) to CHARACTER(1) genmap.f:3215.21: & ('Error reading byte bcs ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (23/40) at (1) genmap.f:290.24: call rd_bc_bin(cbc,bc,nelv,nelt,ifbswap) 1 Warning: Actual argument contains too few elements for dummy argument 'cbc' (18/9000000) at (1) genmap.f:294.14: $ ('Error closing file in makemesh ',ierr) 1 Warning: Character length of actual argument shorter than of dummy argument 'name' (31/40) at (1) genmap.f:519.24: call cscan(string,'BOUNDARY',8) ! for now, fluid only 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (8/80) at (1) genmap.f:530.26: if (indx1(string,'NO ',3).ne.0) then 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (3/80) at (1) genmap.f:532.30: call cscan(string,'BOUNDARY',8) ! then, temp only 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (8/80) at (1) genmap.f:2901.53: call tuple_sort(dx(0,i),lda,ninseg(iseg),j1,1,ind,dxt) !key= 1 Warning: Rank mismatch in argument 'key' at (1) (rank-1 and scalar) genmap.f:314.54: call unique_vertex2(cell,dx,ndim,nelt,q,i_n,j_n,j_o,wk) 1 Warning: Type mismatch in argument 'ifseg' at (1); passed INTEGER(4) to LOGICAL(4) genmap.f:141.59: $ (cell,nv,nelt,irnk,dx,ndim,cbc,bc,nfc,w14,w5) 1 Warning: Type mismatch in argument 'iper' at (1); passed REAL(8) to INTEGER(4) genmap.f:2500.30: call sbisect (pmap,f,p2,w,n) 1 Warning: Type mismatch in argument 'p' at (1); passed REAL(8) to INTEGER(4) genmap.f:2594.21: call ax(w,p,ia,ja,va,n) 1 Warning: Actual argument contains too few elements for dummy argument 'ia' (1/2) at (1) genmap.f:2519.30: call lanczos2(f,rr,n,ev,d,u,niter) 1 Warning: Rank mismatch in argument 'ev' at (1) (rank-2 and scalar) genmap.f:2524.27: call sbisect (pmap,f,p2,w,n) 1 Warning: Type mismatch in argument 'p' at (1); passed REAL(8) to INTEGER(4) genmap.f:4025.46: $ ,nel,d,u,r,p2,w,rr,ev,m,ndim) 1 Warning: Rank mismatch in argument 'ev' at (1) (scalar and rank-1) genmap.f:1418.22: call icadd(pmap,p,nel) 1 Warning: Type mismatch in argument 'c' at (1); passed REAL(8) to INTEGER(4) genmap.f:1202.59: $ (n1,n2,pmap(j0),order,mo,elist(j0),n,cell,nv,p,w1,w2,w3) 1 Warning: Type mismatch in argument 'p' at (1); passed INTEGER(4) to REAL(8) genmap.f:146.62: $ ,w1,w2,w3,w4,w5) 1 Warning: Type mismatch in argument 'w3' at (1); passed REAL(8) to INTEGER(4) genmap.f:167.62: $ ,w1,w2,w3,w4,w5) 1 Warning: Type mismatch in argument 'w3' at (1); passed REAL(8) to INTEGER(4) genmap.f:1102.27: call isort(ja(j0),ind,nj) 1 Warning: Rank mismatch in argument 'ind' at (1) (rank-1 and scalar) genmap.f:3605.30: call breadth_first_fill(pb,pmax) 1 Warning: Actual argument contains too few elements for dummy argument 'p' (1/2) at (1) genmap.f:225.21: common /arrayi/ i_n(lpts) , j_n(4*lpts) 1 Warning: Named COMMON block 'arrayi' at (1) shall be of the same size as elsewhere (144000000 vs 48000000 bytes) genmap.f:81.22: common /carrayw/ w1 (lpts) , w2 (lpts) 1 Warning: Named COMMON block 'carrayw' at (1) shall be of the same size as elsewhere (128000000 vs 160000000 bytes) genmap.f:1922.22: common /arrayi2/ face (3*lpts) , elist(lelm) , ind (lpts) 1 Warning: Named COMMON block 'arrayi2' at (1) shall be of the same size as elsewhere (66000000 vs 130000000 bytes) gcc -mcmodel=medium -c -DUNDERSCORE ../../nek/byte.c gfortran -mcmodel=medium -fdefault-real-8 -o /home/kchu10/bin/genmap genmap.o byte.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/genmap' ---------------------- Make n2to3... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/n2to3' gfortran -mcmodel=medium -c n2to3.f n2to3.f:1538.19: len = indx1 (stringo,'$',1) 1 Warning: Rank mismatch in argument 's1' at (1) (scalar and rank-1) n2to3.f:88.20: $ call exitrr('Error, must have zmax > zmin.$',zmin,zmax) 1 Warning: Actual argument contains too few elements for dummy argument 'stringi' (30/132) at (1) n2to3.f:1013.24: if (indx1(sout,skey,nk).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) n2to3.f:1566.28: call readwrite(string,'NEKTON',6) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (6/80) at (1) n2to3.f:1590.28: call readwrite(string,'LOGICAL',7) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (7/80) at (1) n2to3.f:1599.25: $ indx1(string,' T ',3).ne.0) ifflow=.true. 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (3/80) at (1) n2to3.f:1598.25: if(indx1(string,'IFFLOW',6).ne.0.and. 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (6/80) at (1) n2to3.f:1601.25: $ indx1(string,' T ',3).ne.0) ifheat=.true. 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (3/80) at (1) n2to3.f:1600.25: if(indx1(string,'IFHEAT',6).ne.0.and. 1 Warning: Character length of actual argument shorter than of dummy argument 's2' (6/80) at (1) n2to3.f:292.28: call readwrite(string,'XFAC,YFAC',9) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) n2to3.f:1370.31: call sweep_circ (xc,yc,zc,xm,ym,1,z0) ! z0=theta 1 Warning: Rank mismatch in argument 'xc' at (1) (rank-1 and scalar) n2to3.f:1453.22: call chcopy(buf(8),cc,1) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:1379.31: call sweep_circ (xc,yc,zc,xm,ym,1,z1) ! z1=theta 1 Warning: Rank mismatch in argument 'xc' at (1) (rank-1 and scalar) n2to3.f:1387.28: call sweep_circ(xc,yc,zc,x(i,e),y(i,e),1,zh) ! zh=theta 1 Warning: Rank mismatch in argument 'xc' at (1) (rank-1 and scalar) n2to3.f:1214.29: call chcopy(buf(8),ans,1) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:1223.29: call chcopy(buf(16),ans,1) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:1249.29: call chcopy(buf(8),ans,1) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:1258.29: call chcopy(buf(16),ans,1) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:735.31: call blank (buf(8),8) 1 Warning: Type mismatch in argument 's' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:736.31: call chcopy (buf(8),cbc(k,e),3) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:798.33: call blank (buf(8),8) 1 Warning: Type mismatch in argument 's' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:799.33: call chcopy (buf(8),cbc(k,e),3) 1 Warning: Type mismatch in argument 'x' at (1); passed REAL(8) to CHARACTER(1) n2to3.f:616.28: call readwrite(string,'endendend',9) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) n2to3.f:568.28: call readwrite(string,'endendend',9) 1 Warning: Character length of actual argument shorter than of dummy argument 'key' (9/80) at (1) gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -o /home/kchu10/bin/n2to3 n2to3.o byte.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/n2to3' ---------------------- Make postnek... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/postnek' gfortran -mcmodel=medium -c postnek.f postnek.f:1977.19: ifbswap = if_byte_swap_test(test) 1 Warning: Extension: Conversion from INTEGER(4) to LOGICAL(4) at (1) postnek.f:2052.28: call copyi(ig,buf(1 ),1) !1-2 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:2053.31: call copy8b(x,buf( 3),4,iel,nelm) !3-10 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(8) postnek.f:2054.31: call copy8b(y,buf( 11),4,iel,nelm)!11-18 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(8) postnek.f:2058.38: call copy4b(x(iel,1),buf( 2),4,iel,nelm) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) postnek.f:2059.38: call copy4b(y(iel,1),buf( 6),4,iel,nelm) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) postnek.f:2093.28: call copyi(ig,buf(1),1) !1-2 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:2094.31: call copy8b(x,buf( 3),8,iel,nelm) !3-18 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(8) postnek.f:2095.31: call copy8b(y,buf(19),8,iel,nelm) !19-34 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(8) postnek.f:2096.31: call copy8b(z,buf(35),8,iel,nelm) !35-50 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(8) postnek.f:2100.31: call copy4b(x,buf( 2),8,iel,nelm) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) postnek.f:2101.31: call copy4b(y,buf(10),8,iel,nelm) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) postnek.f:2102.31: call copy4b(z,buf(18),8,iel,nelm) 1 Warning: Type mismatch in argument 'b' at (1); passed INTEGER(4) to REAL(4) postnek.f:2159.26: call copyi(iedge,buf(1),1) !1-2 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:2160.26: call copyi(iel ,buf(3),1) !3-4 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:2270.28: call copyi(iel,buf(1),1) !1-2 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:2271.28: call copyi(iside,buf(3),1)!3-4 1 Warning: Rank mismatch in argument 'a' at (1) (rank-1 and scalar) postnek.f:1321.47: CALL GETPT(XLINE(1),YLINE(1),ZLINE(1),' ') 1 Warning: Character length of actual argument shorter than of dummy argument 'flag' (1/26) at (1) postnek.f:1323.47: CALL GETPT(XLINE(2),YLINE(2),ZLINE(2),' ') 1 Warning: Character length of actual argument shorter than of dummy argument 'flag' (1/26) at (1) postnek.f:1386.41: CALL GETPT(XPOINT,YPOINT,ZPOINT,' ') 1 Warning: Character length of actual argument shorter than of dummy argument 'flag' (1/26) at (1) gfortran -mcmodel=medium -c postnek2.f postnek2.f:2129.25: call sgefa(a,lda,n,x,info) 1 Warning: Type mismatch in argument 'ipvt' at (1); passed REAL(4) to INTEGER(4) postnek2.f:2135.25: call sgesl(a,lda,n,x,b,0) 1 Warning: Type mismatch in argument 'ipvt' at (1); passed REAL(4) to INTEGER(4) postnek2.f:2692.25: call compute_f (f1,w ,t ) 1 Warning: Actual argument contains too few elements for dummy argument 'xpos' (1/3) at (1) postnek2.f:3423.31: if_closed = if_close (w,w0,tnew,dtn,k,nstep,iflast) 1 Warning: Actual argument contains too few elements for dummy argument 'w' (3/4) at (1) postnek2.f:1144.44: CALL PROJECT(XLG(1,IS),XXIS,YYIS,2) 1 Warning: Rank mismatch in argument 'v1' at (1) (rank-1 and scalar) postnek2.f:1515.22: CALL PROJECT(U0,V0,W0,4) 1 Warning: Rank mismatch in argument 'v0' at (1) (rank-1 and scalar) gfortran -mcmodel=medium -c postnek3.f postnek3.f:1295.21: lam(i) = zbrent(x1,x0,tol,tolf,kiter,ierr) 1 Warning: More actual than formal arguments in procedure call at (1) postnek3.f:989.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) postnek3.f:1655.20: COMMON /CTMP4/ wk(LXYZ,3,3) 1 Warning: Named COMMON block 'ctmp4' at (1) shall be of the same size as elsewhere (209952 vs 46656 bytes) postnek3.f:3116.20: COMMON /CTMP4/ WORK1(LXYZ),WORK2(LXYZ) 1 Warning: Named COMMON block 'ctmp4' at (1) shall be of the same size as elsewhere (46656 vs 209952 bytes) postnek3.f:1123.20: COMMON /CTMP4/ WORK1(LXYZ),WORK2(LXYZ) 1 Warning: Named COMMON block 'ctmp4' at (1) shall be of the same size as elsewhere (46656 vs 209952 bytes) gfortran -mcmodel=medium -c postnek5.f postnek5.f:1820.33: call map_gll_2_gl(xpr,nx-2,xp(m),nx,if3d) 1 Warning: Rank mismatch in argument 'ugl' at (1) (scalar and rank-1) postnek5.f:1821.33: call map_gll_2_gl(ypr,nx-2,yp(m),nx,if3d) 1 Warning: Rank mismatch in argument 'ugl' at (1) (scalar and rank-1) postnek5.f:1822.33: call map_gll_2_gl(zpr,nx-2,zp(m),nx,if3d) 1 Warning: Rank mismatch in argument 'ugl' at (1) (scalar and rank-1) postnek5.f:1832.33: call map_gll_2_gl(xpr,nx-2,xp(m),nx,if3d) 1 Warning: Rank mismatch in argument 'ugl' at (1) (scalar and rank-1) postnek5.f:1833.33: call map_gll_2_gl(ypr,nx-2,yp(m),nx,if3d) 1 Warning: Rank mismatch in argument 'ugl' at (1) (scalar and rank-1) postnek5.f:1399.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) postnek5.f:48.21: COMMON /ccdiag/ iee 1 Warning: Named COMMON block 'ccdiag' at (1) shall be of the same size as elsewhere (4 vs 8 bytes) postnek5.f:875.21: COMMON /CTMP1x/ TWORK(NXG2),XWORK(NXG2),YWORK(NXG2),ZWORK(NXG2) 1 Warning: Named COMMON block 'ctmp1x' at (1) shall be of the same size as elsewhere (43568 vs 102088 bytes) postnek5.f:1348.21: COMMON /CTMP1x/ VEC(3),VEC1(3),VEC2(3),VEC3(3) 1 Warning: Named COMMON block 'ctmp1x' at (1) shall be of the same size as elsewhere (48 vs 102088 bytes) postnek5.f:1791.21: COMMON /CTMP1x/ xpr(mx2*my2*nzm) 1 Warning: Named COMMON block 'ctmp1x' at (1) shall be of the same size as elsewhere (55296 vs 102088 bytes) postnek5.f:2338.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) gfortran -mcmodel=medium -c postnek6.f gfortran -mcmodel=medium -c tsort.f gfortran -mcmodel=medium -c postnek8.f postnek8.f:737.48: $ (se_to_face,nfctot,vertex,ncrnr,wrk,tmp_face,nfcs) 1 Warning: Type mismatch in argument 'wrk' at (1); passed REAL(4) to INTEGER(4) postnek8.f:1050.20: call selite(nelpf,se_to_face,nfcs,3) 1 Warning: Rank mismatch in argument 'nelpf' at (1) (rank-1 and scalar) postnek8.f:760.21: $ ,nelpf,se_to_face,nfcs) 1 Warning: Rank mismatch in argument 'nelpf' at (1) (scalar and rank-2) postnek8.f:1340.20: call selite(nelpf,se_to_face,nfcs,3) 1 Warning: Rank mismatch in argument 'nelpf' at (1) (rank-1 and scalar) postnek8.f:765.21: $ ,nelpf,se_to_face,nfcs) 1 Warning: Rank mismatch in argument 'nelpf' at (1) (scalar and rank-2) postnek8.f:770.21: $ ,nelpf,se_to_face,nfcs) 1 Warning: Rank mismatch in argument 'nelpf' at (1) (scalar and rank-2) postnek8.f:2703.48: $ (se_to_face,nfctot,vertex,ncrnr,wrk,tmp_face,nfcs) 1 Warning: Type mismatch in argument 'wrk' at (1); passed REAL(4) to INTEGER(4) postnek8.f:2640.38: call get_gxyz(nv,cell,nvc,ncell,ww(n1),ww,ierr) 1 Warning: Type mismatch in argument 'ww' at (1); passed REAL(4) to INTEGER(4) postnek8.f:2657.23: call build_adj (ja,ia,n,cell,nvc,ncell,edge,ne,ww,ww(n1),ww(n2)) 1 Warning: Actual argument contains too few elements for dummy argument 'ja' (1/9) at (1) postnek8.f:2782.38: call build_graph(cell,nvc,ia,ja,ww,b,g 1 Warning: Type mismatch in argument 'ww' at (1); passed INTEGER(4) to REAL(4) postnek8.f:2163.38: call get_gxyz(nv,cell,nvc,ncell,ww(n1),ww,ierr) 1 Warning: Type mismatch in argument 'ww' at (1); passed REAL(4) to INTEGER(4) postnek8.f:2184.23: call build_adj (ja,ia,n,cell,nvc,ncell,edge,ne,ww,ww(n1),ww(n2)) 1 Warning: Actual argument contains too few elements for dummy argument 'ja' (1/9) at (1) postnek8.f:1538.24: call smoother(wkv1,nvc,wkv2,wkv3,work,wrk2,jacm1 1 Warning: Type mismatch in argument 'cell' at (1); passed REAL(4) to INTEGER(4) postnek8.f:2468.38: call get_gxyz(nv,cell,nvc,ncell,ww(n1),ww,ierr) 1 Warning: Type mismatch in argument 'ww' at (1); passed REAL(4) to INTEGER(4) postnek8.f:2490.23: call build_adj (ja,ia,n,cell,nvc,ncell,edge,ne,ww,ww(n1),ww(n2)) 1 Warning: Actual argument contains too few elements for dummy argument 'ja' (1/9) at (1) postnek8.f:1541.13: $ (wkv1,nvc,wkv2,wkv3,work,wrk2,jacm1,x0,x1,x0,x1,z0,z1,eps) 1 Warning: Type mismatch in argument 'cell' at (1); passed REAL(4) to INTEGER(4) postnek8.f:1554.24: call smoother(wkv1,nvc,wkv2,wkv3,work,wrk2,jacm1 1 Warning: Type mismatch in argument 'cell' at (1); passed REAL(4) to INTEGER(4) postnek8.f:1567.13: $ (wkv1,nvc,wkv2,wkv3,work,wrk2,jacm1,x0,x1,x0,x1,z0,z1,eps) 1 Warning: Type mismatch in argument 'cell' at (1); passed REAL(4) to INTEGER(4) postnek8.f:6.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) gfortran -mcmodel=medium -c postnek9.f postnek9.f:1370.25: call compute_fp(f1,w ,t ) 1 Warning: Actual argument contains too few elements for dummy argument 'xpos' (1/3) at (1) gfortran -mcmodel=medium -c plot.f plot.f:401.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) plot.f:414.19: COMMON/SCALE/XFAC,YFAC,XZERO,YZERO 1 Warning: Named COMMON block 'scale' at (1) shall be of the same size as elsewhere (16 vs 32 bytes) gfortran -mcmodel=medium -c getfld.f getfld.f:176.23: do 8 i=1,maxfld-4 1 Warning: DO loop at (1) will be executed zero times getfld.f:797.19: A(1)=REVERTq(A(1),ioldexp,izero) 1 Warning: Type mismatch in argument 't' at (1); passed REAL(4) to CHARACTER(1) getfld.f:800.22: A(I)=REVERTq(A(I),inewexp,izero) 1 Warning: Type mismatch in argument 't' at (1); passed REAL(4) to CHARACTER(1) gfortran -mcmodel=medium -c legend.f gfortran -mcmodel=medium -c userf.f userf.f:5495.32: call tensr3(uh,nx,u,nx,Lj,Ljt,Ljt,w,ndim) 1 Warning: Rank mismatch in argument 'bt' at (1) (scalar and rank-1) userf.f:5211.48: call get_map(pmap,nelp,depth,cell,nv,nrnk,npts,noutflow,73) 1 Warning: Rank mismatch in argument 'npts' at (1) (scalar and rank-1) userf.f:2000.21: common /rlobjs/ col(12,0:mopts-1) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (432 vs 792 bytes) userf.f:1816.21: common /rlobjs/ avg(6,0:mopts-1,3) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (1296 vs 792 bytes) userf.f:1531.21: common /rlobjs/ col(12,0:mopts-1) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (432 vs 1296 bytes) userf.f:2752.20: COMMON /CTMP1/ ARCR(NXM,NYM),ARCS(NXM,NYM) 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (210368 vs 400000 bytes) userf.f:2852.20: COMMON /CTMP1/ ARCR(NXM,NYM),ARCS(NXM,NYM) 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (210368 vs 400000 bytes) userf.f:4794.20: common /ctmp1/ wwz(nxm*nym*nzm),bfh(nzm*nzm),lam(nzm) 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (24696 vs 400000 bytes) userf.f:5336.20: common /ctmp1/ uavg(nxm*nelm),vavg(nxm*nelm),wavg(nxm*nelm) 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (14400000 vs 400000 bytes) userf.f:5588.20: common /ctmp1/ ue(nxm*nym*nzm),ve(nxm*nym*nzm),we(nxm*nym*nzm) 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (116640 vs 14400000 bytes) userf.f:1120.21: common /rlobjs/ x_l_objs(mopts),y_l_objs(mopts),z_l_objs(mopts) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (252 vs 1296 bytes) userf.f:1282.21: common /rlobjs/ x_l_objs(mopts),y_l_objs(mopts),z_l_objs(mopts) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (432 vs 1296 bytes) userf.f:3565.21: common /rlobjs/ col(22,0:mopts-1) 1 Warning: Named COMMON block 'rlobjs' at (1) shall be of the same size as elsewhere (792 vs 1296 bytes) gcc -mcmodel=medium -c -DUNDERSCORE revert.c gfortran -mcmodel=medium -c trap.f trap.f:1567.35: call draw_poly_fill(xyz,3,ifill) 1 Warning: Type mismatch in argument 'iffill' at (1); passed INTEGER(4) to LOGICAL(4) trap.f:1579.35: call draw_poly_fill(xyz,3,ifill) 1 Warning: Type mismatch in argument 'iffill' at (1); passed INTEGER(4) to LOGICAL(4) trap.f:2224.34: call outfld(nx,ny,1,nelxy,2,wkv1,wkv2,wkv3,wkv3,work) 1 Warning: Rank mismatch in argument 'uu' at (1) (scalar and rank-1) trap.f:1454.21: common /vtkwsi/ mx_save,nvtk,nelclip,ncells 1 Warning: Named COMMON block 'vtkwsi' at (1) shall be of the same size as elsewhere (16 vs 12 bytes) trap.f:2017.21: common /vtkwka/ w1 (lvtk) 1 Warning: Named COMMON block 'vtkwka' at (1) shall be of the same size as elsewhere (8000000 vs 16000000 bytes) trap.f:2805.21: common /vtkwka/ w1 (lvtk) 1 Warning: Named COMMON block 'vtkwka' at (1) shall be of the same size as elsewhere (8000000 vs 16000000 bytes) gfortran -mcmodel=medium -c animate.f gfortran -mcmodel=medium -c genxyz.f genxyz.f:518.20: COMMON /CTMP1/ dummy1 1 Warning: Named COMMON block 'ctmp1' at (1) shall be of the same size as elsewhere (4 vs 4752 bytes) genxyz.f:129.20: COMMON /CTMP0/ XCV(3,2,2),VN1(3),VN2(3) 1 Warning: Named COMMON block 'ctmp0' at (1) shall be of the same size as elsewhere (216 vs 4 bytes) gfortran -mcmodel=medium -c screen.f screen.f:608.19: COMMON /CLIP/ XMOVEC,YMOVEC,WT,WB,WL,WR 1 Warning: Named COMMON block 'clip' at (1) shall be of the same size as elsewhere (24 vs 28 bytes) gfortran -mcmodel=medium -c g3d.f gfortran -mcmodel=medium -c subs.f gfortran -mcmodel=medium -c xinterface.f xinterface.f:363.19: COMMON /CLIP/ XMOVEC,YMOVEC,WT,WB,WL,WR 1 Warning: Named COMMON block 'clip' at (1) shall be of the same size as elsewhere (24 vs 28 bytes) gfortran -mcmodel=medium -c locglob.f gfortran -mcmodel=medium -c postnek5a.f postnek5a.f:36.29: call getplane(nsect,stepval) 1 Warning: Type mismatch in argument 'stepval' at (1); passed INTEGER(4) to REAL(4) postnek5a.f:39.34: call new_contour(nsect,stepval,is) 1 Warning: Type mismatch in argument 'stepval' at (1); passed INTEGER(4) to REAL(4) postnek5a.f:40.34: call out_contour(nsect,stepval,is) 1 Warning: Type mismatch in argument 'stepval' at (1); passed INTEGER(4) to REAL(4) postnek5a.f:45.34: call new_contour(nsect,stepval,is) 1 Warning: Type mismatch in argument 'stepval' at (1); passed INTEGER(4) to REAL(4) postnek5a.f:46.34: call out_contour(nsect,stepval,is) 1 Warning: Type mismatch in argument 'stepval' at (1); passed INTEGER(4) to REAL(4) postnek5a.f:259.21: common/Cutting/ptx,pty,ptz,xnor,ynor,znor 1 Warning: Named COMMON block 'cutting' at (1) shall be of the same size as elsewhe re (24 vs 2584 bytes) gfortran -mcmodel=medium -c ../../nek/3rd_party/blas.f ../../nek/3rd_party/blas.f:9764.15: GO TO IGO,(120,150,180,210) 1 Warning: Deleted feature: Assigned GOTO statement at (1) ../../nek/3rd_party/blas.f:9770.72: ASSIGN 120 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:9782.72: ASSIGN 150 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:9795.72: ASSIGN 180 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:9806.72: ASSIGN 210 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:17277.15: GO TO IGO,(120,150,180,210) 1 Warning: Deleted feature: Assigned GOTO statement at (1) ../../nek/3rd_party/blas.f:17283.72: ASSIGN 120 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:17295.72: ASSIGN 150 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:17308.72: ASSIGN 180 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) ../../nek/3rd_party/blas.f:17319.72: ASSIGN 210 TO IGO 1 Warning: Deleted feature: ASSIGN statement at (1) gcc -mcmodel=medium -c -O2 -DUNDERSCORE xdriver.c gfortran -mcmodel=medium -c scrdmp.f gfortran -mcmodel=medium -c coef.f gfortran -mcmodel=medium -c postnek7.f gfortran -mcmodel=medium -c speclib.f gfortran -mcmodel=medium -c mxm.f gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -c ssyev.f gfortran -mcmodel=medium -c iolib.f gfortran -mcmodel=medium -o /home/kchu10/bin/postx postnek.o postnek2.o postnek3 .o postnek5.o postnek6.o tsort.o postnek8.o postnek9.o plot.o getfld.o legend.o u serf.o revert.o trap.o animate.o genxyz.o screen.o g3d.o subs.o xinterface.o locg lob.o postnek5a.o blas.o xdriver.o scrdmp.o coef.o postnek7.o speclib.o mxm.o byt e.o ssyev.o iolib.o -L/usr/lib/X11 -lX11 -lm Linux 2.6.32-504.8.1.el6.x86_64 gfortran -mcmodel=medium -c iolib_no_graph.f iolib_no_graph.f:385.22: CALL GETSOLD(S) 1 Warning: Rank mismatch in argument 's' at (1) (scalar and rank-1) gfortran -mcmodel=medium -o /home/kchu10/bin/postex postnek.o postnek2.o postnek 3.o postnek5.o postnek6.o tsort.o postnek8.o postnek9.o plot.o getfld.o legend.o userf.o revert.o trap.o animate.o genxyz.o screen.o g3d.o subs.o xinterface.o loc glob.o postnek5a.o blas.o xdriver.o scrdmp.o coef.o postnek7.o speclib.o mxm.o by te.o ssyev.o iolib_no_graph.o -L/usr/lib/X11 -lX11 -lm make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/postnek' ---------------------- Make reatore2... ---------------------- make[1]: Entering directory `/home/kchu10/nek5_svn/trunk/tools/reatore2' gfortran -mcmodel=medium -c reatore2.f gcc -mcmodel=medium -c -DUNDERSCORE byte.c gfortran -mcmodel=medium -c strings.f strings.f:17.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) strings.f:44.26: if (indx1(string,input,len).ne.0) return 1 Warning: Rank mismatch in argument 's2' at (1) (scalar and rank-1) gfortran -mcmodel=medium -o /home/kchu10/bin/reatore2 reatore2.o byte.o strings.o gfortran -mcmodel=medium -c re2torea.f gfortran -mcmodel=medium -o /home/kchu10/bin/re2torea re2torea.o byte.o strings.o make[1]: Leaving directory `/home/kchu10/nek5_svn/trunk/tools/reatore2' From nek5000-users at lists.mcs.anl.gov Sat Mar 14 13:54:50 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 14 Mar 2015 14:54:50 -0400 Subject: [Nek5000-users] Error message when executing Nek Message-ID: Hey all, I successfully compiled the eddy example but when I try to execute the nek5000 executable it says the .rea file doesn't exist. The file itself is in the same directory. Any thoughts? Thanks. David H. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 13:57:06 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 14 Mar 2015 18:57:06 +0000 Subject: [Nek5000-users] Error message when executing Nek In-Reply-To: References: Message-ID: Hi David, Are you using the "nek" script in trunk/tools/scripts ? This sets up all the file info for the run. Paul From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Saturday, March 14, 2015 1:54 PM To: Nek Mailing List Subject: [Nek5000-users] Error message when executing Nek Hey all, I successfully compiled the eddy example but when I try to execute the nek5000 executable it says the .rea file doesn't exist. The file itself is in the same directory. Any thoughts? Thanks. David H. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 15:28:07 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 14 Mar 2015 16:28:07 -0400 Subject: [Nek5000-users] Error message when executing Nek In-Reply-To: References: Message-ID: I had forgot about that. On Mar 14, 2015 2:57 PM, wrote: > > > Hi David, > > Are you using the "nek" script in trunk/tools/scripts ? > > This sets up all the file info for the run. > > Paul > > > From: nek5000-users-bounces at lists.mcs.anl.gov [ nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > Sent: Saturday, March 14, 2015 1:54 PM > To: Nek Mailing List > Subject: [Nek5000-users] Error message when executing Nek > > Hey all, > > I successfully compiled the eddy example but when I try to execute the nek5000 executable it says the .rea file doesn't exist. The file itself is in the same directory. Any thoughts? Thanks. > > David H. > > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > Nope, forgot about that. Now that I have the time step files, what's the best way to create the necessary files to upload into VisIt? -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 21:20:57 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 14 Mar 2015 22:20:57 -0400 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Thanks for your help, but I'm not sure I understand. What do you mean by out posting the files? On Mar 1, 2015 10:48 AM, wrote: > Hi David, > > Which files are you referring to? Your own output files or nek outpost > generated ones? The easiest would be to just make a call to outpost and > overwrite the velocity fields and pressure, and use a different name than > your current SESSION, instead of writing out your own data file. > > In this way you can still use the script 'visnek' to create a Visit > readable file (the format visit has for nek is .nek5000 which looks very > simple to tweak if needed). > > Hope I understood your problem correctly, > Oana > > > > ------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > *Sent:* Sunday, March 01, 2015 9:32 AM > *To:* Nek Mailing List > *Subject:* [Nek5000-users] Metadata files > > Hi all, > Would someone be able to help me create a Metadata file, so I can upload > my results into VisIt? I'm under the impression that you have to create a > new file, is that correct? Thanks. > > David H. > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 21:42:52 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 02:42:52 +0000 Subject: [Nek5000-users] Metadata files In-Reply-To: References: , Message-ID: Hi David, I guess your question was in fact simpler, you just need run visnek from scripts and this would create a file *.nek5000 which is readable in visit. You could also write out files using the outpost command in case you have some special fields to visualize (thus outposting, sorry for inventing a new word). Oana ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Saturday, March 14, 2015 9:20 PM To: Nek Mailing List Subject: Re: [Nek5000-users] Metadata files Thanks for your help, but I'm not sure I understand. What do you mean by out posting the files? On Mar 1, 2015 10:48 AM, > wrote: Hi David, Which files are you referring to? Your own output files or nek outpost generated ones? The easiest would be to just make a call to outpost and overwrite the velocity fields and pressure, and use a different name than your current SESSION, instead of writing out your own data file. In this way you can still use the script 'visnek' to create a Visit readable file (the format visit has for nek is .nek5000 which looks very simple to tweak if needed). Hope I understood your problem correctly, Oana ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Sunday, March 01, 2015 9:32 AM To: Nek Mailing List Subject: [Nek5000-users] Metadata files Hi all, Would someone be able to help me create a Metadata file, so I can upload my results into VisIt? I'm under the impression that you have to create a new file, is that correct? Thanks. David H. _______________________________________________ Nek5000-users mailing list Nek5000-users at lists.mcs.anl.gov https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 21:42:51 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 14 Mar 2015 22:42:51 -0400 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Hi David, I have attached a metafile required for opening output of nek5000 in VisIt. You just need to change the name and number of outputs appropriately upon your results. Regards, Ami On Sat, Mar 14, 2015 at 10:20 PM, wrote: > Thanks for your help, but I'm not sure I understand. What do you mean by > out posting the files? > On Mar 1, 2015 10:48 AM, wrote: > >> Hi David, >> >> Which files are you referring to? Your own output files or nek outpost >> generated ones? The easiest would be to just make a call to outpost and >> overwrite the velocity fields and pressure, and use a different name than >> your current SESSION, instead of writing out your own data file. >> >> In this way you can still use the script 'visnek' to create a Visit >> readable file (the format visit has for nek is .nek5000 which looks very >> simple to tweak if needed). >> >> Hope I understood your problem correctly, >> Oana >> >> >> >> ------------------------------ >> *From:* nek5000-users-bounces at lists.mcs.anl.gov [ >> nek5000-users-bounces at lists.mcs.anl.gov] on behalf of >> nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] >> *Sent:* Sunday, March 01, 2015 9:32 AM >> *To:* Nek Mailing List >> *Subject:* [Nek5000-users] Metadata files >> >> Hi all, >> Would someone be able to help me create a Metadata file, so I can upload >> my results into VisIt? I'm under the impression that you have to create a >> new file, is that correct? Thanks. >> >> David H. >> >> _______________________________________________ >> 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test.nek Type: application/octet-stream Size: 85 bytes Desc: not available URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 14 22:54:31 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 03:54:31 +0000 Subject: [Nek5000-users] Metadata files In-Reply-To: References: , Message-ID: I normally use the visnek or nekvis script Paul ________________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Saturday, March 14, 2015 9:42 PM To: nek5000-users at lists.mcs.anl.gov Subject: Re: [Nek5000-users] Metadata files Hi David, I have attached a metafile required for opening output of nek5000 in VisIt. You just need to change the name and number of outputs appropriately upon your results. Regards, Ami On Sat, Mar 14, 2015 at 10:20 PM, > wrote: Thanks for your help, but I'm not sure I understand. What do you mean by out posting the files? On Mar 1, 2015 10:48 AM, > wrote: Hi David, Which files are you referring to? Your own output files or nek outpost generated ones? The easiest would be to just make a call to outpost and overwrite the velocity fields and pressure, and use a different name than your current SESSION, instead of writing out your own data file. In this way you can still use the script 'visnek' to create a Visit readable file (the format visit has for nek is .nek5000 which looks very simple to tweak if needed). Hope I understood your problem correctly, Oana ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Sunday, March 01, 2015 9:32 AM To: Nek Mailing List Subject: [Nek5000-users] Metadata files Hi all, Would someone be able to help me create a Metadata file, so I can upload my results into VisIt? I'm under the impression that you have to create a new file, is that correct? Thanks. David H. _______________________________________________ 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 Sun Mar 15 13:18:28 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 14:18:28 -0400 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Yes, that makes sense, but I get the error "bash: ./visnek: /bin/tcsh: bad interpreter: No such file or directory". Does this mean I'm missing a file in my bin folder? On Mar 14, 2015 10:42 PM, wrote: > Hi David, > > I guess your question was in fact simpler, you just need run visnek from > scripts and this would create a file *.nek5000 which is readable in visit. > You could also write out files using the outpost command in case you have > some special fields to visualize (thus outposting, sorry for inventing a > new word). > > Oana > ------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > *Sent:* Saturday, March 14, 2015 9:20 PM > *To:* Nek Mailing List > *Subject:* Re: [Nek5000-users] Metadata files > > Thanks for your help, but I'm not sure I understand. What do you mean > by out posting the files? > On Mar 1, 2015 10:48 AM, wrote: > >> Hi David, >> >> Which files are you referring to? Your own output files or nek outpost >> generated ones? The easiest would be to just make a call to outpost and >> overwrite the velocity fields and pressure, and use a different name than >> your current SESSION, instead of writing out your own data file. >> >> In this way you can still use the script 'visnek' to create a Visit >> readable file (the format visit has for nek is .nek5000 which looks very >> simple to tweak if needed). >> >> Hope I understood your problem correctly, >> Oana >> >> >> >> ------------------------------ >> *From:* nek5000-users-bounces at lists.mcs.anl.gov [ >> nek5000-users-bounces at lists.mcs.anl.gov] on behalf of >> nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] >> *Sent:* Sunday, March 01, 2015 9:32 AM >> *To:* Nek Mailing List >> *Subject:* [Nek5000-users] Metadata files >> >> Hi all, >> Would someone be able to help me create a Metadata file, so I can upload >> my results into VisIt? I'm under the impression that you have to create a >> new file, is that correct? Thanks. >> >> David H. >> >> _______________________________________________ >> 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 15 13:25:09 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 19:25:09 +0100 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Hi, you need to install tcsh on your system because the visnek script is written for tcsh. Just do (on a Ubuntu system): > sudo apt-get install tcsh and it should work. Philipp On 2015-03-15 19:18, nek5000-users at lists.mcs.anl.gov wrote: > Yes, that makes sense, but I get the error "bash: ./visnek: /bin/tcsh: > bad interpreter: No such file or directory". Does this mean I'm missing > a file in my bin folder? > > On Mar 14, 2015 10:42 PM, > wrote: > > Hi David, > > I guess your question was in fact simpler, you just need run visnek > from scripts and this would create a file *.nek5000 which is > readable in visit. You could also write out files using the outpost > command in case you have some special fields to visualize (thus > outposting, sorry for inventing a new word). > > Oana > ------------------------------------------------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov > > [nek5000-users-bounces at lists.mcs.anl.gov > ] on behalf of > nek5000-users at lists.mcs.anl.gov > > [nek5000-users at lists.mcs.anl.gov > ] > *Sent:* Saturday, March 14, 2015 9:20 PM > *To:* Nek Mailing List > *Subject:* Re: [Nek5000-users] Metadata files > > Thanks for your help, but I'm not sure I understand. What do you > mean by out posting the files? > > On Mar 1, 2015 10:48 AM, > wrote: > > Hi David, > > Which files are you referring to? Your own output files or nek > outpost generated ones? The easiest would be to just make a call > to outpost and overwrite the velocity fields and pressure, and > use a different name than your current SESSION, instead of > writing out your own data file. > > In this way you can still use the script 'visnek' to create a > Visit readable file (the format visit has for nek is .nek5000 > which looks very simple to tweak if needed). > > Hope I understood your problem correctly, > Oana > > > > ------------------------------------------------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov > > [nek5000-users-bounces at lists.mcs.anl.gov > ] on behalf of > nek5000-users at lists.mcs.anl.gov > > [nek5000-users at lists.mcs.anl.gov > ] > *Sent:* Sunday, March 01, 2015 9:32 AM > *To:* Nek Mailing List > *Subject:* [Nek5000-users] Metadata files > > Hi all, > Would someone be able to help me create a Metadata file, so I > can upload my results into VisIt? I'm under the impression that > you have to create a new file, is that correct? Thanks. > > David H. > > > _______________________________________________ > 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 Sun Mar 15 14:16:28 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 19:16:28 +0000 Subject: [Nek5000-users] Output data format and VisIt issue Message-ID: Dear Neks, Recently I've been playing with VisIt and it seems there is still problem reading nek5000 output data in 8-byte format. VisIt reads 4-byte output data successfully but not 8-byte. Is it essential to output data in 4-byte format if I want to use VisIt (ParaView actually can handle both data format well)? Also, in terms of continuing simulations, would 4-byte precision affect the restarting condition? Hope anyone can help. Thank you very much in advance. Kind regards, Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 15 14:37:42 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 15:37:42 -0400 Subject: [Nek5000-users] Metadata files In-Reply-To: References: Message-ID: Thanks, its working fine now. On Mar 15, 2015 2:25 PM, wrote: > Hi, > you need to install tcsh on your system because the visnek script is > written for tcsh. > > Just do (on a Ubuntu system): > > sudo apt-get install tcsh > and it should work. > > Philipp > > On 2015-03-15 19:18, nek5000-users at lists.mcs.anl.gov wrote: > >> Yes, that makes sense, but I get the error "bash: ./visnek: /bin/tcsh: >> bad interpreter: No such file or directory". Does this mean I'm missing >> a file in my bin folder? >> >> On Mar 14, 2015 10:42 PM, > > wrote: >> >> Hi David, >> >> I guess your question was in fact simpler, you just need run visnek >> from scripts and this would create a file *.nek5000 which is >> readable in visit. You could also write out files using the outpost >> command in case you have some special fields to visualize (thus >> outposting, sorry for inventing a new word). >> >> Oana >> ------------------------------------------------------------ >> ------------ >> *From:* nek5000-users-bounces at lists.mcs.anl.gov >> >> [nek5000-users-bounces at lists.mcs.anl.gov >> ] on behalf of >> nek5000-users at lists.mcs.anl.gov >> >> [nek5000-users at lists.mcs.anl.gov >> ] >> *Sent:* Saturday, March 14, 2015 9:20 PM >> *To:* Nek Mailing List >> *Subject:* Re: [Nek5000-users] Metadata files >> >> Thanks for your help, but I'm not sure I understand. What do you >> mean by out posting the files? >> >> On Mar 1, 2015 10:48 AM, > > wrote: >> >> Hi David, >> >> Which files are you referring to? Your own output files or nek >> outpost generated ones? The easiest would be to just make a call >> to outpost and overwrite the velocity fields and pressure, and >> use a different name than your current SESSION, instead of >> writing out your own data file. >> >> In this way you can still use the script 'visnek' to create a >> Visit readable file (the format visit has for nek is .nek5000 >> which looks very simple to tweak if needed). >> >> Hope I understood your problem correctly, >> Oana >> >> >> >> ------------------------------------------------------------ >> ------------ >> *From:* nek5000-users-bounces at lists.mcs.anl.gov >> >> [nek5000-users-bounces at lists.mcs.anl.gov >> ] on behalf of >> nek5000-users at lists.mcs.anl.gov >> >> [nek5000-users at lists.mcs.anl.gov >> ] >> *Sent:* Sunday, March 01, 2015 9:32 AM >> *To:* Nek Mailing List >> *Subject:* [Nek5000-users] Metadata files >> >> Hi all, >> Would someone be able to help me create a Metadata file, so I >> can upload my results into VisIt? I'm under the impression that >> you have to create a new file, is that correct? Thanks. >> >> David H. >> >> >> _______________________________________________ >> 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 > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 15 14:50:53 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 15 Mar 2015 20:50:53 +0100 Subject: [Nek5000-users] Output data format and VisIt issue In-Reply-To: References: Message-ID: Hi, indeed, VisIt even in the latest version does not read the 8-byte format properly. The problem, in fact, is mainly related to the computations of the limits (at least in 2D), and by just setting these manually (in Controls/View) it can be corrected. The data appears to be read in without problem. Jing has analysed the source code of the Nek reader, and fixed the corresponding parts; he has already sent it further to the VisIt developers, and hopefully the next version will read 8-byte files as well. Regarding the restart with 4-byte files, I guess the answer is that it depends on the case and the requirements on accuracy you have. In my opinion, for stability calculations you will not only need 8-byte files, but also the restart from 4 files (aka proper restart). Similar observations we have made for high-Reynolds-number turbulence. On the other hand, for low-Re cases I guess there is not much of a problem. Best regards, Philipp On 2015-03-15 20:16, nek5000-users at lists.mcs.anl.gov wrote: > Dear Neks, > > > Recently I've been playing with VisIt and it seems there is still > problem reading nek5000 output data in 8-byte format. VisIt reads 4-byte > output data successfully but not 8-byte. Is it essential to output data > in 4-byte format if I want to use VisIt (ParaView actually can handle > both data format well)? > > > Also, in terms of continuing simulations, would 4-byte precision affect > the restarting condition? > > > Hope anyone can help. Thank you very much in advance. > > > Kind regards, > > Tony > > > _______________________________________________ > 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 Mon Mar 16 13:46:16 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 16 Mar 2015 18:46:16 +0000 Subject: [Nek5000-users] Nek5000-users Digest, Vol 73, Issue 10 In-Reply-To: References: Message-ID: Hi Philipp, After changing the setting in 'Control/View', VisIt indeed read in the 8-byte output data. However, it seems there are still some problems visualising the data. It didn't show the contour plots properly when I created some slices. I guess we need to look forward to the next version as you mentioned. Thank you very much for your help. Best regards, Tony ________________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov on behalf of nek5000-users-request at lists.mcs.anl.gov Sent: 16 March 2015 17:00 To: nek5000-users at lists.mcs.anl.gov Subject: Nek5000-users Digest, Vol 73, Issue 10 Send Nek5000-users mailing list submissions to nek5000-users at lists.mcs.anl.gov To subscribe or unsubscribe via the World Wide Web, visit https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users or, via email, send a message with subject or body 'help' to nek5000-users-request at lists.mcs.anl.gov You can reach the person managing the list at nek5000-users-owner at lists.mcs.anl.gov When replying, please edit your Subject line so it is more specific than "Re: Contents of Nek5000-users digest..." Today's Topics: 1. Re: Output data format and VisIt issue (nek5000-users at lists.mcs.anl.gov) ---------------------------------------------------------------------- Message: 1 Date: Sun, 15 Mar 2015 20:50:53 +0100 From: nek5000-users at lists.mcs.anl.gov To: nek5000-users at lists.mcs.anl.gov Subject: Re: [Nek5000-users] Output data format and VisIt issue Message-ID: Content-Type: text/plain; charset=windows-1252; format=flowed Hi, indeed, VisIt even in the latest version does not read the 8-byte format properly. The problem, in fact, is mainly related to the computations of the limits (at least in 2D), and by just setting these manually (in Controls/View) it can be corrected. The data appears to be read in without problem. Jing has analysed the source code of the Nek reader, and fixed the corresponding parts; he has already sent it further to the VisIt developers, and hopefully the next version will read 8-byte files as well. Regarding the restart with 4-byte files, I guess the answer is that it depends on the case and the requirements on accuracy you have. In my opinion, for stability calculations you will not only need 8-byte files, but also the restart from 4 files (aka proper restart). Similar observations we have made for high-Reynolds-number turbulence. On the other hand, for low-Re cases I guess there is not much of a problem. Best regards, Philipp On 2015-03-15 20:16, nek5000-users at lists.mcs.anl.gov wrote: > Dear Neks, > > > Recently I've been playing with VisIt and it seems there is still > problem reading nek5000 output data in 8-byte format. VisIt reads 4-byte > output data successfully but not 8-byte. Is it essential to output data > in 4-byte format if I want to use VisIt (ParaView actually can handle > both data format well)? > > > Also, in terms of continuing simulations, would 4-byte precision affect > the restarting condition? > > > Hope anyone can help. Thank you very much in advance. > > > Kind regards, > > Tony > > > _______________________________________________ > 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 End of Nek5000-users Digest, Vol 73, Issue 10 ********************************************* From nek5000-users at lists.mcs.anl.gov Mon Mar 16 16:01:41 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 16 Mar 2015 22:01:41 +0100 Subject: [Nek5000-users] Nek5000-users Digest, Vol 73, Issue 10 In-Reply-To: References: Message-ID: Not sure whether it helps in your case, but this might in fact be related not to 4 vs 8-byte, but rather to interpolation inside Visit. Try to not cut exactly at element boundaries, but just a tiny bit away from is, so for instance don't put a cut at z=0, but rather at z=0.001. This has fixed the problem for us in some situations. Philipp On 2015-03-16 19:46, nek5000-users at lists.mcs.anl.gov wrote: > Hi Philipp, > > After changing the setting in 'Control/View', VisIt indeed read in > the 8-byte output data. However, it seems there are still some > problems visualising the data. It didn't show the contour plots > properly when I created some slices. I guess we need to look forward > to the next version as you mentioned. > > Thank you very much for your help. > > Best regards, Tony > > ________________________________________ From: > nek5000-users-bounces at lists.mcs.anl.gov > on behalf of > nek5000-users-request at lists.mcs.anl.gov > Sent: 16 March 2015 17:00 > To: nek5000-users at lists.mcs.anl.gov Subject: Nek5000-users Digest, > Vol 73, Issue 10 > > Send Nek5000-users mailing list submissions to > nek5000-users at lists.mcs.anl.gov > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users or, via > email, send a message with subject or body 'help' to > nek5000-users-request at lists.mcs.anl.gov > > You can reach the person managing the list at > nek5000-users-owner at lists.mcs.anl.gov > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Nek5000-users digest..." > > > Today's Topics: > > 1. Re: Output data format and VisIt issue > (nek5000-users at lists.mcs.anl.gov) > > > ---------------------------------------------------------------------- > > Message: 1 Date: Sun, 15 Mar 2015 20:50:53 +0100 From: > nek5000-users at lists.mcs.anl.gov To: nek5000-users at lists.mcs.anl.gov > Subject: Re: [Nek5000-users] Output data format and VisIt issue > Message-ID: > > Content-Type: text/plain; charset=windows-1252; format=flowed > > Hi, indeed, VisIt even in the latest version does not read the 8-byte > format properly. The problem, in fact, is mainly related to the > computations of the limits (at least in 2D), and by just setting > these manually (in Controls/View) it can be corrected. The data > appears to be read in without problem. > > Jing has analysed the source code of the Nek reader, and fixed the > corresponding parts; he has already sent it further to the VisIt > developers, and hopefully the next version will read 8-byte files as > well. > > Regarding the restart with 4-byte files, I guess the answer is that > it depends on the case and the requirements on accuracy you have. In > my opinion, for stability calculations you will not only need 8-byte > files, but also the restart from 4 files (aka proper restart). > Similar observations we have made for high-Reynolds-number > turbulence. On the other hand, for low-Re cases I guess there is not > much of a problem. > > Best regards, Philipp > > > On 2015-03-15 20:16, nek5000-users at lists.mcs.anl.gov wrote: >> Dear Neks, >> >> >> Recently I've been playing with VisIt and it seems there is still >> problem reading nek5000 output data in 8-byte format. VisIt reads >> 4-byte output data successfully but not 8-byte. Is it essential to >> output data in 4-byte format if I want to use VisIt (ParaView >> actually can handle both data format well)? >> >> >> Also, in terms of continuing simulations, would 4-byte precision >> affect the restarting condition? >> >> >> Hope anyone can help. Thank you very much in advance. >> >> >> Kind regards, >> >> Tony >> >> >> _______________________________________________ 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 > > > End of Nek5000-users Digest, Vol 73, Issue 10 > ********************************************* > _______________________________________________ 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 Mon Mar 16 16:23:09 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 16 Mar 2015 17:23:09 -0400 Subject: [Nek5000-users] VisIt error: The first time step in a Nek file must contain a mesh In-Reply-To: References: Message-ID: Hi Muhsin, Could you solve your problem? It's weird but I kinda have the same issue. I'm working on an example for heat transfer in a rectangle (2D problem) and when I use elements of the form 2X2 or 4X4 it works fine. However, when I increase the number of elements to, say, 8X8 (to exploit using more nodes of course), although the solver works fine and generates all the corresponding fld files as expected but there is the error of "The first time step in a Nek file must contain a mesh" in Visit. As I said, for fewer number of elements for very same problem I don't get the problem. I appreciate if you or anyone share any solutions here. Just to reiterate, I also checked the first line of first time step and meta data, etc. but found no issue. PS is there a way to export results as csv without referring to Visit? If it is so, I'd sometimes prefer to use it. Best, Saleh On 12/18/2014 7:54 AM, nek5000-users at lists.mcs.anl.gov wrote: > Hi all, > > I get error of mesh need to contain the first time step in Nek file > everytime I run .nek5000 file from results of some example > (turbchannel, blasius and expansion). However for the 3dbox example, I > got no error to open it. > I've checked the first line in the first time step file (.f00001) and > have the geometry (X) in them. I also changed the logic for coordinate > output to (T COORDINATES) and different param66, but still getting the > same error. Perhaps even if I put the mesh output for each timestep > not just in first timestep, I still getting the same error. Note that > I've already set the right plugin and type file during open the > .Nek5000 file. In addition, I've checked the same parameters for 3dbox > example which is same with the other example rea file, plus 3dbox > still gives me no error even if i not switch the coordinate output to > true (F COORDINATES) > > I really hope that anyone who has encountered the same problem and has > solved it to assist me. That would be really helpful. > > Regards, > -- > Muhsin Mohd Amin > Graduate Student > Department of Mechanical Engineering > The University of Sheffield > > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Tue Mar 17 13:08:30 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Tue, 17 Mar 2015 19:08:30 +0100 Subject: [Nek5000-users] Wall BC Message-ID: Hi Neks, I'm new user, and I'd like to know if using the "v" boundary condition at wall in the .rea file and then imposing the velocity equals to zero in the .usr file, gives the same result as directly imposing the Wall BC "W" in the .rea file. thanks Regards Alessandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Tue Mar 17 16:26:44 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Tue, 17 Mar 2015 21:26:44 +0000 Subject: [Nek5000-users] Wall BC In-Reply-To: References: Message-ID: Yes -- those would be the same... Paul ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Tuesday, March 17, 2015 1:08 PM To: nek5000-users at lists.mcs.anl.gov Subject: [Nek5000-users] Wall BC Hi Neks, I'm new user, and I'd like to know if using the "v" boundary condition at wall in the .rea file and then imposing the velocity equals to zero in the .usr file, gives the same result as directly imposing the Wall BC "W" in the .rea file. thanks Regards Alessandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Wed Mar 18 14:11:44 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 18 Mar 2015 15:11:44 -0400 Subject: [Nek5000-users] End time / time step settings Message-ID: Hey all, Where can I edit run time/ timestep values? Thanks. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Fri Mar 20 06:57:27 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 20 Mar 2015 11:57:27 +0000 Subject: [Nek5000-users] Test case example1 In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Neks, I was wondering if there would be a way of testing the output of Nekbone(example1) for a given input parameters. The reason behind is that we are currently working on the communication section of Nekbone and any modification could obviously change the output and therefore correctness of the code. Any ideas would very useful. Regards, L -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJVDAsnAAoJEIhcgrtekvd+L0gIAJVuy7i3SM96gBnzJxDiey7d AP4XlPNGYmWHd+j3RIy76fLOGq8CQDDTzJrmFlcz+1I3GP3+NTrhCk3uc2cl7D/P 1TdGQei5a6z/tDUs7mlTg44gNRH5Jl0GWV8LjaJYccHMNKJYX3nWhgRTlQWABrAa yJx/+sRCu1VRtyLF246PeZ0PfCHtCDnmteoprLTphUI4MUA1ynaYnmoMZR4e4b6W eQLHSLcr5gdaQiwIntcoEshjvj8XsAWGJXLjyW3ew4yKaSNdOolPbTeZSzeWE0vB 9HqtZ4PeXJbUaaNM8UNLgiiW3lUUbDgOyL7InIr6U87OJi7I42uhuHLR8Hv+GBo= =xHH0 -----END PGP SIGNATURE----- -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. From nek5000-users at lists.mcs.anl.gov Wed Mar 25 13:09:05 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 25 Mar 2015 13:09:05 -0500 Subject: [Nek5000-users] Merging mesh - mesh tolerance Message-ID: Dear nek5000 users, I got the following error after merging two meshes. However, I don't understand the message. Is there any problem? What does it mean? Thank you very much. Regards, Simon Error message : 2773 2 4 Matrix: SELF!! 1 SELF!! 1189 1377 1189 1377 2 SELF!! 1360 1206 1360 1206 cont: SELF!! 2773 ?? ABORT: SELF-CHK 1 5 2773 0 Try to tighten the mesh tolerance! 3024 8 10 Matrix T: slfchk 3024 0 1 slfchk 2116 2275 2288 2133 2121 2276 2289 2138 2 slfchk 2275 2587 2574 2288 2276 2588 2575 2289 3 slfchk 2587 2821 2769 2574 2588 2822 2770 2575 4 slfchk 2821 2951 2912 2769 2822 2952 2913 2770 5 slfchk 2951 3120 3081 2912 2952 3121 3082 2913 6 slfchk 3120 3237 3224 3081 3121 3238 3225 3082 7 slfchk 3237 3302 3263 3224 3238 3303 3264 3225 8 slfchk 3302 3341 3289 3263 3303 3342 3290 3264 9 slfchk 3341 3354 3328 3289 3342 3355 3329 3290 10 slfchk 2133 2288 2301 2150 2138 2289 2302 2155 3024 this is nel in prexit -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Thu Mar 26 04:40:50 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 26 Mar 2015 10:40:50 +0100 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores Message-ID: Dear All, I have setup a simulation with Nek's constant flow rate option. The simulation consisted of a number of restarts, in particular one restart was carried out on 16384 cores whilst all the other runs where on 8192 cores. In the plot of flow rate against dump in the following link, which I carry out with my post-processor, the flow rate oscillates strangely in the region where the run was on 16384 cores, i.e. between 220 and 343. https://www.dropbox.com/s/fnfuqhj2nxbh5g5/FlowRate_restart_section.png?dl=0 Any idea on what might be causing this oscillation? All parameters, geometry, machine settings etc. have been left the same for the run on 16384 cores (except for changing the max no. of processors and max no. of elements per processor in SIZE). Regards, JP -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Thu Mar 26 07:07:55 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Thu, 26 Mar 2015 13:07:55 +0100 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores In-Reply-To: References: Message-ID: Dear JP, We have been using the constant flow rate feature in a number of cases as well, but we have not seen your problem. Maybe a more general question; why does the flow rate vary at all in your case? In all our cases, due to the implicit superposition of the Stokes solution, we get the flow rate exactly constant without fluctuations. Best regards, Philipp On 2015-03-26 10:40, nek5000-users at lists.mcs.anl.gov wrote: > Dear All, > > I have setup a simulation with Nek's constant flow rate option. The > simulation consisted of a number of restarts, in particular one restart > was carried out on 16384 cores whilst all the other runs where on 8192 > cores. In the plot of flow rate against dump in the following link, > which I carry out with my post-processor, the flow rate oscillates > strangely in the region where the run was on 16384 cores, i.e. between > 220 and 343. > > https://www.dropbox.com/s/fnfuqhj2nxbh5g5/FlowRate_restart_section.png?dl=0 > > Any idea on what might be causing this oscillation? All parameters, > geometry, machine settings etc. have been left the same for the run on > 16384 cores (except for changing the max no. of processors and max no. > of elements per processor in SIZE). > > Regards, > JP > > > _______________________________________________ > 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 Mar 25 12:25:03 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Wed, 25 Mar 2015 12:25:03 -0500 Subject: [Nek5000-users] Cartesian-to-cylindrical mesh resolution Message-ID: Dear nek5000 users, Recently I have defined a cylinder geometry, with boxes at the centre, curved elements at the side. However, the connection of elements at the transition is not perfect, in the attachment. Will the resolution be fine? Is there any better way to solve this problem? It seems I need to draw my own grid through prenek. Thank you. Regards, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: issue.jpg Type: image/jpeg Size: 85228 bytes Desc: not available URL: From nek5000-users at lists.mcs.anl.gov Fri Mar 27 12:41:06 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 27 Mar 2015 17:41:06 +0000 Subject: [Nek5000-users] Cartesian-to-cylindrical mesh resolution In-Reply-To: References: Message-ID: Hi Simon, I'm not certain of the origins of your mesh, but the resolution would be to define a 6x6 box for the interior, instead of 8x8. That part can be done with genbox. hth, Paul ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Wednesday, March 25, 2015 12:25 PM To: nek5000-users Subject: [Nek5000-users] Cartesian-to-cylindrical mesh resolution Dear nek5000 users, Recently I have defined a cylinder geometry, with boxes at the centre, curved elements at the side. However, the connection of elements at the transition is not perfect, in the attachment. Will the resolution be fine? Is there any better way to solve this problem? It seems I need to draw my own grid through prenek. Thank you. Regards, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Fri Mar 27 12:47:30 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 27 Mar 2015 12:47:30 -0500 Subject: [Nek5000-users] Cartesian-to-cylindrical mesh resolution In-Reply-To: References: Message-ID: Dear Paul, Yes, that's what I did. But I got another error message, which I don't know how to solve. Do you have any idea? 2773 2 4 Matrix: SELF!! 1 SELF!! 1189 1377 1189 1377 2 SELF!! 1360 1206 1360 1206 cont: SELF!! 2773 ?? ABORT: SELF-CHK 1 5 2773 0 Try to tighten the mesh tolerance! 3024 8 10 Matrix T: slfchk 3024 0 1 slfchk 2116 2275 2288 2133 2121 2276 2289 2138 2 slfchk 2275 2587 2574 2288 2276 2588 2575 2289 3 slfchk 2587 2821 2769 2574 2588 2822 2770 2575 4 slfchk 2821 2951 2912 2769 2822 2952 2913 2770 5 slfchk 2951 3120 3081 2912 2952 3121 3082 2913 6 slfchk 3120 3237 3224 3081 3121 3238 3225 3082 7 slfchk 3237 3302 3263 3224 3238 3303 3264 3225 8 slfchk 3302 3341 3289 3263 3303 3342 3290 3264 9 slfchk 3341 3354 3328 3289 3342 3355 3329 3290 10 slfchk 2133 2288 2301 2150 2138 2289 2302 2155 3024 this is nel in prexit Thanks. Regards, Simon 2015-03-27 12:41 GMT-05:00 : > > Hi Simon, > > I'm not certain of the origins of your mesh, but the resolution would be > to > define a 6x6 box for the interior, instead of 8x8. That part can be done > with genbox. > > hth, > > Paul > > ------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > *Sent:* Wednesday, March 25, 2015 12:25 PM > *To:* nek5000-users > *Subject:* [Nek5000-users] Cartesian-to-cylindrical mesh resolution > > Dear nek5000 users, > > Recently I have defined a cylinder geometry, with boxes at the centre, > curved elements at the side. However, the connection of elements at the > transition is not perfect, in the attachment. > > Will the resolution be fine? Is there any better way to solve this > problem? It seems I need to draw my own grid through prenek. > > Thank you. > > Regards, > Simon > > _______________________________________________ > Nek5000-users mailing list > Nek5000-users at lists.mcs.anl.gov > https://lists.mcs.anl.gov/mailman/listinfo/nek5000-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Fri Mar 27 19:43:12 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Fri, 27 Mar 2015 20:43:12 -0400 Subject: [Nek5000-users] NELGT is 0! Message-ID: Hi, I am running this example with 512 elements, however I get an error: read .rea file nelgt/nelgv/lelt: 512 512 512 lx1 /lx2 /lx3 : 6 4 6 mapping elements to processors ABORT: Too many processors ( 1) for to few elements ( 0). ABORTING IN MAPELPR. This is on Cetus at ANL. As can be seen, the .rea file is read successfully and nelgt is set to 512 in connect2.f, however, inside subroutine mapelpr, NELGT gets set to 0. I have no clue why its value is changing. This does not happen on my local machine. The program was compiled on Cetus using mpixlf77 and mpixlc. Any help is greatly appreciated. Thanks, Tania From nek5000-users at lists.mcs.anl.gov Sat Mar 28 14:01:07 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 28 Mar 2015 20:01:07 +0100 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores Message-ID: Dear Philipp, The slight flow rate variations are probably due to quick way we calculate the flow rate.. this is calculated on custom files that contain data which was converted from the original nek dumps.. the mesh spacing is not constant in the y direction and probably causes some oscillations.. what I cannot understand is how changing the number of cores affects this oscillation so much in the region where more cores were used... Regards, JP -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 28 14:10:11 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 28 Mar 2015 20:10:11 +0100 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores In-Reply-To: References: Message-ID: Hi JP, Yes, but I was just thinking that the fact that you do not recover an exactly constant flow rate, while the algorithm in Nek in principle assures exact constancy, might have something to do with your problem. If you check the output of Nek (the logfile), there should be a line with the computed flow rates and the forcing amplitude (the line ends with something like "volflow"). Could it be that your postprocessing routines are somehow affected by the different numbers of processors? philipp On 2015-03-28 20:01, nek5000-users at lists.mcs.anl.gov wrote: > Dear Philipp, > > The slight flow rate variations are probably due to quick way we > calculate the flow rate.. this is calculated on custom files that > contain data which was converted from the original nek dumps.. the mesh > spacing is not constant in the y direction and probably causes some > oscillations.. what I cannot understand is how changing the number of > cores affects this oscillation so much in the region where more cores > were used... > > Regards, > JP > > > _______________________________________________ > 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 Sat Mar 28 20:49:52 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sat, 28 Mar 2015 20:49:52 -0500 Subject: [Nek5000-users] Mesh merging - no curved side data left Message-ID: Dear all, I tried to merge a cylinder with a rectangular hole, with a rectangular box. After merging them, the curved side data in the cylinder is lost. Is there a way to preserve the curvature? Also, I got error with mesh tolerance. Anyone knows what the error means? Performing unique_vertex2 self_chk 24192 2773 2 4 Matrix: SELF!! 1 SELF!! 1189 1377 1189 1377 2 SELF!! 1360 1206 1360 1206 cont: SELF!! 2773 ?? ABORT: SELF-CHK 1 5 2773 0 Try to tighten the mesh tolerance! 3024 8 10 Matrix T: slfchk 3024 0 1 slfchk 2116 2275 2288 2133 2121 2276 2289 2138 2 slfchk 2275 2587 2574 2288 2276 2588 2575 2289 3 slfchk 2587 2821 2769 2574 2588 2822 2770 2575 4 slfchk 2821 2951 2912 2769 2822 2952 2913 2770 5 slfchk 2951 3120 3081 2912 2952 3121 3082 2913 6 slfchk 3120 3237 3224 3081 3121 3238 3225 3082 7 slfchk 3237 3302 3263 3224 3238 3303 3264 3225 8 slfchk 3302 3341 3289 3263 3303 3342 3290 3264 9 slfchk 3341 3354 3328 3289 3342 3355 3329 3290 10 slfchk 2133 2288 2301 2150 2138 2289 2302 2155 3024 this is nel in prexit Thank you very much. Regards, Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sat Mar 28 22:40:27 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 29 Mar 2015 03:40:27 +0000 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores In-Reply-To: References: , Message-ID: Hi JP, Are you using p54 and p55 in the .rea file to set the flow rate to a fixed value? This is by far the best approach to doing so for periodic bcs. Paul ________________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Saturday, March 28, 2015 2:10 PM To: nek5000-users at lists.mcs.anl.gov Subject: Re: [Nek5000-users] Flow Rate Oscillation on 16384 cores Hi JP, Yes, but I was just thinking that the fact that you do not recover an exactly constant flow rate, while the algorithm in Nek in principle assures exact constancy, might have something to do with your problem. If you check the output of Nek (the logfile), there should be a line with the computed flow rates and the forcing amplitude (the line ends with something like "volflow"). Could it be that your postprocessing routines are somehow affected by the different numbers of processors? philipp On 2015-03-28 20:01, nek5000-users at lists.mcs.anl.gov wrote: > Dear Philipp, > > The slight flow rate variations are probably due to quick way we > calculate the flow rate.. this is calculated on custom files that > contain data which was converted from the original nek dumps.. the mesh > spacing is not constant in the y direction and probably causes some > oscillations.. what I cannot understand is how changing the number of > cores affects this oscillation so much in the region where more cores > were used... > > Regards, > JP > > > _______________________________________________ > 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 Sun Mar 29 12:57:29 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 29 Mar 2015 19:57:29 +0200 Subject: [Nek5000-users] Flow Rate Oscillation on 16384 cores Message-ID: Hi Philipp, Yes thanks I solved the problem. It was in fact a slight change I had to do when converting Nek files since changing the number of cores slightly changes the way the Nek dump is written. All is ok now. Thank you, jp -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 29 16:58:27 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 29 Mar 2015 16:58:27 -0500 Subject: [Nek5000-users] lx1 ly1 lz1 not match Message-ID: Hi, I am currently running a case, which gives me this error. Does anyone know which part of .rea it belongs to? read .rea file ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D I have checked in SIZE and the parameters match there. I don't know where they are in .rea Thanks, Chu -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Sun Mar 29 17:04:25 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 30 Mar 2015 00:04:25 +0200 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: Message-ID: Hi, you need to set ldim=2 in the SIZE file for a 2D case, or - if you want 3D - set lz1=12. Best regards, Philipp On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov wrote: > Hi, > > I am currently running a case, which gives me this error. Does anyone > know which part of .rea it belongs to? > > read .rea file > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > I have checked in SIZE and the parameters match there. I don't know > where they are in .rea > > Thanks, > Chu > > > _______________________________________________ > 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 Sun Mar 29 17:45:41 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 29 Mar 2015 22:45:41 +0000 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: , Message-ID: Yes, exactly -- I would recommend, Chu, to start from a 3D example case, like SIZE for turbChannel Aleks ________________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Sunday, March 29, 2015 5:04 PM To: nek5000-users at lists.mcs.anl.gov Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match Hi, you need to set ldim=2 in the SIZE file for a 2D case, or - if you want 3D - set lz1=12. Best regards, Philipp On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov wrote: > Hi, > > I am currently running a case, which gives me this error. Does anyone > know which part of .rea it belongs to? > > read .rea file > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > I have checked in SIZE and the parameters match there. I don't know > where they are in .rea > > Thanks, > Chu > > > _______________________________________________ > 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 Sun Mar 29 17:55:31 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Sun, 29 Mar 2015 17:55:31 -0500 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: Message-ID: Hi, I have already set ldim = 3 and lx1=ly1=lz1 here. Is there anything wrong here? parameter (ldim=3) parameter (lx1=12,ly1=lx1,lz1=lx1,lelt=100,lelv=lelt) parameter (lxd=18,lyd=lxd,lzd=lxd) parameter (lelx=1,lely=1,lelz=1) Thanks, Chu 2015-03-29 17:45 GMT-05:00 : > Yes, exactly -- I would recommend, Chu, to start from a 3D example case, > like SIZE for turbChannel > > Aleks > ________________________________________ > From: nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > Sent: Sunday, March 29, 2015 5:04 PM > To: nek5000-users at lists.mcs.anl.gov > Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match > > Hi, > you need to set ldim=2 in the SIZE file for a 2D case, or - if you want > 3D - set lz1=12. > > Best regards, > Philipp > > On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov wrote: > > Hi, > > > > I am currently running a case, which gives me this error. Does anyone > > know which part of .rea it belongs to? > > > > read .rea file > > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > > > I have checked in SIZE and the parameters match there. I don't know > > where they are in .rea > > > > Thanks, > > Chu > > > > > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Mon Mar 30 06:53:59 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 30 Mar 2015 13:53:59 +0200 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: Message-ID: the other location where you should set the dimensionality is the third line of the rea file (ndim), but Nek checks whether ldim is the same as ndim before the error message you mention. Otherwise your snippet looks good. Philipp On 2015-03-30 00:55, nek5000-users at lists.mcs.anl.gov wrote: > Hi, > > I have already set ldim = 3 and lx1=ly1=lz1 here. Is there anything > wrong here? > > parameter (ldim=3) > parameter (lx1=12,ly1=lx1,lz1=lx1,lelt=100,lelv=lelt) > parameter (lxd=18,lyd=lxd,lzd=lxd) > parameter (lelx=1,lely=1,lelz=1) > > Thanks, > Chu > > > 2015-03-29 17:45 GMT-05:00 >: > > Yes, exactly -- I would recommend, Chu, to start from a 3D example > case, like SIZE for turbChannel > > Aleks > ________________________________________ > From: nek5000-users-bounces at lists.mcs.anl.gov > > [nek5000-users-bounces at lists.mcs.anl.gov > ] on behalf of > nek5000-users at lists.mcs.anl.gov > > [nek5000-users at lists.mcs.anl.gov > ] > Sent: Sunday, March 29, 2015 5:04 PM > To: nek5000-users at lists.mcs.anl.gov > > Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match > > Hi, > you need to set ldim=2 in the SIZE file for a 2D case, or - if you want > 3D - set lz1=12. > > Best regards, > Philipp > > On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov > wrote: > > Hi, > > > > I am currently running a case, which gives me this error. Does anyone > > know which part of .rea it belongs to? > > > > read .rea file > > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > > > I have checked in SIZE and the parameters match there. I don't know > > where they are in .rea > > > > Thanks, > > Chu > > > > > > _______________________________________________ > > 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 Mon Mar 30 17:06:51 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 30 Mar 2015 17:06:51 -0500 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: Message-ID: Hi everyone, I did try a few times, but the problem persists. Any idea what's going on? Thanks, Chu 2015-03-30 6:53 GMT-05:00 : > the other location where you should set the dimensionality is the third > line of the rea file (ndim), but Nek checks whether ldim is the same as > ndim before the error message you mention. Otherwise your snippet looks > good. > Philipp > > On 2015-03-30 00:55, nek5000-users at lists.mcs.anl.gov wrote: > > Hi, > > > > I have already set ldim = 3 and lx1=ly1=lz1 here. Is there anything > > wrong here? > > > > parameter (ldim=3) > > parameter (lx1=12,ly1=lx1,lz1=lx1,lelt=100,lelv=lelt) > > parameter (lxd=18,lyd=lxd,lzd=lxd) > > parameter (lelx=1,lely=1,lelz=1) > > > > Thanks, > > Chu > > > > > > 2015-03-29 17:45 GMT-05:00 > >: > > > > Yes, exactly -- I would recommend, Chu, to start from a 3D example > > case, like SIZE for turbChannel > > > > Aleks > > ________________________________________ > > From: nek5000-users-bounces at lists.mcs.anl.gov > > > > [nek5000-users-bounces at lists.mcs.anl.gov > > ] on behalf of > > nek5000-users at lists.mcs.anl.gov > > > > [nek5000-users at lists.mcs.anl.gov > > ] > > Sent: Sunday, March 29, 2015 5:04 PM > > To: nek5000-users at lists.mcs.anl.gov > > > > Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match > > > > Hi, > > you need to set ldim=2 in the SIZE file for a 2D case, or - if you > want > > 3D - set lz1=12. > > > > Best regards, > > Philipp > > > > On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov > > wrote: > > > Hi, > > > > > > I am currently running a case, which gives me this error. Does > anyone > > > know which part of .rea it belongs to? > > > > > > read .rea file > > > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > > > > > I have checked in SIZE and the parameters match there. I don't know > > > where they are in .rea > > > > > > Thanks, > > > Chu > > > > > > > > > _______________________________________________ > > > 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 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 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Mon Mar 30 17:24:07 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 30 Mar 2015 22:24:07 +0000 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: , Message-ID: Hi Chu, Does the "vortex" example run for you? Paul Fischer ________________________________ From: nek5000-users-bounces at lists.mcs.anl.gov [nek5000-users-bounces at lists.mcs.anl.gov] on behalf of nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] Sent: Monday, March 30, 2015 5:06 PM To: nek5000-users Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match Hi everyone, I did try a few times, but the problem persists. Any idea what's going on? Thanks, Chu 2015-03-30 6:53 GMT-05:00 >: the other location where you should set the dimensionality is the third line of the rea file (ndim), but Nek checks whether ldim is the same as ndim before the error message you mention. Otherwise your snippet looks good. Philipp On 2015-03-30 00:55, nek5000-users at lists.mcs.anl.gov wrote: > Hi, > > I have already set ldim = 3 and lx1=ly1=lz1 here. Is there anything > wrong here? > > parameter (ldim=3) > parameter (lx1=12,ly1=lx1,lz1=lx1,lelt=100,lelv=lelt) > parameter (lxd=18,lyd=lxd,lzd=lxd) > parameter (lelx=1,lely=1,lelz=1) > > Thanks, > Chu > > > 2015-03-29 17:45 GMT-05:00 > >>: > > Yes, exactly -- I would recommend, Chu, to start from a 3D example > case, like SIZE for turbChannel > > Aleks > ________________________________________ > From: nek5000-users-bounces at lists.mcs.anl.gov > > > [nek5000-users-bounces at lists.mcs.anl.gov > >] on behalf of > nek5000-users at lists.mcs.anl.gov > > > [nek5000-users at lists.mcs.anl.gov > >] > Sent: Sunday, March 29, 2015 5:04 PM > To: nek5000-users at lists.mcs.anl.gov > > > Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match > > Hi, > you need to set ldim=2 in the SIZE file for a 2D case, or - if you want > 3D - set lz1=12. > > Best regards, > Philipp > > On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov > > wrote: > > Hi, > > > > I am currently running a case, which gives me this error. Does anyone > > know which part of .rea it belongs to? > > > > read .rea file > > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D > > > > I have checked in SIZE and the parameters match there. I don't know > > where they are in .rea > > > > Thanks, > > Chu > > > > > > _______________________________________________ > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Mon Mar 30 17:37:36 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Mon, 30 Mar 2015 17:37:36 -0500 Subject: [Nek5000-users] lx1 ly1 lz1 not match In-Reply-To: References: Message-ID: Yes, I did a nek10s. It works all fine. Thanks, Chu 2015-03-30 17:24 GMT-05:00 : > > Hi Chu, > > Does the "vortex" example run for you? > > Paul Fischer > > ------------------------------ > *From:* nek5000-users-bounces at lists.mcs.anl.gov [ > nek5000-users-bounces at lists.mcs.anl.gov] on behalf of > nek5000-users at lists.mcs.anl.gov [nek5000-users at lists.mcs.anl.gov] > *Sent:* Monday, March 30, 2015 5:06 PM > *To:* nek5000-users > > *Subject:* Re: [Nek5000-users] lx1 ly1 lz1 not match > > Hi everyone, > > I did try a few times, but the problem persists. Any idea what's going > on? > > Thanks, > Chu > > 2015-03-30 6:53 GMT-05:00 : > >> the other location where you should set the dimensionality is the third >> line of the rea file (ndim), but Nek checks whether ldim is the same as >> ndim before the error message you mention. Otherwise your snippet looks >> good. >> Philipp >> >> On 2015-03-30 00:55, nek5000-users at lists.mcs.anl.gov wrote: >> > Hi, >> > >> > I have already set ldim = 3 and lx1=ly1=lz1 here. Is there anything >> > wrong here? >> > >> > parameter (ldim=3) >> > parameter (lx1=12,ly1=lx1,lz1=lx1,lelt=100,lelv=lelt) >> > parameter (lxd=18,lyd=lxd,lzd=lxd) >> > parameter (lelx=1,lely=1,lelz=1) >> > >> > Thanks, >> > Chu >> > >> > >> > 2015-03-29 17:45 GMT-05:00 > > >: >> > >> > Yes, exactly -- I would recommend, Chu, to start from a 3D example >> > case, like SIZE for turbChannel >> > >> > Aleks >> > ________________________________________ >> > From: nek5000-users-bounces at lists.mcs.anl.gov >> > >> > [nek5000-users-bounces at lists.mcs.anl.gov >> > ] on behalf of >> > nek5000-users at lists.mcs.anl.gov >> > >> > [nek5000-users at lists.mcs.anl.gov >> > ] >> > Sent: Sunday, March 29, 2015 5:04 PM >> > To: nek5000-users at lists.mcs.anl.gov >> > >> > Subject: Re: [Nek5000-users] lx1 ly1 lz1 not match >> > >> > Hi, >> > you need to set ldim=2 in the SIZE file for a 2D case, or - if you >> want >> > 3D - set lz1=12. >> > >> > Best regards, >> > Philipp >> > >> > On 2015-03-29 23:58, nek5000-users at lists.mcs.anl.gov >> > wrote: >> > > Hi, >> > > >> > > I am currently running a case, which gives me this error. Does >> anyone >> > > know which part of .rea it belongs to? >> > > >> > > read .rea file >> > > ERROR: lx1,ly1,lz1: 12 12 1 must be equal for 3D >> > > >> > > I have checked in SIZE and the parameters match there. I don't >> know >> > > where they are in .rea >> > > >> > > Thanks, >> > > Chu >> > > >> > > >> > > _______________________________________________ >> > > 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 > 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 > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Tue Mar 31 08:14:35 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Tue, 31 Mar 2015 13:14:35 +0000 Subject: [Nek5000-users] Grid to grid interpolation and 8-byte data format Message-ID: Dear Neks, I noticed that '8-byte fld files are currently not supported' as stated in g2gi subroutine. However, it worked fine when I used 8-byte old field to interpolate to 4-byte new geometry field (8-byte to 8-byte doesn't work). I'm just wondering is there anyway that I can generate 8-byte new field data using g2gi? Anywhere I can change in the interpolation subroutine? Hope anyone can help. Thank you very much in advance. Kind regards, Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From nek5000-users at lists.mcs.anl.gov Tue Mar 31 11:35:34 2015 From: nek5000-users at lists.mcs.anl.gov (nek5000-users at lists.mcs.anl.gov) Date: Tue, 31 Mar 2015 18:35:34 +0200 Subject: [Nek5000-users] Regarding Interpolation on to a Cylindrical Grid Message-ID: Hi Paul, Alex and Nek's, I want to interpolate the data from the Cartesian mesh on to a Cylindrical mesh that I created using python. The Idea is to interpolate the data at each step and to perform post processing on it. 1) I tried to dump data using hpts(), but the problem is that the size of hpts.out gets larger after each time step. 2) Looking into g2gi subroutine, tells that both the *.rea have to be built via nek5000. It would be really helpful for all the users, If some kind of example (stenosis or turbchannel) is added about the solver based data post processing with USERCHK(), (GLL --> Uniform grid) interpolation. Best Regards, KS