Hi Sam, Thanks for offering the help.
I looked at the case file you sent, NEK5000 also has a similar ASCII meta file and time-depended mesh data is saved in a set of binary files. I am not able to read this changing mesh into Paraview. I have been using Paraview to visualize moving-mesh which are saved in VTK format for quite sometime and it was working fine. But not able to do the same with NEK5000 output files. I am guessing that this is still a bug/pending enhancement since Paraview has added the NEK5000 compatibility only recently, starting from 4.1.0. Regards, Ravi On Sun, Mar 2, 2014 at 1:45 PM, Samuel Key <[email protected]> wrote: > Giuseppe, Ravi; > > I have no knowledge of NEK-5000, nor the content of the results files > produced by NEK-5000. However, in my use of ParaView, ParaView routinely > provides moving and distorting meshes in my animations. For me, there are > at least two ways that the moving and distorting meshes are produced: > > 1) If there are vector displacement values supplied at the grid points, > and ParaView's Warp filter is available (that is, not grayed-out), then the > Warp filter will can be used with a scale value to reduce, amplify, or give > true position of the grid, > > 2) If one uses the EnSight-formatted simulation results file, and > true-scale deformed mesh plots are the routine case, then EnSight's *.geom > file can contain by time-step the mesh coordinates, and then without the > use of ParaView's Warp filter, true-scale deformed meshes are obtained > automatically. A small EnSight *.case file (an ASCII-formatted meta file > the points to all of the binary files that contain the simulation results) > is attached. > > Sam Key > > > > On 3/2/2014 9:16 AM, Ravi Tumkur wrote: > > Hello Giuseppe, > > Thanks a lot for replying to my query. > > I understand that you are also facing the same issue of only one > time-step's mesh geometry begin loaded when you try to use Paraview 4.1.0 > to visualize your post-processed data. > > When you say using Praview 4.1.0 resolved your issue at the beginning of > your email, do you mean you were able to visualize *.fld* data in Paraview? > If so, can you please send an example database set and the metadata file? > > I am trying to visualize moving-mesh results for the basic problem of > vortex-shedding past a cylinder moving with prescribed motion. The flow > results are rendered as expected in Paraview for each time step, but the > mesh appears stationary, corresponding to "firsttimestep", as you also > observe too. > > I appreciate your help, a set to example database will get me started on > using Paraview for visualizing NEK-5000 data. > > > Regards > Ravi > > > > > > On Sat, Mar 1, 2014 at 2:45 AM, Giuseppe Pitton <[email protected] > > wrote: > >> Hello Ravi, >> although Paraview 4.1.0 solved my issue, now I am experiencing the same >> problem you report with some postprocessed data (but I have a fixed mesh). >> In my opinion this happens when the dataset has mesh information stored on >> each .f or .fld file. I think Paraview expects to have mesh information >> only in the first file of the dataset, and it is not behaving well if this >> is not the case. >> I suspect this because if I edit my .nek5000 file and change the value >> of firsttimestep setting it to n, then Paraview correctly visualizes the >> data of the n-th time step, but again it cannot display correctly the data >> of the following timesteps. >> I also can share some example dataset if it can help. >> Best regards, >> Giuseppe >> >> >> >> Il giorno 28/feb/2014, alle ore 12:40, Ravi Tumkur ha scritto: >> >> Hello Patrick and Giuseppe, >> >> I am also facing the same issue as Giuseppe did on visualizing the >> NEK5000 solution data. I have simulated a moving boundary problem using >> NEK5000, and have the output saved in *.fld* format. When I load the meta >> file to read the files in Paraview, only one time-step mesh geometry is >> loaded, whereas the field results of all the time-steps are available in >> Paraview. >> >> I would appreciate if either of you could suggest any workaround to read >> the moving mesh geometry which is saved for each time-step of the solution. >> >> I am trying to read my NEK5000 output in version 4.1.0 64-bit Paraview >> installation. If you want the data files, please let me know, I can send >> them across. >> >> Thanks in advance for you help. >> >> Sincerely, >> Ravi >> >> >> >> >> >> On Mon, Jan 20, 2014 at 10:44 AM, Patrick O'Leary < >> [email protected]> wrote: >> >>> Dear Giuseppe, >>> >>> Yes I remember the issue. I have a test data set, and I just tested it. >>> It works with version 4.1. Send me your data set and I'll look at what we >>> might have missed. >>> >>> Best regards, >>> Patrick >>> >>> >>> On Mon, Jan 20, 2014 at 8:37 AM, Giuseppe Pitton < >>> [email protected]> wrote: >>> >>>> Dear Patrick, >>>> I am a ParaView user, and I am experiencing some issues with NEK5000 >>>> output format, both with the 4.0.1 and the 4.1 version. >>>> I have found a user already reported this bug, but I have not found any >>>> solution online. The problem is that only the first timestep is visualized, >>>> and not the following ones. If you want, I could send you an example output >>>> (few Mb). >>>> Thank you in advance, best regards. >>>> Giuseppe Pitton >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/mailman/listinfo/paraview >>> >>> >> >> >> -- >> Ravi Kumar T R >> >> University of Illinois at Urbana-Champaign >> ph : +1 217 778 7538 <%2B1%20217%20778%207538> >> http://lndvl.mechse.illinois.edu/ >> >> >> > > > -- > Ravi Kumar T R > > University of Illinois at Urbana-Champaign > ph : +1 217 778 7538 > http://lndvl.mechse.illinois.edu/ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to > subscribe/unsubscribe:http://www.paraview.org/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > -- Ravi Kumar T R University of Illinois at Urbana-Champaign ph : +1 217 778 7538 http://lndvl.mechse.illinois.edu/
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
