Hi Stefan, Many thanks for your reply. Please contact me via [email protected]. Best regards, Tony ________________________________ From: [email protected] <[email protected]> on behalf of [email protected] <[email protected]> Sent: 30 March 2017 13:17 To: [email protected] Subject: Nek5000-users Digest, Vol 97, Issue 37 Today's Topics: 1. Outflow BC with negative velocity ([email protected]) 2. Re: NekNek with PN-PN ([email protected]) 3. Re: NekNek with PN-PN ([email protected]) 4. Re: Interpolation between two meshes ([email protected]) 5. Accessing the value of drag and lift coefficients in usrchk ([email protected]) Message: 4 Date: Thu, 30 Mar 2017 11:46:40 +0200 From: [email protected] To: [email protected] <[email protected]> Subject: Re: [Nek5000-users] Interpolation between two meshes Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Please let me know how I can contact you off list. Stefan? On 29 Mar 2017, at 14:59, "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> > wrote: Hi Stefan, Thank you very much for your quick reply. 1. Yes, my source field is in double precision since I need to keep the accuracy. 2. I added several print lines in gfldr.f to check where the interpolation hangs (see below). I also put 'call nekgsync()' before and after findpts as you suggested. I can confirm that findpts is exactly where the interpolation hangs. The last output in the logfile is 'CHECK interp findpts before' and it never gets updated again. 3. I've just tested gfldr() with turbChannel example. Everything worked fine and the?source field was interpolated onto the turbChannel mesh (512 elements). So I moved on increasing the number of elements of turbChannel case. First, I used 234300 elements?in the turbChannel example (half of my current simulation size) and the interpolation was done successfully. Then, I used 468600 elements for?the turbChannel example (similar to my current simulation size), the interpolation hangs again at findpts. I guess it might be something to do with the memory. What do you think? Is there any solution to this? Best regards, Tony ??????? if(nid==0) print*,'CHECK interp findpts before' ??????? call nekgsync() ??????? call findpts(inth_gfldr, ???? &?????????????? rcode,1, ???? &?????????????? proc,1, ???? &?????????????? elid,1, ???? &?????????????? rst,ndim, ???? &?????????????? dist,1, ???? &?????????????? xm1,1, ???? &?????????????? ym1,1, ???? &?????????????? zm1,1,ntot) ??????? call nekgsync() ??????? if(nid==0) print*,'CHECK interp findpts after'