|
[Sponsors] |
November 23, 2011, 12:27 |
Saving ParaFoam views and case
|
#1 |
Senior Member
Vieri Abolaffio
Join Date: Jul 2010
Location: Always on the move.
Posts: 308
Rep Power: 17 |
Dear Foamers.
I would like to know if it si possible to save a certain postprocessing in parafoam. for example, one 'ive loaded the foam case, done all my cuts, contours, lines, planes etc, i would like to save the paraview case, so next time i open it (for showing to a client or modification, i don't have to start over. it would be perfect if this can be made indipendetly for the OF case, ie i'm able to move the saved paraview fiel at my pleasure. how can this be made? i googoled a bit, but was not able to find an answer. thanks in advance. |
|
November 23, 2011, 16:22 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Greetings Sail,
You've got at least two options for file format:
Best regards, Bruno
__________________
|
|
November 23, 2011, 22:48 |
|
#3 | |
Senior Member
Vieri Abolaffio
Join Date: Jul 2010
Location: Always on the move.
Posts: 308
Rep Power: 17 |
Quote:
unfortuantely i'm not still able to get it right, with nither of the strategies you suggested. it must be noted that i'm using paraview 3.10.1 32bit on a ubuntu 10.4 LTS virtual machine. after saving the state, if i load it back as "load state" from a blank project i got the following error: Code:
ERROR: In /home/opencfd/OpenFOAM/ThirdParty-2.0.0/ParaView-3.10.1/VTK/IO/vtkXMLParser.cxx, line 483 vtkPVXMLParser (0x9960c18): Error parsing XML in stream at line 1, column 0, byte index 0: not well-formed (invalid token) Root does not exist. Either state file could not be opened or it does not contain valid xml ERROR: In /home/opencfd/OpenFOAM/ThirdParty-2.0.0/ParaView-3.10.1/VTK/IO/vtkXMLParser.cxx, line 483 vtkPVXMLParser (0x3eea33f8): Error parsing XML in stream at line 1, column 0, byte index 0: not well-formed (invalid token) Root does not exist. Either state file could not be opened or it does not contain valid xml am i doing something blatantly wrong? am i missing something? thanks again |
||
November 24, 2011, 15:55 |
|
#4 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Hi Sail,
There is definitely something wrong somewhere... it looks like your save state file was 0 in size! Try something simpler, like saving the state after the following steps:
Code:
rm ~/.config/ParaView/*.ini Good luck! Bruno
__________________
|
|
November 24, 2011, 17:00 |
|
#5 | |
Senior Member
Vieri Abolaffio
Join Date: Jul 2010
Location: Always on the move.
Posts: 308
Rep Power: 17 |
Quote:
on the other hands i've managed to make it almost work: for future reference i was using a ubuntu vm and all my saves state where done on the windows shared directory (created following OpenCFD guidelines) it was already known that gedit have some problems in writng to files placed in this mounted directory, and now it appears that paraview as well. I tired to move everything to a "normal" position on the vm hard drive and now the state seems to be written correctly. now all is left to do is try to understand why paraview 3.10.1 crashes bringing down the virtual machine with him when i try to load a saved state... Last edited by sail; November 24, 2011 at 18:37. |
||
November 25, 2011, 04:07 |
|
#6 | ||
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Hi Sail,
Quote:
The mounted drives in virtual machines that link directly to the real machine are only meant to be used when copying files from the real to virtual and vice-versa. Working directly can, sooner or later, lead to problems. Quote:
Best regards, Bruno
__________________
|
|||
November 25, 2011, 14:29 |
|
#7 | |
Senior Member
Vieri Abolaffio
Join Date: Jul 2010
Location: Always on the move.
Posts: 308
Rep Power: 17 |
Quote:
disabling the 3d accelleration worked , a new problem arised: Code:
X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016bd X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x48016c0 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 112 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 116 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 116 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 104 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 101 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 102 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 1 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 117 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1 X Error: GLXBadContextTag 172 Extension: 154 (Uknown extension) Minor opcode: 145 (Unknown request) Resource id: 0x1 paraview: ../../src/xcb_io.c:549: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed. Aborted looks something wrong with the xserver or something related... maybe if i try a suse distro i would be more lucky? i would prefer keep using the pakaged distribution of OF and paraview to keep it simple and (almost) failproof, but if there is no other way i could resort to compile paraview from scratch. thanks again for your time and insights, you're a life saver. Last edited by sail; November 25, 2011 at 15:40. |
||
November 25, 2011, 16:01 |
|
#8 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Hi Sail,
The problem now is related to the following situation:
Er, no, wait, you have Ubuntu 10.04. OK, I found a solution here: Quote:
Bruno
__________________
Last edited by wyldckat; November 25, 2011 at 16:01. Reason: typos... |
||
November 25, 2011, 16:25 |
|
#9 |
Senior Member
Vieri Abolaffio
Join Date: Jul 2010
Location: Always on the move.
Posts: 308
Rep Power: 17 |
Great! it worked!
thank you really much, with your help not only i've managed to make it work, but also i learnt lots of dos and dont's in virtualization and linux in general. thank you. |
|
November 25, 2011, 16:46 |
|
#10 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
I'm glad I could help you
Good luck! Bruno
__________________
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CFX post-exprestion for reffrencing a case | hmasenger | CFX | 18 | February 11, 2021 21:05 |
[waves2Foam] Had some issues reconstructing the case for post-processing | arieljeds | OpenFOAM Community Contributions | 4 | May 5, 2016 19:44 |
Case Comparison in CFD-Post | Tristan | CFX | 2 | February 4, 2016 02:07 |
[General] paraview render multiple views - off-screen | FerdiFuchs | ParaView | 1 | September 25, 2015 11:26 |
Save views and load them in another case | HHOS | EnSight | 4 | June 16, 2015 03:37 |