Steady-state fluid flow in the human eye

[raback]

Hi, You can of course use ElmerPost as well. It uses less resources than Paraview. Just change the suffix to .ep. -Peter

[mzenker]

Hi Peter,

They come automatically inlined images if they are small enough when you choose "Upload attachments" below this edit window where I'm typing right now.

apparently it is not that easy, see my post here.
Strange...

Matthias

[cosswald]

Using ElmerPost I got it to work. Thanks again for all your help.

And to Matthias, all I did was upload the image and it put it inline like Peter mentioned.
--
Chris

[annier]

I have run ElmerSolver with a much finer mesh generated in Gmsh and am attempting to open the case.vtu file with ParaView (3.14.1 64-bit). I have never used ParaView, nor other post-processors, and it is asking for a reader to open the VTU file.

I've tried opening the VTU file with all of my available options (see list). The only one that maybe works is the MFIX Unstructured Grid, however ParaView crashes due to not enough memory.

AVS UCD Binary/ASCII Files
Comma-separated-values
Cosmology files
Digital Elevation Map files
Enzo Files
Flash Files
Fluent Case Files
Gaussian Cube Files
MFIX Unstructured Grid Files
OpenFOAM
PLOT3D Files
POP Ocean Files
POP Ocen NetCDF (Rectilinear)
ProSTAR Files
Protein Data Bank Files
Raw (binary) Files
SESAME
Spy Plot History Files
Stereo Lithography
Tecplot Files
VPIC Files
VTK Particle Files
Wavefront OBJ Files

Hi Chris,
I am not clear about the cause but adding the solver "ResultOutputSolver" in the SIF instead of using "Post File =case.vtu" can provide us the solution for the cause in my guess.
Once, i used

Code: Select all

Post File = Case.Vtu

and tried to run the Postprocessing through paraview.The same options appeared when the Paraview screen loaded on.
Then i moved into the SIF and did like this

Code: Select all

!Post File = Case.Vtu

...
Solver n !(Use the last number here)
      Exec Solver = String "after saving"   
      exec interval = 1
      Equation = String "ResultOutput"
      Procedure = File "ResultOutputSolve" "ResultOutputSolver"
      Output File Name = String "case."
      Output Format = String "vtu"
      Vtu Format = Logical True
      Binary Output = Logical True  ! binary format is the default
     Single Precision = Logical True ! double precision is the default

   ! In the Vtu format all fields are saved if the user does not list them explicitely.
End

And when i reopened the Paraview, it worked on.
In conclusion, defining an additional solver "ResultOutputSolver" for vtu format is always a reliable option for postprocessing in Paraview. Yet, I am still not clear of the reason why the paraview does not open file when we only depend on Post File = case.vtu as some users have been using this option successfully for paraview postprocessing too. Or, they might have used both the Post File = case.vtu in Simulation section as well as the ResultOutputSolver. Or, maybe there are other answers for it.
yours
annier

[cosswald]

Thanks, Annier, I will give this a try. I find ElmerPost to not be that intuitive, so using another post-processor will be nice.

[raback]

Why the .vtu suffix alone does not work probably depends that the Solver you are using is quite old. Just a guess though... -Peter

[annier]

Hi,
Yes, after i installed a fresher version of Elmer, the code

Code: Select all

Simulation
...
Post file = case.vtu 
...
End

has started working.
Yours
Anil Kunwar

[annier]

Hi Peter,

They come automatically inlined images if they are small enough when you choose "Upload attachments" below this edit window where I'm typing right now.

apparently it is not that easy, see my post here.
Strange...

Matthias

Hi Matthias,
After a lot of trials, it is found that image could be enabled appearing inline by reducing the pixels of the image. The testing has been posted in the same "here"

Yours
Anil Kunwar

[raback]

Hi

There is a setting for this in Administrator panel:

Image Size Limit Setting

ImageSizeLimit.PNG (12.61 KiB) Viewed 8327 times

-Peter

[mzenker]

Hi Peter,

this explains everything, thanx!

Matthias