Bravo Bruno!
it works fine now.but I have trouble with saving it.when I save state and exit from paraView and then start it and use load state another file with the same name appear in biltin part in paraView and filds became disappear! and doesn't work correctly. |
Before opening ParaView, run:
Code:
paraFoam -touch |
Hi Bruno
this type of error occurs again when save and load state: Code:
ERROR: In /home/opencfd/OpenFOAM/ThirdParty-dev/ParaView-3.12.0/VTK/IO/vtkOpenFOAMReader.cxx, line 6481 |
Hi Ehsan,
Sorry, apparently last night I was a bit tired already and I didn't notice that I wrote "-builtin" instead of "-touch". I've corrected the previous post. OK, to avoid future problems with the state files, I suggest that you follow this procedure:
Bruno |
why when paraview is making images for animation,it abruptly closes itself and making animations discontinues?
|
what does this error(warning) means? :mad::(
Code:
Traceback (most recent call last): |
2 Attachment(s)
when above error is shown,the maximums in images are saved wrong,
in attachments KE.0116.jpg is saved by the python script and 116 is screenshot. ---------------------------------- then troubles are these: 1) paraFoam doesn't act good with extremes of variables,means legends are in 0,1 region 2)because of 1,I open cases by paraview -dr as dear Bruno mentioned somewhere, 3)in one case,when it reaches to a middle time,paraview suddenly closes (during saving animation), 4)in other case,paraview doesn't save correct values in ranges for maximum in saving animation |
Hi Ehsan,
Quote:
Use the command top in a new terminal, to confirm if the memory occupied by ParaView keeps rising. Or use "System Tools -> System Monitor" instead of top. Quote:
Quote:
3) Explained in the first paragraph of this post I'm writing. 4) Uh... the answer after the 2nd quote? Best regards, Bruno |
Quote:
Quote:
-------------- forgot to attach system Monitor. |
But how exactly did the memory occupancy by ParaView evolve along the animation?
And no, you didn't attach the image of the System Monitor :( |
1 Attachment(s)
forgot to attach system Monitor.
|
Bruno something occupies the memory when paraview's are closed!
how can find out what it is? it hardly attaches. |
Have you looked in the "Processes" tab on the "System Monitor"?
|
a corrupted pidgin run had occupied the memory.
|
dear Bruno Hi,
I added this code according to what you said and I had done before also, Code:
from paraview.simple import * Code:
Traceback (most recent call last): |
Hi Ehsan,
Is the case file actually named "WR_4.OpenFOAM"? Because that error message implies that it is not. Best regards, Bruno |
no its name is case.foam,I'm mixed up with names!
is the folder name important too? I have to make a file with name: case.foam and open it after running "paraFoam4"? |
The name and folder are not relevant to this filter. All that matters is the name you gave to it in the "Pipeline Browser" (yes, you can rename the entries there as well!).
This is because this instruction: Code:
FindSource("WR_4.OpenFOAM") |
1 Attachment(s)
Bruno I made a file named case.foam in the case folder and used paraFoam4 command as you said me,copy the python code and take animations but the maximums are not correct,they don't match to real local maximum values and another issue is that again " Automatic Color scaling" doesn't work and scale bar doesn't change :( :mad:
|
Bruno I closed that and open a new paraview and rescaling problem is resolved,I worry if I add the python code it occurs again! it was working fine before,why it has became so?
|
All times are GMT -4. The time now is 07:32. |