[Paraview] [EXTERNAL] PROBLEM IMPORTING ENSIGHT SOS FILE

Tue Mar 17 04:37:11 EDT 2015

Dear Alan,

thank you for your time.

The userguide you linked in your mail was interesting but it seems
that the problem is correlated to Paraview, because the *.sos file
format I used was correct.

Just for a general knowledge: for some reason Paraview search the case
files in the same directory of the sos file, independently from the
path you write in the *sos file (it is not important what path to case
file you write, I tried totally wrong path but the error was the
same).

Ensight write his data with the following structure:
\general_path\3D_EnSight\*sos
\general_path\3D_EnSight\DOM_0\*case
\general_path\3D_EnSight\DOM_1\*case
\general_path\3D_EnSight\DOM_n\*case

Because the case files are stored in DOM_x folders, Paraview doens't
find them. You have to put all the content of the DOM_x folders one
step up, at the same path of the *sos file.

Now it works.

I hope it could be useful for someone.

Gaspare

2015-03-13 20:34 GMT+01:00 Scott, W Alan <wascott at sandia.gov>:
> Gaspare,
>
> I tried opening your .case files with ParaView and EnSight, and they seem OK.  I then tried opening the .sos file, and had issues - even after removing the site specific information.  I had issues with ParaView, and it crashed EnSight.   Thus, I believe the issue is with the .sos file.  I am not an expert on .sos files at all - so let me aim you at the online documentation.  By doing a google search, I found the following:  http://www3.ensight.com/EnSight10_Docs/UserManual.pdf.  Look in chapter 9.8, SOS file formats.
>
> That's about all I know...
>
> Alan
>
> -----Original Message-----
> From: Gaspare Argento [mailto:gaspare.argento at gmail.com]
> Sent: Tuesday, March 10, 2015 5:04 AM
> To: Scott, W Alan
> Cc: paraview at paraview.org
> Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE
>
> Hi Scott,
>
> please find attached a case test that was launched on two cores. In the first folder you can find the *.sos file, manually edited with the correct machine name and the absolute path to the Ensight server (I'm not sure it is the correct file to use); in the folders DOM_0 and
> DOM_1 you can find the *.case files (I can load them one by one correctly).
>
> These files are written by AVL Fire. Because Paraview doesn't support the native format of FIRE for 3D Results, I ask to the software to write them also in the Ensight format.
>
> Thanks for your support,
>
> Gaspare
>
> 2015-03-09 22:27 GMT+01:00 Scott, W Alan <wascott at sandia.gov>:
>> I believe my thoughts below were wrong.  Ignore them.
>>
>> Could you give us a trivial dataset that shows this issue?
>>
>> Thanks,
>>
>> Alan
>>
>> -----Original Message-----
>> From: Gaspare Argento [mailto:gaspare.argento at gmail.com]
>> Sent: Friday, March 06, 2015 12:47 AM
>> To: Scott, W Alan
>> Cc: paraview at paraview.org
>> Subject: Re: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE
>>
>> Hi Scott,
>>
>> thanks for answering.
>>
>> I'm sorry but I didn't understand exactly what do you mean: could you please explain it better? Did you ask me to attach the .sos file?
>>
>> Thanks,
>>
>> Gaspare
>>
>> 2015-03-05 18:39 GMT+01:00 Scott, W Alan <wascott at sandia.gov>:
>>> I just opened an .sos file, with a 16 file dataset, with ParaView 4.3.1.  Worked fine.  Linux, local server.
>>>
>>> * I wonder if you have a problem with your SOS file.
>>> * Mind posting a/the dataset?
>>>
>>> Alan
>>>
>>> -----Original Message-----
>>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
>>> Gaspare Argento
>>> Sent: Thursday, March 05, 2015 2:20 AM
>>> To: paraview at paraview.org
>>> Subject: [EXTERNAL] [Paraview] PROBLEM IMPORTING ENSIGHT SOS FILE
>>>
>>> Hi everybody,
>>>
>>> I have a problem when importing an Ensight .sos file in Paraview.
>>>
>>> Loading the .sos file I get the following message (I attach only the lines about the first *.case file, because these are repeated for all *case files listed in the .sos):
>>> =====================================================================
>>> = ====================================================
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight
>>> R
>>> eader.cxx,
>>> line 340
>>>
>>> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file:
>>> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM
>>> _
>>> 0.case
>>>
>>>
>>>
>>>
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight
>>> R
>>> eader.cxx,
>>> line 340
>>>
>>> vtkPGenericEnSightReader (000000000DC5E6E0): Unable to open file:
>>> J:\SERVER\CALC\VOF_TEST\Calculation\VOF_TEST\3D_EnSight\/VOF_TEST_DOM
>>> _
>>> 0.case
>>>
>>>
>>>
>>>
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\EnSight\vtkGenericEnSight
>>> R
>>> eader.cxx,
>>> line 811
>>>
>>> vtkPGenericEnSightReader (000000000DC5E6E0): Error determining
>>> EnSightVersion
>>>
>>>
>>>
>>>
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe
>>> c
>>> utive.cxx,
>>> line 784
>>>
>>> vtkCompositeDataPipeline (000000000DBF33A0): Algorithm
>>> vtkPGenericEnSightReader(000000000DC5E6E0) returned failure for
>>> request: vtkInformation (000000000DEC2F60)
>>>
>>> Debug: Off
>>>
>>> Modified Time: 160501
>>>
>>> Reference Count: 1
>>>
>>> Registered Events: (none)
>>>
>>> Request: REQUEST_INFORMATION
>>>
>>> ALGORITHM_AFTER_FORWARD: 1
>>>
>>> FORWARD_DIRECTION: 0
>>>
>>>
>>>
>>>
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\ParaViewCore\VTKExtensions\Defau
>>> l t\vtkPVEnSightMasterServerReader2.cxx,
>>> line 255
>>>
>>> vtkPVEnSightMasterServerReader2 (0000000018693C90): Error reading case file on at least one node.
>>>
>>>
>>>
>>>
>>>
>>> ERROR: In
>>> C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExe
>>> c
>>> utive.cxx,
>>> line 784
>>>
>>> vtkPVCompositeDataPipeline (0000000017BEA7E0): Algorithm
>>> vtkPVEnSightMasterServerReader2(0000000018693C90) returned failure
>>> for
>>> request: vtkInformation (0000000016F654A0)
>>>
>>> Debug: Off
>>>
>>> Modified Time: 6920520
>>>
>>> Reference Count: 1
>>>
>>> Registered Events: (none)
>>>
>>> Request: REQUEST_INFORMATION
>>>
>>> ALGORITHM_AFTER_FORWARD: 1
>>>
>>> FORWARD_DIRECTION: 0
>>>
>>> =====================================================================
>>> = ====================================================
>>>
>>>
>>>
>>> Below you can find an extract of the loaded .sos file (only the lines relative to the first server):
>>> =====================================================================
>>> = ====================================================
>>>
>>> #
>>>
>>> # Example Server-of-server case file
>>>
>>> #   parts in <> have to be filled in by the user
>>>
>>> #
>>>
>>> FORMAT
>>>
>>> type: master_server gold
>>>
>>> SERVERS
>>>
>>> number of servers:      64
>>>
>>> #Server       1
>>>
>>> machine id: MACHINE_NAME
>>>
>>> executable: <ensight sever executable name with full path>
>>>
>>> casefile:
>>> J:/SERVER/CALC/VOF_TEST/Calculation/VOF_TEST/3D_EnSight/DOM_0/VOF_TES
>>> T
>>> _DOM_0.case
>>>
>>> =====================================================================
>>> = ====================================================
>>>
>>>
>>>
>>> If I load the *.case files one by one I have no problem.
>>>
>>>
>>>
>>> Thanks for your support
>>>
>>> Gaspare
>>> _______________________________________________
>>> 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
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview