From mathieu.westphal at kitware.com  Mon May  2 03:41:27 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Mon, 2 May 2016 09:41:27 +0200
Subject: [Paraview] pv freezes when merging blocks of angular periodic
 filter data
In-Reply-To: <CAC2t4UTaxiDtKPR66-JOdf1tDroV9-4cOJp2EuqKr6BL=xh_qw@mail.gmail.com>
References: <57246F48.5020109@mail.ru> <572474D8.9040807@mail.ru>
 <CAC2t4UTaxiDtKPR66-JOdf1tDroV9-4cOJp2EuqKr6BL=xh_qw@mail.gmail.com>
Message-ID: <CAC2t4UTv+mwcA0+Chus=fMh8CN8pr7S1WG8Df9MMqF6LXLUW7g@mail.gmail.com>

This bug has already been corrected in the master branch of paraview. You
can clone it and compile it, or wait for ParaView 5.0.1 to come out in a
few weeks.

Regards,

Mathieu Westphal

On Sat, Apr 30, 2016 at 12:04 PM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> I will take a look at it next week.
>
> Regards,
>
> Mathieu Westphal
>
> On Sat, Apr 30, 2016 at 11:03 AM, Gena Bug <archaerolog at mail.ru> wrote:
>
>> UPD: Seems it somehow related to cell-data vector arrays, because it
>> works with point-data arrays.
>>
>> I attached a smallest example I came up with that could help. If you load
>> the state-file you'll see the next pipeline:
>> test.vtp
>> AngularPeriodicFilter (with angle = 90 and axiz = Z)
>> CellDatatoPointData
>> MergeBlocks
>>
>> That works. However if you remove CellDatatoPointData from this pipeline
>> and try to merge the result of AngularPeriodicFilter you'll see the problem.
>>
>>
>> On 30.04.2016 11:39, Gena Bug wrote:
>>
>>> Hi!
>>>
>>> I was able to freeze Paraview by applying MergeBlocks filter to the data
>>> generated by AngularPeriodicFilter. In console I see a bunch of warnings:
>>> {
>>> Warning: In
>>>
>>> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx,
>>> line 47
>>> 20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is
>>> very expensive for vtkMappedDataArray subclasses, since the scalar array
>>> must be generated for each call. Consider using a
>>> vtkTypedDataArrayIterator instead.
>>> }
>>>
>>> Env: debian testing amd64, KF5, pv downloaded from the site.
>>> _______________________________________________
>>> 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
>>>
>>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/456ef43d/attachment.html>

From archaerolog at mail.ru  Mon May  2 11:45:31 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Mon, 2 May 2016 18:45:31 +0300
Subject: [Paraview] pv freezes when merging blocks of angular periodic
 filter data
In-Reply-To: <CAC2t4UTv+mwcA0+Chus=fMh8CN8pr7S1WG8Df9MMqF6LXLUW7g@mail.gmail.com>
References: <57246F48.5020109@mail.ru> <572474D8.9040807@mail.ru>
 <CAC2t4UTaxiDtKPR66-JOdf1tDroV9-4cOJp2EuqKr6BL=xh_qw@mail.gmail.com>
 <CAC2t4UTv+mwcA0+Chus=fMh8CN8pr7S1WG8Df9MMqF6LXLUW7g@mail.gmail.com>
Message-ID: <5727761B.2020800@mail.ru>

On 02.05.2016 10:41, Mathieu Westphal wrote:
> This bug has already been corrected in the master branch of paraview. You
> can clone it and compile it, or wait for ParaView 5.0.1 to come out in a
> few weeks.
I checked the last nightly and it works. Great! Thanks for the info, 
Mathieu!

>
> Regards,
>
> Mathieu Westphal
>
> On Sat, Apr 30, 2016 at 12:04 PM, Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
>> I will take a look at it next week.
>>
>> Regards,
>>
>> Mathieu Westphal
>>
>> On Sat, Apr 30, 2016 at 11:03 AM, Gena Bug <archaerolog at mail.ru> wrote:
>>
>>> UPD: Seems it somehow related to cell-data vector arrays, because it
>>> works with point-data arrays.
>>>
>>> I attached a smallest example I came up with that could help. If you load
>>> the state-file you'll see the next pipeline:
>>> test.vtp
>>> AngularPeriodicFilter (with angle = 90 and axiz = Z)
>>> CellDatatoPointData
>>> MergeBlocks
>>>
>>> That works. However if you remove CellDatatoPointData from this pipeline
>>> and try to merge the result of AngularPeriodicFilter you'll see the problem.
>>>
>>>
>>> On 30.04.2016 11:39, Gena Bug wrote:
>>>
>>>> Hi!
>>>>
>>>> I was able to freeze Paraview by applying MergeBlocks filter to the data
>>>> generated by AngularPeriodicFilter. In console I see a bunch of warnings:
>>>> {
>>>> Warning: In
>>>>
>>>> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx,
>>>> line 47
>>>> 20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is
>>>> very expensive for vtkMappedDataArray subclasses, since the scalar array
>>>> must be generated for each call. Consider using a
>>>> vtkTypedDataArrayIterator instead.
>>>> }
>>>>
>>>> Env: debian testing amd64, KF5, pv downloaded from the site.
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>

From wascott at sandia.gov  Mon May  2 13:32:10 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 2 May 2016 17:32:10 +0000
Subject: [Paraview] [EXTERNAL] Re: pv freezes when merging blocks of
 angular periodic filter data
In-Reply-To: <CAC2t4UTv+mwcA0+Chus=fMh8CN8pr7S1WG8Df9MMqF6LXLUW7g@mail.gmail.com>
References: <57246F48.5020109@mail.ru> <572474D8.9040807@mail.ru>
 <CAC2t4UTaxiDtKPR66-JOdf1tDroV9-4cOJp2EuqKr6BL=xh_qw@mail.gmail.com>
 <CAC2t4UTv+mwcA0+Chus=fMh8CN8pr7S1WG8Df9MMqF6LXLUW7g@mail.gmail.com>
Message-ID: <a1eccf12419d41ef95a4156600d64273@ES01AMSNLNT.srn.sandia.gov>

Thanks Mathieu.  I will benefit also.

Note that the next version of PV is 5.1.0, scheduled for next month.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Mathieu Westphal
Sent: Monday, May 02, 2016 1:41 AM
To: Gena Bug <archaerolog at mail.ru>
Cc: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] pv freezes when merging blocks of angular periodic filter data

This bug has already been corrected in the master branch of paraview. You can clone it and compile it, or wait for ParaView 5.0.1 to come out in a few weeks.
Regards,

Mathieu Westphal

On Sat, Apr 30, 2016 at 12:04 PM, Mathieu Westphal <mathieu.westphal at kitware.com<mailto:mathieu.westphal at kitware.com>> wrote:
I will take a look at it next week.
Regards,

Mathieu Westphal

On Sat, Apr 30, 2016 at 11:03 AM, Gena Bug <archaerolog at mail.ru<mailto:archaerolog at mail.ru>> wrote:
UPD: Seems it somehow related to cell-data vector arrays, because it works with point-data arrays.

I attached a smallest example I came up with that could help. If you load the state-file you'll see the next pipeline:
test.vtp
AngularPeriodicFilter (with angle = 90 and axiz = Z)
CellDatatoPointData
MergeBlocks

That works. However if you remove CellDatatoPointData from this pipeline and try to merge the result of AngularPeriodicFilter you'll see the problem.


On 30.04.2016 11:39, Gena Bug wrote:
Hi!

I was able to freeze Paraview by applying MergeBlocks filter to the data
generated by AngularPeriodicFilter. In console I see a bunch of warnings:
{
Warning: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx,
line 47
20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is
very expensive for vtkMappedDataArray subclasses, since the scalar array
must be generated for each call. Consider using a
vtkTypedDataArrayIterator instead.
}

Env: debian testing amd64, KF5, pv downloaded from the site.
_______________________________________________
Powered by www.kitware.com<http://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

_______________________________________________
Powered by www.kitware.com<http://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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/2c8c9483/attachment.html>

From nikos.beratlis at gmail.com  Mon May  2 14:09:00 2016
From: nikos.beratlis at gmail.com (Nikolaos Beratlis)
Date: Mon, 2 May 2016 14:09:00 -0400
Subject: [Paraview] Help with adjusting contour levels in python script
Message-ID: <CALdMxnzp7d61K8=+sMCiQ6KijyFYRya+kGEmojj_=Ezw4BJ-BA@mail.gmail.com>

Hi,

I am running a small python code with pvbatch that read a XDMF file and
plots contours:

    cf_VP_anim_xmf = XDMFReader( FileName=wdir+'VPfield_files/XDMF/cf_VP'
+index[i]+'.xmf' )


    cf_VP_anim_xmf.CellArrays = []

    cf_VP_anim_xmf.Sets = []

    cf_VP_anim_xmf.PointArrays = ['Cf']


    RenderView1 = GetRenderView()

    a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1 )


    Cfcontours = Show()

    Cfcontours.EdgeColor = [0.0, 0.0, 0.50000762951094835]

    Cfcontours.SelectionPointFieldDataArrayName = 'Cf'

    Cfcontours.ScalarOpacityFunction = []

    Cfcontours.ColorArrayName = 'Cf'

    Cfcontours.ScalarOpacityUnitDistance = 2.4071425938556859

    Cfcontours.LookupTable = a1_Cf_PVLookupTable

    Cfcontours.ScaleFactor = 15.0


    cf_VP_anim_xmf.Grids = ['STL Grid']


    RenderView1.CacheKey = 2.0

    RenderView1.CameraClippingRange = [288.47079837284241,
299.16435388730815]

    RenderView1.UseCache = 0


    a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1, RGBPoints=[-
0.0001, 0.0, 0.0, 1.0, 0.0001, 1.0, 0.0, 0.0], LockScalarRange=1,
ColorSpace='HSV' )


    separationline = Contour( PointMergeMethod="Uniform Binning" )


    separationline.ContourBy = ['POINTS', 'Cf']

    separationline.Isosurfaces = [0.0]


    DataSeparationLine = Show()

    DataSeparationLine.ScaleFactor = 12.321390008926393

    DataSeparationLine.SelectionPointFieldDataArrayName = 'Cf'

    DataSeparationLine.EdgeColor = [0.0, 0.0, 0.50000762951094835]

    DataSeparationLine.LineWidth = 2.0

    DataSeparationLine.DiffuseColor = [0.0, 0.0, 0.0]


    DataSeparationLine.ColorArrayName = ''


    Cfcontours.Visibility = 1


    #--- Setup view

    RenderView1 = GetRenderView()

    RenderView1.Background = [1.0, 1.0, 1.0]

    RenderView1.CenterAxesVisibility = 0

    RenderView1.OrientationAxesVisibility = 0

    RenderView1.ViewSize = [1450, 300]


    RenderView1.InteractionMode = '3D'

    RenderView1.CameraClippingRange = [120.40716073726786,
126.85668499830999]

    RenderView1.CameraPosition = [25.95, 41.63, 1.43]

    RenderView1.CameraFocalPoint = [4.31, 5.36, 4.77]

    RenderView1.CameraViewUp = [0.93, -0.36, -0.053]


    #--- Uncomment for 2D Interaction Mode

    #RenderView1.CameraParallelScale = 5.5


    a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1, RGBPoints=[-
0.0001, 0.0, 0.0, 1.0, 0.0001, 1.0, 0.0, 0.0], LockScalarRange=1 )


    #--- Export image

    Render()

    WriteImage(wdir+'POSTPRO/IMAGES/cf_view1_'+index[i]+'.jpg')

I set the range of the contours from -0.0001 to 0.0001 but the contours
levels revert back to automatic scaling instead of the range that I
specify. I am using version 3.98 of Paraview but I also tried with version
4.1.0. Why is this happening? Do I miss something in my script?

Nikos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/220d9566/attachment.html>

From kevin.dean at decisionsciencescorp.com  Mon May  2 14:18:02 2016
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Mon, 2 May 2016 11:18:02 -0700
Subject: [Paraview] Writing Filter Plugin
Message-ID: <CAFvyM3Sx0zEWX6=TKf0hJNK4zM-rsJEwrU4jGfrvxrV7uK6AgA@mail.gmail.com>

Is there a way to do multiclass inheritance while writing your xml for a
Plugin?

Kevin Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/3c8cfa2a/attachment.html>

From utkarsh.ayachit at kitware.com  Mon May  2 14:32:00 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 2 May 2016 14:32:00 -0400
Subject: [Paraview] Writing Filter Plugin
In-Reply-To: <CAFvyM3Sx0zEWX6=TKf0hJNK4zM-rsJEwrU4jGfrvxrV7uK6AgA@mail.gmail.com>
References: <CAFvyM3Sx0zEWX6=TKf0hJNK4zM-rsJEwrU4jGfrvxrV7uK6AgA@mail.gmail.com>
Message-ID: <CADHSJjAL=Lw+KzuTjy1cXVZJc5czD2Tsf7T2H+1brwdXZAzOQQ@mail.gmail.com>

Alas, no. Sometimes, using sub-proxies instead may work, but depends
on your usecase.

Utkarsh

On Mon, May 2, 2016 at 2:18 PM, Dean, Kevin
<kevin.dean at decisionsciencescorp.com> wrote:
> Is there a way to do multiclass inheritance while writing your xml for a
> Plugin?
>
> Kevin Dean
>
> This email and its contents are confidential. If you are not the intended
> recipient, please do not disclose or use the information within this email
> or its attachments. If you have received this email in error, please report
> the error to the sender by return email and delete this communication from
> your records.
> _______________________________________________
> 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
>

From cgunases at gmail.com  Mon May  2 14:34:29 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Tue, 3 May 2016 00:04:29 +0530
Subject: [Paraview] [ParaView] Generating a 3D model
Message-ID: <CAJFKOL3XFza9hGtGnnH9J2d_SSrmt5jWjNfxO_AKOOhoi8YuMg@mail.gmail.com>

Hello everyone,

 Since i need to generate a human organ using my data first of all i
registered my images. Second of all, segmented the organ first . Third of
all, segmented the rest of the sub objects inside the organ.

Basically, segmentation was done and saved in following formats.
1st mask(for the organ) ; saved as .mat file
2nd mask(for sub objects with in the organ) : saved as .mat file
3rd mask(for sub objects within the organ)  : saved as .mat file

(note: segmentation is done for the whole image)

Since i have these masks saved in Mat format i combined all the masks and
converted to VTK format.

When i run in the Paraview, i can only view the slice, surface, etc but NOT
the VOLUME (which is what i want).

What is the reason to this?

How to overcome this issue now?

Thank you in advance.
-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160503/ac3ac477/attachment.html>

From wascott at sandia.gov  Mon May  2 16:58:59 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 2 May 2016 20:58:59 +0000
Subject: [Paraview] Cron job and ParaView
Message-ID: <c9549c21add8479e85119644405999ac@ES01AMSNLNT.srn.sandia.gov>

I have a user that is trying to run ParaView in a cron job, and keeps getting the following error on PV 4.4.0: 4.4.0/ParaView4/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 542 vtkXOpenGLRenderWindow (0x5197850): bad X server connection

Has anyone tried to do this, and figured out a solution?  User has tried running a build I did - which attaches to Mesa - and has -use-offscreen-rendering turned on, and is running pvbatch.  Same error.

Any ideas?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/fe12ec58/attachment.html>

From kmorel at sandia.gov  Mon May  2 17:01:22 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 2 May 2016 21:01:22 +0000
Subject: [Paraview] Cron job and ParaView
Message-ID: <F6145F5F-AB6C-4A8F-91FD-6880B3D02D0A@sandia.gov>

Are you sure you are building with osmesa? Just using mesa is not sufficient.

-Ken

From: ParaView <paraview-bounces at paraview.org> on behalf of Walter Scott <wascott at sandia.gov>
Date: Monday, May 2, 2016 at 2:58 PM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Cron job and ParaView

I have a user that is trying to run ParaView in a cron job, and keeps getting the following error on PV 4.4.0: 4.4.0/ParaView4/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 542 vtkXOpenGLRenderWindow (0x5197850): bad X server connection

Has anyone tried to do this, and figured out a solution?  User has tried running a build I did ? which attaches to Mesa ? and has ?use-offscreen-rendering turned on, and is running pvbatch.  Same error.

Any ideas?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/f4d9fc83/attachment.html>

From utkarsh.ayachit at kitware.com  Mon May  2 17:07:29 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 2 May 2016 17:07:29 -0400
Subject: [Paraview] Help with adjusting contour levels in python script
In-Reply-To: <CALdMxnzp7d61K8=+sMCiQ6KijyFYRya+kGEmojj_=Ezw4BJ-BA@mail.gmail.com>
References: <CALdMxnzp7d61K8=+sMCiQ6KijyFYRya+kGEmojj_=Ezw4BJ-BA@mail.gmail.com>
Message-ID: <CADHSJjCdn6sh2VTZPhL0Wxr9hVWpBnRNX8kZXybc+-8NgPV_nw@mail.gmail.com>

Nikos,

When you say you're "set the range of the contours from -0.0001 to
0.0001 but the contours levels revert back to automatic scaling", what
do you mean? Do you mean you're setting separationline.Isosurfaces to
be values in the given range, but the rendered countour is still the
same old value?

If so, there was a with how the contour filter was modified when the
contour values where changed that was fixed recently. You may want to
give 5.0.1 a try to see if you can reproduce the issue with 5.0.1.

Utkarsh

On Mon, May 2, 2016 at 2:09 PM, Nikolaos Beratlis
<nikos.beratlis at gmail.com> wrote:
> Hi,
>
> I am running a small python code with pvbatch that read a XDMF file and
> plots contours:
>
>     cf_VP_anim_xmf = XDMFReader(
> FileName=wdir+'VPfield_files/XDMF/cf_VP'+index[i]+'.xmf' )
>
>
>     cf_VP_anim_xmf.CellArrays = []
>
>     cf_VP_anim_xmf.Sets = []
>
>     cf_VP_anim_xmf.PointArrays = ['Cf']
>
>
>     RenderView1 = GetRenderView()
>
>     a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1 )
>
>
>     Cfcontours = Show()
>
>     Cfcontours.EdgeColor = [0.0, 0.0, 0.50000762951094835]
>
>     Cfcontours.SelectionPointFieldDataArrayName = 'Cf'
>
>     Cfcontours.ScalarOpacityFunction = []
>
>     Cfcontours.ColorArrayName = 'Cf'
>
>     Cfcontours.ScalarOpacityUnitDistance = 2.4071425938556859
>
>     Cfcontours.LookupTable = a1_Cf_PVLookupTable
>
>     Cfcontours.ScaleFactor = 15.0
>
>
>     cf_VP_anim_xmf.Grids = ['STL Grid']
>
>
>     RenderView1.CacheKey = 2.0
>
>     RenderView1.CameraClippingRange = [288.47079837284241,
> 299.16435388730815]
>
>     RenderView1.UseCache = 0
>
>
>     a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1,
> RGBPoints=[-0.0001, 0.0, 0.0, 1.0, 0.0001, 1.0, 0.0, 0.0],
> LockScalarRange=1, ColorSpace='HSV' )
>
>
>     separationline = Contour( PointMergeMethod="Uniform Binning" )
>
>
>     separationline.ContourBy = ['POINTS', 'Cf']
>
>     separationline.Isosurfaces = [0.0]
>
>
>     DataSeparationLine = Show()
>
>     DataSeparationLine.ScaleFactor = 12.321390008926393
>
>     DataSeparationLine.SelectionPointFieldDataArrayName = 'Cf'
>
>     DataSeparationLine.EdgeColor = [0.0, 0.0, 0.50000762951094835]
>
>     DataSeparationLine.LineWidth = 2.0
>
>     DataSeparationLine.DiffuseColor = [0.0, 0.0, 0.0]
>
>
>     DataSeparationLine.ColorArrayName = ''
>
>
>     Cfcontours.Visibility = 1
>
>
>     #--- Setup view
>
>     RenderView1 = GetRenderView()
>
>     RenderView1.Background = [1.0, 1.0, 1.0]
>
>     RenderView1.CenterAxesVisibility = 0
>
>     RenderView1.OrientationAxesVisibility = 0
>
>     RenderView1.ViewSize = [1450, 300]
>
>
>     RenderView1.InteractionMode = '3D'
>
>     RenderView1.CameraClippingRange = [120.40716073726786,
> 126.85668499830999]
>
>     RenderView1.CameraPosition = [25.95, 41.63, 1.43]
>
>     RenderView1.CameraFocalPoint = [4.31, 5.36, 4.77]
>
>     RenderView1.CameraViewUp = [0.93, -0.36, -0.053]
>
>
>     #--- Uncomment for 2D Interaction Mode
>
>     #RenderView1.CameraParallelScale = 5.5
>
>
>     a1_Cf_PVLookupTable = GetLookupTableForArray( "Cf", 1,
> RGBPoints=[-0.0001, 0.0, 0.0, 1.0, 0.0001, 1.0, 0.0, 0.0], LockScalarRange=1
> )
>
>
>     #--- Export image
>
>     Render()
>
>     WriteImage(wdir+'POSTPRO/IMAGES/cf_view1_'+index[i]+'.jpg')
>
>
> I set the range of the contours from -0.0001 to 0.0001 but the contours
> levels revert back to automatic scaling instead of the range that I specify.
> I am using version 3.98 of Paraview but I also tried with version 4.1.0. Why
> is this happening? Do I miss something in my script?
>
> Nikos
>
>
> _______________________________________________
> 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
>

From wascott at sandia.gov  Mon May  2 17:11:41 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 2 May 2016 21:11:41 +0000
Subject: [Paraview] Cron job and ParaView
In-Reply-To: <F6145F5F-AB6C-4A8F-91FD-6880B3D02D0A@sandia.gov>
References: <F6145F5F-AB6C-4A8F-91FD-6880B3D02D0A@sandia.gov>
Message-ID: <f1b4aba4eee544a7ad2696702d5f0bf9@ES01AMSNLNT.srn.sandia.gov>

OK, taking small steps here,  what is OSMesa, and want is Mesa?  Utkarsh and I had this discussion, but I never understood the difference.

Having just googled the difference, If I understand correctly, OSMesa actually means Off Screen Mesa, and is compiled into Mesa.  Otherwise, you get Mesa ? software rendering, but into a GLX window?

You are correct ? I am not building OSMesa.  Thus, my problem?

Alan



From: Moreland, Kenneth
Sent: Monday, May 02, 2016 3:01 PM
To: Scott, W Alan <wascott at sandia.gov>; paraview at paraview.org
Subject: Re: [Paraview] Cron job and ParaView

Are you sure you are building with osmesa? Just using mesa is not sufficient.

-Ken

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Walter Scott <wascott at sandia.gov<mailto:wascott at sandia.gov>>
Date: Monday, May 2, 2016 at 2:58 PM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Cron job and ParaView

I have a user that is trying to run ParaView in a cron job, and keeps getting the following error on PV 4.4.0: 4.4.0/ParaView4/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 542 vtkXOpenGLRenderWindow (0x5197850): bad X server connection

Has anyone tried to do this, and figured out a solution?  User has tried running a build I did ? which attaches to Mesa ? and has ?use-offscreen-rendering turned on, and is running pvbatch.  Same error.

Any ideas?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/d5b24232/attachment.html>

From kmorel at sandia.gov  Mon May  2 17:21:46 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 2 May 2016 21:21:46 +0000
Subject: [Paraview] Cron job and ParaView
In-Reply-To: <f1b4aba4eee544a7ad2696702d5f0bf9@ES01AMSNLNT.srn.sandia.gov>
References: <F6145F5F-AB6C-4A8F-91FD-6880B3D02D0A@sandia.gov>
 <f1b4aba4eee544a7ad2696702d5f0bf9@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <E7C036B2-CAE8-4416-A9C4-05440FBFAFF5@sandia.gov>

That is basically the difference. To use any implementation of OpenGL (which is what Mesa3D is), you first need an OpenGL context. On *nix you typically get this by opening a window with the Xhost. Even when doing offscreen rendering you need to get a context with the Xhost (because classically this was the interface to the graphics hardware).

Osmesa is a small library that sits on top of Mesa3D. It creates an OpenGL context without having to go to an Xhost. It has a different interface than GLX, so your software needs to specifically open an osmesa ?window? in addition to linking to the correct library.

As I recall, in order to use osmesa, you need to set VTK_OPENGL_HAS_OSMESA to ON and then set OSMESA_INCLUDE_DIR and OSMESA_LIBRARY. Typically the osmesa headers and libraries are in the same location as the Mesa 3D install.

See this Wiki page for more info: http://www.paraview.org/Wiki/ParaView_And_Mesa_3D

-Ken


From: Walter Scott <wascott at sandia.gov>
Date: Monday, May 2, 2016 at 3:11 PM
To: Kenneth Moreland <kmorel at sandia.gov>, "paraview at paraview.org" <paraview at paraview.org>
Subject: RE: [Paraview] Cron job and ParaView

OK, taking small steps here,  what is OSMesa, and want is Mesa?  Utkarsh and I had this discussion, but I never understood the difference.

Having just googled the difference, If I understand correctly, OSMesa actually means Off Screen Mesa, and is compiled into Mesa.  Otherwise, you get Mesa ? software rendering, but into a GLX window?

You are correct ? I am not building OSMesa.  Thus, my problem?

Alan



From: Moreland, Kenneth
Sent: Monday, May 02, 2016 3:01 PM
To: Scott, W Alan <wascott at sandia.gov>; paraview at paraview.org
Subject: Re: [Paraview] Cron job and ParaView

Are you sure you are building with osmesa? Just using mesa is not sufficient.

-Ken

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Walter Scott <wascott at sandia.gov<mailto:wascott at sandia.gov>>
Date: Monday, May 2, 2016 at 2:58 PM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Cron job and ParaView

I have a user that is trying to run ParaView in a cron job, and keeps getting the following error on PV 4.4.0: 4.4.0/ParaView4/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 542 vtkXOpenGLRenderWindow (0x5197850): bad X server connection

Has anyone tried to do this, and figured out a solution?  User has tried running a build I did ? which attaches to Mesa ? and has ?use-offscreen-rendering turned on, and is running pvbatch.  Same error.

Any ideas?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/76777850/attachment.html>

From chrisneal at ufl.edu  Mon May  2 16:20:13 2016
From: chrisneal at ufl.edu (Neal,Christopher R)
Date: Mon, 2 May 2016 20:20:13 +0000
Subject: [Paraview] Preserve color map style when changing variables
Message-ID: <BY2PR0801MB157375679C6819E6E0D07832BA790@BY2PR0801MB1573.namprd08.prod.outlook.com>


Hi,


I'm using Paraview 4.4. Can Paraview preserve the style of a color map & the associated color map layout? I've spent time creating a nice layout that involves the position of the color bar, the size of the text on the color bar, the precision of the numbers displayed on the color bar, and the color map(red to blue rainbow). It's exactly what I want. The problem is that if I go from plotting pressure to temperature, the entire layout reverts back to the default Paraview hot/cold colormap and the colorbar resets to the default.

Can I tell Paraview to maintain my style for all variables in the dataset?


Thank you,

Christopher R. Neal
Graduate Student
University of Florida

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/340a0764/attachment.html>

From dave.demarle at kitware.com  Mon May  2 20:26:46 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 2 May 2016 20:26:46 -0400
Subject: [Paraview] Cron job and ParaView
In-Reply-To: <E7C036B2-CAE8-4416-A9C4-05440FBFAFF5@sandia.gov>
References: <F6145F5F-AB6C-4A8F-91FD-6880B3D02D0A@sandia.gov>
 <f1b4aba4eee544a7ad2696702d5f0bf9@ES01AMSNLNT.srn.sandia.gov>
 <E7C036B2-CAE8-4416-A9C4-05440FBFAFF5@sandia.gov>
Message-ID: <CANjZAi8pZgjQ0b12Kp=CEGkoEadXVWmEw2FxoC_oY6ow=va5ug@mail.gmail.com>

Also, be wary of environment variables in the cron job which are not the
same (think empty) as when you log into an interactive session.

If the machine happens to be setup to have X and you are OK with onscreen
rendering for the job (many nighty dashboards work this way for instance)
it is entirely possible that the process has no DISPLAY environment
variable and that you have to manually set it to :0 or something like that.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, May 2, 2016 at 5:21 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:

> That is basically the difference. To use any implementation of OpenGL
> (which is what Mesa3D is), you first need an OpenGL context. On *nix you
> typically get this by opening a window with the Xhost. Even when doing
> offscreen rendering you need to get a context with the Xhost (because
> classically this was the interface to the graphics hardware).
>
>
>
> Osmesa is a small library that sits on top of Mesa3D. It creates an OpenGL
> context without having to go to an Xhost. It has a different interface than
> GLX, so your software needs to specifically open an osmesa ?window? in
> addition to linking to the correct library.
>
>
>
> As I recall, in order to use osmesa, you need to set VTK_OPENGL_HAS_OSMESA
> to ON and then set OSMESA_INCLUDE_DIR and OSMESA_LIBRARY. Typically the
> osmesa headers and libraries are in the same location as the Mesa 3D
> install.
>
>
>
> See this Wiki page for more info:
> http://www.paraview.org/Wiki/ParaView_And_Mesa_3D
>
>
>
> -Ken
>
>
>
>
>
> *From: *Walter Scott <wascott at sandia.gov>
> *Date: *Monday, May 2, 2016 at 3:11 PM
> *To: *Kenneth Moreland <kmorel at sandia.gov>, "paraview at paraview.org" <
> paraview at paraview.org>
> *Subject: *RE: [Paraview] Cron job and ParaView
>
>
>
> OK, taking small steps here,  what is OSMesa, and want is Mesa?  Utkarsh
> and I had this discussion, but I never understood the difference.
>
>
>
> Having just googled the difference, If I understand correctly, OSMesa
> actually means Off Screen Mesa, and is compiled into Mesa.  Otherwise, you
> get Mesa ? software rendering, but into a GLX window?
>
>
>
> You are correct ? I am not building OSMesa.  Thus, my problem?
>
>
>
> Alan
>
>
>
>
>
>
>
> *From:* Moreland, Kenneth
> *Sent:* Monday, May 02, 2016 3:01 PM
> *To:* Scott, W Alan <wascott at sandia.gov>; paraview at paraview.org
> *Subject:* Re: [Paraview] Cron job and ParaView
>
>
>
> Are you sure you are building with osmesa? Just using mesa is not
> sufficient.
>
>
>
> -Ken
>
>
>
> *From: *ParaView <paraview-bounces at paraview.org> on behalf of Walter
> Scott <wascott at sandia.gov>
> *Date: *Monday, May 2, 2016 at 2:58 PM
> *To: *"paraview at paraview.org" <paraview at paraview.org>
> *Subject: *[EXTERNAL] [Paraview] Cron job and ParaView
>
>
>
> I have a user that is trying to run ParaView in a cron job, and keeps
> getting the following error on PV 4.4.0:
> 4.4.0/ParaView4/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 542
> vtkXOpenGLRenderWindow (0x5197850): bad X server connection
>
>
>
> Has anyone tried to do this, and figured out a solution?  User has tried
> running a build I did ? which attaches to Mesa ? and has
> ?use-offscreen-rendering turned on, and is running pvbatch.  Same error.
>
>
>
> Any ideas?
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160502/a617123a/attachment.html>

From Jim.Eliot at awe.co.uk  Wed May  4 05:10:55 2016
From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk)
Date: Wed, 4 May 2016 09:10:55 +0000
Subject: [Paraview] Axis labels and ticks vanish at high zoom
Message-ID: <201605040908.u4498aWJ005450@msw1.awe.co.uk>

Good morning,

When I zoom into a dataset, the axes grid labels, ticks and grid disappear.

I turn on the axes grid (optionally turn on 'show grid' in the settings) and then zoom in on the axis. At a certain point, the axis labels, ticks and grid fail to show. Sometimes they show only part way up the axis.

Has anyone else seen this? Is there a way to get around it?

For info, I'm using ParaView 5.0.1 on Linux (built from source).

Cheers,
Jim


Jim Eliot
High Performance Computing Group
AWE, Aldermaston, Reading, RG7 4PR





The information in this email and in any attachment(s) is 
commercial in confidence. If you are not the named addressee(s) 
or 
if you receive this email in error then any distribution, copying or 
use of this communication or the information in it is strictly 
prohibited. Please notify us immediately by email at 
admin.internet(at)awe.co.uk, and then delete this message from 
your computer. While attachments are virus checked, AWE plc 
does not accept any liability in respect of any virus which is not 
detected.

AWE Plc
Registered in England and Wales
Registration No 02763902
AWE, Aldermaston, Reading, RG7 4PR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/ae149154/attachment.html>

From info at seoaachen.de  Wed May  4 06:43:09 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Wed, 4 May 2016 12:43:09 +0200
Subject: [Paraview] Mesa compilation
Message-ID: <70d0a00d-a72c-9280-771b-afa440cbe5f2@seoaachen.de>

Hello,

I try to compile Paraview with Mesa support (I need Paraviewweb on a 
server without GPU).

I use the tutorial on: 
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa

I get the Error:

CMake Error at VTK/CMake/FindPAckageHandlesSTandardArgs.cmake:97

Could NOT find OSMesa.


|there is nothing in my Ubuntu: OPENGL_INCLUDE_DIR 
/opt/mesa/9.2.2/llvmpipe/include |

What to do?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/28f1bcfe/attachment.html>

From info at seoaachen.de  Wed May  4 06:45:01 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Wed, 4 May 2016 12:45:01 +0200
Subject: [Paraview] Compile PV with Paraviewweb on Windows
Message-ID: <7a178602-7609-a925-c266-ef624671cbdb@seoaachen.de>

Hello,

Paraviewweb is only included in the 4.1 builds of PV on Windows.

Is it possible to compile newer Versions with Paraviewweb support?

regards

-- 
Daniel Zuidinga
Dipl.-Ing.

SEO Aachen
Passstr. 5
52070 Aachen

Tel   : 0241 / 450 912 67
E-Mail: info at seoaachen.de
Web   : http://www.seoaachen.de (nur zum Teil aktuell)
Xing  : https://www.xing.com/profile/Daniel_Zuidinga

Bald online: Software Tools f?r Konstrukteure und Bauteilhersteller
http://www.engineeringonline.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/cb091d35/attachment.html>

From info at seoaachen.de  Wed May  4 08:45:56 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Wed, 4 May 2016 14:45:56 +0200
Subject: [Paraview] Mesa compilation
In-Reply-To: <70d0a00d-a72c-9280-771b-afa440cbe5f2@seoaachen.de>
References: <70d0a00d-a72c-9280-771b-afa440cbe5f2@seoaachen.de>
Message-ID: <75415245-1cb8-4c87-95db-b68b919928ea@seoaachen.de>

I downloaded and build mesa 9.2.2 and now the make stops at:

4%] Building C object 
VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeFiles/vtkgl2ps.dir/gl2ps.c.omake[2]: 
*** No rule to make target 
`/work/apps/mesa/9.2.2/llvmpipe/lib/libOSMesa.[so', needed by 
`lib/libvtkgl2ps-pv4.3.so.1'. Stop.make[1]: *** 
[VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeFiles/vtkgl2ps.dir/all] Error 2make: 
*** [all] Error 2
libOSMesa.so does exist in that directory.

Am 04.05.2016 um 12:43 schrieb Daniel Zuidinga:
>
> Hello,
>
> I try to compile Paraview with Mesa support (I need Paraviewweb on a 
> server without GPU).
>
> I use the tutorial on: 
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa
>
> I get the Error:
>
> CMake Error at VTK/CMake/FindPAckageHandlesSTandardArgs.cmake:97
>
> Could NOT find OSMesa.
>
>
> |there is nothing in my Ubuntu: OPENGL_INCLUDE_DIR 
> /opt/mesa/9.2.2/llvmpipe/include |
>
> What to do?
>
>
>
> _______________________________________________
> 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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/c2b731aa/attachment.html>

From sebastien.jourdain at kitware.com  Wed May  4 09:48:23 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 4 May 2016 07:48:23 -0600
Subject: [Paraview] Compile PV with Paraviewweb on Windows
In-Reply-To: <7a178602-7609-a925-c266-ef624671cbdb@seoaachen.de>
References: <7a178602-7609-a925-c266-ef624671cbdb@seoaachen.de>
Message-ID: <CABObKxf9km_y2E7HSnH+qv=dwuD1cZTwuYMLCeHxewEAqW_C0A@mail.gmail.com>

Hi Daniel,

We are going to work on the Windows support in June for the next release of
ParaView 5.1+.
At the moment, building ParaViewWeb for windows won't be easy. But once we
iron out the process, it will be back by default in our binaries.

Seb

2016-05-04 4:45 GMT-06:00 Daniel Zuidinga <info at seoaachen.de>:

> Hello,
> Paraviewweb is only included in the 4.1 builds of PV on Windows.
>
> Is it possible to compile newer Versions with Paraviewweb support?
>
> regards
>
> --
> Daniel Zuidinga
> Dipl.-Ing.
>
> SEO Aachen
> Passstr. 5
> 52070 Aachen
>
> Tel   : 0241 / 450 912 67
> E-Mail: info at seoaachen.de
> Web   : http://www.seoaachen.de (nur zum Teil aktuell)
> Xing  : https://www.xing.com/profile/Daniel_Zuidinga
>
> Bald online: Software Tools f?r Konstrukteure und Bauteilherstellerhttp://www.engineeringonline.de
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/d2073930/attachment.html>

From sebastien.jourdain at kitware.com  Wed May  4 09:54:12 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 4 May 2016 07:54:12 -0600
Subject: [Paraview] Mesa compilation
In-Reply-To: <75415245-1cb8-4c87-95db-b68b919928ea@seoaachen.de>
References: <70d0a00d-a72c-9280-771b-afa440cbe5f2@seoaachen.de>
 <75415245-1cb8-4c87-95db-b68b919928ea@seoaachen.de>
Message-ID: <CABObKxe5KYLevQqjM1E_o4HH6o-Nbh_KYV_ENEygYruH5OqsnQ@mail.gmail.com>

Hi Daniel,

here is an updated version of the documentation.
We are in the process of migrating the documentation and code base. Once it
will be done the later will be the official one.

http://kitware.github.io/paraviewweb/docs/guides/os_mesa.html

Moreover, if you are on linux and you are using the latest ParaView, you
can use our binaries as they embed the llvm libraries.
When running ParaViewWeb, you just need to add an extra argument
--mesa-llvm.

Seb



On Wed, May 4, 2016 at 6:45 AM, Daniel Zuidinga <info at seoaachen.de> wrote:

> I downloaded and build mesa 9.2.2 and now the make stops at:
>
> 4%] Building C object
> VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeFiles/vtkgl2ps.dir/gl2ps.c.omake[2]:
> *** No rule to make target
> `/work/apps/mesa/9.2.2/llvmpipe/lib/libOSMesa.[so', needed by
> `lib/libvtkgl2ps-pv4.3.so.1'. Stop.make[1]: ***
> [VTK/ThirdParty/gl2ps/vtkgl2ps/CMakeFiles/vtkgl2ps.dir/all] Error 2make:
> *** [all] Error 2
> libOSMesa.so does exist in that directory.
>
>
> Am 04.05.2016 um 12:43 schrieb Daniel Zuidinga:
>
> Hello,
>
> I try to compile Paraview with Mesa support (I need Paraviewweb on a
> server without GPU).
>
> I use the tutorial on:
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa
>
> I get the Error:
>
> CMake Error at VTK/CMake/FindPAckageHandlesSTandardArgs.cmake:97
>
> Could NOT find OSMesa.
>
>
> there is nothing in my Ubuntu:
>
>   OPENGL_INCLUDE_DIR          /opt/mesa/9.2.2/llvmpipe/include
>
>
> What to do?
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/015d660e/attachment.html>

From utkarsh.ayachit at kitware.com  Wed May  4 10:33:34 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 4 May 2016 10:33:34 -0400
Subject: [Paraview] Dropping support for OpenGL1 in ParaView 5.2.
Message-ID: <CADHSJjCqyUm8UEYFqkn2cYP8BL_06yQTmymn1J7h_qaHde56wg@mail.gmail.com>

Folks,

As we continue to make progress on the new OpenGL2 rendering backend,
I wanted to get a feel from the community if there's any objection to
dropping support entirely for the legacy OpenGL1 rendering backend in
ParaView for 5.2?

Note this will only affect ParaView and ParaView-based applications.

Utkarsh

From utkarsh.ayachit at kitware.com  Wed May  4 14:47:32 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 4 May 2016 14:47:32 -0400
Subject: [Paraview] Dropping support for OpenGL1 in ParaView 5.2.
In-Reply-To: <CADHSJjCqyUm8UEYFqkn2cYP8BL_06yQTmymn1J7h_qaHde56wg@mail.gmail.com>
References: <CADHSJjCqyUm8UEYFqkn2cYP8BL_06yQTmymn1J7h_qaHde56wg@mail.gmail.com>
Message-ID: <CADHSJjCY8RO3=Kdsf+kS07cJ_cqFMXPL6h4Vipcy4-vzLCDaqA@mail.gmail.com>

Following discussions with folks here, we're tabling this for another
year as the OpenGL2 backend continues to stabilize.


On Wed, May 4, 2016 at 10:33 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Folks,
>
> As we continue to make progress on the new OpenGL2 rendering backend,
> I wanted to get a feel from the community if there's any objection to
> dropping support entirely for the legacy OpenGL1 rendering backend in
> ParaView for 5.2?
>
> Note this will only affect ParaView and ParaView-based applications.
>
> Utkarsh

From andy.bauer at kitware.com  Wed May  4 15:37:34 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 4 May 2016 15:37:34 -0400
Subject: [Paraview] volume rendering with Catalyst ...
In-Reply-To: <6f6c30d4-28f2-12f2-b1ac-195e824baa13@be.itu.edu.tr>
References: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
 <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>
 <6f6c30d4-28f2-12f2-b1ac-195e824baa13@be.itu.edu.tr>
Message-ID: <CAMaOp+EauL+DK52MXpE7nF3e+TcAqbHiM-XWwinS_FbcVh50kw@mail.gmail.com>

Hi,

Are you generating the Catalyst script with PV built with the OpenGL2
backend and then linking with a version of Catalyst built with the OpenGL1
backend? I'd guess that this is the problem.

To isolate the issue further, you can do a Python trace in the GUI to see
if you get the same issue when you run pvpython with that script.

Best,
Andy

On Fri, Apr 29, 2016 at 10:12 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Cory,
>
> Do you think that it is a bug in Catalyst side. In this case, i am running
> the code as follows
>
> export LD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${LD_LIBRARY_PATH}
> export DYLD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${DYLD_LIBRARY_PATH}
> mpirun -np 12 ./main.x
>
> Thanks for your help,
>
> --ufuk
>
>
>
> On 29/04/16 16:58, Cory Quammen wrote:
>
>> It indeed looks like the scalar opacity function is not being set up
>> properly when using Catalyst. Looking at your script, it looks like it
>> should be, though.
>>
>> Could you describe how you are running this with Catalyst?
>>
>> Thanks,
>> Cory
>>
>> On Tue, Apr 26, 2016 at 4:18 AM, Ufuk Utku Turuncoglu (BE)
>> <u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>
>>> Hi,
>>>
>>> I had a problem in Catalyst when i run a visualization pipeline with
>>> volume
>>> rendering. The attached figures shows the problem and belong to same
>>> visualization with and without Catalyst. In my case, the co-processing
>>> Python script (dvr.py) is generated from multi-block dataset and the
>>> Catalyst code uses MPI code to define multi-block dataset also. So, it is
>>> consistent in both side. The visualization pipeline includes Transform
>>> and
>>> MergeBlocks filters to create the final image and mapper is set as Bunyk
>>> Ray
>>> Cast. It seems that there is a problem in the color transfer function
>>> but i
>>> am not sure. I also test with different mapper such as projected-tetra
>>> but
>>> the result is same. I just wonder that did you see any similar problem
>>> before.
>>>
>>> Regards,
>>>
>>> Istanbul Technical University
>>> Informatics Institute
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160504/822b2427/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Thu May  5 01:46:57 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Thu, 5 May 2016 08:46:57 +0300
Subject: [Paraview] volume rendering with Catalyst ...
In-Reply-To: <CAMaOp+EauL+DK52MXpE7nF3e+TcAqbHiM-XWwinS_FbcVh50kw@mail.gmail.com>
References: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
 <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>
 <6f6c30d4-28f2-12f2-b1ac-195e824baa13@be.itu.edu.tr>
 <CAMaOp+EauL+DK52MXpE7nF3e+TcAqbHiM-XWwinS_FbcVh50kw@mail.gmail.com>
Message-ID: <1947e1b2-e218-8576-199f-1c02d4e7ed19@be.itu.edu.tr>

Hi,

Actually, i am using same ParaView installation (under Mac OS) to create 
the Catalyst script and compiling the model code. So, OpenGL backend 
must be consistent.  In any case, i'll try your suggestion and let you 
know about it.

Regards,

--ufuk

On 04/05/16 22:37, Andy Bauer wrote:
> Hi,
>
> Are you generating the Catalyst script with PV built with the OpenGL2 
> backend and then linking with a version of Catalyst built with the 
> OpenGL1 backend? I'd guess that this is the problem.
>
> To isolate the issue further, you can do a Python trace in the GUI to 
> see if you get the same issue when you run pvpython with that script.
>
> Best,
> Andy
>
> On Fri, Apr 29, 2016 at 10:12 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Hi Cory,
>
>     Do you think that it is a bug in Catalyst side. In this case, i am
>     running the code as follows
>
>     export
>     LD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${LD_LIBRARY_PATH}
>     export
>     DYLD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${DYLD_LIBRARY_PATH}
>     mpirun -np 12 ./main.x
>
>     Thanks for your help,
>
>     --ufuk
>
>
>
>     On 29/04/16 16:58, Cory Quammen wrote:
>
>         It indeed looks like the scalar opacity function is not being
>         set up
>         properly when using Catalyst. Looking at your script, it looks
>         like it
>         should be, though.
>
>         Could you describe how you are running this with Catalyst?
>
>         Thanks,
>         Cory
>
>         On Tue, Apr 26, 2016 at 4:18 AM, Ufuk Utku Turuncoglu (BE)
>         <u.utku.turuncoglu at be.itu.edu.tr
>         <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>             Hi,
>
>             I had a problem in Catalyst when i run a visualization
>             pipeline with volume
>             rendering. The attached figures shows the problem and
>             belong to same
>             visualization with and without Catalyst. In my case, the
>             co-processing
>             Python script (dvr.py) is generated from multi-block
>             dataset and the
>             Catalyst code uses MPI code to define multi-block dataset
>             also. So, it is
>             consistent in both side. The visualization pipeline
>             includes Transform and
>             MergeBlocks filters to create the final image and mapper
>             is set as Bunyk Ray
>             Cast. It seems that there is a problem in the color
>             transfer function but i
>             am not sure. I also test with different mapper such as
>             projected-tetra but
>             the result is same. I just wonder that did you see any
>             similar problem
>             before.
>
>             Regards,
>
>             Istanbul Technical University
>             Informatics Institute
>
>             _______________________________________________
>             Powered by www.kitware.com <http://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
>
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/9265484e/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Thu May  5 04:59:22 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Thu, 5 May 2016 11:59:22 +0300
Subject: [Paraview] volume rendering with Catalyst ...
In-Reply-To: <CAMaOp+EauL+DK52MXpE7nF3e+TcAqbHiM-XWwinS_FbcVh50kw@mail.gmail.com>
References: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
 <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>
 <6f6c30d4-28f2-12f2-b1ac-195e824baa13@be.itu.edu.tr>
 <CAMaOp+EauL+DK52MXpE7nF3e+TcAqbHiM-XWwinS_FbcVh50kw@mail.gmail.com>
Message-ID: <63761151-483c-368b-7bcf-bb1ee42c6674@be.itu.edu.tr>

Hi,

I tested the pipeline as follows,

1 - using original Catalyst script, i created new python script (also 
includes that read part). In this case, i removed all co-processing 
calls.  See the attached script (dvr_pv.py). You could also compare it 
with original Co-processing generated script (dvr.py).

2 - Then, i opened PV and after Tools-> Python Shell -> Run Script, i 
run the dvr_pv.py

The strange thing is that it produces exactly same problematic DVR in 
this case. So, it seems that problem is not related with Catalyst but it 
seems related with Python interface. So, i think that this information 
could narrow down the places that might cause the problem. Please let me 
know, if you need more information and test.

Thanks again for your kindly help,
Regards,

--ufuk

On 04/05/16 22:37, Andy Bauer wrote:
> Hi,
>
> Are you generating the Catalyst script with PV built with the OpenGL2 
> backend and then linking with a version of Catalyst built with the 
> OpenGL1 backend? I'd guess that this is the problem.
>
> To isolate the issue further, you can do a Python trace in the GUI to 
> see if you get the same issue when you run pvpython with that script.
>
> Best,
> Andy
>
> On Fri, Apr 29, 2016 at 10:12 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Hi Cory,
>
>     Do you think that it is a bug in Catalyst side. In this case, i am
>     running the code as follows
>
>     export
>     LD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${LD_LIBRARY_PATH}
>     export
>     DYLD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${DYLD_LIBRARY_PATH}
>     mpirun -np 12 ./main.x
>
>     Thanks for your help,
>
>     --ufuk
>
>
>
>     On 29/04/16 16:58, Cory Quammen wrote:
>
>         It indeed looks like the scalar opacity function is not being
>         set up
>         properly when using Catalyst. Looking at your script, it looks
>         like it
>         should be, though.
>
>         Could you describe how you are running this with Catalyst?
>
>         Thanks,
>         Cory
>
>         On Tue, Apr 26, 2016 at 4:18 AM, Ufuk Utku Turuncoglu (BE)
>         <u.utku.turuncoglu at be.itu.edu.tr
>         <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>             Hi,
>
>             I had a problem in Catalyst when i run a visualization
>             pipeline with volume
>             rendering. The attached figures shows the problem and
>             belong to same
>             visualization with and without Catalyst. In my case, the
>             co-processing
>             Python script (dvr.py) is generated from multi-block
>             dataset and the
>             Catalyst code uses MPI code to define multi-block dataset
>             also. So, it is
>             consistent in both side. The visualization pipeline
>             includes Transform and
>             MergeBlocks filters to create the final image and mapper
>             is set as Bunyk Ray
>             Cast. It seems that there is a problem in the color
>             transfer function but i
>             am not sure. I also test with different mapper such as
>             projected-tetra but
>             the result is same. I just wonder that did you see any
>             similar problem
>             before.
>
>             Regards,
>
>             Istanbul Technical University
>             Informatics Institute
>
>             _______________________________________________
>             Powered by www.kitware.com <http://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
>
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/58ba3540/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dvr_pv.py
Type: text/x-python-script
Size: 3892 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/58ba3540/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dvr.py
Type: text/x-python-script
Size: 7020 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/58ba3540/attachment-0001.bin>

From cgunases at gmail.com  Thu May  5 07:37:18 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Thu, 5 May 2016 17:07:18 +0530
Subject: [Paraview] Building a 3D volume but an error message pop up,
	kind assistance needed
Message-ID: <CAJFKOL2DSw3Ebtq9VjRx4WuFxjayNL-bqpZ33qvyGdFnTrktcw@mail.gmail.com>

Hi all,


I performed the boundary detection(eg:Canny edge detection) on the
segmented images(they are binary images) and then converted to .mat file.
Next, stacked the matrices(3D) and converted to vtk format.

I am getting the following error when i try to build a 3Dvolume in
Paraview. Hence,i  cannot build the volume, what would be the cause for
that?

 Can anyone please help me to resolve this matter?
[image: Inline image 2]

Thank you so much in advance.

-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/821ef50f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 44022 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/821ef50f/attachment.png>

From jiri.vyskocil at fjfi.cvut.cz  Thu May  5 08:58:38 2016
From: jiri.vyskocil at fjfi.cvut.cz (=?UTF-8?B?SmnFmcOtIFZ5c2tvxI1pbA==?=)
Date: Thu, 5 May 2016 14:58:38 +0200
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server with
	GPU
Message-ID: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>

Hello,


I'm trying to set up a Paraview Web server on a Fedora 23 machine. The serves is not connected to a 
monitor or a keyboard (I only have access through ssh), but it has a nvidia GPU which I want to use 
for paraview.


I have installed xdm to run the X server, and verified that it is in fact running with the correct 
nvidia drivers (by checking the Xorg.0.log file). The problem is I don't know how to run the 
paraview webserver on the X display when there's no one physically logged in - I can only get to the 
server via ssh. When I log in, and switch to the paraview user, the DISPLAY and XAUTHORITY variables 
are empty.


The webserver itself is running (apache + the python launcher), but when I try to open any of the 
example applications, I get an error like this:


$ ./launch-paraview.sh
2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
2016-05-05 14:54:17,528:INFO:twisted:Starting factory <twisted.web.server.Site instance at 
0x7fe20da6a998>
2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09 +0000] "POST /paraview/ 
HTTP/1.1" 503 78 "https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11; Fedora; Linux 
x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"


$ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
2016-05-05 14:55:06+0200 [-] Log opened.
ERROR: In /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, 
line 333
vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=


Specifying DISPLAY=:0 when running the launcher gives this error:

$ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
2016-05-05 14:57:22+0200 [-] Log opened.
No protocol specified
No protocol specified
No protocol specified
ERROR: In /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, 
line 333
vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0. Aborting.



Thanks for any hints,

Jiri



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3733 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/93fcd692/attachment.bin>

From sebastien.jourdain at kitware.com  Thu May  5 10:23:11 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 5 May 2016 08:23:11 -0600
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
Message-ID: <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>

You were on the right track with DISPLAY=:0 but I'm wondering if you setup
a "virtual" monitor or if your "paraview" user is auto logged in a X
session or if it stuck at the "login" panel?

You can find some information about the virtual screen here: (Search for
"Screen")

http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html

And for the autologin if it is needed. (Note on EC2 the user start X hence
no need to login...)

https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml

Seb

On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz>
wrote:

> Hello,
>
>
> I'm trying to set up a Paraview Web server on a Fedora 23 machine. The
> serves is not connected to a monitor or a keyboard (I only have access
> through ssh), but it has a nvidia GPU which I want to use for paraview.
>
>
> I have installed xdm to run the X server, and verified that it is in fact
> running with the correct nvidia drivers (by checking the Xorg.0.log file).
> The problem is I don't know how to run the paraview webserver on the X
> display when there's no one physically logged in - I can only get to the
> server via ssh. When I log in, and switch to the paraview user, the DISPLAY
> and XAUTHORITY variables are empty.
>
>
> The webserver itself is running (apache + the python launcher), but when I
> try to open any of the example applications, I get an error like this:
>
>
> $ ./launch-paraview.sh
> 2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
> 2016-05-05 14:54:17,528:INFO:twisted:Starting factory
> <twisted.web.server.Site instance at 0x7fe20da6a998>
> 2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09
> +0000] "POST /paraview/ HTTP/1.1" 503 78 "
> https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11; Fedora;
> Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>
>
> $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
> 2016-05-05 14:55:06+0200 [-] Log opened.
> ERROR: In
> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
> line 333
> vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>
>
> Specifying DISPLAY=:0 when running the launcher gives this error:
>
> $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
> 2016-05-05 14:57:22+0200 [-] Log opened.
> No protocol specified
> No protocol specified
> No protocol specified
> ERROR: In
> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
> line 333
> vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0.
> Aborting.
>
>
>
> Thanks for any hints,
>
> Jiri
>
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/4c6ccce3/attachment.html>

From ganesh.iitm at gmail.com  Thu May  5 11:40:07 2016
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 05 May 2016 15:40:07 +0000
Subject: [Paraview] Problem importing vtk inside pvpython
Message-ID: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>

Hello,

  I'm having trouble importing vtk inside pvpython while it imports just
fine inside python. I installed paraview-python with paraview-5.0.1 using
debian stretch. Any ideas on why this might be the case?

ganesh at tesla:~$ pvpython
Python 2.7.10 (default, Jul  1 2015, 10:54:53)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
<module>
    from vtkCommonCore import *
  File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1, in
<module>
    from vtkCommonCorePython import *
TypeError: value must be a class or type
>>>
>>>
Segmentation fault
ganesh at tesla:~$ python
Python 2.7.10 (default, Jul  1 2015, 10:54:53)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
>>>

ganesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/fd5e39a2/attachment.html>

From mathieu.westphal at kitware.com  Thu May  5 12:41:31 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Thu, 5 May 2016 18:41:31 +0200
Subject: [Paraview] Problem importing vtk inside pvpython
In-Reply-To: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>
References: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>
Message-ID: <CAC2t4URpk73P2j43zn5wKeLdqsjSdy=+GtB6cJJSH+3-rHk4yw@mail.gmail.com>

pvpython is a paraview client, and it is not suposed to execute vtk code,
wich is executed on the server.
in pvpython you can do:
from paraview import *

What are you trying to achieve ?

Mathieu Westphal

On Thu, May 5, 2016 at 5:40 PM, Ganesh Vijayakumar <ganesh.iitm at gmail.com>
wrote:

> Hello,
>
>   I'm having trouble importing vtk inside pvpython while it imports just
> fine inside python. I installed paraview-python with paraview-5.0.1 using
> debian stretch. Any ideas on why this might be the case?
>
> ganesh at tesla:~$ pvpython
> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
> [GCC 4.9.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import vtk
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
> <module>
>     from vtkCommonCore import *
>   File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1, in
> <module>
>     from vtkCommonCorePython import *
> TypeError: value must be a class or type
> >>>
> >>>
> Segmentation fault
> ganesh at tesla:~$ python
> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
> [GCC 4.9.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import vtk
> >>>
>
> ganesh
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/90d6adb1/attachment.html>

From ganesh.iitm at gmail.com  Thu May  5 13:03:36 2016
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 05 May 2016 17:03:36 +0000
Subject: [Paraview] Problem importing vtk inside pvpython
In-Reply-To: <CAC2t4URpk73P2j43zn5wKeLdqsjSdy=+GtB6cJJSH+3-rHk4yw@mail.gmail.com>
References: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>
 <CAC2t4URpk73P2j43zn5wKeLdqsjSdy=+GtB6cJJSH+3-rHk4yw@mail.gmail.com>
Message-ID: <CAFtK+etUkKigjsJQiKgcosfw87hdsgsvkS6pn--ZSur8d4Ln0w@mail.gmail.com>

Thanks. Could I reproduce what's going on here?

https://blog.kitware.com/improved-vtk-numpy-integration/



On Thu, May 5, 2016 at 10:41 AM Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> pvpython is a paraview client, and it is not suposed to execute vtk code,
> wich is executed on the server.
> in pvpython you can do:
> from paraview import *
>
> What are you trying to achieve ?
>
> Mathieu Westphal
>
> On Thu, May 5, 2016 at 5:40 PM, Ganesh Vijayakumar <ganesh.iitm at gmail.com>
> wrote:
>
>> Hello,
>>
>>   I'm having trouble importing vtk inside pvpython while it imports just
>> fine inside python. I installed paraview-python with paraview-5.0.1 using
>> debian stretch. Any ideas on why this might be the case?
>>
>> ganesh at tesla:~$ pvpython
>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>> [GCC 4.9.2] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import vtk
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>>   File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
>> <module>
>>     from vtkCommonCore import *
>>   File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1,
>> in <module>
>>     from vtkCommonCorePython import *
>> TypeError: value must be a class or type
>> >>>
>> >>>
>> Segmentation fault
>> ganesh at tesla:~$ python
>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>> [GCC 4.9.2] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import vtk
>> >>>
>>
>> ganesh
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/127b159d/attachment.html>

From sebastien.jourdain at kitware.com  Thu May  5 13:30:47 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 5 May 2016 11:30:47 -0600
Subject: [Paraview] Problem importing vtk inside pvpython
In-Reply-To: <CAFtK+etUkKigjsJQiKgcosfw87hdsgsvkS6pn--ZSur8d4Ln0w@mail.gmail.com>
References: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>
 <CAC2t4URpk73P2j43zn5wKeLdqsjSdy=+GtB6cJJSH+3-rHk4yw@mail.gmail.com>
 <CAFtK+etUkKigjsJQiKgcosfw87hdsgsvkS6pn--ZSur8d4Ln0w@mail.gmail.com>
Message-ID: <CABObKxcLBrndg_A9=W3q5WEngFwonbUZrY7FYoYeDzEWq2ozzA@mail.gmail.com>

I think you have VTK installed on your system which conflict with your
ParaView one. Hence the segfault inside ParaView.

Otherwise nothing should prevent you from doing pure VTK code in ParaView
as long as you are aware of the possible issue when running remotely and/or
in parallel.


On Thu, May 5, 2016 at 11:03 AM, Ganesh Vijayakumar <ganesh.iitm at gmail.com>
wrote:

> Thanks. Could I reproduce what's going on here?
>
> https://blog.kitware.com/improved-vtk-numpy-integration/
>
>
>
> On Thu, May 5, 2016 at 10:41 AM Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
>> pvpython is a paraview client, and it is not suposed to execute vtk code,
>> wich is executed on the server.
>> in pvpython you can do:
>> from paraview import *
>>
>> What are you trying to achieve ?
>>
>> Mathieu Westphal
>>
>> On Thu, May 5, 2016 at 5:40 PM, Ganesh Vijayakumar <ganesh.iitm at gmail.com
>> > wrote:
>>
>>> Hello,
>>>
>>>   I'm having trouble importing vtk inside pvpython while it imports just
>>> fine inside python. I installed paraview-python with paraview-5.0.1 using
>>> debian stretch. Any ideas on why this might be the case?
>>>
>>> ganesh at tesla:~$ pvpython
>>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>>> [GCC 4.9.2] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> import vtk
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in <module>
>>>   File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
>>> <module>
>>>     from vtkCommonCore import *
>>>   File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1,
>>> in <module>
>>>     from vtkCommonCorePython import *
>>> TypeError: value must be a class or type
>>> >>>
>>> >>>
>>> Segmentation fault
>>> ganesh at tesla:~$ python
>>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>>> [GCC 4.9.2] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> import vtk
>>> >>>
>>>
>>> ganesh
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/79fbb9c3/attachment.html>

From ganesh.iitm at gmail.com  Thu May  5 13:57:25 2016
From: ganesh.iitm at gmail.com (Ganesh Vijayakumar)
Date: Thu, 05 May 2016 17:57:25 +0000
Subject: [Paraview] Problem importing vtk inside pvpython
In-Reply-To: <CABObKxcLBrndg_A9=W3q5WEngFwonbUZrY7FYoYeDzEWq2ozzA@mail.gmail.com>
References: <CAFtK+es6vpx3SsjRqC5CGh9d9hJH126A1EjfXa-dwMAw43MCsw@mail.gmail.com>
 <CAC2t4URpk73P2j43zn5wKeLdqsjSdy=+GtB6cJJSH+3-rHk4yw@mail.gmail.com>
 <CAFtK+etUkKigjsJQiKgcosfw87hdsgsvkS6pn--ZSur8d4Ln0w@mail.gmail.com>
 <CABObKxcLBrndg_A9=W3q5WEngFwonbUZrY7FYoYeDzEWq2ozzA@mail.gmail.com>
Message-ID: <CAFtK+etu-NAfj9Djr9EKBNX_p4E=Qh1R_pEzbE=Y7J4A_W1nMQ@mail.gmail.com>

oh. This looks like it's getting out of scope this mailing list. Feel free
to ignore. I should probably file a bug report there. I'll just leave this
here for others to comment/see if they run into a similar problem.

https://packages.debian.org/testing/python/paraview-python
https://packages.debian.org/stretch/python-vtk6

I just checked. paraview-python depends on python-vtk6 which in turn
depends on libvtk6.2. I have all of them installed. Something else must be
up. Strangely there's a vtk module inside paraview itself which also fails
to import dataset_adapter. I don't know if this is a conflict or not.

ganesh at tesla:$ pvpython
Python 2.7.10 (default, Jul  1 2015, 10:54:53)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
<module>
    from vtkCommonCore import *
  File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1, in
<module>
    from vtkCommonCorePython import *
TypeError: value must be a class or type
>>> import paraview.vtk
>>> import paraview.vtk.numpy_interface
>>> import paraview.vtk.numpy_interface.dataset_adapter
Segmentation fault
ganesh at tesla:$


My old python scripts used the dataset_adapter under a different tree
within the paraview module. Now it's broken. Crap!

ganesh

On Thu, May 5, 2016 at 11:30 AM Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> I think you have VTK installed on your system which conflict with your
> ParaView one. Hence the segfault inside ParaView.
>
> Otherwise nothing should prevent you from doing pure VTK code in ParaView
> as long as you are aware of the possible issue when running remotely and/or
> in parallel.
>
>
> On Thu, May 5, 2016 at 11:03 AM, Ganesh Vijayakumar <ganesh.iitm at gmail.com
> > wrote:
>
>> Thanks. Could I reproduce what's going on here?
>>
>> https://blog.kitware.com/improved-vtk-numpy-integration/
>>
>>
>>
>> On Thu, May 5, 2016 at 10:41 AM Mathieu Westphal <
>> mathieu.westphal at kitware.com> wrote:
>>
>>> pvpython is a paraview client, and it is not suposed to execute vtk
>>> code, wich is executed on the server.
>>> in pvpython you can do:
>>> from paraview import *
>>>
>>> What are you trying to achieve ?
>>>
>>> Mathieu Westphal
>>>
>>> On Thu, May 5, 2016 at 5:40 PM, Ganesh Vijayakumar <
>>> ganesh.iitm at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>>   I'm having trouble importing vtk inside pvpython while it imports
>>>> just fine inside python. I installed paraview-python with paraview-5.0.1
>>>> using debian stretch. Any ideas on why this might be the case?
>>>>
>>>> ganesh at tesla:~$ pvpython
>>>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>>>> [GCC 4.9.2] on linux2
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> import vtk
>>>> Traceback (most recent call last):
>>>>   File "<stdin>", line 1, in <module>
>>>>   File "/usr/lib/python2.7/dist-packages/vtk/__init__.py", line 39, in
>>>> <module>
>>>>     from vtkCommonCore import *
>>>>   File "/usr/lib/python2.7/dist-packages/vtk/vtkCommonCore.py", line 1,
>>>> in <module>
>>>>     from vtkCommonCorePython import *
>>>> TypeError: value must be a class or type
>>>> >>>
>>>> >>>
>>>> Segmentation fault
>>>> ganesh at tesla:~$ python
>>>> Python 2.7.10 (default, Jul  1 2015, 10:54:53)
>>>> [GCC 4.9.2] on linux2
>>>> Type "help", "copyright", "credits" or "license" for more information.
>>>> >>> import vtk
>>>> >>>
>>>>
>>>> ganesh
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160505/316cb0df/attachment.html>

From info at seoaachen.de  Fri May  6 06:45:05 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Fri, 6 May 2016 12:45:05 +0200
Subject: [Paraview] Plugin Compatibility (Medreader)
Message-ID: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>

Hi,

I try to use a Paraview Plugin (Medreader) which works in PV3.14 in PV 
4.1.3. Does this work in general? When loading the dll file I get the error:

ERROR: In 
C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx, 
line 360

vtkPVPluginLoader (0AF78238): D


regards

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/f7e9ed27/attachment.html>

From mathieu.westphal at kitware.com  Fri May  6 06:58:17 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 6 May 2016 12:58:17 +0200
Subject: [Paraview] Plugin Compatibility (Medreader)
In-Reply-To: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>
References: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>
Message-ID: <CAC2t4US9-Cd4cbnqYG4nBD3TpHi3da+apxS5KxrZzG-8xVO3Vg@mail.gmail.com>

Hello

As far as I know, there is no officially supported MEDReader plugin for
paraview.
There is a working one, part of the Salome project.
Other versions can be found on the internet.

Which plugin are you referring to ? Can you provide a upstream link ?

Regards,

Mathieu Westphal

On Fri, May 6, 2016 at 12:45 PM, Daniel Zuidinga <info at seoaachen.de> wrote:

> Hi,
>
> I try to use a Paraview Plugin (Medreader) which works in PV3.14 in PV
> 4.1.3. Does this work in general? When loading the dll file I get the error:
> ERROR: In
> C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx,
> line 360
>
> vtkPVPluginLoader (0AF78238): D
>
>
> regards
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/08e9b1ed/attachment.html>

From jiri.vyskocil at fjfi.cvut.cz  Fri May  6 07:06:11 2016
From: jiri.vyskocil at fjfi.cvut.cz (=?UTF-8?B?SmnFmcOtIFZ5c2tvxI1pbA==?=)
Date: Fri, 6 May 2016 13:06:11 +0200
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
 <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
Message-ID: <56c031a3-f4f6-fa0f-b668-dbe3225f3d41@fjfi.cvut.cz>

Thanks Sebastien. It seems I'm getting somewhere - I installed "slim" instead of xdm, and had the 
paraview user login automatically. Now when I login via ssh, I can see the X server is running, and 
the paraview user has the ~/.Xauthority file created in its homedir (so I guess it did login 
successfuly). The DISPLAY variable is still unset, but I get a new error if I set it manually:

[paraview at vbl-sim ~] $ DISPLAY=:0 glxinfo
Invalid MIT-MAGIC-COOKIE-1 keyError: unable to open display :0

and the same error for any X program (so I can't run i.e. "xhost +" recommended somewhere). This 
situation persists through restarts. I trie ro remove the ~/.Xauthority file as recommended 
elsewhere, but that didn't help either.

(I also tried a second method - starting the launcher through .xinitrc, but it seems slim ignores 
this file altogether. That's a different problem anyways, as for testing it would be more 
comfortable if I could launch the server form command line)


Jiri



On 05/05/16 16:23, Sebastien Jourdain wrote:
> You were on the right track with DISPLAY=:0 but I'm wondering if you setup a "virtual" monitor or 
> if your "paraview" user is auto logged in a X session or if it stuck at the "login" panel?
>
> You can find some information about the virtual screen here: (Search for "Screen")
>
> http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>
> And for the autologin if it is needed. (Note on EC2 the user start X hence no need to login...)
>
> https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>
> Seb
>
> On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz 
> <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>
>     Hello,
>
>
>     I'm trying to set up a Paraview Web server on a Fedora 23 machine. The serves is not connected
>     to a monitor or a keyboard (I only have access through ssh), but it has a nvidia GPU which I
>     want to use for paraview.
>
>
>     I have installed xdm to run the X server, and verified that it is in fact running with the
>     correct nvidia drivers (by checking the Xorg.0.log file). The problem is I don't know how to
>     run the paraview webserver on the X display when there's no one physically logged in - I can
>     only get to the server via ssh. When I log in, and switch to the paraview user, the DISPLAY
>     and XAUTHORITY variables are empty.
>
>
>     The webserver itself is running (apache + the python launcher), but when I try to open any of
>     the example applications, I get an error like this:
>
>
>     $ ./launch-paraview.sh
>     2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>     2016-05-05 14:54:17,528:INFO:twisted:Starting factory <twisted.web.server.Site instance at
>     0x7fe20da6a998>
>     2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09 +0000] "POST
>     /paraview/ HTTP/1.1" 503 78 "https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11;
>     Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>
>
>     $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>     2016-05-05 14:55:06+0200 [-] Log opened.
>     ERROR: In
>     /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333
>     vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>
>
>     Specifying DISPLAY=:0 when running the launcher gives this error:
>
>     $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>     2016-05-05 14:57:22+0200 [-] Log opened.
>     No protocol specified
>     No protocol specified
>     No protocol specified
>     ERROR: In
>     /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333
>     vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0. Aborting.
>
>
>
>     Thanks for any hints,
>
>     Jiri
>
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/0d7189f6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3733 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/0d7189f6/attachment.bin>

From cgunases at gmail.com  Fri May  6 07:20:09 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Fri, 6 May 2016 16:50:09 +0530
Subject: [Paraview] ParaView : resolve the error message.
Message-ID: <CAJFKOL2PdDuk3Ormf+EkuRW2ZnexNb1ZiqWCLv7yzoxDhQdQvQ@mail.gmail.com>

Hello,

I have installed Paraview 5.0 on my machine(Windows 8.1). When i try to
visualize a 3D model in vtk format, i am getting an error.

I have no idea why i get the following error? What does it depicts?
*error:In C:\bbd\df0abce0\build\src\paraview\VTK\Rendering|Volume\vtkGPUVolumeRayCastMap*


Can anyone help me to resolve this issue ?

Thank you.
-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/d7cc73fe/attachment.html>

From mathieu.westphal at kitware.com  Fri May  6 07:27:45 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 6 May 2016 13:27:45 +0200
Subject: [Paraview] ParaView : resolve the error message.
In-Reply-To: <CAJFKOL2PdDuk3Ormf+EkuRW2ZnexNb1ZiqWCLv7yzoxDhQdQvQ@mail.gmail.com>
References: <CAJFKOL2PdDuk3Ormf+EkuRW2ZnexNb1ZiqWCLv7yzoxDhQdQvQ@mail.gmail.com>
Message-ID: <CAC2t4UTd7Lk_tgNDHYUm_14ZTw-AQCsmMQrL7MWUdP+j2hobfg@mail.gmail.com>

Hello

This is actually a truncated error message, could you check the "Console
View" checkbox in the error message dialog to get a more informative
message ?


Mathieu Westphal

On Fri, May 6, 2016 at 1:20 PM, Chathuri Gunasekera <cgunases at gmail.com>
wrote:

> Hello,
>
> I have installed Paraview 5.0 on my machine(Windows 8.1). When i try to
> visualize a 3D model in vtk format, i am getting an error.
>
> I have no idea why i get the following error? What does it depicts?
>
> *error:In C:\bbd\df0abce0\build\src\paraview\VTK\Rendering|Volume\vtkGPUVolumeRayCastMap*
>
>
> Can anyone help me to resolve this issue ?
>
> Thank you.
> --
> Warm regards,
> Chathuri Gunasekera.
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/cad2f25d/attachment.html>

From jiri.vyskocil at fjfi.cvut.cz  Fri May  6 07:47:26 2016
From: jiri.vyskocil at fjfi.cvut.cz (=?UTF-8?B?SmnFmcOtIFZ5c2tvxI1pbA==?=)
Date: Fri, 6 May 2016 13:47:26 +0200
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
 <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
Message-ID: <83d35a36-b3f6-e4f7-4ed9-f2f66e10dddf@fjfi.cvut.cz>

One more step closer to the goal it seems - if run:


export XAUTHORITY=/var/run/slim/slim.auth
DISPLAY=:0 xhost +


as root, I can get the launcher to start, and not die with an X-related error (cumbersome 
workaround, but I guess I can find a better way later).


[paraview at vbl-sim ~] $ cat /etc/httpd/paraview-mapping/proxy.txt
be12802a-137f-11e6-b12c-002590e6af35 vbl-sim.eli-beams.eu:9003

[paraview at vbl-sim ~] $ ps aux | grep pvpython
paraview  1792  1.2  0.1 1393740 144956 pts/1  S+   13:42   0:02 
/usr/local/lib/paraview-5.0/pvpython /usr/local/lib/paraview-5.0/site-packages/vtk/web/launcher.py 
/etc/httpd/paraview-launcher.config -d
paraview  1887  1.6  0.1 1519164 237520 pts/1  Sl+  13:43   0:02 
/usr/local/lib/paraview-5.0/pvpython -dr 
/usr/local/lib/paraview-5.0/site-packages/paraview/web/pv_web_visualizer.py --port 9003 --data-dir 
/var/paraview/data -f --authKey 3ZXwyWwTz7aPjT9p


Now when I try to open an app from the browser, it still doesn't work (waits forever to load some 
part, etc.), and I see thist in the paraview log:


[strazce at vbl-sim ~] $ cat /var/log/paraview-viz-logs/be12802a-137f-11e6-b12c-002590e6af35.txt
2016-05-06 13:43:27+0200 [-] Log opened.
2016-05-06 13:43:27+0200 [-] Site starting on 9003
2016-05-06 13:43:27+0200 [-] Starting factory <twisted.web.server.Site instance at 0x7fd34014f3b0>
2016-05-06 13:43:27+0200 [-] 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2016-05-06 13:43:27+0200 [-] 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


and a lot of lines which contain just the repeating plus signs.







On 05/05/16 16:23, Sebastien Jourdain wrote:
> You were on the right track with DISPLAY=:0 but I'm wondering if you setup a "virtual" monitor or 
> if your "paraview" user is auto logged in a X session or if it stuck at the "login" panel?
>
> You can find some information about the virtual screen here: (Search for "Screen")
>
> http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>
> And for the autologin if it is needed. (Note on EC2 the user start X hence no need to login...)
>
> https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>
> Seb
>
> On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz 
> <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>
>     Hello,
>
>
>     I'm trying to set up a Paraview Web server on a Fedora 23 machine. The serves is not connected
>     to a monitor or a keyboard (I only have access through ssh), but it has a nvidia GPU which I
>     want to use for paraview.
>
>
>     I have installed xdm to run the X server, and verified that it is in fact running with the
>     correct nvidia drivers (by checking the Xorg.0.log file). The problem is I don't know how to
>     run the paraview webserver on the X display when there's no one physically logged in - I can
>     only get to the server via ssh. When I log in, and switch to the paraview user, the DISPLAY
>     and XAUTHORITY variables are empty.
>
>
>     The webserver itself is running (apache + the python launcher), but when I try to open any of
>     the example applications, I get an error like this:
>
>
>     $ ./launch-paraview.sh
>     2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>     2016-05-05 14:54:17,528:INFO:twisted:Starting factory <twisted.web.server.Site instance at
>     0x7fe20da6a998>
>     2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09 +0000] "POST
>     /paraview/ HTTP/1.1" 503 78 "https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11;
>     Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>
>
>     $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>     2016-05-05 14:55:06+0200 [-] Log opened.
>     ERROR: In
>     /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333
>     vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>
>
>     Specifying DISPLAY=:0 when running the launcher gives this error:
>
>     $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>     2016-05-05 14:57:22+0200 [-] Log opened.
>     No protocol specified
>     No protocol specified
>     No protocol specified
>     ERROR: In
>     /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333
>     vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0. Aborting.
>
>
>
>     Thanks for any hints,
>
>     Jiri
>
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/00c36cba/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3733 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/00c36cba/attachment.bin>

From info at seoaachen.de  Fri May  6 09:21:17 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Fri, 6 May 2016 15:21:17 +0200
Subject: [Paraview] Plugin Compatibility (Medreader)
In-Reply-To: <CAC2t4US9-Cd4cbnqYG4nBD3TpHi3da+apxS5KxrZzG-8xVO3Vg@mail.gmail.com>
References: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>
 <CAC2t4US9-Cd4cbnqYG4nBD3TpHi3da+apxS5KxrZzG-8xVO3Vg@mail.gmail.com>
Message-ID: <19796c35-2847-b3d9-f490-8f1aedb0e05c@seoaachen.de>

They bundled the MedReader Plugin from Salome with PV 3.14:
http://www.alneos.com/en/downloads/paraview-with-med

I want to use it with a newer version of PV. Salome 7.7.1 has PV 4.3.1 
but I don't know how I can bundle the Plugins with PV.

Am 06.05.2016 um 12:58 schrieb Mathieu Westphal:
> Hello
>
> As far as I know, there is no officially supported MEDReader plugin 
> for paraview.
> There is a working one, part of the Salome project.
> Other versions can be found on the internet.
>
> Which plugin are you referring to ? Can you provide a upstream link ?
>
> Regards,
>
> Mathieu Westphal
>
> On Fri, May 6, 2016 at 12:45 PM, Daniel Zuidinga <info at seoaachen.de 
> <mailto:info at seoaachen.de>> wrote:
>
>     Hi,
>
>     I try to use a Paraview Plugin (Medreader) which works in PV3.14
>     in PV 4.1.3. Does this work in general? When loading the dll file
>     I get the error:
>
>     ERROR: In
>     C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx,
>     line 360
>
>     vtkPVPluginLoader (0AF78238): D
>
>
>     regards
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/1f0096ae/attachment.html>

From mathieu.westphal at kitware.com  Fri May  6 09:47:00 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 6 May 2016 15:47:00 +0200
Subject: [Paraview] Plugin Compatibility (Medreader)
In-Reply-To: <19796c35-2847-b3d9-f490-8f1aedb0e05c@seoaachen.de>
References: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>
 <CAC2t4US9-Cd4cbnqYG4nBD3TpHi3da+apxS5KxrZzG-8xVO3Vg@mail.gmail.com>
 <19796c35-2847-b3d9-f490-8f1aedb0e05c@seoaachen.de>
Message-ID: <CAC2t4UTcq2yG09eqwGK8Zf2Rq1N5OXXWPRi_G8GGZp6e4uLxzw@mail.gmail.com>

Hello

Sadly this plugin is out dated, and is made to work with paraview 3.14
There is no reason for it to work with any newer version of paraview, bth
VTK and ParaView have changed a lot since.
Also, as far as i see, the plugin distributed on alneos website is binary
only, so it can only be used with the correct binary version of paraview,
since you can't recompile it.

No solution for you, unless you want to try and extract the MEDReader
plugin from the current salome (
http://salome-platform.org/downloads/current-version),
And compile everything.
You can use this tutorial to help you, using the version of salome that
fits your need, but i can't give you assurance that it will work, I tried
it myself but quickly run into issues.
Good luck, and in case you want support, don't hesitate to ask kitware
commercial team.

Regards,

Mathieu Westphal

On Fri, May 6, 2016 at 3:21 PM, Daniel Zuidinga <info at seoaachen.de> wrote:

> They bundled the MedReader Plugin from Salome with PV 3.14:
> http://www.alneos.com/en/downloads/paraview-with-med
>
> I want to use it with a newer version of PV. Salome 7.7.1 has PV 4.3.1 but
> I don't know how I can bundle the Plugins with PV.
>
> Am 06.05.2016 um 12:58 schrieb Mathieu Westphal:
>
> Hello
>
> As far as I know, there is no officially supported MEDReader plugin for
> paraview.
> There is a working one, part of the Salome project.
> Other versions can be found on the internet.
>
> Which plugin are you referring to ? Can you provide a upstream link ?
>
> Regards,
>
> Mathieu Westphal
>
> On Fri, May 6, 2016 at 12:45 PM, Daniel Zuidinga <info at seoaachen.de>
> wrote:
>
>> Hi,
>>
>> I try to use a Paraview Plugin (Medreader) which works in PV3.14 in PV
>> 4.1.3. Does this work in general? When loading the dll file I get the error:
>> ERROR: In
>> C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx,
>> line 360
>>
>> vtkPVPluginLoader (0AF78238): D
>>
>>
>> regards
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> 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
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/dcf2d350/attachment.html>

From mathieu.westphal at kitware.com  Fri May  6 09:47:28 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 6 May 2016 15:47:28 +0200
Subject: [Paraview] Plugin Compatibility (Medreader)
In-Reply-To: <CAC2t4UTcq2yG09eqwGK8Zf2Rq1N5OXXWPRi_G8GGZp6e4uLxzw@mail.gmail.com>
References: <ca5eb1f5-8bb2-a91f-3d60-6fbbb55d8cdd@seoaachen.de>
 <CAC2t4US9-Cd4cbnqYG4nBD3TpHi3da+apxS5KxrZzG-8xVO3Vg@mail.gmail.com>
 <19796c35-2847-b3d9-f490-8f1aedb0e05c@seoaachen.de>
 <CAC2t4UTcq2yG09eqwGK8Zf2Rq1N5OXXWPRi_G8GGZp6e4uLxzw@mail.gmail.com>
Message-ID: <CAC2t4USGViJq4kCFYmbTq9f2=ypf-hKcSvxiJsw90St=-JYKog@mail.gmail.com>

Miss the link to the tutorial : http://www.ogoethel.de/?e=12

Mathieu Westphal

On Fri, May 6, 2016 at 3:47 PM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> Hello
>
> Sadly this plugin is out dated, and is made to work with paraview 3.14
> There is no reason for it to work with any newer version of paraview, bth
> VTK and ParaView have changed a lot since.
> Also, as far as i see, the plugin distributed on alneos website is binary
> only, so it can only be used with the correct binary version of paraview,
> since you can't recompile it.
>
> No solution for you, unless you want to try and extract the MEDReader
> plugin from the current salome (
> http://salome-platform.org/downloads/current-version),
> And compile everything.
> You can use this tutorial to help you, using the version of salome that
> fits your need, but i can't give you assurance that it will work, I tried
> it myself but quickly run into issues.
> Good luck, and in case you want support, don't hesitate to ask kitware
> commercial team.
>
> Regards,
>
> Mathieu Westphal
>
> On Fri, May 6, 2016 at 3:21 PM, Daniel Zuidinga <info at seoaachen.de> wrote:
>
>> They bundled the MedReader Plugin from Salome with PV 3.14:
>> http://www.alneos.com/en/downloads/paraview-with-med
>>
>> I want to use it with a newer version of PV. Salome 7.7.1 has PV 4.3.1
>> but I don't know how I can bundle the Plugins with PV.
>>
>> Am 06.05.2016 um 12:58 schrieb Mathieu Westphal:
>>
>> Hello
>>
>> As far as I know, there is no officially supported MEDReader plugin for
>> paraview.
>> There is a working one, part of the Salome project.
>> Other versions can be found on the internet.
>>
>> Which plugin are you referring to ? Can you provide a upstream link ?
>>
>> Regards,
>>
>> Mathieu Westphal
>>
>> On Fri, May 6, 2016 at 12:45 PM, Daniel Zuidinga <info at seoaachen.de>
>> wrote:
>>
>>> Hi,
>>>
>>> I try to use a Paraview Plugin (Medreader) which works in PV3.14 in PV
>>> 4.1.3. Does this work in general? When loading the dll file I get the error:
>>> ERROR: In
>>> C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx,
>>> line 360
>>>
>>> vtkPVPluginLoader (0AF78238): D
>>>
>>>
>>> regards
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> 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
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/6980d9c4/attachment.html>

From sebastien.jourdain at kitware.com  Fri May  6 10:54:16 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 6 May 2016 08:54:16 -0600
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <83d35a36-b3f6-e4f7-4ed9-f2f66e10dddf@fjfi.cvut.cz>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
 <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
 <83d35a36-b3f6-e4f7-4ed9-f2f66e10dddf@fjfi.cvut.cz>
Message-ID: <CABObKxeTmnhJ4Mz72F7SB2OXBr-K=++1BYQmhSF6mjS38yHdww@mail.gmail.com>

You are getting really close...

Basically you have the ParaView process that properly started at the
request of the client and waits to it to connect, which never happen.

Usually that mean, you have a mistake either in your Apache config and/or
in your launcher.

Could you share your Apache virtual host with your launcher config along
with the URL the web client connects to?

Seb

On Fri, May 6, 2016 at 5:47 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz>
wrote:

> One more step closer to the goal it seems - if run:
>
>
> export XAUTHORITY=/var/run/slim/slim.auth
> DISPLAY=:0 xhost +
>
>
> as root, I can get the launcher to start, and not die with an X-related
> error (cumbersome workaround, but I guess I can find a better way later).
>
>
> [paraview at vbl-sim ~] $ cat /etc/httpd/paraview-mapping/proxy.txt
> be12802a-137f-11e6-b12c-002590e6af35 vbl-sim.eli-beams.eu:9003
>
> [paraview at vbl-sim ~] $ ps aux | grep pvpython
> paraview  1792  1.2  0.1 1393740 144956 pts/1  S+   13:42   0:02
> /usr/local/lib/paraview-5.0/pvpython
> /usr/local/lib/paraview-5.0/site-packages/vtk/web/launcher.py
> /etc/httpd/paraview-launcher.config -d
> paraview  1887  1.6  0.1 1519164 237520 pts/1  Sl+  13:43   0:02
> /usr/local/lib/paraview-5.0/pvpython -dr
> /usr/local/lib/paraview-5.0/site-packages/paraview/web/pv_web_visualizer.py
> --port 9003 --data-dir /var/paraview/data -f --authKey 3ZXwyWwTz7aPjT9p
>
>
> Now when I try to open an app from the browser, it still doesn't work
> (waits forever to load some part, etc.), and I see thist in the paraview
> log:
>
>
> [strazce at vbl-sim ~] $ cat
> /var/log/paraview-viz-logs/be12802a-137f-11e6-b12c-002590e6af35.txt
> 2016-05-06 13:43:27+0200 [-] Log opened.
> 2016-05-06 13:43:27+0200 [-] Site starting on 9003
> 2016-05-06 13:43:27+0200 [-] Starting factory <twisted.web.server.Site
> instance at 0x7fd34014f3b0>
> 2016-05-06 13:43:27+0200 [-]
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2016-05-06 13:43:27+0200 [-]
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> and a lot of lines which contain just the repeating plus signs.
>
>
>
>
>
>
>
> On 05/05/16 16:23, Sebastien Jourdain wrote:
>
> You were on the right track with DISPLAY=:0 but I'm wondering if you setup
> a "virtual" monitor or if your "paraview" user is auto logged in a X
> session or if it stuck at the "login" panel?
>
> You can find some information about the virtual screen here: (Search for
> "Screen")
>
> http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>
> And for the autologin if it is needed. (Note on EC2 the user start X hence
> no need to login...)
>
>
> https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>
> Seb
>
> On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz>
> wrote:
>
>> Hello,
>>
>>
>> I'm trying to set up a Paraview Web server on a Fedora 23 machine. The
>> serves is not connected to a monitor or a keyboard (I only have access
>> through ssh), but it has a nvidia GPU which I want to use for paraview.
>>
>>
>> I have installed xdm to run the X server, and verified that it is in fact
>> running with the correct nvidia drivers (by checking the Xorg.0.log file).
>> The problem is I don't know how to run the paraview webserver on the X
>> display when there's no one physically logged in - I can only get to the
>> server via ssh. When I log in, and switch to the paraview user, the DISPLAY
>> and XAUTHORITY variables are empty.
>>
>>
>> The webserver itself is running (apache + the python launcher), but when
>> I try to open any of the example applications, I get an error like this:
>>
>>
>> $ ./launch-paraview.sh
>> 2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>> 2016-05-05 14:54:17,528:INFO:twisted:Starting factory
>> <twisted.web.server.Site instance at 0x7fe20da6a998>
>> 2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - -
>> [05/May/2016:12:55:09 +0000] "POST /paraview/ HTTP/1.1" 503 78 "
>> https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11;
>> Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>>
>>
>> $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>> 2016-05-05 14:55:06+0200 [-] Log opened.
>> ERROR: In
>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>> line 333
>> vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>>
>>
>> Specifying DISPLAY=:0 when running the launcher gives this error:
>>
>> $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>> 2016-05-05 14:57:22+0200 [-] Log opened.
>> No protocol specified
>> No protocol specified
>> No protocol specified
>> ERROR: In
>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>> line 333
>> vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0.
>> Aborting.
>>
>>
>>
>> Thanks for any hints,
>>
>> Jiri
>>
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> 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
>>
>>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/52d0af96/attachment.html>

From jiri.vyskocil at fjfi.cvut.cz  Fri May  6 11:49:30 2016
From: jiri.vyskocil at fjfi.cvut.cz (=?UTF-8?B?SmnFmcOtIFZ5c2tvxI1pbA==?=)
Date: Fri, 6 May 2016 17:49:30 +0200
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <CABObKxeTmnhJ4Mz72F7SB2OXBr-K=++1BYQmhSF6mjS38yHdww@mail.gmail.com>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
 <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
 <83d35a36-b3f6-e4f7-4ed9-f2f66e10dddf@fjfi.cvut.cz>
 <CABObKxeTmnhJ4Mz72F7SB2OXBr-K=++1BYQmhSF6mjS38yHdww@mail.gmail.com>
Message-ID: <9c7918cc-8bfe-a643-2c62-1ebdf0933cea@fjfi.cvut.cz>

Ha! I got it - I had apache configured as SSL-only. That is: http at port 80 was hard redirected to 
https at port 443. I changed the config to only use http, and now it works. For now that's not 
critical -  this is an experimental server accessible only from our internal network, I can try to 
fix this later.

Now I'll start playing with the visualizer app. So far it seems to work pretty well - I just need to 
make it use all available resources (it just runs sigle-core).


Thank you for your help, Sebastien!



For the record, this was the apache config that didn't work:

NameVirtualHost *:80
<VirtualHost *:80>
     ServerName vbl-sim.eli-beams.eu
     Redirect permanent / https://vbl-sim.eli-beams.eu/
</VirtualHost>

NameVirtualHost *:443
<VirtualHost *:443>
ServerName vbl-sim.eli-beams.eu
ServerAdmin jiri.vyskocil at eli-beams.eu
DocumentRoot /usr/local/share/paraview-5.0/www/

ErrorLog "logs/pv-error_log"
CustomLog "logs/pv-access_log" common

  <Location /usr/local/share/paraview-5.0/www/>
    SSLRequireSSL On
    SSLVerifyClient optional
    SSLVerifyDepth 1
    SSLOptions +StdEnvVars +StrictRequire
  </Location>

ProxyPass /paraview http://localhost:9000/paraview
RewriteEngine On
RewriteMap session-to-port txt:/etc/httpd/paraview-mapping/proxy.txt
RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]

SSLEngine on
SSLCertificateFile /etc/pki/tls/certs/vblpar.crt
SSLCertificateKeyFile /etc/pki/tls/private/vblpar.key

     <Directory /usr/local/share/paraview-5.0/www/>
         Options Indexes FollowSymLinks
         Order allow,deny
         Allow from all
         AllowOverride None
         Require all granted
     </Directory>

</VirtualHost>





On 06/05/16 16:54, Sebastien Jourdain wrote:
> You are getting really close...
>
> Basically you have the ParaView process that properly started at the request of the client and 
> waits to it to connect, which never happen.
>
> Usually that mean, you have a mistake either in your Apache config and/or in your launcher.
>
> Could you share your Apache virtual host with your launcher config along with the URL the web 
> client connects to?
>
> Seb
>
> On Fri, May 6, 2016 at 5:47 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz 
> <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>
>     One more step closer to the goal it seems - if run:
>
>
>     export XAUTHORITY=/var/run/slim/slim.auth
>     DISPLAY=:0 xhost +
>
>
>     as root, I can get the launcher to start, and not die with an X-related error (cumbersome
>     workaround, but I guess I can find a better way later).
>
>
>     [paraview at vbl-sim ~] $ cat /etc/httpd/paraview-mapping/proxy.txt
>     be12802a-137f-11e6-b12c-002590e6af35 vbl-sim.eli-beams.eu:9003 <http://vbl-sim.eli-beams.eu:9003>
>
>     [paraview at vbl-sim ~] $ ps aux | grep pvpython
>     paraview  1792  1.2  0.1 1393740 144956 pts/1  S+ 13:42   0:02
>     /usr/local/lib/paraview-5.0/pvpython
>     /usr/local/lib/paraview-5.0/site-packages/vtk/web/launcher.py
>     /etc/httpd/paraview-launcher.config -d
>     paraview  1887  1.6  0.1 1519164 237520 pts/1  Sl+ 13:43   0:02
>     /usr/local/lib/paraview-5.0/pvpython -dr
>     /usr/local/lib/paraview-5.0/site-packages/paraview/web/pv_web_visualizer.py --port 9003
>     --data-dir /var/paraview/data -f --authKey 3ZXwyWwTz7aPjT9p
>
>
>     Now when I try to open an app from the browser, it still doesn't work (waits forever to load
>     some part, etc.), and I see thist in the paraview log:
>
>
>     [strazce at vbl-sim ~] $ cat /var/log/paraview-viz-logs/be12802a-137f-11e6-b12c-002590e6af35.txt
>     2016-05-06 13:43:27+0200 [-] Log opened.
>     2016-05-06 13:43:27+0200 [-] Site starting on 9003
>     2016-05-06 13:43:27+0200 [-] Starting factory <twisted.web.server.Site instance at 0x7fd34014f3b0>
>     2016-05-06 13:43:27+0200 [-]
>     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>     2016-05-06 13:43:27+0200 [-]
>     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>     and a lot of lines which contain just the repeating plus signs.
>
>
>
>
>
>
>
>     On 05/05/16 16:23, Sebastien Jourdain wrote:
>>     You were on the right track with DISPLAY=:0 but I'm wondering if you setup a "virtual"
>>     monitor or if your "paraview" user is auto logged in a X session or if it stuck at the
>>     "login" panel?
>>
>>     You can find some information about the virtual screen here: (Search for "Screen")
>>
>>     http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>>
>>     And for the autologin if it is needed. (Note on EC2 the user start X hence no need to login...)
>>
>>     https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>>
>>     Seb
>>
>>     On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz
>>     <mailto:jiri.vyskocil at fjfi.cvut.cz>> wrote:
>>
>>         Hello,
>>
>>
>>         I'm trying to set up a Paraview Web server on a Fedora 23 machine. The serves is not
>>         connected to a monitor or a keyboard (I only have access through ssh), but it has a
>>         nvidia GPU which I want to use for paraview.
>>
>>
>>         I have installed xdm to run the X server, and verified that it is in fact running with
>>         the correct nvidia drivers (by checking the Xorg.0.log file). The problem is I don't know
>>         how to run the paraview webserver on the X display when there's no one physically logged
>>         in - I can only get to the server via ssh. When I log in, and switch to the paraview
>>         user, the DISPLAY and XAUTHORITY variables are empty.
>>
>>
>>         The webserver itself is running (apache + the python launcher), but when I try to open
>>         any of the example applications, I get an error like this:
>>
>>
>>         $ ./launch-paraview.sh
>>         2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>>         2016-05-05 14:54:17,528:INFO:twisted:Starting factory <twisted.web.server.Site instance
>>         at 0x7fe20da6a998>
>>         2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - - [05/May/2016:12:55:09 +0000] "POST
>>         /paraview/ HTTP/1.1" 503 78 "https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0
>>         (X11; Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>>
>>
>>         $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>>         2016-05-05 14:55:06+0200 [-] Log opened.
>>         ERROR: In
>>         /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>>         line 333
>>         vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>>
>>
>>         Specifying DISPLAY=:0 when running the launcher gives this error:
>>
>>         $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>>         2016-05-05 14:57:22+0200 [-] Log opened.
>>         No protocol specified
>>         No protocol specified
>>         No protocol specified
>>         ERROR: In
>>         /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>>         line 333
>>         vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0. Aborting.
>>
>>
>>
>>         Thanks for any hints,
>>
>>         Jiri
>>
>>
>>
>>
>>         _______________________________________________
>>         Powered by www.kitware.com <http://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
>>
>>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/4b7cabf2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3733 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/4b7cabf2/attachment.bin>

From cgunases at gmail.com  Fri May  6 12:38:30 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Fri, 6 May 2016 22:08:30 +0530
Subject: [Paraview] ParaView : resolve the error message.
In-Reply-To: <CAC2t4UTd7Lk_tgNDHYUm_14ZTw-AQCsmMQrL7MWUdP+j2hobfg@mail.gmail.com>
References: <CAJFKOL2PdDuk3Ormf+EkuRW2ZnexNb1ZiqWCLv7yzoxDhQdQvQ@mail.gmail.com>
 <CAC2t4UTd7Lk_tgNDHYUm_14ZTw-AQCsmMQrL7MWUdP+j2hobfg@mail.gmail.com>
Message-ID: <CAJFKOL0DVKPKkpSy9Pom5KAFGdha_2rG6kQC6B_g9bxNjWG8sQ@mail.gmail.com>

Hello,
Thank you so much for your response, Mathieu.

 Here is what i am getting when i check the 'console view' option.

ERROR: In
C:\bbd\df0abce0\build\paraview\src\paraview\VTK\Rendering\Volume\vtkGPUVolumeRayCastMapper.cxx,
line 340

vtkOpenGLGPUVolumeRayCastMapper (000000D7783182B0): scalar of type VTK_CHAR
is not supported because this type is platform dependent. Use
VTK_SIGNED_CHAR or VTK_UNSIGNED_CHAR instead.



 Do you see why i am getting this error exactly?


Actually the files were orginally created as .Mat file then they are
converted to VTK format. But how can i convert to VTK_SIGNED_CHAR or
VTK_UNSIGNED_CHAR ? I am sorry i simply don't know how to do it. Any
guidance is really appreciated.


-- 
Warm regards,
Chathuri Gunasekera.


On Fri, May 6, 2016 at 4:57 PM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> Hello
>
> This is actually a truncated error message, could you check the "Console
> View" checkbox in the error message dialog to get a more informative
> message ?
>
>
> Mathieu Westphal
>
> On Fri, May 6, 2016 at 1:20 PM, Chathuri Gunasekera <cgunases at gmail.com>
> wrote:
>
>> Hello,
>>
>> I have installed Paraview 5.0 on my machine(Windows 8.1). When i try to
>> visualize a 3D model in vtk format, i am getting an error.
>>
>> I have no idea why i get the following error? What does it depicts?
>>
>> *error:In C:\bbd\df0abce0\build\src\paraview\VTK\Rendering|Volume\vtkGPUVolumeRayCastMap*
>>
>>
>> Can anyone help me to resolve this issue ?
>>
>> Thank you.
>> --
>> Warm regards,
>> Chathuri Gunasekera.
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/e3be1651/attachment.html>

From mathieu.westphal at kitware.com  Fri May  6 12:42:24 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 6 May 2016 18:42:24 +0200
Subject: [Paraview] ParaView : resolve the error message.
In-Reply-To: <CAJFKOL0DVKPKkpSy9Pom5KAFGdha_2rG6kQC6B_g9bxNjWG8sQ@mail.gmail.com>
References: <CAJFKOL2PdDuk3Ormf+EkuRW2ZnexNb1ZiqWCLv7yzoxDhQdQvQ@mail.gmail.com>
 <CAC2t4UTd7Lk_tgNDHYUm_14ZTw-AQCsmMQrL7MWUdP+j2hobfg@mail.gmail.com>
 <CAJFKOL0DVKPKkpSy9Pom5KAFGdha_2rG6kQC6B_g9bxNjWG8sQ@mail.gmail.com>
Message-ID: <CAC2t4UQOs_qk35RDTqpRd1gQT0o+ei_KhrHkT1XqP8kXnzjj0A@mail.gmail.com>

Looks like your try to visualize your data which is of VTK_CHAR format,
which is unsupported.
I can't tell much more without the actual data.

Mathieu Westphal

On Fri, May 6, 2016 at 6:38 PM, Chathuri Gunasekera <cgunases at gmail.com>
wrote:

> Hello,
> Thank you so much for your response, Mathieu.
>
>  Here is what i am getting when i check the 'console view' option.
>
> ERROR: In
> C:\bbd\df0abce0\build\paraview\src\paraview\VTK\Rendering\Volume\vtkGPUVolumeRayCastMapper.cxx,
> line 340
>
> vtkOpenGLGPUVolumeRayCastMapper (000000D7783182B0): scalar of type
> VTK_CHAR is not supported because this type is platform dependent. Use
> VTK_SIGNED_CHAR or VTK_UNSIGNED_CHAR instead.
>
>
>
>  Do you see why i am getting this error exactly?
>
>
> Actually the files were orginally created as .Mat file then they are
> converted to VTK format. But how can i convert to VTK_SIGNED_CHAR or
> VTK_UNSIGNED_CHAR ? I am sorry i simply don't know how to do it. Any
> guidance is really appreciated.
>
>
> --
> Warm regards,
> Chathuri Gunasekera.
>
>
> On Fri, May 6, 2016 at 4:57 PM, Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
>> Hello
>>
>> This is actually a truncated error message, could you check the "Console
>> View" checkbox in the error message dialog to get a more informative
>> message ?
>>
>>
>> Mathieu Westphal
>>
>> On Fri, May 6, 2016 at 1:20 PM, Chathuri Gunasekera <cgunases at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I have installed Paraview 5.0 on my machine(Windows 8.1). When i try to
>>> visualize a 3D model in vtk format, i am getting an error.
>>>
>>> I have no idea why i get the following error? What does it depicts?
>>>
>>> *error:In C:\bbd\df0abce0\build\src\paraview\VTK\Rendering|Volume\vtkGPUVolumeRayCastMap*
>>>
>>>
>>> Can anyone help me to resolve this issue ?
>>>
>>> Thank you.
>>> --
>>> Warm regards,
>>> Chathuri Gunasekera.
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/3fec4466/attachment.html>

From svenkramer40 at gmail.com  Fri May  6 16:17:38 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Fri, 6 May 2016 22:17:38 +0200
Subject: [Paraview] ParaviewWeb with remote, distributed data
Message-ID: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>

Dear all,
I am currently running a VTK application, which is visualizing large grids
distributed on a MPI cluster.
My task is to migrate this application to the Web. But I cannot manage more
than what is described at
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
that is I can serve a local data directory through the provided webapps.

I have two essential questions that stop me from getting started:
1) How do I connect the pvpython server to remote data/render servers just
like I can do in Paraview?
2) All ParaviewWeb examples seem to react on webclient requests. Our
application is processing data as they come in, and also the visualization
pipeline is frequently updated depending on an automatic analysis of the
arriving data. Can the newly rendered datasets be pushed to the webclient,
or does the webclient have to poll for available datasets?

Thank you
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/c13bef41/attachment.html>

From sebastien.jourdain at kitware.com  Fri May  6 16:21:12 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 6 May 2016 14:21:12 -0600
Subject: [Paraview] Setting up Paraview Web on a headless Fedora server
 with GPU
In-Reply-To: <9c7918cc-8bfe-a643-2c62-1ebdf0933cea@fjfi.cvut.cz>
References: <507a18c0-3bac-fae8-da55-c5ea33e8e1d0@fjfi.cvut.cz>
 <CABObKxefXtqmpADYSvv1un3Q-i7Ri5kFgqYDdMfV3Dgr=12cow@mail.gmail.com>
 <83d35a36-b3f6-e4f7-4ed9-f2f66e10dddf@fjfi.cvut.cz>
 <CABObKxeTmnhJ4Mz72F7SB2OXBr-K=++1BYQmhSF6mjS38yHdww@mail.gmail.com>
 <9c7918cc-8bfe-a643-2c62-1ebdf0933cea@fjfi.cvut.cz>
Message-ID: <CABObKxdhgX7ue3oxP+HKhZkmy5Z6beKcQG=LR8J4CJ62SF6wOQ@mail.gmail.com>

Glad to hear you figure it out.

You can setup Apache to use https/wss and just redirect to ws:// internally.

Usually one core is enough especially if you have ParaView build with some
SMP/tbb. MPI will introduce some overhead. Unless you need many machine for
your model to fit in memory.

If you need to interface a cluster, you also can to that with some
mpi-pvserver connecting back to your pvpython client.
But that will be probably another thread. ;-)

Enjoy,

Seb



On Fri, May 6, 2016 at 9:49 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz>
wrote:

> Ha! I got it - I had apache configured as SSL-only. That is: http at port
> 80 was hard redirected to https at port 443. I changed the config to only
> use http, and now it works. For now that's not critical -  this is an
> experimental server accessible only from our internal network, I can try to
> fix this later.
>
> Now I'll start playing with the visualizer app. So far it seems to work
> pretty well - I just need to make it use all available resources (it just
> runs sigle-core).
>
>
> Thank you for your help, Sebastien!
>
>
>
> For the record, this was the apache config that didn't work:
>
> NameVirtualHost *:80
> <VirtualHost *:80>
>     ServerName vbl-sim.eli-beams.eu
>     Redirect permanent / https://vbl-sim.eli-beams.eu/
> </VirtualHost>
>
> NameVirtualHost *:443
> <VirtualHost *:443>
> ServerName vbl-sim.eli-beams.eu
> ServerAdmin jiri.vyskocil at eli-beams.eu
> DocumentRoot /usr/local/share/paraview-5.0/www/
>
> ErrorLog "logs/pv-error_log"
> CustomLog "logs/pv-access_log" common
>
>  <Location /usr/local/share/paraview-5.0/www/>
>    SSLRequireSSL On
>    SSLVerifyClient optional
>    SSLVerifyDepth 1
>    SSLOptions +StdEnvVars +StrictRequire
>  </Location>
>
> ProxyPass /paraview http://localhost:9000/paraview
> RewriteEngine On
> RewriteMap session-to-port txt:/etc/httpd/paraview-mapping/proxy.txt
> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
> SSLEngine on
> SSLCertificateFile /etc/pki/tls/certs/vblpar.crt
> SSLCertificateKeyFile /etc/pki/tls/private/vblpar.key
>
>     <Directory /usr/local/share/paraview-5.0/www/>
>         Options Indexes FollowSymLinks
>         Order allow,deny
>         Allow from all
>         AllowOverride None
>         Require all granted
>     </Directory>
>
> </VirtualHost>
>
>
>
>
>
> On 06/05/16 16:54, Sebastien Jourdain wrote:
>
> You are getting really close...
>
> Basically you have the ParaView process that properly started at the
> request of the client and waits to it to connect, which never happen.
>
> Usually that mean, you have a mistake either in your Apache config and/or
> in your launcher.
>
> Could you share your Apache virtual host with your launcher config along
> with the URL the web client connects to?
>
> Seb
>
> On Fri, May 6, 2016 at 5:47 AM, Ji?? Vysko?il <jiri.vyskocil at fjfi.cvut.cz>
> wrote:
>
>> One more step closer to the goal it seems - if run:
>>
>>
>> export XAUTHORITY=/var/run/slim/slim.auth
>> DISPLAY=:0 xhost +
>>
>>
>> as root, I can get the launcher to start, and not die with an X-related
>> error (cumbersome workaround, but I guess I can find a better way later).
>>
>>
>> [paraview at vbl-sim ~] $ cat /etc/httpd/paraview-mapping/proxy.txt
>> be12802a-137f-11e6-b12c-002590e6af35 vbl-sim.eli-beams.eu:9003
>>
>> [paraview at vbl-sim ~] $ ps aux | grep pvpython
>> paraview  1792  1.2  0.1 1393740 144956 pts/1  S+   13:42   0:02
>> /usr/local/lib/paraview-5.0/pvpython
>> /usr/local/lib/paraview-5.0/site-packages/vtk/web/launcher.py
>> /etc/httpd/paraview-launcher.config -d
>> paraview  1887  1.6  0.1 1519164 237520 pts/1  Sl+  13:43   0:02
>> /usr/local/lib/paraview-5.0/pvpython -dr
>> /usr/local/lib/paraview-5.0/site-packages/paraview/web/pv_web_visualizer.py
>> --port 9003 --data-dir /var/paraview/data -f --authKey 3ZXwyWwTz7aPjT9p
>>
>>
>> Now when I try to open an app from the browser, it still doesn't work
>> (waits forever to load some part, etc.), and I see thist in the paraview
>> log:
>>
>>
>> [strazce at vbl-sim ~] $ cat
>> /var/log/paraview-viz-logs/be12802a-137f-11e6-b12c-002590e6af35.txt
>> 2016-05-06 13:43:27+0200 [-] Log opened.
>> 2016-05-06 13:43:27+0200 [-] Site starting on 9003
>> 2016-05-06 13:43:27+0200 [-] Starting factory <twisted.web.server.Site
>> instance at 0x7fd34014f3b0>
>> 2016-05-06 13:43:27+0200 [-]
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 2016-05-06 13:43:27+0200 [-]
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>> and a lot of lines which contain just the repeating plus signs.
>>
>>
>>
>>
>>
>>
>>
>> On 05/05/16 16:23, Sebastien Jourdain wrote:
>>
>> You were on the right track with DISPLAY=:0 but I'm wondering if you
>> setup a "virtual" monitor or if your "paraview" user is auto logged in a X
>> session or if it stuck at the "login" panel?
>>
>> You can find some information about the virtual screen here: (Search for
>> "Screen")
>>
>> http://kitware.github.io/paraviewweb/docs/guides/graphics_on_ec2_g2.html
>>
>> And for the autologin if it is needed. (Note on EC2 the user start X
>> hence no need to login...)
>>
>>
>> https://github.com/Kitware/paraviewweb/blob/master/tools/ansible/roles/paraview/tasks/Ubuntu.yml
>>
>> Seb
>>
>> On Thu, May 5, 2016 at 6:58 AM, Ji?? Vysko?il <
>> <jiri.vyskocil at fjfi.cvut.cz>jiri.vyskocil at fjfi.cvut.cz> wrote:
>>
>>> Hello,
>>>
>>>
>>> I'm trying to set up a Paraview Web server on a Fedora 23 machine. The
>>> serves is not connected to a monitor or a keyboard (I only have access
>>> through ssh), but it has a nvidia GPU which I want to use for paraview.
>>>
>>>
>>> I have installed xdm to run the X server, and verified that it is in
>>> fact running with the correct nvidia drivers (by checking the Xorg.0.log
>>> file). The problem is I don't know how to run the paraview webserver on the
>>> X display when there's no one physically logged in - I can only get to the
>>> server via ssh. When I log in, and switch to the paraview user, the DISPLAY
>>> and XAUTHORITY variables are empty.
>>>
>>>
>>> The webserver itself is running (apache + the python launcher), but when
>>> I try to open any of the example applications, I get an error like this:
>>>
>>>
>>> $ ./launch-paraview.sh
>>> 2016-05-05 14:54:17,528:INFO:twisted:Site starting on 9000
>>> 2016-05-05 14:54:17,528:INFO:twisted:Starting factory
>>> <twisted.web.server.Site instance at 0x7fe20da6a998>
>>> 2016-05-05 14:55:09,655:INFO:twisted:"127.0.0.1" - -
>>> [05/May/2016:12:55:09 +0000] "POST /paraview/ HTTP/1.1" 503 78 "
>>> <https://vbl-sim.eli-beams.eu/apps/Visualizer/>
>>> https://vbl-sim.eli-beams.eu/apps/Visualizer/" "Mozilla/5.0 (X11;
>>> Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
>>>
>>>
>>> $ cat 965318f2-12c0-11e6-a3cb-002590e6af35.txt
>>> 2016-05-05 14:55:06+0200 [-] Log opened.
>>> ERROR: In
>>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>>> line 333
>>> vtkXOpenGLRenderWindow (0x3f00be0): bad X server connection. DISPLAY=
>>>
>>>
>>> Specifying DISPLAY=:0 when running the launcher gives this error:
>>>
>>> $ cat e73921bc-12c0-11e6-b002-002590e6af35.txt
>>> 2016-05-05 14:57:22+0200 [-] Log opened.
>>> No protocol specified
>>> No protocol specified
>>> No protocol specified
>>> ERROR: In
>>> /home/strazce/hax/ParaView-v5.0.0-source/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx,
>>> line 333
>>> vtkXOpenGLRenderWindow (0x4127c10): bad X server connection. DISPLAY=:0.
>>> Aborting.
>>>
>>>
>>>
>>> Thanks for any hints,
>>>
>>> Jiri
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> 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>
>>> http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> 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
>>
>>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/1eaafcbf/attachment.html>

From sebastien.jourdain at kitware.com  Fri May  6 16:26:40 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 6 May 2016 14:26:40 -0600
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
Message-ID: <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>

Hi Sven,

1) Yes, assuming you are using pv_web_visualizer.py you can look here:

https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28

2) The server can push notification to the client. Need to slightly edit
the client and server to match your needs.

Seb


On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Dear all,
> I am currently running a VTK application, which is visualizing large grids
> distributed on a MPI cluster.
> My task is to migrate this application to the Web. But I cannot manage
> more than what is described at
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
> that is I can serve a local data directory through the provided webapps.
>
> I have two essential questions that stop me from getting started:
> 1) How do I connect the pvpython server to remote data/render servers just
> like I can do in Paraview?
> 2) All ParaviewWeb examples seem to react on webclient requests. Our
> application is processing data as they come in, and also the visualization
> pipeline is frequently updated depending on an automatic analysis of the
> arriving data. Can the newly rendered datasets be pushed to the webclient,
> or does the webclient have to poll for available datasets?
>
> Thank you
> Sven
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/23dd143c/attachment.html>

From svenkramer40 at gmail.com  Fri May  6 16:53:40 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Fri, 6 May 2016 22:53:40 +0200
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
 <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
Message-ID: <CAJZHu4RdZBcPMxQp2=Vj6NT3uOdy5RRn+7QRYbbuodESLw7Ezw@mail.gmail.com>

Thank you, Seb, I'll try those settings beginning of next week.

Probably you can also help me with a few points of my huge lack of
understanding ParaviewWeb. Here, http://www.vtk.org/Wiki/ParaViewWeb_Design
a tomcat web server is mentioned to provide the PWService. Where does
pv_web_visualizer.py fit into those design diagrams? Does it replace tomcat
by providing PWService independently?

There are so many outdated ParaviewWeb articles in the Wiki that I find it
extremely difficult to understand the current design. Can't somebody remove
the old articles or clearly mark them as "Applicable only to Paraview
<x.y.z"?
Is http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html the
most recent documentation? Or is it also not valid for Paraview 4.x and 5.x
as ".../Paraview3/..." in the link address suggests?

Thank you
Sven

2016-05-06 22:26 GMT+02:00 Sebastien Jourdain <
sebastien.jourdain at kitware.com>:

> Hi Sven,
>
> 1) Yes, assuming you are using pv_web_visualizer.py you can look here:
>
>
> https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28
>
> 2) The server can push notification to the client. Need to slightly edit
> the client and server to match your needs.
>
> Seb
>
>
> On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Dear all,
>> I am currently running a VTK application, which is visualizing large
>> grids distributed on a MPI cluster.
>> My task is to migrate this application to the Web. But I cannot manage
>> more than what is described at
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
>> that is I can serve a local data directory through the provided webapps.
>>
>> I have two essential questions that stop me from getting started:
>> 1) How do I connect the pvpython server to remote data/render servers
>> just like I can do in Paraview?
>> 2) All ParaviewWeb examples seem to react on webclient requests. Our
>> application is processing data as they come in, and also the visualization
>> pipeline is frequently updated depending on an automatic analysis of the
>> arriving data. Can the newly rendered datasets be pushed to the webclient,
>> or does the webclient have to poll for available datasets?
>>
>> Thank you
>> Sven
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/3cf7e7a7/attachment.html>

From sebastien.jourdain at kitware.com  Fri May  6 17:45:41 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 6 May 2016 15:45:41 -0600
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CAJZHu4RdZBcPMxQp2=Vj6NT3uOdy5RRn+7QRYbbuodESLw7Ezw@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
 <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
 <CAJZHu4RdZBcPMxQp2=Vj6NT3uOdy5RRn+7QRYbbuodESLw7Ezw@mail.gmail.com>
Message-ID: <CABObKxdfmKj+oiGgNpTGssk5mwtWC-LfuVZfTnf10i3F=zwEGQ@mail.gmail.com>

The ParaViewWeb_Design you found is 5 years old but some users are still
using it.
=> The future matching doc would be:
http://kitware.github.io/paraviewweb/docs/guides/architecture.html

The second link should still be somewhat ok until ParaView 5.1 (Valid till
June 2016).

As starting June (~July), the old documentation should disappear and only
the http://kitware.github.io/paraviewweb will be the official one. But as
we are transitioning both documentations are available.


On Fri, May 6, 2016 at 2:53 PM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Thank you, Seb, I'll try those settings beginning of next week.
>
> Probably you can also help me with a few points of my huge lack of
> understanding ParaviewWeb. Here,
> http://www.vtk.org/Wiki/ParaViewWeb_Design a tomcat web server is
> mentioned to provide the PWService. Where does pv_web_visualizer.py fit
> into those design diagrams? Does it replace tomcat by providing PWService
> independently?
>
> There are so many outdated ParaviewWeb articles in the Wiki that I find it
> extremely difficult to understand the current design. Can't somebody remove
> the old articles or clearly mark them as "Applicable only to Paraview
> <x.y.z"?
> Is http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html
> the most recent documentation? Or is it also not valid for Paraview 4.x and
> 5.x as ".../Paraview3/..." in the link address suggests?
>
> Thank you
> Sven
>
> 2016-05-06 22:26 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Hi Sven,
>>
>> 1) Yes, assuming you are using pv_web_visualizer.py you can look here:
>>
>>
>> https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28
>>
>> 2) The server can push notification to the client. Need to slightly edit
>> the client and server to match your needs.
>>
>> Seb
>>
>>
>> On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Dear all,
>>> I am currently running a VTK application, which is visualizing large
>>> grids distributed on a MPI cluster.
>>> My task is to migrate this application to the Web. But I cannot manage
>>> more than what is described at
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
>>> that is I can serve a local data directory through the provided webapps.
>>>
>>> I have two essential questions that stop me from getting started:
>>> 1) How do I connect the pvpython server to remote data/render servers
>>> just like I can do in Paraview?
>>> 2) All ParaviewWeb examples seem to react on webclient requests. Our
>>> application is processing data as they come in, and also the visualization
>>> pipeline is frequently updated depending on an automatic analysis of the
>>> arriving data. Can the newly rendered datasets be pushed to the webclient,
>>> or does the webclient have to poll for available datasets?
>>>
>>> Thank you
>>> Sven
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160506/bbb4ca83/attachment.html>

From jandeca at gmail.com  Sat May  7 18:30:19 2016
From: jandeca at gmail.com (Jan Deca)
Date: Sat, 7 May 2016 16:30:19 -0600
Subject: [Paraview] Table of points to colored tube.
Message-ID: <572E6C7B.9020500@gmail.com>

Hi all,

I've been stuck with the following for a while.

Given is a table (using the TableToPoints filter) of X,Y,Z,N (4 columns, 
3 coordinates and the density at those coordinates) over time. I would 
like to connect those points and color the tube according to the 
density, N, at that point.

Using the Programmable Filter I managed to connect the points as follows:

pdi =self.GetPolyDataInput()

pdo =self.GetPolyDataOutput()

numPoints =pdi.GetNumberOfPoints()

pdo.Allocate()

fori inrange(0, numPoints-1):

points =[i, i+1]

pdo.InsertNextCell(3, 2, points)

Unfortunately I do not manage to include the density component.

It would be awesome if somebody could help me out.

Thank you!

Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160507/b0a9dbf9/attachment.html>

From jandeca at gmail.com  Sat May  7 20:17:45 2016
From: jandeca at gmail.com (Jan Deca)
Date: Sat, 7 May 2016 18:17:45 -0600
Subject: [Paraview] Table of points to colored tube.
In-Reply-To: <572E6C7B.9020500@gmail.com>
References: <572E6C7B.9020500@gmail.com>
Message-ID: <572E85A9.8030605@gmail.com>

So, I'm almost there with this script:

"
pdi = self.GetPolyDataInput()
pdo =  self.GetPolyDataOutput()
numPoints = pdi.GetNumberOfPoints()
pdo.Allocate()
for i in range(0, numPoints-1):
  points = [i, i+1]
  pdo.InsertNextCell(3, 2, points)

ivals = pdi.GetPointData().GetScalars("u")
ca = vtk.vtkFloatArray()
ca.SetName(ivals.GetName())
ca.SetNumberOfComponents(1)
ca.SetNumberOfTuples(numPoints-1)
pdo.GetCellData().AddArray(ca)
for i in range(0, numPoints-1):
   ca.SetValue(i, ivals.GetValue(i))
"

The only issue now is that the Tube filter is unhappy as it is unable to 
compute the normals making its output segmented looking like a 
collection of separate disks. I've attached a test-file and screenshot 
of the output.

"

Generic Warning: In 
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/DataModel/vtkPolyLine.cxx, 
line 106

Coincident points in polyline...can't compute normals

Warning: In 
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Filters/Core/vtkTubeFilter.cxx, 
line 243

vtkTubeFilter (0x7f840214ca40): Could not generate normals for line. 
Skipping to next.

"

Anybody any suggestions?

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160507/ca63efa0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TubeFilterOutput.png
Type: image/png
Size: 288031 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160507/ca63efa0/attachment-0001.png>
-------------- next part --------------
x y z u
0.48 0.53208718441 0.465358168082 0.015827736896
0.480015868191 0.532075753183 0.465349509398 0.0159084404236
0.480031814754 0.532064157098 0.465341182625 0.0159844839492
0.480047835018 0.532052399243 0.465333190341 0.0160558396844
0.480063924283 0.532040482745 0.465325535038 0.0161224810919
0.48008007782 0.53202841076 0.465318219113 0.0161843829012
0.48009629088 0.532016186479 0.465311244872 0.0162415211177
0.480112558687 0.532003813122 0.465304614527 0.0162938730288
0.480128876444 0.53199129394 0.465298330194 0.0163414172109
0.480145239333 0.531978632215 0.465292393899 0.0163841335347
0.480161642516 0.531965831256 0.465286807568 0.0164220031712
0.480178081138 0.531952894399 0.465281573034 0.0164550085962
0.480194550328 0.531939825009 0.465276692033 0.0164831335954
0.480211045196 0.531926626474 0.465272166204 0.0165063632688
0.48022756084 0.531913302208 0.46526799709 0.0165246840346
0.480244092346 0.531899855652 0.465264186136 0.0165380836327
0.480260634787 0.531886290264 0.465260734689 0.0165465511283
0.480277183225 0.531872609531 0.465257643998 0.0165500769148
0.480293732715 0.531858816955 0.465254915212 0.016548652716
0.480310278303 0.531844916062 0.465252549382 0.0165422715889
0.48032681503 0.531830910396 0.465250547462 0.0165309279252
0.48034333793 0.531816803521 0.465248910303 0.0165146174529
0.480359842035 0.531802599016 0.465247638658 0.0164933372376
0.480376322375 0.531788300477 0.46524673318 0.0164670856829
0.480392773978 0.531773911517 0.465246194422 0.0164358625312
0.480409191873 0.531759435762 0.465246022838 0.0163996688638
0.48042557109 0.531744876851 0.465246218779 0.0163585071002
0.480441906663 0.531730238439 0.465246782497 0.016312380998
0.48045819363 0.531715524188 0.465247714144 0.0162612956516
0.480474427036 0.531700737773 0.46524901377 0.0162052574906
0.480490600244 0.531685875934 0.465250697152 0.016140758755
0.480506706066 0.531670935921 0.46525278002 0.0160704846006
0.480522738732 0.531655922208 0.465255262211 0.0159944474713
0.480538692485 0.531640839279 0.465258143429 0.0159126616449
0.480554561585 0.531625691626 0.465261423254 0.0158251432281
0.480570340308 0.531610483751 0.465265101132 0.0157319101516
0.48058602295 0.531595220161 0.465269176384 0.0156329821644
0.480601603825 0.531579905367 0.4652736482 0.0155283808274
0.480617077273 0.531564543884 0.465278515645 0.0154181295066
0.480632437656 0.531549140231 0.465283777651 0.0153022533659
0.480647679361 0.531533698925 0.465289433027 0.0151807793585
0.480662796807 0.531518224484 0.465295480453 0.0150537362191
0.480677784437 0.531502721421 0.465301918482 0.014921154454
0.480692636731 0.531487194247 0.465308745541 0.014783066332
0.480707348198 0.531471647469 0.465315959931 0.0146395058738
0.480721913385 0.531456085586 0.465323559827 0.0144905088412
0.480736326872 0.531440513089 0.46533154328 0.014336112726
0.48075058328 0.531424934458 0.465339908218 0.0141763567378
0.48076467727 0.531409354166 0.465348652443 0.0140112817913
0.480778603545 0.53139377667 0.465357773637 0.013840930494
0.480792356849 0.531378206415 0.465367269357 0.0136653471321
0.480805931973 0.53136264783 0.465377137041 0.0134845776564
0.480819323755 0.531347105328 0.465387374006 0.0132986696679
0.480832527082 0.531331583304 0.465397977449 0.0131076724027
0.480845536888 0.531316086134 0.465408944449 0.0129116367162
0.480858348162 0.531300618172 0.465420271967 0.0127106150668
0.480870955945 0.53128518375 0.465431956846 0.0125046614995
0.480883355332 0.531269787178 0.465443995816 0.0122938316285
0.480895541476 0.53125443274 0.465456385489 0.0120781826198
0.480907509586 0.531239124694 0.465469122365 0.0118577731725
0.480919255046 0.53122386278 0.465482200276 0.0116328775881
0.480930773159 0.531208646455 0.465495612911 0.0114030875477
0.480942059062 0.531193479443 0.465509356383 0.0111684687265
0.480953107961 0.531178365438 0.465523426695 0.0109290883528
0.480963915129 0.531163308105 0.465537819746 0.0106850151865
0.480974475906 0.531148311078 0.465552531326 0.0104363194967
0.480984785707 0.531133377959 0.465567557122 0.0101830730395
0.480994840018 0.531118512317 0.46558289272 0.00992534903462
0.481004634398 0.531103717687 0.465598533602 0.00966322214205
0.481014164481 0.531088997568 0.465614475151 0.00939676843808
0.481023425981 0.531074355422 0.465630712652 0.0091260653908
0.481032414686 0.531059794675 0.465647241293 0.00885119183524
0.481041126466 0.531045318713 0.465664056166 0.00857222794808
0.481049557272 0.531030930882 0.46568115227 0.00828925522188
0.481057703136 0.531016634489 0.46569852451 0.00800235643894
0.481065560173 0.531002432797 0.465716167703 0.00771161564473
0.481073124585 0.530988329026 0.465734076575 0.00741711812095
0.481080392664 0.530974326348 0.465752245774 0.00711895021122
0.481087360783 0.530960427893 0.465770669858 0.00681719955684
0.481094025404 0.530946636748 0.465789343296 0.00651195497169
0.481100383077 0.530932955951 0.465808260478 0.00620330639328
0.481106430445 0.530919388491 0.465827415712 0.00589134485385
0.481112164239 0.530905937311 0.465846803229 0.00557616245108
0.481117581286 0.530892605302 0.465866417184 0.00525785231849
0.481122678504 0.530879395304 0.465886251655 0.00493650859547
0.481127452906 0.530866310105 0.46590630065 0.00461222639701
0.481131901604 0.530853352443 0.465926558104 0.00428510178312
0.481136021802 0.530840524999 0.465947017886 0.00395523172793
0.481139810803 0.5308278304 0.465967673794 0.00362271408851
0.481143266009 0.530815271221 0.465988519566 0.00328764757336
0.481146384922 0.530802849976 0.466009548874 0.00295013171075
0.481149165141 0.530790569126 0.466030755331 0.00261026681662
0.481151604368 0.530778431073 0.466052132488 0.00226815396238
0.481153700405 0.530766438159 0.466073673844 0.00192389494238
0.481155451159 0.53075459267 0.46609537284 0.00157759224116
0.481156854636 0.530742896828 0.466117222867 0.00122934900054
0.481157908947 0.530731352798 0.466139217262 0.000879268986407
0.481158612309 0.530719962681 0.466161349319 0.000527456555343
0.48115896304 0.530708728518 0.466183612281 0.000174016621092
0.481158959567 0.530697652285 0.466205999351 -0.0001809453792

From pichler.richard at gmail.com  Sun May  8 20:50:30 2016
From: pichler.richard at gmail.com (Richard Pichler)
Date: Mon, 9 May 2016 10:50:30 +1000
Subject: [Paraview] tikz/tex export for paraview contour plots
Message-ID: <572FDED6.9030405@gmail.com>

Hi,

We are currently trying to export paraview contour plots and include
them into a latex document. The straight forward way of exporting an eps
or similar image has some issues. In particular the axis are not scaling
with the camera view, hence, if you zoom in, you don't get them on the
plot since they are only at the exterior of the data. We created a small
python tool, that essentially embeds the figure created in paraview into
a tikz picture and adds axes. However, we still need to manually specify
the the extent of the plot in that script which is tedious.

a) Did anyone encounter the same issue and is willing to share a script
or so?
b) If not, is there a way to extract the Viewport extent in a python
script so that we can directly set them in the script?
c) In addition it would be great if also the text in the legend would be
rendered in latex. Therefore it would be great if we could place it in
the Paraview window and then only plot the colorbar and add the text to
the tikz file.

Thanks,
Richard

PS: the core of the python script that prepares the tikz file:

ifile=open(outfilename,'w')
formstring=' {:>10.8f}'
line='% this picture was created with the axisNlable_generator.py script
\n'\
+    '% \n \n'
ifile.write(line)
line='\\begin{tikzpicture} \n' \
+    '\\begin{axis}[ \n' \
+    'axis on top,enlargelimits=false,\n'\
+    'width=\\figurewidth, \n' \
+    'axis equal image,\n'\
+    'xlabel='+xlabel+',\n'\
+    'ylabel='+ylabel+']\n'\
+    '\\addplot[]
graphics[xmin='+str(xmin)+',ymin='+str(ymin)+',xmax='+str(xmax)+',ymax='+str(ymax)+']\n'
\
+    '{'+enbed_fname+'};\n'\
+    '\\end{axis} \n' \
+    '\\end{tikzpicture} \n' \

ifile.write(line)
ifile.close()

From padamsen at grundfos.com  Mon May  9 05:00:25 2016
From: padamsen at grundfos.com (Per Adamsen)
Date: Mon, 9 May 2016 09:00:25 +0000
Subject: [Paraview] Camera focus being tangent to camera path
Message-ID: <VI1PR03MB14391536B1FBE17AD34AFE08A4700@VI1PR03MB1439.eurprd03.prod.outlook.com>

Hi,

Would it be possible to specify a new camera focus point for each camera position in a path so that you make the illusion that the camera moves with e.g. a pipe flow?

It seems only to be possible to specify *one* focus point for a camera path.

Regards,
Per Adamsen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/891f5755/attachment.html>

From cory.quammen at kitware.com  Mon May  9 09:52:51 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 9 May 2016 09:52:51 -0400
Subject: [Paraview] [ParaView] Generating a 3D model
In-Reply-To: <CAJFKOL3XFza9hGtGnnH9J2d_SSrmt5jWjNfxO_AKOOhoi8YuMg@mail.gmail.com>
References: <CAJFKOL3XFza9hGtGnnH9J2d_SSrmt5jWjNfxO_AKOOhoi8YuMg@mail.gmail.com>
Message-ID: <CAB5Fpx75qtqnwVpuC1Gyjxrv14WppxH72coUhDVZ1-K5=vPTVw@mail.gmail.com>

When you say you can't see the volume, do you mean a volume rendering
of the surface? Or do you want to see the volume of the segmented
organ? If that is the case, use either the Contour filter or Threshold
filter to show the boundary surface of your segmentation. Either one
should work, but the Contour filter may produce a bit smoother
surface.

Hope that helps,
Cory

On Mon, May 2, 2016 at 2:34 PM, Chathuri Gunasekera <cgunases at gmail.com> wrote:
> Hello everyone,
>
>  Since i need to generate a human organ using my data first of all i
> registered my images. Second of all, segmented the organ first . Third of
> all, segmented the rest of the sub objects inside the organ.
>
> Basically, segmentation was done and saved in following formats.
> 1st mask(for the organ) ; saved as .mat file
> 2nd mask(for sub objects with in the organ) : saved as .mat file
> 3rd mask(for sub objects within the organ)  : saved as .mat file
>
> (note: segmentation is done for the whole image)
>
> Since i have these masks saved in Mat format i combined all the masks and
> converted to VTK format.
>
> When i run in the Paraview, i can only view the slice, surface, etc but NOT
> the VOLUME (which is what i want).
>
> What is the reason to this?
>
> How to overcome this issue now?
>
> Thank you in advance.
> --
> Warm regards,
> Chathuri Gunasekera.
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Mon May  9 09:54:11 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 9 May 2016 09:54:11 -0400
Subject: [Paraview] visualising a numpy array
In-Reply-To: <CAB5Fpx60MexHWQfztmncxpR6bYDAQW4OsR5=kmxkeCq7r0SE9Q@mail.gmail.com>
References: <3016982.g3SsLEMJvk@vega>
 <CAB5Fpx55wZjw8Ty+_4rD-O6ZhqnW8-n5ccNY13zoGZU1fejmgw@mail.gmail.com>
 <7473615.6gLVRJUW11@vega>
 <CAB5Fpx60MexHWQfztmncxpR6bYDAQW4OsR5=kmxkeCq7r0SE9Q@mail.gmail.com>
Message-ID: <CAB5Fpx4K3ykzDzRaBFnWWYdmnctY+3wLwQHBgihbyK6voqEKRw@mail.gmail.com>

Hi Juha,

This is a bit beyond my current numpy-foo. Hopefully I'll get a chance
to look at it in more depth in the next couple months.

If you figure anything else out, I and others on the list would surely
appreciate knowing what you find.

Thanks,
Cory

On Fri, Apr 29, 2016 at 2:19 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
> On Wed, Apr 27, 2016 at 11:39 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
>>> How are you getting the PETSc._DMDA_Vec_array into ParaView? The
>>> Programmable Filter is also available in ParaView...
>>
>> I was going to use
>>
>> my_numpy_data = petsc_dmda_array[:]
>> vtkobject = paraview.numpy_support.numpy_to_vtk(my_numpy_data.copy())
>>
>> That works fine, but then I got stuck with how to stick this into paraview's
>> pipeline.
>>
>>> You'll need to set up a vtkImageData as the output of a Programmable
>>> Source/Filter at the very least with the proper dimensions, then use
>>> the vtk.numpy_interface.dataset_adapter tools to adapt your numpy
>>> array as a VTK data array that you add to the vtkImageData's point
>>> data.
>>
>> I would have thought I need a vtkStructuredGrid or vtkRectilinearGrid, but I
>> don't seem able to figure out how to use them.
>
> If your grid points are regularly spaced in each dimension, which I
> think they are in this case, you can use a vtkImageData. See the
> ParaViewGuide (http://www.paraview.org/paraview-guide/) pages 33 and
> 34 for pictorial representations of where vtkStructuredGrid or
> vtkRectilinearGrid are needed.
>
>> With vSG I can
>>
>> pts = vtk.vtkPoints()
>> pdo = self.GetOutput()
>> newArray = vtk.vtkDoubleArray()
>> # this is how far I've got before...
>> newArray.SetName("testdata")
>> newArray.SetNumberOfComponents(1)
>> pdo.GetPointData().AddArray(newArray)
>>
>> # stuff our numbers into pdo.GetPointData().GetArray(0).InsertNextValue(float)
>> one by one,
>> # followed by pts.InsertNextPoint(x,y,z), so need to get xyz as well
>> xmin,xmax,Nx,ymin,ymax,Ny,zmin,zmax,Nz = -1,1,10,-1,2,20,-1,3,30
>> loci =
>> numpy.mgrid[xmin:xmax:1j*Nx,ymin:ymax:1j*Ny,zmin:zmax:1j*Nz].reshape(3,-1)
>> values = numpy.random.random(loci[0].shape)
>> for ind in range(loci[0].shape[0]):
>>     pdo.GetPointData().GetArray(0).InsertNextValue(values[ind])
>>     pts.InsertNextPoint(loci[0,ind],loci[1,ind],loci[2,ind])
>> pdo.SetPoints(pts)
>> exts = [xmin,xmax,ymin,ymax,zmin,zmax]
>> pdo.SetExtent(exts)
>
> Note that the extents are in the integer index space (e.g., i-j-k) of
> the grid points rather than physical space, so exts should be
> something like
>
> [0, 9, 0, 19, 0, 29]
>
> Also note that xmax, ymax, and zmax should be the highest possible
> index, not the number of grid positions in that dimension.
>
>> which seems to do the right thing except I can not make paraview plot anything
>> using this. In the ProgrammableSource's Information tab I do see the right
>> bounds and extents (but I am a bit confused about what the "dimension" means
>> in extents: it says 3, 4, 5 for x, y, z, which makes me think it has used unit
>> lattice spacing even though I would have thought it uses whatever it finds in
>> pts. The "Data Arrays" box has "testdata" in it and has the correct value
>> range. Also the number of points is correct (6000). I don't know where it gets
>> its 24 cells from, though. (24 = 2*3*4, so I am a bit concerned it gets this
>> implicitly from bounds again with unit spacing).
>>
>> But I don't understand what I'm doing wrong as I'm basically modifying
>> examples from the wiki.
>>
>> Using vtkImageData I can only get a Number of Points: 60 (and no plot) and
>> using vtkRectilinearGrid I get the same. I can fix the 60 -> 6000 by fixing
>> the extents, but that still leaves the bounds and no plot on screen.
>>
>>> Parallel is tougher... You can do the full data set in serial and
>>> distribute using the D3 filter, but obviously that has some downsides.
>>
>> Unacceptable ones: I cannot even imagine what that bottleneck would do to the
>> code.
>>
>>> I believe it is possible to distribute the dataset using MPI in a
>>> Programmable Source/Filter, but have never done so myself.
>>
>> Hmm... so where does the ProgrammableSource run? I was planning on running the
>> whole code in parallel, but didn't really think about how to do that yet. Now
>> that I start thinking about it, Catalyst is probably the way to do it, isn't
>> it?
>
> The Programmable Source is a VTK filter that runs on all nodes on
> which you are running the ParaView server. Catalyst may indeed be
> useful for you.
>
> Cory
>
>> Cheers,
>> Juha
>>
>>> On Tue, Apr 26, 2016 at 8:49 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
>>> > Dear list,
>>> >
>>> > What's the current best practice to visualise a (3D) numpy array with
>>> > paraview? In particular, I'm wondering if
>>> >
>>> > vtkdata = numpy_support.numpy_to_vtk(num_array=NumPy_data.ravel(),
>>> > deep=True, array_type=vtk.VTK_FLOAT)
>>> >
>>> > can somehow be directly visualised? In parallel.
>>> >
>>> > I'm aware of ProgrammableSource() and how to do it using that, but only
>>> > from a file! What I'd very much like to do is avoid the file (if I cannot
>>> > avoid the file, I'll just do xdmf and hdf5.)
>>> >
>>> > Just in case it matters, the numpy array is actually not really a numpy
>>> > array, but petsc4py.PETSc._DMDA_Vec_array which of course can be "cast"
>>> > as numpy.ndarray.
>>> >
>>> > Best regards,
>>> > Juha
>>> >
>>> > _______________________________________________
>>> > 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
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From utkarsh.ayachit at kitware.com  Mon May  9 10:26:08 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 9 May 2016 10:26:08 -0400
Subject: [Paraview] Dropping support for OsX 10.7 (Lion)
Message-ID: <CADHSJjBycd1r_LwF=2hjcwvjpjQK-_K_w_dPfjLpQUh2gJF+bg@mail.gmail.com>

Folks,

I wanted to check if there's any objection to dropping support for OsX 10.7
(Lion) in future ParaView releases. 10.7 has been unsupported by Apple
since October 2014 [1]. This will change minimum OsX version for ParaView
to 10.8 (Mountain Lion).

Utkarsh

[1] https://en.wikipedia.org/wiki/Mac_OS_X_Lion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/811fa62f/attachment.html>

From kmorel at sandia.gov  Mon May  9 13:36:07 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 9 May 2016 17:36:07 +0000
Subject: [Paraview] Table of points to colored tube.
Message-ID: <BE86061F-8C11-4281-9905-087109E36BA8@sandia.gov>

Jan,

I think you want to copy the field data as point data, not cell data. Since the points of your input are the same as your output, you can just call ?PassData? to copy them over. Try this version of the script for the programmable filter:

pdi = self.GetPolyDataInput()
pdo = self.GetPolyDataOutput()
numPoints = pdi.GetNumberOfPoints()
pdo.Allocate()
for i in range(0, numPoints-1):
 points = [i, i+1]
 pdo.InsertNextCell(3, 2, points)

pdo.GetPointData().PassData(pdi.GetPointData())

-Ken


From: ParaView <paraview-bounces at paraview.org> on behalf of Jan Deca <jandeca at gmail.com>
Date: Saturday, May 7, 2016 at 6:17 PM
To: "paraview at paraview.org" <ParaView at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Table of points to colored tube.

So, I'm almost there with this script:

"
pdi = self.GetPolyDataInput()
pdo =  self.GetPolyDataOutput()
numPoints = pdi.GetNumberOfPoints()
pdo.Allocate()
for i in range(0, numPoints-1):
 points = [i, i+1]
 pdo.InsertNextCell(3, 2, points)

ivals = pdi.GetPointData().GetScalars("u")
ca = vtk.vtkFloatArray()
ca.SetName(ivals.GetName())
ca.SetNumberOfComponents(1)
ca.SetNumberOfTuples(numPoints-1)
pdo.GetCellData().AddArray(ca)
for i in range(0, numPoints-1):
  ca.SetValue(i, ivals.GetValue(i))
"

The only issue now is that the Tube filter is unhappy as it is unable to compute the normals making its output segmented looking like a collection of separate disks. I've attached a test-file and screenshot of the output.

"


Generic Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/DataModel/vtkPolyLine.cxx, line 106

Coincident points in polyline...can't compute normals

Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Filters/Core/vtkTubeFilter.cxx, line 243

vtkTubeFilter (0x7f840214ca40): Could not generate normals for line. Skipping to next.
"

Anybody any suggestions?

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/6626eb72/attachment.html>

From svenkramer40 at gmail.com  Mon May  9 15:34:07 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Mon, 9 May 2016 21:34:07 +0200
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
 <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
Message-ID: <CAJZHu4Rc3QXCopX+DBtCNuajG4vr6AYR1hEKwrV9FetL8drkuQ@mail.gmail.com>

Hello Seb,
I got a working connection from pv_web_visualizer.py to a couple of
pvservers (started with mpirun on <hostname>) by just giving "--ds-host
<hostname> --ds-port 11111" from the link you mentioned. Is this correct,
without --rs-host? It is working in principle, but the renderview update
rate is not more than 2 updates/second for a tiny datasource even when
everything is running on the same machine.

Thank you
Sven

2016-05-06 22:26 GMT+02:00 Sebastien Jourdain <
sebastien.jourdain at kitware.com>:

> Hi Sven,
>
> 1) Yes, assuming you are using pv_web_visualizer.py you can look here:
>
>
> https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28
>
> 2) The server can push notification to the client. Need to slightly edit
> the client and server to match your needs.
>
> Seb
>
>
> On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Dear all,
>> I am currently running a VTK application, which is visualizing large
>> grids distributed on a MPI cluster.
>> My task is to migrate this application to the Web. But I cannot manage
>> more than what is described at
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
>> that is I can serve a local data directory through the provided webapps.
>>
>> I have two essential questions that stop me from getting started:
>> 1) How do I connect the pvpython server to remote data/render servers
>> just like I can do in Paraview?
>> 2) All ParaviewWeb examples seem to react on webclient requests. Our
>> application is processing data as they come in, and also the visualization
>> pipeline is frequently updated depending on an automatic analysis of the
>> arriving data. Can the newly rendered datasets be pushed to the webclient,
>> or does the webclient have to poll for available datasets?
>>
>> Thank you
>> Sven
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/d912fc28/attachment.html>

From tim.gallagher at gatech.edu  Mon May  9 15:58:44 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 9 May 2016 19:58:44 +0000
Subject: [Paraview] Linking to Catalyst
Message-ID: <BN3PR07MB26275B660A48EDA6B6833ED09D700@BN3PR07MB2627.namprd07.prod.outlook.com>

Hello again,


I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link my code to it (and this is a code that works fine with Catalyst on other platforms), I get:


 CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):
   Requested modules not available:

     vtkPVPythonCatalyst
 Call Stack (most recent call first):
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)
   CMakeLists.txt:218 (find_package)

The section in my CMakeLists that looks for paraview is:

option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
if(LESLIE_USE_COPROCESSING)
  find_package(ParaView REQUIRED vtkPVPythonCatalyst
               HINTS $ENV{PARAVIEW_CP_ROOT})
  include(${PARAVIEW_USE_FILE})
  include_directories(${PROJECT_SOURCE_DIR}/utils)
  add_definitions(-DPARAVIEW_COPROCESSING)
endif()
mark_as_advanced(LESLIE_USE_COPROCESSING)

and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:


/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4


and it seems to find it okay.


Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so* and libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/


I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?


Thanks as always,


Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/f114a129/attachment.html>

From andy.bauer at kitware.com  Mon May  9 16:43:42 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 9 May 2016 16:43:42 -0400
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <BN3PR07MB26275B660A48EDA6B6833ED09D700@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB26275B660A48EDA6B6833ED09D700@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CAMaOp+G+x0yvFTmnKCSM29W8nEugo-GTojg+vgzy1MH+a1D9bQ@mail.gmail.com>

Hi Tim,

Is the PV directory you're pointing to a build directory or an install
directory? If it's an install directory you'll need to enable
PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be
to try linking one of the Catalyst examples from
https://github.com/Kitware/ParaViewCatalystExampleCode and see how that
works for you. Another thing you could try is using a newer version of
CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you
can just untar the executables from that and use directly.

Let us know if none of those ideas don't work for you.

Best,
Andy

On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <
tim.gallagher at gatech.edu> wrote:

> Hello again,
>
>
> I'm (finally) trying to get Catalyst to successfully link to our
> application code on Excalibur (Cray, ARL HPC). I was able to build paraview
> and all of the dependencies thanks to help I've gotten on the list here in
> the past. However, when I try to link my code to it (and this is a code
> that works fine with Catalyst on other platforms), I get:
>
>
>  CMake Error at
> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120
> (message):
>    Requested modules not available:
>
>      vtkPVPythonCatalyst
>  Call Stack (most recent call first):
>
> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80
> (vtk_module_config)
>
> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49
> (include)
>    CMakeLists.txt:218 (find_package)
>
> The section in my CMakeLists that looks for paraview is:
>
> option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
> if(LESLIE_USE_COPROCESSING)
>   find_package(ParaView REQUIRED vtkPVPythonCatalyst
>                HINTS $ENV{PARAVIEW_CP_ROOT})
>   include(${PARAVIEW_USE_FILE})
>   include_directories(${PROJECT_SOURCE_DIR}/utils)
>   add_definitions(-DPARAVIEW_COPROCESSING)
> endif()
> mark_as_advanced(LESLIE_USE_COPROCESSING)
>
> and it doesn't seem to work. On other machines, I never needed to set the
> PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I
> point the paraview directory (where it finds the paraviewConfig.cmake file)
> to:
>
>
> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4
>
>
> and it seems to find it okay.
>
>
> Lastly, the vtkPVPythonCatalyst.so library is in the
> lib/paraview-4.4/site-packages/vtk directory and there is
> libvtkPVPythonCatalyst-pv4.4.so* and
> libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/
>
>
> I'm at a loss to understand why it is reporting the module is missing --
> did I miss something somewhere?
>
>
> Thanks as always,
>
>
> Tim
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/0431c63a/attachment.html>

From andy.bauer at kitware.com  Mon May  9 16:54:57 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 9 May 2016 16:54:57 -0400
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>

Hmm, that could be a bug in the superbuild. The superbuild arguments aren't
all passed to the ParaView build itself and it could be that this option
was missing for the PV specific build part. Instead of doing the whole
build from scratch, I'd suggest you just search for the
ParaViewConfig.cmake file to find where PV was actually built and just
point to that.

On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <
tim.gallagher at gatech.edu> wrote:

> Well shoot, it looks like I didn't build with the install development
> files on, even though I set it when I configured the superbuild. I must
> have done that part wrong
>
> My configure line is:
>
>
> cmake \
> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
> -DCMAKE_BUILD_TYPE=Release \
> ...
>
> -DPARAVIEW_ENABLE_CATALYST=ON \
> -DPARAVIEW_ENABLE_PYTHON=ON \
> -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
> -DPARAVIEW_BUILD_QT_GUI=OFF \
> -DBUILD_TESTING=OFF \
> -DVTK_USE_X=OFF \
> ...
>
> -DVTK_OPENGL_HAS_OSMESA=ON \
> -DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
> -DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
> ./ParaViewSuperbuild
>
>
> and all of the other PARAVIEW* options seemed to pass through properly
> when the superbuild made paraview. Any ideas why that option didn't pass
> through?
>
>
> Thanks -- I knew it had to be something really obvious!
>
>
> Tim
>
>
>
> ------------------------------
> *From:* Andy Bauer <andy.bauer at kitware.com>
> *Sent:* Monday, May 9, 2016 4:43 PM
> *To:* Gallagher, Timothy P
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Linking to Catalyst
>
> Hi Tim,
>
> Is the PV directory you're pointing to a build directory or an install
> directory? If it's an install directory you'll need to enable
> PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be
> to try linking one of the Catalyst examples from
> https://github.com/Kitware/ParaViewCatalystExampleCode and see how that
> works for you. Another thing you could try is using a newer version of
> CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you
> can just untar the executables from that and use directly.
> <https://github.com/Kitware/ParaViewCatalystExampleCode>
> GitHub - Kitware/ParaViewCatalystExampleCode: Example ...
> <https://github.com/Kitware/ParaViewCatalystExampleCode>
> github.com
> ParaViewCatalystExampleCode - Example problems and snippets of code to
> demonstrate ParaView's Catalyst.
>
>
> Let us know if none of those ideas don't work for you.
>
> Best,
> Andy
>
> On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <
> tim.gallagher at gatech.edu> wrote:
>
>> Hello again,
>>
>>
>> I'm (finally) trying to get Catalyst to successfully link to our
>> application code on Excalibur (Cray, ARL HPC). I was able to build paraview
>> and all of the dependencies thanks to help I've gotten on the list here in
>> the past. However, when I try to link my code to it (and this is a code
>> that works fine with Catalyst on other platforms), I get:
>>
>>
>>  CMake Error at
>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120
>> (message):
>>    Requested modules not available:
>>
>>      vtkPVPythonCatalyst
>>  Call Stack (most recent call first):
>>
>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80
>> (vtk_module_config)
>>
>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49
>> (include)
>>    CMakeLists.txt:218 (find_package)
>>
>> The section in my CMakeLists that looks for paraview is:
>>
>> option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
>> if(LESLIE_USE_COPROCESSING)
>>   find_package(ParaView REQUIRED vtkPVPythonCatalyst
>>                HINTS $ENV{PARAVIEW_CP_ROOT})
>>   include(${PARAVIEW_USE_FILE})
>>   include_directories(${PROJECT_SOURCE_DIR}/utils)
>>   add_definitions(-DPARAVIEW_COPROCESSING)
>> endif()
>> mark_as_advanced(LESLIE_USE_COPROCESSING)
>>
>> and it doesn't seem to work. On other machines, I never needed to set the
>> PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I
>> point the paraview directory (where it finds the paraviewConfig.cmake file)
>> to:
>>
>>
>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4
>>
>>
>> and it seems to find it okay.
>>
>>
>> Lastly, the vtkPVPythonCatalyst.so library is in the
>> lib/paraview-4.4/site-packages/vtk directory and there is
>> libvtkPVPythonCatalyst-pv4.4.so* and
>> libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/
>>
>>
>> I'm at a loss to understand why it is reporting the module is missing --
>> did I miss something somewhere?
>>
>>
>> Thanks as always,
>>
>>
>> Tim
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/919dc825/attachment.html>

From tim.gallagher at gatech.edu  Mon May  9 17:13:47 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 9 May 2016 21:13:47 +0000
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>
Message-ID: <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>

Yeah -- okay, pointing it to the build directory instead of the install made sure everything was found.


One step closer to getting this working on Cray.


Thanks,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com>
Sent: Monday, May 9, 2016 4:54 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org
Subject: Re: [Paraview] Linking to Catalyst

Hmm, that could be a bug in the superbuild. The superbuild arguments aren't all passed to the ParaView build itself and it could be that this option was missing for the PV specific build part. Instead of doing the whole build from scratch, I'd suggest you just search for the ParaViewConfig.cmake file to find where PV was actually built and just point to that.

On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Well shoot, it looks like I didn't build with the install development files on, even though I set it when I configured the superbuild. I must have done that part wrong


My configure line is:


cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
...

-DPARAVIEW_ENABLE_CATALYST=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DBUILD_TESTING=OFF \
-DVTK_USE_X=OFF \
...

-DVTK_OPENGL_HAS_OSMESA=ON \
-DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
-DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
./ParaViewSuperbuild


and all of the other PARAVIEW* options seemed to pass through properly when the superbuild made paraview. Any ideas why that option didn't pass through?


Thanks -- I knew it had to be something really obvious!


Tim



________________________________
From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Sent: Monday, May 9, 2016 4:43 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Linking to Catalyst

Hi Tim,

Is the PV directory you're pointing to a build directory or an install directory? If it's an install directory you'll need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be to try linking one of the Catalyst examples from https://github.com/Kitware/ParaViewCatalystExampleCode and see how that works for you. Another thing you could try is using a newer version of CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you can just untar the executables from that and use directly.
[https://avatars3.githubusercontent.com/u/87549?v=3&s=400]<https://github.com/Kitware/ParaViewCatalystExampleCode>

GitHub - Kitware/ParaViewCatalystExampleCode: Example ...<https://github.com/Kitware/ParaViewCatalystExampleCode>
github.com<http://github.com>
ParaViewCatalystExampleCode - Example problems and snippets of code to demonstrate ParaView's Catalyst.



Let us know if none of those ideas don't work for you.

Best,
Andy

On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hello again,


I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link my code to it (and this is a code that works fine with Catalyst on other platforms), I get:


 CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):
   Requested modules not available:

     vtkPVPythonCatalyst
 Call Stack (most recent call first):
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)
   CMakeLists.txt:218 (find_package)

The section in my CMakeLists that looks for paraview is:

option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
if(LESLIE_USE_COPROCESSING)
  find_package(ParaView REQUIRED vtkPVPythonCatalyst
               HINTS $ENV{PARAVIEW_CP_ROOT})
  include(${PARAVIEW_USE_FILE})
  include_directories(${PROJECT_SOURCE_DIR}/utils)
  add_definitions(-DPARAVIEW_COPROCESSING)
endif()
mark_as_advanced(LESLIE_USE_COPROCESSING)

and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:


/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4


and it seems to find it okay.


Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so<http://libvtkPVPythonCatalyst-pv4.4.so>* and libvtkPVPythonCatalystPython27D-pv4.4.so<http://libvtkPVPythonCatalystPython27D-pv4.4.so>* in lib/paraview-4.4/


I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?


Thanks as always,


Tim

_______________________________________________
Powered by www.kitware.com<http://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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/71e8feab/attachment.html>

From tim.gallagher at gatech.edu  Mon May  9 16:50:26 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 9 May 2016 20:50:26 +0000
Subject: [Paraview] Linking to Catalyst
Message-ID: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>

Well shoot, it looks like I didn't build with the install development files on, even though I set it when I configured the superbuild. I must have done that part wrong


My configure line is:


cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
...

-DPARAVIEW_ENABLE_CATALYST=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DBUILD_TESTING=OFF \
-DVTK_USE_X=OFF \
...

-DVTK_OPENGL_HAS_OSMESA=ON \
-DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
-DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
./ParaViewSuperbuild


and all of the other PARAVIEW* options seemed to pass through properly when the superbuild made paraview. Any ideas why that option didn't pass through?


Thanks -- I knew it had to be something really obvious!


Tim



________________________________
From: Andy Bauer <andy.bauer at kitware.com>
Sent: Monday, May 9, 2016 4:43 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org
Subject: Re: [Paraview] Linking to Catalyst

Hi Tim,

Is the PV directory you're pointing to a build directory or an install directory? If it's an install directory you'll need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be to try linking one of the Catalyst examples from https://github.com/Kitware/ParaViewCatalystExampleCode and see how that works for you. Another thing you could try is using a newer version of CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you can just untar the executables from that and use directly.
[https://avatars3.githubusercontent.com/u/87549?v=3&s=400]<https://github.com/Kitware/ParaViewCatalystExampleCode>

GitHub - Kitware/ParaViewCatalystExampleCode: Example ...<https://github.com/Kitware/ParaViewCatalystExampleCode>
github.com
ParaViewCatalystExampleCode - Example problems and snippets of code to demonstrate ParaView's Catalyst.



Let us know if none of those ideas don't work for you.

Best,
Andy

On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hello again,


I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link my code to it (and this is a code that works fine with Catalyst on other platforms), I get:


 CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):
   Requested modules not available:

     vtkPVPythonCatalyst
 Call Stack (most recent call first):
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)
   CMakeLists.txt:218 (find_package)

The section in my CMakeLists that looks for paraview is:

option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
if(LESLIE_USE_COPROCESSING)
  find_package(ParaView REQUIRED vtkPVPythonCatalyst
               HINTS $ENV{PARAVIEW_CP_ROOT})
  include(${PARAVIEW_USE_FILE})
  include_directories(${PROJECT_SOURCE_DIR}/utils)
  add_definitions(-DPARAVIEW_COPROCESSING)
endif()
mark_as_advanced(LESLIE_USE_COPROCESSING)

and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:


/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4


and it seems to find it okay.


Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so<http://libvtkPVPythonCatalyst-pv4.4.so>* and libvtkPVPythonCatalystPython27D-pv4.4.so<http://libvtkPVPythonCatalystPython27D-pv4.4.so>* in lib/paraview-4.4/


I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?


Thanks as always,


Tim

_______________________________________________
Powered by www.kitware.com<http://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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/31395306/attachment.html>

From sebastien.jourdain at kitware.com  Mon May  9 18:11:31 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 9 May 2016 18:11:31 -0400
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CAJZHu4Rc3QXCopX+DBtCNuajG4vr6AYR1hEKwrV9FetL8drkuQ@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
 <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
 <CAJZHu4Rc3QXCopX+DBtCNuajG4vr6AYR1hEKwrV9FetL8drkuQ@mail.gmail.com>
Message-ID: <CABObKxe6eq5HkNovrW8J-ytG-yUT09FF0xhzOaLtHyM2Bf3P+g@mail.gmail.com>

Hi Scen,

that's a correct way, but I'm not sure to know why it is that much slower.
Wondering if all the pvserver are fighting for the same GPU and hence
waiting more than anything... ?
You may be able to change the remote rendering threshold to make sure only
pvpython is doing the rendering.

Seb

On Mon, May 9, 2016 at 3:34 PM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Hello Seb,
> I got a working connection from pv_web_visualizer.py to a couple of
> pvservers (started with mpirun on <hostname>) by just giving "--ds-host
> <hostname> --ds-port 11111" from the link you mentioned. Is this correct,
> without --rs-host? It is working in principle, but the renderview update
> rate is not more than 2 updates/second for a tiny datasource even when
> everything is running on the same machine.
>
> Thank you
> Sven
>
> 2016-05-06 22:26 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Hi Sven,
>>
>> 1) Yes, assuming you are using pv_web_visualizer.py you can look here:
>>
>>
>> https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28
>>
>> 2) The server can push notification to the client. Need to slightly edit
>> the client and server to match your needs.
>>
>> Seb
>>
>>
>> On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Dear all,
>>> I am currently running a VTK application, which is visualizing large
>>> grids distributed on a MPI cluster.
>>> My task is to migrate this application to the Web. But I cannot manage
>>> more than what is described at
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
>>> that is I can serve a local data directory through the provided webapps.
>>>
>>> I have two essential questions that stop me from getting started:
>>> 1) How do I connect the pvpython server to remote data/render servers
>>> just like I can do in Paraview?
>>> 2) All ParaviewWeb examples seem to react on webclient requests. Our
>>> application is processing data as they come in, and also the visualization
>>> pipeline is frequently updated depending on an automatic analysis of the
>>> arriving data. Can the newly rendered datasets be pushed to the webclient,
>>> or does the webclient have to poll for available datasets?
>>>
>>> Thank you
>>> Sven
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/ff38ac45/attachment.html>

From tim.gallagher at gatech.edu  Mon May  9 18:14:49 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 9 May 2016 22:14:49 +0000
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>,
 <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <BN3PR07MB26272549A8D549D8BFF588F79D700@BN3PR07MB2627.namprd07.prod.outlook.com>

Okay, really close to finally crossing this off my list -- it's been on it for years.


I can get the code to generate images but it won't save data files. I don't get any errors and I get my images, just no VTK files. I have tried the default that the catalyst generator creates:


parallelMultiBlockDataSetWriter1 = servermanager.writers.XMLMultiBlockDataWriter(Input=slice1)

coprocessor.RegisterWriter(parallelMultiBlockDataSetWriter1, filename='slices_%t.vtm', freq=freq_file)


and I tried another form that the grid writer you've send me in the past used:


writer = coprocessor.CreateWriter(XMLMultiBlockDataWriter, filename='slices_%t.vtm', freq=freq_file)


in all cases, freq_file = 1000.


Neither one will output any vtk files.


Any thoughts?


Also, minor note but it is kind of annoying -- both the catalyst generator and the trace generator seem to do this, but they add commands that set attributes that are not part of the classes when run through the python script. For example, I had to comment out:


#      slice1Display.SelectInputVectors = ['CELLS', 'Velocity [m/s]']
#      slice1Display.WriteLog = ''


Any ideas why it does that? Or is there a way (and downfall) to just let it add attributes without manually calling add_attribute() each time?


Tim


________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Gallagher, Timothy P <tim.gallagher at gatech.edu>
Sent: Monday, May 9, 2016 5:13 PM
To: Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Linking to Catalyst


Yeah -- okay, pointing it to the build directory instead of the install made sure everything was found.


One step closer to getting this working on Cray.


Thanks,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com>
Sent: Monday, May 9, 2016 4:54 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org
Subject: Re: [Paraview] Linking to Catalyst

Hmm, that could be a bug in the superbuild. The superbuild arguments aren't all passed to the ParaView build itself and it could be that this option was missing for the PV specific build part. Instead of doing the whole build from scratch, I'd suggest you just search for the ParaViewConfig.cmake file to find where PV was actually built and just point to that.

On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Well shoot, it looks like I didn't build with the install development files on, even though I set it when I configured the superbuild. I must have done that part wrong


My configure line is:


cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
...

-DPARAVIEW_ENABLE_CATALYST=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DBUILD_TESTING=OFF \
-DVTK_USE_X=OFF \
...

-DVTK_OPENGL_HAS_OSMESA=ON \
-DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
-DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
./ParaViewSuperbuild


and all of the other PARAVIEW* options seemed to pass through properly when the superbuild made paraview. Any ideas why that option didn't pass through?


Thanks -- I knew it had to be something really obvious!


Tim



________________________________
From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Sent: Monday, May 9, 2016 4:43 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Linking to Catalyst

Hi Tim,

Is the PV directory you're pointing to a build directory or an install directory? If it's an install directory you'll need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be to try linking one of the Catalyst examples from https://github.com/Kitware/ParaViewCatalystExampleCode and see how that works for you. Another thing you could try is using a newer version of CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you can just untar the executables from that and use directly.
[https://avatars3.githubusercontent.com/u/87549?v=3&s=400]<https://github.com/Kitware/ParaViewCatalystExampleCode>

GitHub - Kitware/ParaViewCatalystExampleCode: Example ...<https://github.com/Kitware/ParaViewCatalystExampleCode>
github.com<http://github.com>
ParaViewCatalystExampleCode - Example problems and snippets of code to demonstrate ParaView's Catalyst.



Let us know if none of those ideas don't work for you.

Best,
Andy

On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hello again,


I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link my code to it (and this is a code that works fine with Catalyst on other platforms), I get:


 CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):
   Requested modules not available:

     vtkPVPythonCatalyst
 Call Stack (most recent call first):
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)
   CMakeLists.txt:218 (find_package)

The section in my CMakeLists that looks for paraview is:

option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
if(LESLIE_USE_COPROCESSING)
  find_package(ParaView REQUIRED vtkPVPythonCatalyst
               HINTS $ENV{PARAVIEW_CP_ROOT})
  include(${PARAVIEW_USE_FILE})
  include_directories(${PROJECT_SOURCE_DIR}/utils)
  add_definitions(-DPARAVIEW_COPROCESSING)
endif()
mark_as_advanced(LESLIE_USE_COPROCESSING)

and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:


/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4


and it seems to find it okay.


Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so<http://libvtkPVPythonCatalyst-pv4.4.so>* and libvtkPVPythonCatalystPython27D-pv4.4.so<http://libvtkPVPythonCatalystPython27D-pv4.4.so>* in lib/paraview-4.4/


I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?


Thanks as always,


Tim

_______________________________________________
Powered by www.kitware.com<http://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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/1575e318/attachment.html>

From andy.bauer at kitware.com  Mon May  9 22:41:06 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 9 May 2016 22:41:06 -0400
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <BN3PR07MB26272549A8D549D8BFF588F79D700@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>
 <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB26272549A8D549D8BFF588F79D700@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CAMaOp+E_ddh6WRD+T4BPQR2fA5JrjT9P2VbBUm3LZi=6SXE9Qg@mail.gmail.com>

Hi Tim,

I assume that writing out a data set works on other machines, correct? Can
you try the gridwriter.py script at
https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py
to output the full data set? It should work with PV 4.4. Note that outputs
a full data set every time step. I'm not sure about Python warnings or
errors but the C++ warnings and errors will be sent to std::cerr instead of
std::cout.

Did you make the script with PV 4.4? The PV Python API has some changes
(especially for rendering) between revisions. I think the best option is to
just comment out the parts that are causing trouble.

If you're still having issues, maybe send your full script along with
std::cout and std::cerr outputs so I can get a little deeper into the
issues.

Good luck,
Andy

On Mon, May 9, 2016 at 6:14 PM, Gallagher, Timothy P <
tim.gallagher at gatech.edu> wrote:

> Okay, really close to finally crossing this off my list -- it's been on it
> for years.
>
>
> I can get the code to generate images but it won't save data files. I
> don't get any errors and I get my images, just no VTK files. I have tried
> the default that the catalyst generator creates:
>
>
> parallelMultiBlockDataSetWriter1 =
> servermanager.writers.XMLMultiBlockDataWriter(Input=slice1)
>
> coprocessor.RegisterWriter(parallelMultiBlockDataSetWriter1,
> filename='slices_%t.vtm', freq=freq_file)
>
>
> and I tried another form that the grid writer you've send me in the past
> used:
>
>
> writer = coprocessor.CreateWriter(XMLMultiBlockDataWriter,
> filename='slices_%t.vtm', freq=freq_file)
>
>
> in all cases, freq_file = 1000.
>
>
> Neither one will output any vtk files.
>
>
> Any thoughts?
>
>
> Also, minor note but it is kind of annoying -- both the catalyst generator
> and the trace generator seem to do this, but they add commands that set
> attributes that are not part of the classes when run through the python
> script. For example, I had to comment out:
>
>
> #      slice1Display.SelectInputVectors = ['CELLS', 'Velocity
> [m/s]']
>
> #      slice1Display.WriteLog = ''
>
>
> Any ideas why it does that? Or is there a way (and downfall) to just let
> it add attributes without manually calling add_attribute() each time?
>
>
> Tim
>
>
> ------------------------------
> *From:* ParaView <paraview-bounces at paraview.org> on behalf of Gallagher,
> Timothy P <tim.gallagher at gatech.edu>
> *Sent:* Monday, May 9, 2016 5:13 PM
> *To:* Andy Bauer
>
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Linking to Catalyst
>
>
> Yeah -- okay, pointing it to the build directory instead of the install
> made sure everything was found.
>
>
> One step closer to getting this working on Cray.
>
>
> Thanks,
>
>
> Tim
>
>
> ------------------------------
> *From:* Andy Bauer <andy.bauer at kitware.com>
> *Sent:* Monday, May 9, 2016 4:54 PM
> *To:* Gallagher, Timothy P
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Linking to Catalyst
>
> Hmm, that could be a bug in the superbuild. The superbuild arguments
> aren't all passed to the ParaView build itself and it could be that this
> option was missing for the PV specific build part. Instead of doing the
> whole build from scratch, I'd suggest you just search for the
> ParaViewConfig.cmake file to find where PV was actually built and just
> point to that.
>
> On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <
> tim.gallagher at gatech.edu> wrote:
>
>> Well shoot, it looks like I didn't build with the install development
>> files on, even though I set it when I configured the superbuild. I must
>> have done that part wrong
>>
>> My configure line is:
>>
>>
>> cmake \
>> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
>> -DCMAKE_BUILD_TYPE=Release \
>> ...
>>
>> -DPARAVIEW_ENABLE_CATALYST=ON \
>> -DPARAVIEW_ENABLE_PYTHON=ON \
>> -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
>> -DPARAVIEW_BUILD_QT_GUI=OFF \
>> -DBUILD_TESTING=OFF \
>> -DVTK_USE_X=OFF \
>> ...
>>
>> -DVTK_OPENGL_HAS_OSMESA=ON \
>> -DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
>> -DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
>> ./ParaViewSuperbuild
>>
>>
>> and all of the other PARAVIEW* options seemed to pass through properly
>> when the superbuild made paraview. Any ideas why that option didn't pass
>> through?
>>
>>
>> Thanks -- I knew it had to be something really obvious!
>>
>>
>> Tim
>>
>>
>>
>> ------------------------------
>> *From:* Andy Bauer <andy.bauer at kitware.com>
>> *Sent:* Monday, May 9, 2016 4:43 PM
>> *To:* Gallagher, Timothy P
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Linking to Catalyst
>>
>> Hi Tim,
>>
>> Is the PV directory you're pointing to a build directory or an install
>> directory? If it's an install directory you'll need to enable
>> PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be
>> to try linking one of the Catalyst examples from
>> https://github.com/Kitware/ParaViewCatalystExampleCode and see how that
>> works for you. Another thing you could try is using a newer version of
>> CMake from https://cmake.org/download/. For the Linux x86_64 tarball,
>> you can just untar the executables from that and use directly.
>> <https://github.com/Kitware/ParaViewCatalystExampleCode>
>> GitHub - Kitware/ParaViewCatalystExampleCode: Example ...
>> <https://github.com/Kitware/ParaViewCatalystExampleCode>
>> github.com
>> ParaViewCatalystExampleCode - Example problems and snippets of code to
>> demonstrate ParaView's Catalyst.
>>
>>
>> Let us know if none of those ideas don't work for you.
>>
>> Best,
>> Andy
>>
>> On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <
>> tim.gallagher at gatech.edu> wrote:
>>
>>> Hello again,
>>>
>>>
>>> I'm (finally) trying to get Catalyst to successfully link to our
>>> application code on Excalibur (Cray, ARL HPC). I was able to build paraview
>>> and all of the dependencies thanks to help I've gotten on the list here in
>>> the past. However, when I try to link my code to it (and this is a code
>>> that works fine with Catalyst on other platforms), I get:
>>>
>>>
>>>  CMake Error at
>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120
>>> (message):
>>>    Requested modules not available:
>>>
>>>      vtkPVPythonCatalyst
>>>  Call Stack (most recent call first):
>>>
>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80
>>> (vtk_module_config)
>>>
>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49
>>> (include)
>>>    CMakeLists.txt:218 (find_package)
>>>
>>> The section in my CMakeLists that looks for paraview is:
>>>
>>> option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
>>> if(LESLIE_USE_COPROCESSING)
>>>   find_package(ParaView REQUIRED vtkPVPythonCatalyst
>>>                HINTS $ENV{PARAVIEW_CP_ROOT})
>>>   include(${PARAVIEW_USE_FILE})
>>>   include_directories(${PROJECT_SOURCE_DIR}/utils)
>>>   add_definitions(-DPARAVIEW_COPROCESSING)
>>> endif()
>>> mark_as_advanced(LESLIE_USE_COPROCESSING)
>>>
>>> and it doesn't seem to work. On other machines, I never needed to set
>>> the PARAVIEW_CP_ROOT variable, it always just found it. When I build my
>>> code, I point the paraview directory (where it finds the
>>> paraviewConfig.cmake file) to:
>>>
>>>
>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4
>>>
>>>
>>> and it seems to find it okay.
>>>
>>>
>>> Lastly, the vtkPVPythonCatalyst.so library is in the
>>> lib/paraview-4.4/site-packages/vtk directory and there is
>>> libvtkPVPythonCatalyst-pv4.4.so* and
>>> libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/
>>>
>>>
>>> I'm at a loss to understand why it is reporting the module is missing --
>>> did I miss something somewhere?
>>>
>>>
>>> Thanks as always,
>>>
>>>
>>> Tim
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160509/6330969c/attachment.html>

From tim.gallagher at gatech.edu  Tue May 10 00:35:19 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Tue, 10 May 2016 04:35:19 +0000
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <CAMaOp+E_ddh6WRD+T4BPQR2fA5JrjT9P2VbBUm3LZi=6SXE9Qg@mail.gmail.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>
 <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB26272549A8D549D8BFF588F79D700@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <CAMaOp+E_ddh6WRD+T4BPQR2fA5JrjT9P2VbBUm3LZi=6SXE9Qg@mail.gmail.com>
Message-ID: <BN3PR07MB26276DA9898D45E69D890BA69D710@BN3PR07MB2627.namprd07.prod.outlook.com>

Ah hah, the errors were being sent somewhere else and not caught properly by my submission script.


I found the error and now it works, I get my images and my VTK files. The only warnings now are:


24vtkCPTensorArrayTemplateIdE (0x23b4320): GetVoidPointer called. This is very expensive for vtkMappedDataArray subclasses, since the scalar array must be generated for each call. Consider using a vtkTypedDataArrayIterator instead.


which is something I can deal with later. I have to figure out what the vtkCPTensorArrayTemplate does exactly -- I believe that was something you had added when you took a look at our code awhile back. But it doesn't seem to matter for what we're doing now.


It feels good to close the ticket in our tracker about getting coprocessing on Crays -- it's been open since 2012.


Thanks again for all your help.


Tim

________________________________
From: Andy Bauer <andy.bauer at kitware.com>
Sent: Monday, May 9, 2016 10:41 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org
Subject: Re: [Paraview] Linking to Catalyst

Hi Tim,

I assume that writing out a data set works on other machines, correct? Can you try the gridwriter.py script at https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py to output the full data set? It should work with PV 4.4. Note that outputs a full data set every time step. I'm not sure about Python warnings or errors but the C++ warnings and errors will be sent to std::cerr instead of std::cout.
[https://gitlab.kitware.com/uploads/project/avatar/14/pvIcon-512x512.png]<https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py>

Examples/Catalyst/SampleScripts/gridwriter.py ? master ? ParaView / ParaView<https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py>
gitlab.kitware.com
Parallel Data Analysis and Visualization Application based on VTK.



Did you make the script with PV 4.4? The PV Python API has some changes (especially for rendering) between revisions. I think the best option is to just comment out the parts that are causing trouble.

If you're still having issues, maybe send your full script along with std::cout and std::cerr outputs so I can get a little deeper into the issues.

Good luck,
Andy

On Mon, May 9, 2016 at 6:14 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Okay, really close to finally crossing this off my list -- it's been on it for years.


I can get the code to generate images but it won't save data files. I don't get any errors and I get my images, just no VTK files. I have tried the default that the catalyst generator creates:


parallelMultiBlockDataSetWriter1 = servermanager.writers.XMLMultiBlockDataWriter(Input=slice1)

coprocessor.RegisterWriter(parallelMultiBlockDataSetWriter1, filename='slices_%t.vtm', freq=freq_file)


and I tried another form that the grid writer you've send me in the past used:


writer = coprocessor.CreateWriter(XMLMultiBlockDataWriter, filename='slices_%t.vtm', freq=freq_file)


in all cases, freq_file = 1000.


Neither one will output any vtk files.


Any thoughts?


Also, minor note but it is kind of annoying -- both the catalyst generator and the trace generator seem to do this, but they add commands that set attributes that are not part of the classes when run through the python script. For example, I had to comment out:


#      slice1Display.SelectInputVectors = ['CELLS', 'Velocity [m/s]']
#      slice1Display.WriteLog = ''


Any ideas why it does that? Or is there a way (and downfall) to just let it add attributes without manually calling add_attribute() each time?


Tim


________________________________
From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>>
Sent: Monday, May 9, 2016 5:13 PM
To: Andy Bauer

Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Linking to Catalyst


Yeah -- okay, pointing it to the build directory instead of the install made sure everything was found.


One step closer to getting this working on Cray.


Thanks,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Sent: Monday, May 9, 2016 4:54 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Linking to Catalyst

Hmm, that could be a bug in the superbuild. The superbuild arguments aren't all passed to the ParaView build itself and it could be that this option was missing for the PV specific build part. Instead of doing the whole build from scratch, I'd suggest you just search for the ParaViewConfig.cmake file to find where PV was actually built and just point to that.

On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Well shoot, it looks like I didn't build with the install development files on, even though I set it when I configured the superbuild. I must have done that part wrong


My configure line is:


cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
...

-DPARAVIEW_ENABLE_CATALYST=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DBUILD_TESTING=OFF \
-DVTK_USE_X=OFF \
...

-DVTK_OPENGL_HAS_OSMESA=ON \
-DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
-DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
./ParaViewSuperbuild


and all of the other PARAVIEW* options seemed to pass through properly when the superbuild made paraview. Any ideas why that option didn't pass through?


Thanks -- I knew it had to be something really obvious!


Tim



________________________________
From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Sent: Monday, May 9, 2016 4:43 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Linking to Catalyst

Hi Tim,

Is the PV directory you're pointing to a build directory or an install directory? If it's an install directory you'll need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be to try linking one of the Catalyst examples from https://github.com/Kitware/ParaViewCatalystExampleCode and see how that works for you. Another thing you could try is using a newer version of CMake from https://cmake.org/download/. For the Linux x86_64 tarball, you can just untar the executables from that and use directly.
[https://avatars3.githubusercontent.com/u/87549?v=3&s=400]<https://github.com/Kitware/ParaViewCatalystExampleCode>

GitHub - Kitware/ParaViewCatalystExampleCode: Example ...<https://github.com/Kitware/ParaViewCatalystExampleCode>
github.com<http://github.com>
ParaViewCatalystExampleCode - Example problems and snippets of code to demonstrate ParaView's Catalyst.



Let us know if none of those ideas don't work for you.

Best,
Andy

On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hello again,


I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link my code to it (and this is a code that works fine with Catalyst on other platforms), I get:


 CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):
   Requested modules not available:

     vtkPVPythonCatalyst
 Call Stack (most recent call first):
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)
   /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)
   CMakeLists.txt:218 (find_package)

The section in my CMakeLists that looks for paraview is:

option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
if(LESLIE_USE_COPROCESSING)
  find_package(ParaView REQUIRED vtkPVPythonCatalyst
               HINTS $ENV{PARAVIEW_CP_ROOT})
  include(${PARAVIEW_USE_FILE})
  include_directories(${PROJECT_SOURCE_DIR}/utils)
  add_definitions(-DPARAVIEW_COPROCESSING)
endif()
mark_as_advanced(LESLIE_USE_COPROCESSING)

and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:


/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4


and it seems to find it okay.


Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so<http://libvtkPVPythonCatalyst-pv4.4.so>* and libvtkPVPythonCatalystPython27D-pv4.4.so<http://libvtkPVPythonCatalystPython27D-pv4.4.so>* in lib/paraview-4.4/


I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?


Thanks as always,


Tim

_______________________________________________
Powered by www.kitware.com<http://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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/0fbf0065/attachment.html>

From asaad.sellmann at rwth-aachen.de  Tue May 10 03:04:54 2016
From: asaad.sellmann at rwth-aachen.de (Sellmann, Kai Asaad)
Date: Tue, 10 May 2016 07:04:54 +0000
Subject: [Paraview] Visualizing load paths
In-Reply-To: <1462274379341.43274@rwth-aachen.de>
References: <1462274379341.43274@rwth-aachen.de>
Message-ID: <1462863894054.37762@rwth-aachen.de>

Dear community,

I am currently trying to find a way to visualize load paths with results from static finite element analysis within solid structures. For this FE-analysis I use Altairs software suite (Hypermesh/Optistruct/Hyperview).

>From reading several different publications I know that there is an easy way to visualize the load path with the attached file with the use of TecPlot (Couldn't attach file because it exceeds 500 KB).
I received the attached file from Herbert Moldenhauer who relys on D.W. Kellys methods for visulaizing the load path within structures.

It would really help a lot to get more information about the background of the stream tracer filters, because I am currently struggeling to format the input properly. As far as I know I need a field of vectors ("The dataset must contain a field array with 3 Components. An Array of vectors (point-centered) is required"), but with the attached file for example I am not able to use the stream tracer filter.
I have exported my Stress tensor, my Nodal IDs and Nodaml Coordinates.

Your help would be greatly appreciated!!!
Thank you very much in advance!

Asaad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/edcdf4ac/attachment.html>

From info at seoaachen.de  Tue May 10 04:56:56 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Tue, 10 May 2016 10:56:56 +0200
Subject: [Paraview] Paraview compile download timeout
Message-ID: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>

Hello,

when compiling paraview I get the error:

  http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5 ("Timeout was reached")
http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027 
("HTTP response code said error")

any ideas?



From mathieu.westphal at kitware.com  Tue May 10 05:14:58 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Tue, 10 May 2016 11:14:58 +0200
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
Message-ID: <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>

We are experiencing timeout with midas currently.
Please recompile, it should work.



Mathieu Westphal

On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de> wrote:

> Hello,
>
> when compiling paraview I get the error:
>
>
> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
> ("Timeout was reached")
>
> http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
> ("HTTP response code said error")
>
> any ideas?
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/4871f8d2/attachment.html>

From cgunases at gmail.com  Tue May 10 05:23:29 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Tue, 10 May 2016 14:53:29 +0530
Subject: [Paraview] [ParaView] How to add thickness to each slice when
	generating a 3D model
Message-ID: <CAJFKOL3n3RCU=O0461Ro6c7aiA+Pog_z8mG9dMkneBuSe7nhCQ@mail.gmail.com>

Hello everyone,

My goal is to generate a 3D model of  human organ.

Suppose i have segmented images in each set(each slice is saved using
MatLab software).

So i want to know what are the options which paraview have in order to add
the thickness to each slice.

Your feedback is appreciated.



-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/b118213c/attachment.html>

From mgammar at outlook.fr  Tue May 10 06:11:00 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Tue, 10 May 2016 12:11:00 +0200
Subject: [Paraview] Combining multiple paraview xml files
Message-ID: <BAY182-W7324EB928B8FDAD08E6BD4D1710@phx.gbl>

Hello Miss, Mister,
I have some troubleregarding my paraview file: i must create an paraview type xml programm which calls other xml files each of them specialized in different datas (geometry, topology, et c...)What type of strucuture should i use for that?Thank you very much for your help.
Here is an exemple of what i did (it didn't work):
<?xml version="1.0"?><VTKFile type="PUnstructuredGrid" version="0.1" byte_order="BigEndian" compressor="vtkZLibDataCompressor">  <PUnstructuredGrid GhostLevel="0">     <PPointData Scalars="my_scalars">       <PDataArray type="Float32" Name="my_scalars"/>     </PPointData>                   <Piece Source="polyEx0.vtp"/><PCellData Scalars="cell_scalars" Normals="cell_normals">       <PDataArray type="Int32" Name="cell_scalars"/>       <PDataArray type="Float32" Name="cell_normals" NumberOfComponents="3"/>     </PCellData>    <PPoints>       <PDataArray type="Float32" NumberOfComponents="3" format="ascii"/>    </PPoints>     <Piece Source="polyEx1.vtp"/>  </PUnstructuredGrid></VTKFile>
this is supposed to take some pieces of information from my 2 other programs (polyex0 et polyex1) which are cubes, so in final i should have a cube with some properties of each of the 2 cubes.
Thank you very much for your help,Have a good week! 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/dce3a397/attachment.html>

From cgunases at gmail.com  Tue May 10 06:49:39 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Tue, 10 May 2016 16:19:39 +0530
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
In-Reply-To: <CAJFKOL3n3RCU=O0461Ro6c7aiA+Pog_z8mG9dMkneBuSe7nhCQ@mail.gmail.com>
References: <CAJFKOL3n3RCU=O0461Ro6c7aiA+Pog_z8mG9dMkneBuSe7nhCQ@mail.gmail.com>
Message-ID: <CAJFKOL29WZ-6MjJKO_YkPwOj7bcj5mMFLgEk=uEkvr1DXBqGNA@mail.gmail.com>

Also,i need to mention that segmented images are saved as Masks.

Kindly tell me, when using Paraview software should i have to use the
boundary or the mask of the segmented image for the purpose of building a
3D model. (kindly correct me, if i am wrong as i am new to Paraview)

Hope to hear from you soon.

Thank you.

On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com>
wrote:

> Hello everyone,
>
> My goal is to generate a 3D model of  human organ.
>
> Suppose i have segmented images in each set(each slice is saved using
> MatLab software).
>
> So i want to know what are the options which paraview have in order to add
> the thickness to each slice.
>
> Your feedback is appreciated.
>
>
>
> --
> Warm regards,
> Chathuri Gunasekera.
>



-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/92088430/attachment.html>

From info at seoaachen.de  Tue May 10 09:13:47 2016
From: info at seoaachen.de (Daniel Zuidinga)
Date: Tue, 10 May 2016 15:13:47 +0200
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
 <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
Message-ID: <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>

there are still problems?

Am 10.05.2016 um 11:14 schrieb Mathieu Westphal:
> We are experiencing timeout with midas currently.
> Please recompile, it should work.
>
>
>
> Mathieu Westphal
>
> On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de 
> <mailto:info at seoaachen.de>> wrote:
>
>     Hello,
>
>     when compiling paraview I get the error:
>
>     http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
>     ("Timeout was reached")
>     http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
>     ("HTTP response code said error")
>
>     any ideas?
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/da4c72a7/attachment.html>

From shawn.waldon at kitware.com  Tue May 10 09:48:15 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 10 May 2016 09:48:15 -0400
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
 <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
 <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
Message-ID: <CALSpCT3A0ONOwk6G=ha_TsYg2w_7=jaAXU1WTepxX0OpEBW0jA@mail.gmail.com>

Which version of CMake are you running?  We have had problems in the past
when using a CMake not built with SSL support pulling new data from midas.
The error messages from that generally look like this:


CMake Error at /apps/pkg/paraview-5.0/src/paraview-5.0/CMake/ExternalData.
cmake:749 (message):
  Object MD5=6c0dd882aa361431b95d7e2feb87fece not found at:


http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=6c0dd882aa361431b95d7e2feb87fece&algorithm=MD5
("Unsupported protocol")

http://www.paraview.org/files/ExternalData/MD5/6c0dd882aa361431b95d7e2feb87fece
("HTTP response code said error")
Call Stack (most recent call first):
  /apps/pkg/paraview-5.0/src/paraview-5.0/CMake/ExternalData.cmake:771
(_ExternalData_download_object)

If this is the problem you will need to download a new CMake that is built
with SSL support or build one yourself.

HTH,
Shawn

On Tue, May 10, 2016 at 9:13 AM, Daniel Zuidinga <info at seoaachen.de> wrote:

> there are still problems?
>
>
> Am 10.05.2016 um 11:14 schrieb Mathieu Westphal:
>
> We are experiencing timeout with midas currently.
> Please recompile, it should work.
>
>
>
> Mathieu Westphal
>
> On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de>
> wrote:
>
>> Hello,
>>
>> when compiling paraview I get the error:
>>
>>
>> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
>> ("Timeout was reached")
>>
>> http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
>> ("HTTP response code said error")
>>
>> any ideas?
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> 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
>>
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/f2e55c69/attachment.html>

From shawn.waldon at kitware.com  Tue May 10 10:09:03 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 10 May 2016 10:09:03 -0400
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <CALSpCT3A0ONOwk6G=ha_TsYg2w_7=jaAXU1WTepxX0OpEBW0jA@mail.gmail.com>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
 <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
 <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
 <CALSpCT3A0ONOwk6G=ha_TsYg2w_7=jaAXU1WTepxX0OpEBW0jA@mail.gmail.com>
Message-ID: <CALSpCT1hkeFai16mTTxRQLYokJTpTSZmheYmWgX6swjckUnTdg@mail.gmail.com>

Update: So I just tried to do a clean build of ParaView master.... I get
this error consistently and I know my CMake is built with SSL.  I'll look
into it.

Shawn

On Tue, May 10, 2016 at 9:48 AM, Shawn Waldon <shawn.waldon at kitware.com>
wrote:

> Which version of CMake are you running?  We have had problems in the past
> when using a CMake not built with SSL support pulling new data from midas.
> The error messages from that generally look like this:
>
>
> CMake Error at /apps/pkg/paraview-5.0/src/paraview-5.0/CMake/ExternalData.
> cmake:749 (message):
>   Object MD5=6c0dd882aa361431b95d7e2feb87fece not found at:
>
>
> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=6c0dd882aa361431b95d7e2feb87fece&algorithm=MD5
> ("Unsupported protocol")
>
> http://www.paraview.org/files/ExternalData/MD5/6c0dd882aa361431b95d7e2feb87fece
> ("HTTP response code said error")
> Call Stack (most recent call first):
>   /apps/pkg/paraview-5.0/src/paraview-5.0/CMake/ExternalData.cmake:771
> (_ExternalData_download_object)
>
> If this is the problem you will need to download a new CMake that is built
> with SSL support or build one yourself.
>
> HTH,
> Shawn
>
> On Tue, May 10, 2016 at 9:13 AM, Daniel Zuidinga <info at seoaachen.de>
> wrote:
>
>> there are still problems?
>>
>>
>> Am 10.05.2016 um 11:14 schrieb Mathieu Westphal:
>>
>> We are experiencing timeout with midas currently.
>> Please recompile, it should work.
>>
>>
>>
>> Mathieu Westphal
>>
>> On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de>
>> wrote:
>>
>>> Hello,
>>>
>>> when compiling paraview I get the error:
>>>
>>>
>>> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
>>> ("Timeout was reached")
>>>
>>> http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
>>> ("HTTP response code said error")
>>>
>>> any ideas?
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> 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
>>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/f60a00a9/attachment.html>

From andy.bauer at kitware.com  Tue May 10 10:18:20 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 10 May 2016 10:18:20 -0400
Subject: [Paraview] Linking to Catalyst
In-Reply-To: <BN3PR07MB26276DA9898D45E69D890BA69D710@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB2627A07A9486B0F846E956929D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+F46JuNiL5-96wjP=QDLjW4+nhQQr7wScPw6GTvyFcAeQ@mail.gmail.com>
 <BN3PR07MB2627E0C7DEDC0894525777799D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB26272549A8D549D8BFF588F79D700@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+E_ddh6WRD+T4BPQR2fA5JrjT9P2VbBUm3LZi=6SXE9Qg@mail.gmail.com>
 <BN3PR07MB26276DA9898D45E69D890BA69D710@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CAMaOp+H5rOOpFB19Z-HN4effm4mj=BPXOA=aBZU21pOK7CKsYg@mail.gmail.com>

Hi Tim,

If I remember correctly, that was VTK's suggested way at that time with
dealing with arrays that had different memory layouts than VTK used (and
yes, I think I may have put that in the code). In PV master now there's a
much better way of doing it (it's not in PV 5.0.1 but will be in PV 5.1).
If you use the vtkSOADataArrayTemplate class it will save on memory and be
more efficient. An example looks like:
    vtkSOADataArrayTemplate<double>* coords =
vtkSOADataArrayTemplate<double>::New();
    coords->SetNumberOfComponents(3);
    coords->SetNumberOfTuples(this->NumPoints);
    coords->SetArray(0, this->CoordsArray, this->NumPoints, false, true);
    coords->SetArray(1, this->CoordsArray+this->NumPoints, this->NumPoints,
false, true);
    coords->SetArray(2, this->CoordsArray+this->NumPoints*2,
this->NumPoints, false, true);

Here, CoordsArray is a double* that stores the coordinates in SOA form (x0,
x1, x2, ..., y0, y1, y2, ..., z0, z1, z2, ...) and NumPoints is the number
of points in the array (i.e. the length of the array divided by 3). Some
very fine details are at http://www.vtk.org/Wiki/VTK/Tutorials/DataArrays
if you want to read more about it but that's really for people writing VTK
filters and stuff like that.

As for the warning, you can comment that out in the code if it's generating
too much noise.

Best,
Andy

On Tue, May 10, 2016 at 12:35 AM, Gallagher, Timothy P <
tim.gallagher at gatech.edu> wrote:

> Ah hah, the errors were being sent somewhere else and not caught properly
> by my submission script.
>
>
> I found the error and now it works, I get my images and my VTK files. The
> only warnings now are:
>
>
> 24vtkCPTensorArrayTemplateIdE (0x23b4320): GetVoidPointer called. This is
> very expensive for vtkMappedDataArray subclasses, since the scalar array
> must be generated for each call. Consider using a vtkTypedDataArrayIterator
> instead.
>
>
> which is something I can deal with later. I have to figure out what the
> vtkCPTensorArrayTemplate does exactly -- I believe that was something you
> had added when you took a look at our code awhile back. But it doesn't seem
> to matter for what we're doing now.
>
>
> It feels good to close the ticket in our tracker about getting
> coprocessing on Crays -- it's been open since 2012.
>
> Thanks again for all your help.
>
>
> Tim
>
> ------------------------------
> *From:* Andy Bauer <andy.bauer at kitware.com>
> *Sent:* Monday, May 9, 2016 10:41 PM
> *To:* Gallagher, Timothy P
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Linking to Catalyst
>
> Hi Tim,
>
> I assume that writing out a data set works on other machines, correct? Can
> you try the gridwriter.py script at
> https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py
> to output the full data set? It should work with PV 4.4. Note that outputs
> a full data set every time step. I'm not sure about Python warnings or
> errors but the C++ warnings and errors will be sent to std::cerr instead of
> std::cout.
>
> <https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py>
> Examples/Catalyst/SampleScripts/gridwriter.py ? master ? ParaView /
> ParaView
> <https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/SampleScripts/gridwriter.py>
> gitlab.kitware.com
> Parallel Data Analysis and Visualization Application based on VTK.
>
>
> Did you make the script with PV 4.4? The PV Python API has some changes
> (especially for rendering) between revisions. I think the best option is to
> just comment out the parts that are causing trouble.
>
> If you're still having issues, maybe send your full script along with
> std::cout and std::cerr outputs so I can get a little deeper into the
> issues.
>
> Good luck,
> Andy
>
> On Mon, May 9, 2016 at 6:14 PM, Gallagher, Timothy P <
> tim.gallagher at gatech.edu> wrote:
>
>> Okay, really close to finally crossing this off my list -- it's been on
>> it for years.
>>
>>
>> I can get the code to generate images but it won't save data files. I
>> don't get any errors and I get my images, just no VTK files. I have tried
>> the default that the catalyst generator creates:
>>
>>
>> parallelMultiBlockDataSetWriter1 =
>> servermanager.writers.XMLMultiBlockDataWriter(Input=slice1)
>>
>> coprocessor.RegisterWriter(parallelMultiBlockDataSetWriter1,
>> filename='slices_%t.vtm', freq=freq_file)
>>
>>
>> and I tried another form that the grid writer you've send me in the past
>> used:
>>
>>
>> writer = coprocessor.CreateWriter(XMLMultiBlockDataWriter,
>> filename='slices_%t.vtm', freq=freq_file)
>>
>>
>> in all cases, freq_file = 1000.
>>
>>
>> Neither one will output any vtk files.
>>
>>
>> Any thoughts?
>>
>>
>> Also, minor note but it is kind of annoying -- both the catalyst
>> generator and the trace generator seem to do this, but they add commands
>> that set attributes that are not part of the classes when run through the
>> python script. For example, I had to comment out:
>>
>>
>> #      slice1Display.SelectInputVectors = ['CELLS', 'Velocity
>> [m/s]']
>>
>> #      slice1Display.WriteLog = ''
>>
>>
>> Any ideas why it does that? Or is there a way (and downfall) to just let
>> it add attributes without manually calling add_attribute() each time?
>>
>>
>> Tim
>>
>>
>> ------------------------------
>> *From:* ParaView <paraview-bounces at paraview.org> on behalf of Gallagher,
>> Timothy P <tim.gallagher at gatech.edu>
>> *Sent:* Monday, May 9, 2016 5:13 PM
>> *To:* Andy Bauer
>>
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Linking to Catalyst
>>
>>
>> Yeah -- okay, pointing it to the build directory instead of the install
>> made sure everything was found.
>>
>>
>> One step closer to getting this working on Cray.
>>
>>
>> Thanks,
>>
>>
>> Tim
>>
>>
>> ------------------------------
>> *From:* Andy Bauer <andy.bauer at kitware.com>
>> *Sent:* Monday, May 9, 2016 4:54 PM
>> *To:* Gallagher, Timothy P
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Linking to Catalyst
>>
>> Hmm, that could be a bug in the superbuild. The superbuild arguments
>> aren't all passed to the ParaView build itself and it could be that this
>> option was missing for the PV specific build part. Instead of doing the
>> whole build from scratch, I'd suggest you just search for the
>> ParaViewConfig.cmake file to find where PV was actually built and just
>> point to that.
>>
>> On Mon, May 9, 2016 at 4:50 PM, Gallagher, Timothy P <
>> tim.gallagher at gatech.edu> wrote:
>>
>>> Well shoot, it looks like I didn't build with the install development
>>> files on, even though I set it when I configured the superbuild. I must
>>> have done that part wrong
>>>
>>> My configure line is:
>>>
>>>
>>> cmake \
>>> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
>>> -DCMAKE_BUILD_TYPE=Release \
>>> ...
>>>
>>> -DPARAVIEW_ENABLE_CATALYST=ON \
>>> -DPARAVIEW_ENABLE_PYTHON=ON \
>>> -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
>>> -DPARAVIEW_BUILD_QT_GUI=OFF \
>>> -DBUILD_TESTING=OFF \
>>> -DVTK_USE_X=OFF \
>>> ...
>>>
>>> -DVTK_OPENGL_HAS_OSMESA=ON \
>>> -DOSMESA_INCLUDE_DIR:STRING="${INSTALLPATH}/osmesa/include" \
>>> -DOSMESA_LIBRARY:STRING="${INSTALLPATH}/osmesa/lib/libOSMesa.so" \
>>> ./ParaViewSuperbuild
>>>
>>>
>>> and all of the other PARAVIEW* options seemed to pass through properly
>>> when the superbuild made paraview. Any ideas why that option didn't pass
>>> through?
>>>
>>>
>>> Thanks -- I knew it had to be something really obvious!
>>>
>>>
>>> Tim
>>>
>>>
>>>
>>> ------------------------------
>>> *From:* Andy Bauer <andy.bauer at kitware.com>
>>> *Sent:* Monday, May 9, 2016 4:43 PM
>>> *To:* Gallagher, Timothy P
>>> *Cc:* paraview at paraview.org
>>> *Subject:* Re: [Paraview] Linking to Catalyst
>>>
>>> Hi Tim,
>>>
>>> Is the PV directory you're pointing to a build directory or an install
>>> directory? If it's an install directory you'll need to enable
>>> PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be
>>> to try linking one of the Catalyst examples from
>>> https://github.com/Kitware/ParaViewCatalystExampleCode and see how that
>>> works for you. Another thing you could try is using a newer version of
>>> CMake from https://cmake.org/download/. For the Linux x86_64 tarball,
>>> you can just untar the executables from that and use directly.
>>> <https://github.com/Kitware/ParaViewCatalystExampleCode>
>>> GitHub - Kitware/ParaViewCatalystExampleCode: Example ...
>>> <https://github.com/Kitware/ParaViewCatalystExampleCode>
>>> github.com
>>> ParaViewCatalystExampleCode - Example problems and snippets of code to
>>> demonstrate ParaView's Catalyst.
>>>
>>>
>>> Let us know if none of those ideas don't work for you.
>>>
>>> Best,
>>> Andy
>>>
>>> On Mon, May 9, 2016 at 3:58 PM, Gallagher, Timothy P <
>>> tim.gallagher at gatech.edu> wrote:
>>>
>>>> Hello again,
>>>>
>>>>
>>>> I'm (finally) trying to get Catalyst to successfully link to our
>>>> application code on Excalibur (Cray, ARL HPC). I was able to build paraview
>>>> and all of the dependencies thanks to help I've gotten on the list here in
>>>> the past. However, when I try to link my code to it (and this is a code
>>>> that works fine with Catalyst on other platforms), I get:
>>>>
>>>>
>>>>  CMake Error at
>>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120
>>>> (message):
>>>>    Requested modules not available:
>>>>
>>>>      vtkPVPythonCatalyst
>>>>  Call Stack (most recent call first):
>>>>
>>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80
>>>> (vtk_module_config)
>>>>
>>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49
>>>> (include)
>>>>    CMakeLists.txt:218 (find_package)
>>>>
>>>> The section in my CMakeLists that looks for paraview is:
>>>>
>>>> option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)
>>>> if(LESLIE_USE_COPROCESSING)
>>>>   find_package(ParaView REQUIRED vtkPVPythonCatalyst
>>>>                HINTS $ENV{PARAVIEW_CP_ROOT})
>>>>   include(${PARAVIEW_USE_FILE})
>>>>   include_directories(${PROJECT_SOURCE_DIR}/utils)
>>>>   add_definitions(-DPARAVIEW_COPROCESSING)
>>>> endif()
>>>> mark_as_advanced(LESLIE_USE_COPROCESSING)
>>>>
>>>> and it doesn't seem to work. On other machines, I never needed to set
>>>> the PARAVIEW_CP_ROOT variable, it always just found it. When I build my
>>>> code, I point the paraview directory (where it finds the
>>>> paraviewConfig.cmake file) to:
>>>>
>>>>
>>>> /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4
>>>>
>>>>
>>>> and it seems to find it okay.
>>>>
>>>>
>>>> Lastly, the vtkPVPythonCatalyst.so library is in the
>>>> lib/paraview-4.4/site-packages/vtk directory and there is
>>>> libvtkPVPythonCatalyst-pv4.4.so* and
>>>> libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/
>>>>
>>>>
>>>> I'm at a loss to understand why it is reporting the module is missing
>>>> -- did I miss something somewhere?
>>>>
>>>>
>>>> Thanks as always,
>>>>
>>>>
>>>> Tim
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/c0a3a538/attachment-0001.html>

From dkxls23 at gmail.com  Tue May 10 10:21:26 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Tue, 10 May 2016 17:21:26 +0300
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
 <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
 <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
Message-ID: <5731EE66.8020306@gmail.com>

As a workaround, you could disabled the testing
(-DBUILD_TESTING:BOOL=OFF).

-Armin





On 05/10/2016 04:13 PM, Daniel Zuidinga wrote:
> there are still problems?
>
> Am 10.05.2016 um 11:14 schrieb Mathieu Westphal:
>> We are experiencing timeout with midas currently.
>> Please recompile, it should work.
>>
>>
>>
>> Mathieu Westphal
>>
>> On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de
>> <mailto:info at seoaachen.de>> wrote:
>>
>>     Hello,
>>
>>     when compiling paraview I get the error:
>>
>>     http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
>>     ("Timeout was reached")
>>     http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
>>     ("HTTP response code said error")
>>
>>     any ideas?
>>
>>
>>     _______________________________________________
>>     Powered by www.kitware.com <http://www.kitware.com>
>>
>>     Visit other Kitware open-source projects at
>>     <http://www.kitware.com/opensource/opensource.html>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
>>
>>
>
>
>
> _______________________________________________
> 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
>

From shawn.waldon at kitware.com  Tue May 10 10:35:32 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 10 May 2016 10:35:32 -0400
Subject: [Paraview] Paraview compile download timeout
In-Reply-To: <CALSpCT1hkeFai16mTTxRQLYokJTpTSZmheYmWgX6swjckUnTdg@mail.gmail.com>
References: <e5dbc722-02a2-ae66-a9e5-3a9e65249571@seoaachen.de>
 <CAC2t4USLNiK4JPEZ3pPfJ7E+a6bPoKf=MppKTuzYwTNXHWyRYg@mail.gmail.com>
 <1a20fafe-0d95-b90a-713c-553574ff261e@seoaachen.de>
 <CALSpCT3A0ONOwk6G=ha_TsYg2w_7=jaAXU1WTepxX0OpEBW0jA@mail.gmail.com>
 <CALSpCT1hkeFai16mTTxRQLYokJTpTSZmheYmWgX6swjckUnTdg@mail.gmail.com>
Message-ID: <CALSpCT2Q8WEiC_wnDPR06Rp1tUErBRB22yHS5s8iG4HZMxQPzA@mail.gmail.com>

Looks like it is working again now.

Shawn

On Tue, May 10, 2016 at 10:09 AM, Shawn Waldon <shawn.waldon at kitware.com>
wrote:

> Update: So I just tried to do a clean build of ParaView master.... I get
> this error consistently and I know my CMake is built with SSL.  I'll look
> into it.
>
> Shawn
>
> On Tue, May 10, 2016 at 9:48 AM, Shawn Waldon <shawn.waldon at kitware.com>
> wrote:
>
>> Which version of CMake are you running?  We have had problems in the past
>> when using a CMake not built with SSL support pulling new data from midas.
>> The error messages from that generally look like this:
>>
>>
>> CMake Error at /apps/pkg/paraview-5.0/src/paraview-5.0/CMake
>> /ExternalData.cmake:749 (message):
>>   Object MD5=6c0dd882aa361431b95d7e2feb87fece not found at:
>>
>>
>> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=6c0dd882aa361431b95d7e2feb87fece&algorithm=MD5
>> ("Unsupported protocol")
>>
>> http://www.paraview.org/files/ExternalData/MD5/6c0dd882aa361431b95d7e2feb87fece
>> ("HTTP response code said error")
>> Call Stack (most recent call first):
>>   /apps/pkg/paraview-5.0/src/paraview-5.0/CMake/ExternalData.cmake:771
>> (_ExternalData_download_object)
>>
>> If this is the problem you will need to download a new CMake that is
>> built with SSL support or build one yourself.
>>
>> HTH,
>> Shawn
>>
>> On Tue, May 10, 2016 at 9:13 AM, Daniel Zuidinga <info at seoaachen.de>
>> wrote:
>>
>>> there are still problems?
>>>
>>>
>>> Am 10.05.2016 um 11:14 schrieb Mathieu Westphal:
>>>
>>> We are experiencing timeout with midas currently.
>>> Please recompile, it should work.
>>>
>>>
>>>
>>> Mathieu Westphal
>>>
>>> On Tue, May 10, 2016 at 10:56 AM, Daniel Zuidinga <info at seoaachen.de>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> when compiling paraview I get the error:
>>>>
>>>>
>>>> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=534871355b0e4de0d6b727c8ed317027&algorithm=MD5
>>>> ("Timeout was reached")
>>>>
>>>> http://www.paraview.org/files/ExternalData/MD5/534871355b0e4de0d6b727c8ed317027
>>>> ("HTTP response code said error")
>>>>
>>>> any ideas?
>>>>
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> <http://www.kitware.com/opensource/opensource.html>
>>>> 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
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/118d2f4b/attachment.html>

From kmorel at sandia.gov  Tue May 10 12:20:55 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 10 May 2016 16:20:55 +0000
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
Message-ID: <9FD2921C-2243-4BE3-A1A3-599AE313360D@sandia.gov>

I think we need more information before we can answer your questions.

Your first question was how to ?add thickness? to image slices. If you have image slices, you usually want to load them in as a 3D stack and treat them like a volume. The spacing between the slices is typically specified by the data file itself or by an option in the reader (of which there are almost 100 different types in ParaView). So how you do that depends on your data format.

You simply said that your data comes from MATLAB. That?s not very specific, since it is possible to output lots of different types of files from MATLAB. If you are not doing it yet, you might consider this MATLAB module that writes out VTK files (which ParaView handles very well): http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format . I haven?t used it myself (I use MATLAB very infrequently), but it looks pretty full featured. You might want to check that out.

You also mentioned that the image segmentation is represented by masks. The easiest way to deal with that is probably to use the Threshold filter to remove all cells that are masked out.

-Ken


From: ParaView <paraview-bounces at paraview.org> on behalf of Chathuri Gunasekera <cgunases at gmail.com>
Date: Tuesday, May 10, 2016 at 4:49 AM
To: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Also,i need to mention that segmented images are saved as Masks.

Kindly tell me, when using Paraview software should i have to use the boundary or the mask of the segmented image for the purpose of building a 3D model. (kindly correct me, if i am wrong as i am new to Paraview)

Hope to hear from you soon.

Thank you.

On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>> wrote:
Hello everyone,

My goal is to generate a 3D model of  human organ.

Suppose i have segmented images in each set(each slice is saved using MatLab software).

So i want to know what are the options which paraview have in order to add the thickness to each slice.

Your feedback is appreciated.



--
Warm regards,
Chathuri Gunasekera.



--
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/895f3837/attachment.html>

From samuelkey at bresnan.net  Tue May 10 12:21:43 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Tue, 10 May 2016 10:21:43 -0600
Subject: [Paraview] Combining multiple paraview xml files
In-Reply-To: <BAY182-W7324EB928B8FDAD08E6BD4D1710@phx.gbl>
References: <BAY182-W7324EB928B8FDAD08E6BD4D1710@phx.gbl>
Message-ID: <0bc66a01-12d8-068b-f123-3dc7c13270ec@bresnan.net>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/192ae18f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fmafxc.mesh.pvd
Type: text/xml
Size: 674 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/192ae18f/attachment.xml>

From kmorel at sandia.gov  Tue May 10 12:34:03 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 10 May 2016 16:34:03 +0000
Subject: [Paraview] Combining multiple paraview xml files
Message-ID: <A8551A6E-2B9A-45F9-AD98-57A885AEB0A2@sandia.gov>

The ParaView Data (PVD) file format might do what you want:

http://www.paraview.org/Wiki/ParaView/Data_formats#PVD_File_Format

-Ken


From: ParaView <paraview-bounces at paraview.org> on behalf of Marwen Gammar <mgammar at outlook.fr>
Date: Tuesday, May 10, 2016 at 4:11 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Combining multiple paraview xml files

Hello Miss, Mister,

I have some troubleregarding my paraview file: i must create an paraview type xml programm which calls other xml files each of them specialized in different datas (geometry, topology, et c...)
What type of strucuture should i use for that?
Thank you very much for your help.

Here is an exemple of what i did (it didn't work):

<?xml version="1.0"?>
<VTKFile type="PUnstructuredGrid" version="0.1" byte_order="BigEndian" compressor="vtkZLibDataCompressor">
  <PUnstructuredGrid GhostLevel="0">
     <PPointData Scalars="my_scalars">
       <PDataArray type="Float32" Name="my_scalars"/>
     </PPointData>
    <Piece Source="polyEx0.vtp"/>
<PCellData Scalars="cell_scalars" Normals="cell_normals">
       <PDataArray type="Int32" Name="cell_scalars"/>
       <PDataArray type="Float32" Name="cell_normals" NumberOfComponents="3"/>
     </PCellData>
    <PPoints>
       <PDataArray type="Float32" NumberOfComponents="3" format="ascii"/>
    </PPoints>
    <Piece Source="polyEx1.vtp"/>
  </PUnstructuredGrid>
</VTKFile>

this is supposed to take some pieces of information from my 2 other programs (polyex0 et polyex1) which are cubes, so in final i should have a cube with some properties of each of the 2 cubes.

Thank you very much for your help,
Have a good week!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/e42b9ced/attachment.html>

From kmorel at sandia.gov  Tue May 10 14:38:17 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 10 May 2016 18:38:17 +0000
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
Message-ID: <635E5A68-4AFE-489B-AA95-15613707EF02@sandia.gov>

Chathuri Gunasekera,

(Responding back to ParaView list to allow others to see and comment.)

1. I?m not sure why you are not see the 3 holes you expect in your mask. It looks like most of your process is building the data in MATLAB. Perhaps something is going wrong there. ParaView must be recognizing the mask since the region outside of the external boundary is removed. Are you sure your three holds are represented in the mask?

2. It sounds like you are finding the mask boundary in a slice. A slice is by definition contained in a 2D plane. You can restore the 2mm thickness manually by running the Extract Surface filter and then the Linear Extrusion filter.

-Ken

From: Chathuri Gunasekera <cgunases at gmail.com>
Date: Tuesday, May 10, 2016 at 12:03 PM
To: Kenneth Moreland <kmorel at sandia.gov>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi Ken,

Your  detailed description is very much appreciated. Thank you so much.

Kindly note that following is what i have done in MatLab :
a. Segmented images as Masks (just x,y cordinates)
b. Saved as a .mat file
c. Then append z coordinate( z coordinate is the slice thickness which, each slice has a thickness of 2mm) to the above said mask. Hence, now the image is 3D (saved as .mat file)
d. Convert the 3D image into real world coordinates . So x,y,z all are in mm now.  (saved as .mat file)
e. Since i have about 8 sets and about 50 images per set. Then find the smallest dimension for a particular set.
f. Crop the image (saved as .mat file)
g. Stack the image (saved as .mat file)
h. Finally convert the .mat file to .vtk file
i. Then open the .vtk files in Paraview
Let me send you 2 outputs which i have obtained so far

1. segmented masked images. I prefer this method because this image looks close to my expectation(i expect a 3D model). Also i have 3 more masks which represent 3 more features inside the big mask (meaning i expect 3 holes inside the big image). But i simply cannot see the 3 holes inside this big mask. What mistake i am doing here? Why can't i see the 3 holes inside the big mask.

2. segmented masked --> converted RGB image to binary and then find the boundary of the mask. So the reason for why i asked the thickness is that for this output i can't see the 2mm thickness .

Kindly note that in order to obtain above output i have used couple of masks(slices) and  stacked them together.

Your assistance is really appreciated here as i was struggling to get a proper 3D model for sometime now and all my efforts are not succeeded yet.

Thank you.

--
Warm regards,
Chathuri Gunasekera.



On Tue, May 10, 2016 at 9:50 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
I think we need more information before we can answer your questions.

Your first question was how to ?add thickness? to image slices. If you have image slices, you usually want to load them in as a 3D stack and treat them like a volume. The spacing between the slices is typically specified by the data file itself or by an option in the reader (of which there are almost 100 different types in ParaView). So how you do that depends on your data format.

You simply said that your data comes from MATLAB. That?s not very specific, since it is possible to output lots of different types of files from MATLAB. If you are not doing it yet, you might consider this MATLAB module that writes out VTK files (which ParaView handles very well): http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format . I haven?t used it myself (I use MATLAB very infrequently), but it looks pretty full featured. You might want to check that out.

You also mentioned that the image segmentation is represented by masks. The easiest way to deal with that is probably to use the Threshold filter to remove all cells that are masked out.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 4:49 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Also,i need to mention that segmented images are saved as Masks.

Kindly tell me, when using Paraview software should i have to use the boundary or the mask of the segmented image for the purpose of building a 3D model. (kindly correct me, if i am wrong as i am new to Paraview)

Hope to hear from you soon.

Thank you.

On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>> wrote:
Hello everyone,

My goal is to generate a 3D model of  human organ.

Suppose i have segmented images in each set(each slice is saved using MatLab software).

So i want to know what are the options which paraview have in order to add the thickness to each slice.

Your feedback is appreciated.



--
Warm regards,
Chathuri Gunasekera.



--
Warm regards,
Chathuri Gunasekera.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/632aec5c/attachment.html>

From cgunases at gmail.com  Tue May 10 22:31:19 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Wed, 11 May 2016 08:01:19 +0530
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
In-Reply-To: <635E5A68-4AFE-489B-AA95-15613707EF02@sandia.gov>
References: <635E5A68-4AFE-489B-AA95-15613707EF02@sandia.gov>
Message-ID: <CAJFKOL1dXZ5o0hy+iJ7EtWu2AesppVb+f-36vJrTd+z_uf9PJA@mail.gmail.com>

Hi to all,

@ Ken, thank you so much for your response. Really admire it.

1. Yes, i am 100% certain that all the masks are called in.
But let me be more into detail.
Basically, i have: 1 big mask and 3 patches (which are also saved as
masks). Sorry Ken, i think i should have use patch instead of hole [ this
patch eventually represent some special features{but these features
eventually build up as tubes when it comes to a 3D model.} in a human organ
as i am trying to model a human organ itself ]. ANyhow, i am sorry if i
make you confuse.

You're right Ken, most of the stuff is done in MatLab but all the work
looks error-free(because it works fine atleast in MatLab). But i am skeptic
of one thing. Should i have to have a transparent big mask in order to see
the 3 patches inside the big mask?  Is that why , i don't see the patches ?
Kindly guide me.

2. I will try that out too.

Anyhow, thank you so much for your detailed response Ken. That is a great
help.


-- 
Warm regards,
Chathuri Gunasekera.




On Wed, May 11, 2016 at 12:08 AM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> Chathuri Gunasekera,
>
>
>
> (Responding back to ParaView list to allow others to see and comment.)
>
>
>
> 1. I?m not sure why you are not see the 3 holes you expect in your mask.
> It looks like most of your process is building the data in MATLAB. Perhaps
> something is going wrong there. ParaView must be recognizing the mask since
> the region outside of the external boundary is removed. Are you sure your
> three holds are represented in the mask?
>
>
>
> 2. It sounds like you are finding the mask boundary in a slice. A slice is
> by definition contained in a 2D plane. You can restore the 2mm thickness
> manually by running the Extract Surface filter and then the Linear
> Extrusion filter.
>
>
>
> -Ken
>
>
>
> *From: *Chathuri Gunasekera <cgunases at gmail.com>
> *Date: *Tuesday, May 10, 2016 at 12:03 PM
> *To: *Kenneth Moreland <kmorel at sandia.gov>
>
> *Subject: *[EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to
> each slice when generating a 3D model
>
>
>
> Hi Ken,
>
>
>
> Your  detailed description is very much appreciated. Thank you so much.
>
>
>
> Kindly note that following is what i have done in MatLab :
>
> a. Segmented images as Masks (just x,y cordinates)
>
> b. Saved as a .mat file
>
> c. Then append z coordinate( z coordinate is the slice thickness which,
> each slice has a thickness of 2mm) to the above said mask. Hence, now the
> image is 3D (saved as .mat file)
>
> d. Convert the 3D image into real world coordinates . So x,y,z all are in
> mm now.  (saved as .mat file)
>
> e. Since i have about 8 sets and about 50 images per set. Then find the
> smallest dimension for a particular set.
>
> f. Crop the image (saved as .mat file)
>
> g. Stack the image (saved as .mat file)
>
> h. Finally convert the .mat file to .vtk file
>
> i. Then open the .vtk files in Paraview
>
> Let me send you 2 outputs which i have obtained so far
>
>
>
> 1. segmented masked images. I prefer this method because this image looks
> close to my expectation(i expect a 3D model). Also i have 3 more masks
> which represent 3 more features inside the big mask (meaning i expect 3
> holes inside the big image). But i simply cannot see the 3 holes inside
> this big mask. What mistake i am doing here? Why can't i see the 3 holes
> inside the big mask.
>
>
>
> 2. segmented masked --> converted RGB image to binary and then find the
> boundary of the mask. So the reason for why i asked the thickness is that
> for this output i can't see the 2mm thickness .
>
>
>
> Kindly note that in order to obtain above output i have used couple of
> masks(slices) and  stacked them together.
>
>
>
> Your assistance is really appreciated here as i was struggling to get a
> proper 3D model for sometime now and all my efforts are not succeeded yet.
>
>
>
> Thank you.
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
>
>
> On Tue, May 10, 2016 at 9:50 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>
> I think we need more information before we can answer your questions.
>
>
>
> Your first question was how to ?add thickness? to image slices. If you
> have image slices, you usually want to load them in as a 3D stack and treat
> them like a volume. The spacing between the slices is typically specified
> by the data file itself or by an option in the reader (of which there are
> almost 100 different types in ParaView). So how you do that depends on your
> data format.
>
>
>
> You simply said that your data comes from MATLAB. That?s not very
> specific, since it is possible to output lots of different types of files
> from MATLAB. If you are not doing it yet, you might consider this MATLAB
> module that writes out VTK files (which ParaView handles very well):
> http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format
> . I haven?t used it myself (I use MATLAB very infrequently), but it looks
> pretty full featured. You might want to check that out.
>
>
>
> You also mentioned that the image segmentation is represented by masks.
> The easiest way to deal with that is probably to use the Threshold filter
> to remove all cells that are masked out.
>
>
>
> -Ken
>
>
>
>
>
> *From: *ParaView <paraview-bounces at paraview.org> on behalf of Chathuri
> Gunasekera <cgunases at gmail.com>
> *Date: *Tuesday, May 10, 2016 at 4:49 AM
> *To: *ParaView <paraview at paraview.org>
> *Subject: *[EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to
> each slice when generating a 3D model
>
>
>
> Also,i need to mention that segmented images are saved as Masks.
>
>
>
> Kindly tell me, when using Paraview software should i have to use the
> boundary or the mask of the segmented image for the purpose of building a
> 3D model. (kindly correct me, if i am wrong as i am new to Paraview)
>
>
>
> Hope to hear from you soon.
>
>
>
> Thank you.
>
>
>
> On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com>
> wrote:
>
> Hello everyone,
>
>
>
> My goal is to generate a 3D model of  human organ.
>
>
>
> Suppose i have segmented images in each set(each slice is saved using
> MatLab software).
>
>
>
> So i want to know what are the options which paraview have in order to add
> the thickness to each slice.
>
>
>
> Your feedback is appreciated.
>
>
>
>
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/0b261209/attachment.html>

From fabidi89 at vt.edu  Tue May 10 23:37:57 2016
From: fabidi89 at vt.edu (Faiz Abidi)
Date: Tue, 10 May 2016 23:37:57 -0400
Subject: [Paraview] Paraview in CAVE and remote rendering
Message-ID: <CAA7GnUmU02yvMQfVwX8VOG9t6SdvXEHUzTpx=KSGUc7ipu+07w@mail.gmail.com>

Hi Guys,

Wondering how should I go about remote rendering and visualization in a
CAVE. I can visualize in a CAVE using an on-premise server physically
connected to the projectors driving the CAVE, and using my laptop as the
client. But how would I pass a PVX file if this server is somewhere on
Amazon etc?
-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160510/feea965b/attachment.html>

From svenkramer40 at gmail.com  Wed May 11 02:05:11 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Wed, 11 May 2016 08:05:11 +0200
Subject: [Paraview] ParaviewWeb with remote, distributed data
In-Reply-To: <CABObKxe6eq5HkNovrW8J-ytG-yUT09FF0xhzOaLtHyM2Bf3P+g@mail.gmail.com>
References: <CAJZHu4RMK_PaMmUN3Mv-u1Kor8ZY_6Qvq8LbtGDibhK73rtqzQ@mail.gmail.com>
 <CABObKxeRa_hA1GQC_RhHL_1hW6_+zzPwrv8-ABZdh8sgxzdVfw@mail.gmail.com>
 <CAJZHu4Rc3QXCopX+DBtCNuajG4vr6AYR1hEKwrV9FetL8drkuQ@mail.gmail.com>
 <CABObKxe6eq5HkNovrW8J-ytG-yUT09FF0xhzOaLtHyM2Bf3P+g@mail.gmail.com>
Message-ID: <CAJZHu4SM0xJ8R9ucPe5jQ30a2pUNq-=doFHt2xKD4vrSiEFGBQ@mail.gmail.com>

I could improve the lag by either distributing the MPI processes to another
node or using just a single process. I think the framerate is fine for
larger datasets. Only for my tiny (~20 triangles) dataset I was slightly
disappointed, because I expected more fluent user interaction.

Back to my initial, second question on live rendering of incoming data: I
found that this is probably best handled by Catalyst, isn't it? Then I will
try study how to include the Catalyst Adaptors and Pipelines into my code,
and I will probably come back with a new post asking about some Catalyst
details.

Thank you
Sven

2016-05-10 0:11 GMT+02:00 Sebastien Jourdain <sebastien.jourdain at kitware.com
>:

> Hi Scen,
>
> that's a correct way, but I'm not sure to know why it is that much slower.
> Wondering if all the pvserver are fighting for the same GPU and hence
> waiting more than anything... ?
> You may be able to change the remote rendering threshold to make sure only
> pvpython is doing the rendering.
>
> Seb
>
> On Mon, May 9, 2016 at 3:34 PM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Hello Seb,
>> I got a working connection from pv_web_visualizer.py to a couple of
>> pvservers (started with mpirun on <hostname>) by just giving "--ds-host
>> <hostname> --ds-port 11111" from the link you mentioned. Is this correct,
>> without --rs-host? It is working in principle, but the renderview update
>> rate is not more than 2 updates/second for a tiny datasource even when
>> everything is running on the same machine.
>>
>> Thank you
>> Sven
>>
>> 2016-05-06 22:26 GMT+02:00 Sebastien Jourdain <
>> sebastien.jourdain at kitware.com>:
>>
>>> Hi Sven,
>>>
>>> 1) Yes, assuming you are using pv_web_visualizer.py you can look here:
>>>
>>>
>>> https://github.com/Kitware/ParaView/blob/master/Web/Applications/Visualizer/server/pv_web_visualizer.py#L18-L28
>>>
>>> 2) The server can push notification to the client. Need to slightly edit
>>> the client and server to match your needs.
>>>
>>> Seb
>>>
>>>
>>> On Fri, May 6, 2016 at 2:17 PM, Sven Kramer <svenkramer40 at gmail.com>
>>> wrote:
>>>
>>>> Dear all,
>>>> I am currently running a VTK application, which is visualizing large
>>>> grids distributed on a MPI cluster.
>>>> My task is to migrate this application to the Web. But I cannot manage
>>>> more than what is described at
>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/quick_start,
>>>> that is I can serve a local data directory through the provided webapps.
>>>>
>>>> I have two essential questions that stop me from getting started:
>>>> 1) How do I connect the pvpython server to remote data/render servers
>>>> just like I can do in Paraview?
>>>> 2) All ParaviewWeb examples seem to react on webclient requests. Our
>>>> application is processing data as they come in, and also the visualization
>>>> pipeline is frequently updated depending on an automatic analysis of the
>>>> arriving data. Can the newly rendered datasets be pushed to the webclient,
>>>> or does the webclient have to poll for available datasets?
>>>>
>>>> Thank you
>>>> Sven
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/b700751d/attachment.html>

From benson.muite at ut.ee  Wed May 11 04:27:12 2016
From: benson.muite at ut.ee (Benson Muite)
Date: Wed, 11 May 2016 11:27:12 +0300
Subject: [Paraview] ISC 2016 visualization showcase
Message-ID: <515efd76-94b6-d065-f774-2d0e369c6244@ut.ee>

New for this year is a visualization showcase for ISC 2016. Outstanding
submissions from both expert in visualizations and novices are
encouraged. Please submit visualizations by 21 May. More information at:
http://woiv.org/

From arsh840 at gmail.com  Wed May 11 05:54:32 2016
From: arsh840 at gmail.com (Arshpreet Singh)
Date: Wed, 11 May 2016 15:24:32 +0530
Subject: [Paraview] Paraview build from source error
Message-ID: <CAAstK2GHZ72U+-v_bea0K8+saodb=6c-xb3s0tKZS5Zb3p0oTw@mail.gmail.com>

I am trying to install Paraview from source but after running make
command in get smd5 checksum error at 70% of compilation.


Is this error from Network side?

[ 70%] Built target vtkPVServerManagerApplicationPythonD
[ 70%] Built target vtkPVCatalystPythonD
[ 70%] Built target vtkPVPythonCatalystPythonD
[ 70%] Built target vtkPVPythonCatalystPython
[ 70%] Generating
/home/metal-machine/paraview/Paraview-bin/ExternalData/Testing/Data/Baseline/TileDisplayScatterPlot-2x2.png
-- Fetching "http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=fc79079ddfbbbbe25b4050f9c349c80b&algorithm=MD5"
-- [download 100% complete]
-- Fetching "http://www.paraview.org/files/ExternalData/MD5/fc79079ddfbbbbe25b4050f9c349c80b"
CMake Error at /home/metal-machine/paraview/ParaView/CMake/ExternalData.cmake:749
(message):
  Object MD5=fc79079ddfbbbbe25b4050f9c349c80b not found at:

    http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=fc79079ddfbbbbe25b4050f9c349c80b&algorithm=MD5
("Unsupported protocol")
    http://www.paraview.org/files/ExternalData/MD5/fc79079ddfbbbbe25b4050f9c349c80b
("HTTP response code said error")
Call Stack (most recent call first):
  /home/metal-machine/paraview/ParaView/CMake/ExternalData.cmake:771
(_ExternalData_download_object)



make[2]: *** [ExternalData/Testing/Data/Baseline/TileDisplayScatterPlot-2x2.png.md5-stamp]
Error 1
make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2
make: *** [all] Error 2



-- 

Thanks
Arshpreet Singh

I am Sikh boy, Learning by doing and Learning by teaching is my religion.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

From dennis_conklin at goodyear.com  Wed May 11 08:31:26 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 11 May 2016 12:31:26 +0000
Subject: [Paraview] Dropping support for OpenGL1 in ParaView 5.2
Message-ID: <CY1PR07MB2506E97694DF47E551491D429F720@CY1PR07MB2506.namprd07.prod.outlook.com>

Utkarsh,

As we are having trouble running the latest versions of Paraview due to our antiquated graphics libraries, is there anything special that has to be done to be run the legacy rendering backend?

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/fc8b9c87/attachment.html>

From asaad.sellmann at rwth-aachen.de  Wed May 11 08:44:27 2016
From: asaad.sellmann at rwth-aachen.de (Sellmann, Kai Asaad)
Date: Wed, 11 May 2016 12:44:27 +0000
Subject: [Paraview] Visualizing load paths
In-Reply-To: <1462863894054.37762@rwth-aachen.de>
References: <1462274379341.43274@rwth-aachen.de>,
 <1462863894054.37762@rwth-aachen.de>
Message-ID: <1462970667534.86624@rwth-aachen.de>

Dear community,

I am currently trying to find a way to visualize load paths with results from static finite element analysis within solid structures. For this FE-analysis I use Altairs software suite (Hypermesh/Optistruct/Hyperview).
It would really help a lot to get more information about the background of the stream tracer filters, because I am currently struggeling to format the input properly. As far as I know I need a field of vectors ("The dataset must contain a field array with 3 Components. An Array of vectors (point-centered) is required"), but I am not able to format my FE Output into a proper order so that paraview is able to apply stream tracers.
I have exported my Stress tensor, my Nodal IDs and Nodal Coordinates.

Your help would be greatly appreciated!!!
Thank you very much in advance!

Asaad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/557a70ab/attachment.html>

From utkarsh.ayachit at kitware.com  Wed May 11 08:58:18 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 11 May 2016 08:58:18 -0400
Subject: [Paraview] Dropping support for OpenGL1 in ParaView 5.2
In-Reply-To: <CY1PR07MB2506E97694DF47E551491D429F720@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506E97694DF47E551491D429F720@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CADHSJjA1J7ZLcLmojbYJmG1+0vCzeJ=R9unTFC-x8bti8d2jSg@mail.gmail.com>

You have to build ParaView from source with VTK_RENDERING_BACKEND
cmake variable set to OpenGL. Currently, we don't distribute binaries
legacy OpenGL backend.

On Wed, May 11, 2016 at 8:31 AM, Dennis Conklin
<dennis_conklin at goodyear.com> wrote:
> Utkarsh,
>
>
>
> As we are having trouble running the latest versions of Paraview due to our
> antiquated graphics libraries, is there anything special that has to be done
> to be run the legacy rendering backend?
>
>
>
> Dennis
>
>
> _______________________________________________
> 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
>

From utkarsh.ayachit at kitware.com  Wed May 11 09:00:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 11 May 2016 09:00:42 -0400
Subject: [Paraview] Paraview build from source error
In-Reply-To: <CAAstK2GHZ72U+-v_bea0K8+saodb=6c-xb3s0tKZS5Zb3p0oTw@mail.gmail.com>
References: <CAAstK2GHZ72U+-v_bea0K8+saodb=6c-xb3s0tKZS5Zb3p0oTw@mail.gmail.com>
Message-ID: <CADHSJjAR4eVuRzPNcUGxMwK2Lgvxv=_bdXo76tXjbJP1TR-=mg@mail.gmail.com>

Such errors happen when downloading test data and baselines due to
either server or network issues. If you are not running tests, simply
turn OFF BUILD_TESTING CMake flag. Alternatively try again after some
time. If is was due to server issues, it typically recovers.

On Wed, May 11, 2016 at 5:54 AM, Arshpreet Singh <arsh840 at gmail.com> wrote:
> I am trying to install Paraview from source but after running make
> command in get smd5 checksum error at 70% of compilation.
>
>
> Is this error from Network side?
>
> [ 70%] Built target vtkPVServerManagerApplicationPythonD
> [ 70%] Built target vtkPVCatalystPythonD
> [ 70%] Built target vtkPVPythonCatalystPythonD
> [ 70%] Built target vtkPVPythonCatalystPython
> [ 70%] Generating
> /home/metal-machine/paraview/Paraview-bin/ExternalData/Testing/Data/Baseline/TileDisplayScatterPlot-2x2.png
> -- Fetching "http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=fc79079ddfbbbbe25b4050f9c349c80b&algorithm=MD5"
> -- [download 100% complete]
> -- Fetching "http://www.paraview.org/files/ExternalData/MD5/fc79079ddfbbbbe25b4050f9c349c80b"
> CMake Error at /home/metal-machine/paraview/ParaView/CMake/ExternalData.cmake:749
> (message):
>   Object MD5=fc79079ddfbbbbe25b4050f9c349c80b not found at:
>
>     http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download&checksum=fc79079ddfbbbbe25b4050f9c349c80b&algorithm=MD5
> ("Unsupported protocol")
>     http://www.paraview.org/files/ExternalData/MD5/fc79079ddfbbbbe25b4050f9c349c80b
> ("HTTP response code said error")
> Call Stack (most recent call first):
>   /home/metal-machine/paraview/ParaView/CMake/ExternalData.cmake:771
> (_ExternalData_download_object)
>
>
>
> make[2]: *** [ExternalData/Testing/Data/Baseline/TileDisplayScatterPlot-2x2.png.md5-stamp]
> Error 1
> make[1]: *** [CMakeFiles/ParaViewData.dir/all] Error 2
> make: *** [all] Error 2
>
>
>
> --
>
> Thanks
> Arshpreet Singh
>
> I am Sikh boy, Learning by doing and Learning by teaching is my religion.
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> 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

From cgunases at gmail.com  Wed May 11 09:27:23 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Wed, 11 May 2016 18:57:23 +0530
Subject: [Paraview]  Only 1 mask is shown up in the model,
	what happened to the rest?
Message-ID: <CAJFKOL2BA-UE4Oed4+YgG-BykV5hLh8W5HGKJZe8U-O2JOiM4Q@mail.gmail.com>

Hi all,

Suppose i have saved, segmented masks in separate folders.
say,
mask 1 (the large mask) --> folder_1
mask 2 (small mask which needs to be located inside mask 1)  --> folder_2
mask 3 (small mask which needs to be located inside mask 1)  --> folder_3

Then all three masks are called in and eventually stacked the images and
called in from ParaView.

The question is i only see the mask 1.
Is it because mask 1,2 &3 are in same color?

 Can't i give different colors to different masks?

Or else what would be the remedy to see mask 2 & 3 inside mask 1?

Your support is highly appreciated.
Thank you.




-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/63253935/attachment.html>

From kmorel at sandia.gov  Wed May 11 09:42:08 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 11 May 2016 13:42:08 +0000
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
Message-ID: <2A3A3D64-28AC-488A-9FC3-CCA8F70AF52F@sandia.gov>

Chathuri Gunasekera,

Are your patches available as fields in the data? If so, you should be able to use the Threshold filter with the patches to remove the holes.

-Ken

From: Chathuri Gunasekera <cgunases at gmail.com>
Date: Tuesday, May 10, 2016 at 8:31 PM
To: Kenneth Moreland <kmorel at sandia.gov>
Cc: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi to all,

@ Ken, thank you so much for your response. Really admire it.

1. Yes, i am 100% certain that all the masks are called in.
But let me be more into detail.
Basically, i have: 1 big mask and 3 patches (which are also saved as masks). Sorry Ken, i think i should have use patch instead of hole [ this patch eventually represent some special features{but these features eventually build up as tubes when it comes to a 3D model.} in a human organ as i am trying to model a human organ itself ]. ANyhow, i am sorry if i make you confuse.

You're right Ken, most of the stuff is done in MatLab but all the work looks error-free(because it works fine atleast in MatLab). But i am skeptic of one thing. Should i have to have a transparent big mask in order to see the 3 patches inside the big mask?  Is that why , i don't see the patches ? Kindly guide me.

2. I will try that out too.

Anyhow, thank you so much for your detailed response Ken. That is a great help.


--
Warm regards,
Chathuri Gunasekera.




On Wed, May 11, 2016 at 12:08 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Chathuri Gunasekera,

(Responding back to ParaView list to allow others to see and comment.)

1. I?m not sure why you are not see the 3 holes you expect in your mask. It looks like most of your process is building the data in MATLAB. Perhaps something is going wrong there. ParaView must be recognizing the mask since the region outside of the external boundary is removed. Are you sure your three holds are represented in the mask?

2. It sounds like you are finding the mask boundary in a slice. A slice is by definition contained in a 2D plane. You can restore the 2mm thickness manually by running the Extract Surface filter and then the Linear Extrusion filter.

-Ken

From: Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 12:03 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>

Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi Ken,

Your  detailed description is very much appreciated. Thank you so much.

Kindly note that following is what i have done in MatLab :
a. Segmented images as Masks (just x,y cordinates)
b. Saved as a .mat file
c. Then append z coordinate( z coordinate is the slice thickness which, each slice has a thickness of 2mm) to the above said mask. Hence, now the image is 3D (saved as .mat file)
d. Convert the 3D image into real world coordinates . So x,y,z all are in mm now.  (saved as .mat file)
e. Since i have about 8 sets and about 50 images per set. Then find the smallest dimension for a particular set.
f. Crop the image (saved as .mat file)
g. Stack the image (saved as .mat file)
h. Finally convert the .mat file to .vtk file
i. Then open the .vtk files in Paraview
Let me send you 2 outputs which i have obtained so far

1. segmented masked images. I prefer this method because this image looks close to my expectation(i expect a 3D model). Also i have 3 more masks which represent 3 more features inside the big mask (meaning i expect 3 holes inside the big image). But i simply cannot see the 3 holes inside this big mask. What mistake i am doing here? Why can't i see the 3 holes inside the big mask.

2. segmented masked --> converted RGB image to binary and then find the boundary of the mask. So the reason for why i asked the thickness is that for this output i can't see the 2mm thickness .

Kindly note that in order to obtain above output i have used couple of masks(slices) and  stacked them together.

Your assistance is really appreciated here as i was struggling to get a proper 3D model for sometime now and all my efforts are not succeeded yet.

Thank you.

--
Warm regards,
Chathuri Gunasekera.



On Tue, May 10, 2016 at 9:50 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
I think we need more information before we can answer your questions.

Your first question was how to ?add thickness? to image slices. If you have image slices, you usually want to load them in as a 3D stack and treat them like a volume. The spacing between the slices is typically specified by the data file itself or by an option in the reader (of which there are almost 100 different types in ParaView). So how you do that depends on your data format.

You simply said that your data comes from MATLAB. That?s not very specific, since it is possible to output lots of different types of files from MATLAB. If you are not doing it yet, you might consider this MATLAB module that writes out VTK files (which ParaView handles very well): http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format . I haven?t used it myself (I use MATLAB very infrequently), but it looks pretty full featured. You might want to check that out.

You also mentioned that the image segmentation is represented by masks. The easiest way to deal with that is probably to use the Threshold filter to remove all cells that are masked out.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 4:49 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Also,i need to mention that segmented images are saved as Masks.

Kindly tell me, when using Paraview software should i have to use the boundary or the mask of the segmented image for the purpose of building a 3D model. (kindly correct me, if i am wrong as i am new to Paraview)

Hope to hear from you soon.

Thank you.

On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>> wrote:
Hello everyone,

My goal is to generate a 3D model of  human organ.

Suppose i have segmented images in each set(each slice is saved using MatLab software).

So i want to know what are the options which paraview have in order to add the thickness to each slice.

Your feedback is appreciated.



--
Warm regards,
Chathuri Gunasekera.



--
Warm regards,
Chathuri Gunasekera.








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/0c77c362/attachment.html>

From garcfd at gmail.com  Wed May 11 12:16:23 2016
From: garcfd at gmail.com (Richardson CFD)
Date: Wed, 11 May 2016 17:16:23 +0100
Subject: [Paraview] python script does not run in macro
Message-ID: <CA+Y385x0sCAp5bGWa0q-MVH0=TGgJucP2Durj9s=Ge0cgVxaaA@mail.gmail.com>

If I have some python script such as the double helix example attached,
it works (runs) in Paraview as programmable filter or programmable source,
but it doesn't run in tools > python shell, or as a macro... why is this?

-- 
Richardson CFD
https://sites.google.com/site/garcfd

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/ffede7ad/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: helix.py
Type: application/octet-stream
Size: 2130 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/ffede7ad/attachment.obj>

From dave.demarle at kitware.com  Wed May 11 13:08:55 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 11 May 2016 13:08:55 -0400
Subject: [Paraview] Paraview in CAVE and remote rendering
In-Reply-To: <CAA7GnUmU02yvMQfVwX8VOG9t6SdvXEHUzTpx=KSGUc7ipu+07w@mail.gmail.com>
References: <CAA7GnUmU02yvMQfVwX8VOG9t6SdvXEHUzTpx=KSGUc7ipu+07w@mail.gmail.com>
Message-ID: <CANjZAi-ZRvok2P3WOiM9nzsA6+wRN2GkEvXtFBWPwXAgesi4RQ@mail.gmail.com>

I can think of two ways:
1) vnc or better display forwarding between the N cloud nodes and the N
CAVE tile nodes
2) run paraview in split dataserver/renderserver mode where the cloud runs
data server and does data processing and then the first N nodes send the
surface geometry to the N renderserver nodes which drive the tiles

I haven't personally tried either option with a CAVE so I don't know what
monsters are hiding in either the path.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, May 10, 2016 at 11:37 PM, Faiz Abidi <fabidi89 at vt.edu> wrote:

> Hi Guys,
>
> Wondering how should I go about remote rendering and visualization in a
> CAVE. I can visualize in a CAVE using an on-premise server physically
> connected to the projectors driving the CAVE, and using my laptop as the
> client. But how would I pass a PVX file if this server is somewhere on
> Amazon etc?
> --
> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> +1-540-998-6636
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/0ef79027/attachment.html>

From cgunases at gmail.com  Wed May 11 13:34:36 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Wed, 11 May 2016 23:04:36 +0530
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
In-Reply-To: <2A3A3D64-28AC-488A-9FC3-CCA8F70AF52F@sandia.gov>
References: <2A3A3D64-28AC-488A-9FC3-CCA8F70AF52F@sandia.gov>
Message-ID: <CAJFKOL1Ac2ty3uGi081yDtgS0L=yw0Uj9U7U2My0Oqdf05y3BQ@mail.gmail.com>

Hi,

Thanks alot  for your response, Ken.
Herewith,pls see the attachment: how the 3 small masks are looked like. So
the large mask(it's not seen here) encompass all three masks. All 4 masks
are saved in different folders and all of them have been called in, stacked
together and converted to vtk to call into Paraview.
So how should i move forward in order to make visible the small 3 masks in
the model?
Let me know anyone of your thoughts about it.
-- 
Warm regards,
Chathuri Gunasekera.


On Wed, May 11, 2016 at 7:12 PM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> Chathuri Gunasekera,
>
>
>
> Are your patches available as fields in the data? If so, you should be
> able to use the Threshold filter with the patches to remove the holes.
>
>
>
> -Ken
>
>
>
> *From: *Chathuri Gunasekera <cgunases at gmail.com>
> *Date: *Tuesday, May 10, 2016 at 8:31 PM
> *To: *Kenneth Moreland <kmorel at sandia.gov>
> *Cc: *"paraview at paraview.org" <paraview at paraview.org>
> *Subject: *[EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to
> each slice when generating a 3D model
>
>
>
> Hi to all,
>
>
>
> @ Ken, thank you so much for your response. Really admire it.
>
>
>
> 1. Yes, i am 100% certain that all the masks are called in.
>
> But let me be more into detail.
>
> Basically, i have: 1 big mask and 3 patches (which are also saved as
> masks). Sorry Ken, i think i should have use patch instead of hole [ this
> patch eventually represent some special features{but these features
> eventually build up as tubes when it comes to a 3D model.} in a human organ
> as i am trying to model a human organ itself ]. ANyhow, i am sorry if i
> make you confuse.
>
>
>
> You're right Ken, most of the stuff is done in MatLab but all the work
> looks error-free(because it works fine atleast in MatLab). But i am skeptic
> of one thing. Should i have to have a transparent big mask in order to see
> the 3 patches inside the big mask?  Is that why , i don't see the patches ?
> Kindly guide me.
>
>
>
> 2. I will try that out too.
>
>
>
> Anyhow, thank you so much for your detailed response Ken. That is a great
> help.
>
>
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
>
>
>
>
> On Wed, May 11, 2016 at 12:08 AM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>
> Chathuri Gunasekera,
>
>
>
> (Responding back to ParaView list to allow others to see and comment.)
>
>
>
> 1. I?m not sure why you are not see the 3 holes you expect in your mask.
> It looks like most of your process is building the data in MATLAB. Perhaps
> something is going wrong there. ParaView must be recognizing the mask since
> the region outside of the external boundary is removed. Are you sure your
> three holds are represented in the mask?
>
>
>
> 2. It sounds like you are finding the mask boundary in a slice. A slice is
> by definition contained in a 2D plane. You can restore the 2mm thickness
> manually by running the Extract Surface filter and then the Linear
> Extrusion filter.
>
>
>
> -Ken
>
>
>
> *From: *Chathuri Gunasekera <cgunases at gmail.com>
> *Date: *Tuesday, May 10, 2016 at 12:03 PM
> *To: *Kenneth Moreland <kmorel at sandia.gov>
>
>
> *Subject: *[EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to
> each slice when generating a 3D model
>
>
>
> Hi Ken,
>
>
>
> Your  detailed description is very much appreciated. Thank you so much.
>
>
>
> Kindly note that following is what i have done in MatLab :
>
> a. Segmented images as Masks (just x,y cordinates)
>
> b. Saved as a .mat file
>
> c. Then append z coordinate( z coordinate is the slice thickness which,
> each slice has a thickness of 2mm) to the above said mask. Hence, now the
> image is 3D (saved as .mat file)
>
> d. Convert the 3D image into real world coordinates . So x,y,z all are in
> mm now.  (saved as .mat file)
>
> e. Since i have about 8 sets and about 50 images per set. Then find the
> smallest dimension for a particular set.
>
> f. Crop the image (saved as .mat file)
>
> g. Stack the image (saved as .mat file)
>
> h. Finally convert the .mat file to .vtk file
>
> i. Then open the .vtk files in Paraview
>
> Let me send you 2 outputs which i have obtained so far
>
>
>
> 1. segmented masked images. I prefer this method because this image looks
> close to my expectation(i expect a 3D model). Also i have 3 more masks
> which represent 3 more features inside the big mask (meaning i expect 3
> holes inside the big image). But i simply cannot see the 3 holes inside
> this big mask. What mistake i am doing here? Why can't i see the 3 holes
> inside the big mask.
>
>
>
> 2. segmented masked --> converted RGB image to binary and then find the
> boundary of the mask. So the reason for why i asked the thickness is that
> for this output i can't see the 2mm thickness .
>
>
>
> Kindly note that in order to obtain above output i have used couple of
> masks(slices) and  stacked them together.
>
>
>
> Your assistance is really appreciated here as i was struggling to get a
> proper 3D model for sometime now and all my efforts are not succeeded yet.
>
>
>
> Thank you.
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
>
>
> On Tue, May 10, 2016 at 9:50 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>
> I think we need more information before we can answer your questions.
>
>
>
> Your first question was how to ?add thickness? to image slices. If you
> have image slices, you usually want to load them in as a 3D stack and treat
> them like a volume. The spacing between the slices is typically specified
> by the data file itself or by an option in the reader (of which there are
> almost 100 different types in ParaView). So how you do that depends on your
> data format.
>
>
>
> You simply said that your data comes from MATLAB. That?s not very
> specific, since it is possible to output lots of different types of files
> from MATLAB. If you are not doing it yet, you might consider this MATLAB
> module that writes out VTK files (which ParaView handles very well):
> http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format
> . I haven?t used it myself (I use MATLAB very infrequently), but it looks
> pretty full featured. You might want to check that out.
>
>
>
> You also mentioned that the image segmentation is represented by masks.
> The easiest way to deal with that is probably to use the Threshold filter
> to remove all cells that are masked out.
>
>
>
> -Ken
>
>
>
>
>
> *From: *ParaView <paraview-bounces at paraview.org> on behalf of Chathuri
> Gunasekera <cgunases at gmail.com>
> *Date: *Tuesday, May 10, 2016 at 4:49 AM
> *To: *ParaView <paraview at paraview.org>
> *Subject: *[EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to
> each slice when generating a 3D model
>
>
>
> Also,i need to mention that segmented images are saved as Masks.
>
>
>
> Kindly tell me, when using Paraview software should i have to use the
> boundary or the mask of the segmented image for the purpose of building a
> 3D model. (kindly correct me, if i am wrong as i am new to Paraview)
>
>
>
> Hope to hear from you soon.
>
>
>
> Thank you.
>
>
>
> On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com>
> wrote:
>
> Hello everyone,
>
>
>
> My goal is to generate a 3D model of  human organ.
>
>
>
> Suppose i have segmented images in each set(each slice is saved using
> MatLab software).
>
>
>
> So i want to know what are the options which paraview have in order to add
> the thickness to each slice.
>
>
>
> Your feedback is appreciated.
>
>
>
>
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
> --
>
> Warm regards,
>
> Chathuri Gunasekera.
>
>
>
>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/ad8bceb2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: new_whole_mask_P3290258.jpg
Type: image/jpeg
Size: 45940 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/ad8bceb2/attachment.jpg>

From kmorel at sandia.gov  Wed May 11 15:00:39 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 11 May 2016 19:00:39 +0000
Subject: [Paraview] [ParaView] How to add thickness to each slice when
 generating a 3D model
Message-ID: <5C07B954-B6EA-4690-8061-153502FE4691@sandia.gov>

Without seeing the actual vtk file you are using, it is hard to give you the exact steps. I am assuming that when you say the masks are ?stacked together? that they are available as field variables (for example, you can color the surface by them). Furthermore, I assume by ?make visible? the masks, you mean removed the masked out cells so that you can see through the holes in the data.

To do that, after you load your vtk file, add the Threshold filter. Set the ?Scalars? property to the mask variable and then set the range to the mask value you want to pass.

-Ken


From: Chathuri Gunasekera <cgunases at gmail.com>
Date: Wednesday, May 11, 2016 at 11:34 AM
To: Kenneth Moreland <kmorel at sandia.gov>, ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi,

Thanks alot  for your response, Ken.
Herewith,pls see the attachment: how the 3 small masks are looked like. So the large mask(it's not seen here) encompass all three masks. All 4 masks are saved in different folders and all of them have been called in, stacked together and converted to vtk to call into Paraview.
So how should i move forward in order to make visible the small 3 masks in the model?
Let me know anyone of your thoughts about it.
--
Warm regards,
Chathuri Gunasekera.


On Wed, May 11, 2016 at 7:12 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Chathuri Gunasekera,

Are your patches available as fields in the data? If so, you should be able to use the Threshold filter with the patches to remove the holes.

-Ken

From: Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 8:31 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi to all,

@ Ken, thank you so much for your response. Really admire it.

1. Yes, i am 100% certain that all the masks are called in.
But let me be more into detail.
Basically, i have: 1 big mask and 3 patches (which are also saved as masks). Sorry Ken, i think i should have use patch instead of hole [ this patch eventually represent some special features{but these features eventually build up as tubes when it comes to a 3D model.} in a human organ as i am trying to model a human organ itself ]. ANyhow, i am sorry if i make you confuse.

You're right Ken, most of the stuff is done in MatLab but all the work looks error-free(because it works fine atleast in MatLab). But i am skeptic of one thing. Should i have to have a transparent big mask in order to see the 3 patches inside the big mask?  Is that why , i don't see the patches ? Kindly guide me.

2. I will try that out too.

Anyhow, thank you so much for your detailed response Ken. That is a great help.


--
Warm regards,
Chathuri Gunasekera.




On Wed, May 11, 2016 at 12:08 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Chathuri Gunasekera,

(Responding back to ParaView list to allow others to see and comment.)

1. I?m not sure why you are not see the 3 holes you expect in your mask. It looks like most of your process is building the data in MATLAB. Perhaps something is going wrong there. ParaView must be recognizing the mask since the region outside of the external boundary is removed. Are you sure your three holds are represented in the mask?

2. It sounds like you are finding the mask boundary in a slice. A slice is by definition contained in a 2D plane. You can restore the 2mm thickness manually by running the Extract Surface filter and then the Linear Extrusion filter.

-Ken

From: Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 12:03 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>

Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Hi Ken,

Your  detailed description is very much appreciated. Thank you so much.

Kindly note that following is what i have done in MatLab :
a. Segmented images as Masks (just x,y cordinates)
b. Saved as a .mat file
c. Then append z coordinate( z coordinate is the slice thickness which, each slice has a thickness of 2mm) to the above said mask. Hence, now the image is 3D (saved as .mat file)
d. Convert the 3D image into real world coordinates . So x,y,z all are in mm now.  (saved as .mat file)
e. Since i have about 8 sets and about 50 images per set. Then find the smallest dimension for a particular set.
f. Crop the image (saved as .mat file)
g. Stack the image (saved as .mat file)
h. Finally convert the .mat file to .vtk file
i. Then open the .vtk files in Paraview
Let me send you 2 outputs which i have obtained so far

1. segmented masked images. I prefer this method because this image looks close to my expectation(i expect a 3D model). Also i have 3 more masks which represent 3 more features inside the big mask (meaning i expect 3 holes inside the big image). But i simply cannot see the 3 holes inside this big mask. What mistake i am doing here? Why can't i see the 3 holes inside the big mask.

2. segmented masked --> converted RGB image to binary and then find the boundary of the mask. So the reason for why i asked the thickness is that for this output i can't see the 2mm thickness .

Kindly note that in order to obtain above output i have used couple of masks(slices) and  stacked them together.

Your assistance is really appreciated here as i was struggling to get a proper 3D model for sometime now and all my efforts are not succeeded yet.

Thank you.

--
Warm regards,
Chathuri Gunasekera.



On Tue, May 10, 2016 at 9:50 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
I think we need more information before we can answer your questions.

Your first question was how to ?add thickness? to image slices. If you have image slices, you usually want to load them in as a 3D stack and treat them like a volume. The spacing between the slices is typically specified by the data file itself or by an option in the reader (of which there are almost 100 different types in ParaView). So how you do that depends on your data format.

You simply said that your data comes from MATLAB. That?s not very specific, since it is possible to output lots of different types of files from MATLAB. If you are not doing it yet, you might consider this MATLAB module that writes out VTK files (which ParaView handles very well): http://www.mathworks.com/matlabcentral/fileexchange/47814-export-3d-data-to-paraview-in-vtk-legacy-file-format . I haven?t used it myself (I use MATLAB very infrequently), but it looks pretty full featured. You might want to check that out.

You also mentioned that the image segmentation is represented by masks. The easiest way to deal with that is probably to use the Threshold filter to remove all cells that are masked out.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>>
Date: Tuesday, May 10, 2016 at 4:49 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] [ParaView] How to add thickness to each slice when generating a 3D model

Also,i need to mention that segmented images are saved as Masks.

Kindly tell me, when using Paraview software should i have to use the boundary or the mask of the segmented image for the purpose of building a 3D model. (kindly correct me, if i am wrong as i am new to Paraview)

Hope to hear from you soon.

Thank you.

On Tue, May 10, 2016 at 2:53 PM, Chathuri Gunasekera <cgunases at gmail.com<mailto:cgunases at gmail.com>> wrote:
Hello everyone,

My goal is to generate a 3D model of  human organ.

Suppose i have segmented images in each set(each slice is saved using MatLab software).

So i want to know what are the options which paraview have in order to add the thickness to each slice.

Your feedback is appreciated.



--
Warm regards,
Chathuri Gunasekera.



--
Warm regards,
Chathuri Gunasekera.











-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/2b9e9ff9/attachment.html>

From kevin.dean at decisionsciencescorp.com  Wed May 11 22:41:32 2016
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Wed, 11 May 2016 19:41:32 -0700
Subject: [Paraview] Calling Request Data for Plugin
Message-ID: <CAFvyM3SbkYMWWvmHhmZaXYQCCBYAqgRF=bv=4aRwQiGm=ZD0uQ@mail.gmail.com>

Hey guys,

so I have a plugin that acquires data across a DDS socket in real-time.
However, I am having trouble calling request data continuously. I can see
the data being piped into ParaView no problem. However, I would like to do
something similar to the PCL Plugin as to when there is a new packet of
data, I would like ParaView to Render the polydata. Is there an example of
something similar to this?

I guess what I am asking, is there an example that shows how to easily
control the Proxy for constant rendering?? Any help is much appreciated.
Thanks guys.

Kevin Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160511/646d2fd8/attachment.html>

From s.perticoni at scsitaly.com  Thu May 12 04:29:38 2016
From: s.perticoni at scsitaly.com (stefano perticoni)
Date: Thu, 12 May 2016 10:29:38 +0200
Subject: [Paraview] Paraview 5.0.1 (OpenGL2) selection by picking not
 working with Ubuntu 14.04 and latest Ubuntu Software Center nvidia drivers
Message-ID: <CA+hDRwLzpYRJ26HpNd6r3_eHSz=D6dJ+Z2R6sZi_BHPGuxsdGQ@mail.gmail.com>

Hello,

I found that picking is not working with OpenGL2 VTK_RENDERING_BACKEND when
using most recent nvidia drivers from Ubuntu 14.04 software center ie
nvidia-current 304.131-0ubuntu0.14.04.1:

-> NVidia binary X.Org driver ('current' driver)
-> Optimized hardware acceleration of OpenGL with nvidia graphic cards
-> 190,9 MB when installed
-> Canonical provides critical updates supplied by the developers of NVidia
binary X.Org driver ('current' driver) until maggio 2019.

I'm using a GeforceGTX 560M

This was replicated with both paraview 5.0.1 OpenGL2 binary downloaded from
paraview site and local debug build.

There seems to be some issues with:
int vtkOpenGLRenderWindow::GetColorBufferSizes(int *rgba) and
ParaViewCore/ServerManager/Rendering/vtkSMRenderViewProxy.cxx since line
179 will return:

"Selection not supported due to insufficient color depth."


Selection is OK with latest nvidia drivers from nvidia.com: version 361.42


Regards,

Stefano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160512/ece33dc3/attachment.html>

From asaad.sellmann at rwth-aachen.de  Thu May 12 08:23:06 2016
From: asaad.sellmann at rwth-aachen.de (Sellmann, Kai Asaad)
Date: Thu, 12 May 2016 12:23:06 +0000
Subject: [Paraview] WG: Visualizing load paths
In-Reply-To: <1462970667534.86624@rwth-aachen.de>
References: <1462274379341.43274@rwth-aachen.de>,
 <1462863894054.37762@rwth-aachen.de>, <1462970667534.86624@rwth-aachen.de>
Message-ID: <1463055786647.13616@rwth-aachen.de>

Dear community,

my last two questions haven't been answered, so I guess my way of asking wasn't appropriate. So I'll try again:
I need to put the following Information from a FE-Calculation into a file format that can be read by paraview. And that can be used with Stream Tracers:

(Node ID)
Nodal Coordinates
Nodal Stresses XX YY ZZ XY XZ YZ

I know how to make paraview interpret the Coordinates as Points but I don't know how to make paraview interpret the Nodal Stresses as Components of Vectors.

Any hint or Idea would be greatly appreciated!!!
Thank you very much in advance!

Asaad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160512/af96b960/attachment.html>

From mathieu.westphal at kitware.com  Thu May 12 08:35:32 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Thu, 12 May 2016 14:35:32 +0200
Subject: [Paraview] WG: Visualizing load paths
In-Reply-To: <1463055786647.13616@rwth-aachen.de>
References: <1462274379341.43274@rwth-aachen.de>
 <1462863894054.37762@rwth-aachen.de>
 <1462970667534.86624@rwth-aachen.de>
 <1463055786647.13616@rwth-aachen.de>
Message-ID: <CAC2t4USdOUgvvWBMTjnrzeAqmX9rmGvkR_yKzLwzV5-nz7tGOQ@mail.gmail.com>

Hello

ParaView StreamTracer works only on 3-components arrays, not 6-components
array.
You will need to convert your tensors into a vectors before being able to
use it with the StreamTracer.

Regards,

Mathieu Westphal

On Thu, May 12, 2016 at 2:23 PM, Sellmann, Kai Asaad <
asaad.sellmann at rwth-aachen.de> wrote:

> Dear community,
>
> my last two questions haven't been answered, so I guess my way of asking
> wasn't appropriate. So I'll try again:
> I need to put the following Information from a FE-Calculation into a file
> format that can be read by paraview. And that can be used with Stream
> Tracers:
>
> (Node ID)
> Nodal Coordinates
> Nodal Stresses XX YY ZZ XY XZ YZ
>
> I know how to make paraview interpret the Coordinates as Points but I
> don't know how to make paraview interpret the Nodal Stresses as Components
> of Vectors.
>
> Any hint or Idea would be greatly appreciated!!!
> Thank you very much in advance!
>
> Asaad
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160512/0d380e0a/attachment.html>

From samuelkey at bresnan.net  Thu May 12 10:22:26 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Thu, 12 May 2016 08:22:26 -0600
Subject: [Paraview] WG: Visualizing load paths
In-Reply-To: <1463055786647.13616@rwth-aachen.de>
References: <1462274379341.43274@rwth-aachen.de>
 <1462863894054.37762@rwth-aachen.de> <1462970667534.86624@rwth-aachen.de>
 <1463055786647.13616@rwth-aachen.de>
Message-ID: <8a4589bb-908b-1381-17b3-260847bd8ad4@bresnan.net>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160512/2e1abe01/attachment.html>
-------------- next part --------------
<snip>
!!
!! Start vtk "PointData" data.
!!
            WRITE (IO_UNIT%LVTO,'(A)') '<PointData Tensors="Stress" Scalars="Material">'
            !!
            !! Write element-based (cell) stress data to VTK Data File.
            !! The retrieval function STRESS_DATA( element_n, component_i ) is used 
            !! with the following stress-component retrieval pattern to produce the
            !! the stress-component pattern expected by ParaView (PV):
            !!                   ( 1 4 5 )   ( xx xy xz )   ( 1 2 3 )
            !! Fma-3D Indices => ( 4 2 6 ) = ( yx yy yz ) = ( 4 5 6 ) <= PV Indices
            !!                   ( 5 6 3 )   ( zx zy zz )   ( 7 8 9 )
            !!
            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Float32" Name="Stress" NumberOfComponents="9" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6(1PE15.7)))') 
     &        ((/ STRESS_DATA(NELUSED(L),1),STRESS_DATA(NELUSED(L),4),STRESS_DATA(NELUSED(L),5),
     &            STRESS_DATA(NELUSED(L),4),STRESS_DATA(NELUSED(L),2),STRESS_DATA(NELUSED(L),6),
     &            STRESS_DATA(NELUSED(L),5),STRESS_DATA(NELUSED(L),6),STRESS_DATA(NELUSED(L),3) /),  L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'

            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Float32" Name="Effective_Stress" NumberOfComponents="1" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6(1PE15.7)))') (EFFECTIVE_STRESS(NELUSED(L)), L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'

            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Float32" Name="Pressure" NumberOfComponents="1" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6(1PE15.7)))') (PRESSURE(NELUSED(L)), L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'

            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Float32" Name="Bulk_Strain" NumberOfComponents="1" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6(1PE15.7)))') (BULK_STRAIN(NELUSED(L)), L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'

            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Float32" Name="Strain_Energy" NumberOfComponents="1" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6(1PE15.7)))') (STRAIN_ENERGY_DENSITY(NELUSED(L)), L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'

            WRITE(IO_UNIT%LVTO,'(2X,A)')'<DataArray type="Int32" Name="Material" NumberOfComponents="1" format="ascii">'
            Lbgn = 1
            Lend = LREMAIN
            DO i = 1,LBLOCKS+1
              WRITE(IO_UNIT%LVTO,'((6X,8I10))') (MatID_DATA(NELUSED(L)), L = Lbgn,Lend)
              Lbgn = Lend + 1
              Lend = Lend + LBCOUNT
            ENDDO
            WRITE(IO_UNIT%LVTO,'(2X,A)')'</DataArray>'
!!
!! End vtk "PointData" data.
!!
            WRITE (IO_UNIT%LVTO,'(A)') '</PointData>'
</snip>
-------------- next part --------------
<snip>
!!
!! Initialize sequential Material part counter.
!!
        MPart = 0
!!
!! Start this-time-step block.
!!
        CBUFFER = "BEGIN TIME STEP"
        WRITE (IO_UNIT%LEGO) CBUFFER

        CBUFFER = "Element Stress(xx,yy,zz,xy,xz,yz) Results"
        WRITE (IO_UNIT%LEGO) CBUFFER
!!
!! Loop on Material parts.
!!
        DO M = 1,NUMMT
!!
!! The function ELEMENTS_AND_NODES_USED(*) gen's nodal-points-used array NPTUSED, 
!! elements-used array NELUSED and vtk output-index-translation array NPTNOWI for 
!! this material. If material M is used, the function returns 1, otherwise 0. 
!!
          IF (ELEMENTS_AND_NODES_USED(M) .GT. 0) THEN

            NNodes = MATERIAL(M)%NNodes
            NElems = MATERIAL(M)%NElems

            CBUFFER = "part"
            WRITE (IO_UNIT%LEGO) CBUFFER
            MPart = MPart + 1
            WRITE (IO_UNIT%LEGO) MPart

            Nend = 0
            LBCOUNT = IBCOUNT
            MEL_COUNT = (/MHX,MPX,MPY,MTX,MM3,MP3,MM4,MP4,MTR,MPH,MPG/)

            DO k = 1,10
              MXX = MEL_COUNT(k)
              IF (MXX .GT. 0) THEN
                Nbgn = Nend + 1
                Nend = Nend + MXX
                CBUFFER = ESG_ELEMENT_TYPE(k)         
                WRITE (IO_UNIT%LEGO) CBUFFER

                LBLOCKS = MXX / LBCOUNT
                LREMAIN = MXX - LBCOUNT*LBLOCKS
                !!
                !! NOTE: The symmetric stress tensor components stored in the 1-D 
                !! array STRESS (*,1:6) in the program exactly match the component 
                !! order expected by the EnSight Gold results file.
                !!
                !! Program ==> (/Sxx,Syy,Szz,Sxy,Sxz,Syz/)
                !! EnSight ==> (/S11,S22,S33,S12,S13,S23/)
                !!
                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),1), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),2), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),3), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),4), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),5), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

                Lbgn = Nbgn
                Lend = Lbgn + LREMAIN - 1
                DO i = 1,LBLOCKS+1
                  WRITE (IO_UNIT%LEGO) (STRESS_DATA(NELUSED(n),6), n = Lbgn,Lend)
                  Lbgn = Lend + 1
                  Lend = Lend + LBCOUNT
                ENDDO

              ENDIF
            ENDDO

          ENDIF
        ENDDO
!!
!! Close out this-time-step block.
!!
        CBUFFER = "END TIME STEP"
        WRITE (IO_UNIT%LEGO) CBUFFER

        CLOSE (UNIT=IO_UNIT%LEGO, STATUS='KEEP')

      ENDIF
</snip>
######################################################################################
The EnSight Case file --
######################################################################################
FORMAT
type: ensight gold
GEOMETRY
model:                   1  1  fmaego.results.geom    change_coords_only
VARIABLE
vector per node:         1  1  Displacement          fmaego.results.ndis
vector per node:         1  1  Velocity              fmaego.results.nvel
vector per node:         1  1  Acceleration          fmaego.results.nacc
scalar per element:      1  1  Material              fmaego.results.emat
scalar per element:      1  1  Material-State        fmaego.results.esta
scalar per element:      1  1  Pressure              fmaego.results.eprs
scalar per element:      1  1  Bulk-Strain           fmaego.results.elnv
scalar per element:      1  1  Strain-Energy-Density fmaego.results.esed
scalar per element:      1  1  Effective-Stress      fmaego.results.edev
vector per element:      1  1  Stress*Vel            fmaego.results.estv
tensor symm per element: 1  1  Stress                fmaego.results.estr
TIME
time set:                1
number of steps:       101
time values:                  1.000000000000E-06      2.000000000000E-05
      4.100000000000E-05      6.100000000000E-05      8.100000000000E-05
      1.010000000000E-04      1.210000000000E-04      1.410000000000E-04
      1.610000000000E-04      1.810000000000E-04      2.010000000000E-04
      2.210000000000E-04      2.410000000000E-04      2.610000000000E-04
      2.800000000000E-04      3.000000000000E-04      3.200000000000E-04
      3.400000000000E-04      3.600000000000E-04      3.800000000000E-04
      4.000000000000E-04      4.200000000000E-04      4.400000000000E-04
      4.600000000000E-04      4.800000000000E-04      5.000000000000E-04
      5.200000000000E-04      5.400000000000E-04      5.600000000000E-04
      5.800000000000E-04      6.000000000000E-04      6.200000000000E-04
      6.400000000000E-04      6.600000000000E-04      6.800000000000E-04
      7.000000000000E-04      7.200000000000E-04      7.400000000000E-04
      7.600000000000E-04      7.800000000000E-04      8.000000000000E-04
      8.200000000000E-04      8.400000000000E-04      8.600000000000E-04
      8.800000000000E-04      9.000000000000E-04      9.200000000000E-04
      9.400000000000E-04      9.600000000000E-04      9.800000000000E-04
      1.000000000000E-03      1.020000000000E-03      1.040000000000E-03
      1.060000000000E-03      1.080000000000E-03      1.100000000000E-03
      1.120000000000E-03      1.140000000000E-03      1.161000000000E-03
      1.181000000000E-03      1.201000000000E-03      1.221000000000E-03
      1.241000000000E-03      1.261000000000E-03      1.281000000000E-03
      1.301000000000E-03      1.321000000000E-03      1.341000000000E-03
      1.361000000000E-03      1.381000000000E-03      1.401000000000E-03
      1.421000000000E-03      1.441000000000E-03      1.461000000000E-03
      1.481000000000E-03      1.501000000000E-03      1.521000000000E-03
      1.541000000000E-03      1.561000000000E-03      1.581000000000E-03
      1.601000000000E-03      1.621000000000E-03      1.641000000000E-03
      1.661000000000E-03      1.681000000000E-03      1.701000000000E-03
      1.721000000000E-03      1.741000000000E-03      1.761000000000E-03
      1.781000000000E-03      1.801000000000E-03      1.821000000000E-03
      1.841000000000E-03      1.861000000000E-03      1.881000000000E-03
      1.901000000000E-03      1.921000000000E-03      1.941000000000E-03
      1.961000000000E-03      1.981000000000E-03      2.001000000000E-03
FILE
file set:                   1
number of steps:          101
######################################################################################

From tamas.szep at kit.edu  Thu May 12 13:15:17 2016
From: tamas.szep at kit.edu (=?iso-8859-1?B?U3rpcCwgVGFt4XMgKElWRCk=?=)
Date: Thu, 12 May 2016 17:15:17 +0000
Subject: [Paraview] C++ Plugin Filter
Message-ID: <1463073317462.75301@kit.edu>

Hi,


could somebody help me on how to implement a filter with C++ in Paraview, which is capable of reacting on external events by invalidating itself, so that next time when a frame is rendered, the filter (and the dependent pipeline parts if any) get(s) reexecuted. I mainly need it for view-dependent filtering, but you can also consider an input reader that reexecutes when the file is changed as an example.


Thank you for the answers in advance. Kind regards:


Tam?s Sz?p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160512/8495bd62/attachment.html>

From fabidi89 at vt.edu  Fri May 13 04:00:14 2016
From: fabidi89 at vt.edu (Faiz Abidi)
Date: Fri, 13 May 2016 04:00:14 -0400
Subject: [Paraview] Paraview in CAVE and remote rendering
In-Reply-To: <CANjZAi-ZRvok2P3WOiM9nzsA6+wRN2GkEvXtFBWPwXAgesi4RQ@mail.gmail.com>
References: <CAA7GnUmU02yvMQfVwX8VOG9t6SdvXEHUzTpx=KSGUc7ipu+07w@mail.gmail.com>
 <CANjZAi-ZRvok2P3WOiM9nzsA6+wRN2GkEvXtFBWPwXAgesi4RQ@mail.gmail.com>
Message-ID: <CAA7GnUkPcEpmO7tQNwngBb6dpAgAUKR1FciWKsZzfQ02KwHMTw@mail.gmail.com>

Thanks for your reply.

Yeah, I think biggest one would be network latency. I'll try it soon, and
report how it goes.

On Wed, May 11, 2016 at 1:08 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> I can think of two ways:
> 1) vnc or better display forwarding between the N cloud nodes and the N
> CAVE tile nodes
> 2) run paraview in split dataserver/renderserver mode where the cloud runs
> data server and does data processing and then the first N nodes send the
> surface geometry to the N renderserver nodes which drive the tiles
>
> I haven't personally tried either option with a CAVE so I don't know what
> monsters are hiding in either the path.
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Tue, May 10, 2016 at 11:37 PM, Faiz Abidi <fabidi89 at vt.edu> wrote:
>
>> Hi Guys,
>>
>> Wondering how should I go about remote rendering and visualization in a
>> CAVE. I can visualize in a CAVE using an on-premise server physically
>> connected to the projectors driving the CAVE, and using my laptop as the
>> client. But how would I pass a PVX file if this server is somewhere on
>> Amazon etc?
>> --
>> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
>> +1-540-998-6636
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160513/b5672e36/attachment.html>

From dave.demarle at kitware.com  Fri May 13 07:54:15 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 13 May 2016 07:54:15 -0400
Subject: [Paraview] Paraview in CAVE and remote rendering
In-Reply-To: <CAA7GnUkPcEpmO7tQNwngBb6dpAgAUKR1FciWKsZzfQ02KwHMTw@mail.gmail.com>
References: <CAA7GnUmU02yvMQfVwX8VOG9t6SdvXEHUzTpx=KSGUc7ipu+07w@mail.gmail.com>
 <CANjZAi-ZRvok2P3WOiM9nzsA6+wRN2GkEvXtFBWPwXAgesi4RQ@mail.gmail.com>
 <CAA7GnUkPcEpmO7tQNwngBb6dpAgAUKR1FciWKsZzfQ02KwHMTw@mail.gmail.com>
Message-ID: <CANjZAi-1ikBO2WhcgrpgLbhAfvbKYwd=2aYhyoEohYjHKY82Uw@mail.gmail.com>

Agreed. And comparing options 1 and 2, with 1 you pay the latency on every
camera motion. With 2 you pay it only when the data changes. This is the
same as client side rendering for standard ParaView. This is less of an
advantage as is used to be because video streaming technologies have
recently improved substantially.

good luck


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, May 13, 2016 at 4:00 AM, Faiz Abidi <fabidi89 at vt.edu> wrote:

> Thanks for your reply.
>
> Yeah, I think biggest one would be network latency. I'll try it soon, and
> report how it goes.
>
> On Wed, May 11, 2016 at 1:08 PM, David E DeMarle <dave.demarle at kitware.com
> > wrote:
>
>> I can think of two ways:
>> 1) vnc or better display forwarding between the N cloud nodes and the N
>> CAVE tile nodes
>> 2) run paraview in split dataserver/renderserver mode where the cloud
>> runs data server and does data processing and then the first N nodes send
>> the surface geometry to the N renderserver nodes which drive the tiles
>>
>> I haven't personally tried either option with a CAVE so I don't know what
>> monsters are hiding in either the path.
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Tue, May 10, 2016 at 11:37 PM, Faiz Abidi <fabidi89 at vt.edu> wrote:
>>
>>> Hi Guys,
>>>
>>> Wondering how should I go about remote rendering and visualization in a
>>> CAVE. I can visualize in a CAVE using an on-premise server physically
>>> connected to the projectors driving the CAVE, and using my laptop as the
>>> client. But how would I pass a PVX file if this server is somewhere on
>>> Amazon etc?
>>> --
>>> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
>>> +1-540-998-6636
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
> --
> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> +1-540-998-6636
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160513/5431689c/attachment.html>

From cgunases at gmail.com  Fri May 13 15:32:23 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Sat, 14 May 2016 01:02:23 +0530
Subject: [Paraview] [ParaView] visualization: possible to add different
 layers to combine and come up with a model?
Message-ID: <CAJFKOL0b8ni-Ps9n2hMMmr2Sn_6DuBe=UAQTE0qehT_omOtsUA@mail.gmail.com>

Hi everyone,

With respect to visualization a 3D model, is there a possibility in
ParaView to overlap three pieces(three masks) together (which are saved
separately) and then combine to form a 3D model ?

-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160514/a7f3c9d5/attachment.html>

From arsh840 at gmail.com  Sat May 14 04:26:05 2016
From: arsh840 at gmail.com (Arshpreet Singh)
Date: Sat, 14 May 2016 13:56:05 +0530
Subject: [Paraview] Paraview Climate Science
Message-ID: <CAAstK2HYitjPCJnv4cqXGRQGT1K7Seh1R_XWyYEXD5shqS+vGQ@mail.gmail.com>

Hi I am accessing netcdf file from Python interface in Paraview, My
main goal is to access different parameters change in air and
temperature with respect to time.


Can anyone point me towards and example Python code which can show
demonstration of Paraview and netcdf files from using Python code?

-- 

Thanks
Arshpreet Singh

I am Sikh boy, Learning by doing and Learning by teaching is my religion.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

From cgunases at gmail.com  Sat May 14 05:54:46 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Sat, 14 May 2016 15:24:46 +0530
Subject: [Paraview] [ParaView] How to add slice thickness ?
Message-ID: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>

Hi,

I have lot of image slices which need to employ in generating a 3D model.

Can someone kindly tell me, how to add the  slice thickness in ParaView?

Thanks in advance.
-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160514/0b7740fe/attachment.html>

From houssen at ipgp.fr  Mon May 16 10:55:21 2016
From: houssen at ipgp.fr (houssen)
Date: Mon, 16 May 2016 16:55:21 +0200
Subject: [Paraview] =?utf-8?q?Bug_in_XDMF_reader_=3F?=
Message-ID: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>

Hello,

I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when 
attribute names differ in grids, data can not be visualized : is this 
intended ? If yes why ? If no, how to file a bug ?

Thanks,

Franck

~> diff OK.xdmf KO.xdmf
48c48
<       <Attribute Name="NodeValues" AttributeType="Scalar" 
Center="Node">
---
>       <Attribute Name="NodeVal" AttributeType="Scalar" Center="Node">
52c52
<       <Attribute Name="CellValues" AttributeType="Scalar" 
Center="Cell">
---
>       <Attribute Name="CellVal" AttributeType="Scalar" Center="Cell">
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KO.xdmf
Type: application/xml
Size: 2022 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160516/a21b9689/attachment.wsdl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OK.xdmf
Type: application/xml
Size: 2028 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160516/a21b9689/attachment-0001.wsdl>

From kmorel at sandia.gov  Mon May 16 15:12:35 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 16 May 2016 19:12:35 +0000
Subject: [Paraview] Paraview Climate Science
Message-ID: <5CD7CA5D-1ABA-4D9F-96EE-CCA49F158FD6@sandia.gov>

Arshpreet Singh,

I highly recommend you take a look at the Python trace feature in the ParaView GUI. It will automatically create Python code that replicates things you do in the GUI, which I find much easier than trying to write the Python code from scratch. The Python trace feature is documented in both the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and the ParaView User?s guide (http://www.paraview.org/paraview-guide/), both of which are available for free.

As an example, I have attached a Python script that loads a netCDF file, shows a variable, and animates over time. I generated this in the ParaView GUI in less time than it took me to write the rest of this email.

-Ken 


On 5/14/16, 2:26 AM, "ParaView on behalf of Arshpreet Singh" <paraview-bounces at paraview.org on behalf of arsh840 at gmail.com> wrote:

>Hi I am accessing netcdf file from Python interface in Paraview, My
>main goal is to access different parameters change in air and
>temperature with respect to time.
>
>
>Can anyone point me towards and example Python code which can show
>demonstration of Paraview and netcdf files from using Python code?
>
>-- 
>
>Thanks
>Arshpreet Singh
>
>I am Sikh boy, Learning by doing and Learning by teaching is my religion.
>------------------------------------------------------------------------------
>Slashdot TV.
>Video for Nerds.  Stuff that matters.
>http://tv.slashdot.org/
>_______________________________________________
>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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: LoadNetCDF.py
Type: text/x-python-script
Size: 1937 bytes
Desc: LoadNetCDF.py
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160516/756afc33/attachment.bin>

From u.utku.turuncoglu at be.itu.edu.tr  Tue May 17 03:50:45 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Tue, 17 May 2016 10:50:45 +0300
Subject: [Paraview] Paraview Climate Science
In-Reply-To: <5CD7CA5D-1ABA-4D9F-96EE-CCA49F158FD6@sandia.gov>
References: <5CD7CA5D-1ABA-4D9F-96EE-CCA49F158FD6@sandia.gov>
Message-ID: <356c3a31-f2ca-7e8d-8812-cb2ce9b6f9eb@be.itu.edu.tr>

Hi,

You might want to check following link,

https://www.dkrz.de/Nutzerportal-en/doku/vis/sw/paraview

There are sample datasets (mostly netcdf files) and a tutorial document 
that are dedicated to climate data analysis. I hope it helps.

Regards,

--ufuk

On 16/05/16 22:12, Moreland, Kenneth wrote:
> Arshpreet Singh,
>
> I highly recommend you take a look at the Python trace feature in the ParaView GUI. It will automatically create Python code that replicates things you do in the GUI, which I find much easier than trying to write the Python code from scratch. The Python trace feature is documented in both the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and the ParaView User?s guide (http://www.paraview.org/paraview-guide/), both of which are available for free.
>
> As an example, I have attached a Python script that loads a netCDF file, shows a variable, and animates over time. I generated this in the ParaView GUI in less time than it took me to write the rest of this email.
>
> -Ken
>
>
> On 5/14/16, 2:26 AM, "ParaView on behalf of Arshpreet Singh" <paraview-bounces at paraview.org on behalf of arsh840 at gmail.com> wrote:
>
>> Hi I am accessing netcdf file from Python interface in Paraview, My
>> main goal is to access different parameters change in air and
>> temperature with respect to time.
>>
>>
>> Can anyone point me towards and example Python code which can show
>> demonstration of Paraview and netcdf files from using Python code?
>>
>> -- 
>>
>> Thanks
>> Arshpreet Singh
>>
>> I am Sikh boy, Learning by doing and Learning by teaching is my religion.
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160517/2fc6bc84/attachment.html>

From mgammar at outlook.fr  Tue May 17 05:26:54 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Tue, 17 May 2016 11:26:54 +0200
Subject: [Paraview] Vtp file calling other files
Message-ID: <BAY182-W563FEAEE93A16B5781B805D1480@phx.gbl>

Hello Miss, Mister,
I want to combine lots of files for my animation so that i can save space in my computer, however i get messages of error about the fact that the file cannot be read, could you help me please?
Here is an example with the cube:

<?xml version="1.0"?>
<VTKFile type="PolyData" version="0.1" byte_order="LittleEndian" xmlns:xi="http://www.w3.org/2003/XInclude">
 <PolyData>
   <Piece NumberOfPoints="8" NumberOfVerts="0" NumberOfLines="0"
          NumberOfStrips="0" NumberOfPolys="6">
    <Points>
     <DataArray type="Float32" NumberOfComponents="3" format="XML">
         <xi:include href="nodes.xml" parse="text"/>
     </DataArray>
    </Points>
    <PointData Scalars="my_scalars">
     <DataArray type="Float32" Name="my_scalars" format="ascii">
1 2 3 4 5 6 7 0
     </DataArray>
    </PointData>
    <Polys>
     <DataArray type="Int32" Name="connectivity" format="ascii">
0 1 2 3 4 5 6 7 0 1 5 4 2 3 7 6 0 4 7 3 1 2 6 5
     </DataArray>
     <DataArray type="Int32" Name="offsets" format="ascii">
       4 8 12 16 20 24
     </DataArray>
    </Polys>
   </Piece>
  </PolyData>
</VTKFile>

The use of Xinclude works with xdmf but i have some trouble with the animation, so i want to use through vtp files.

Thank you very much for your help!
GAMMAR Marwen
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160517/50f5304b/attachment.html>

From joachim.pouderoux at kitware.com  Tue May 17 07:57:14 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Tue, 17 May 2016 13:57:14 +0200
Subject: [Paraview] Bug in XDMF reader ?
In-Reply-To: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
References: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
Message-ID: <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>

Houssen,

Could you specify which reader you are using? xdmf2 or xdmf3?
You mention PV5.0.0 - do you mean it used to work with previous releases?

Best,

*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2016-05-16 16:55 GMT+02:00 houssen <houssen at ipgp.fr>:

> Hello,
>
> I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when attribute
> names differ in grids, data can not be visualized : is this intended ? If
> yes why ? If no, how to file a bug ?
>
> Thanks,
>
> Franck
>
> ~> diff OK.xdmf KO.xdmf
> 48c48
> <       <Attribute Name="NodeValues" AttributeType="Scalar" Center="Node">
> ---
>
>>       <Attribute Name="NodeVal" AttributeType="Scalar" Center="Node">
>>
> 52c52
> <       <Attribute Name="CellValues" AttributeType="Scalar" Center="Cell">
> ---
>
>>       <Attribute Name="CellVal" AttributeType="Scalar" Center="Cell">
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160517/1dd029bd/attachment.html>

From houssen at ipgp.fr  Tue May 17 09:07:13 2016
From: houssen at ipgp.fr (houssen)
Date: Tue, 17 May 2016 15:07:13 +0200
Subject: [Paraview] =?utf-8?q?Bug_in_XDMF_reader_=3F?=
In-Reply-To: <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>
References: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
 <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>
Message-ID: <ebf4c9d96a628cea31d376c98435c2da@imap.ipgp.fr>

Just to clarify, the scenario that makes problem is : select all cells, 
go to selection inspector, visualize (in 3D viewer) values on cells and 
/ or points (this triggers errors).
My understanding is that both xdmf (OK and KO) are valid and should 
work. OK.xdmf works (whatever PV version), but, KO.xdmf do not (whatever 
PV version).
The problem appears when attribute names differ on different grids : 
this looks (not sure) like a bug to me.

With PV5.0.0 + default XDMF reader (which should be XDMF2 if I 
understand correctly), I get :
Warning: In 
/scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, 
line 439
vtkLabeledDataMapper (0x36cc600): Could not find label array 
(NodeValues) in input.
Warning: In 
/scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, 
line 439
vtkLabeledDataMapper (0x36cc600): Could not find label array (NodeVal) 
in input.

Note : I tested with all point and cell values, only node values 
triggers error, cell values "do nothing".

With PV5.0.0 + XDMF3 reader, I get:
'Content' not found in itemProperties in XdmfArray::populateItem
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
terminate called after throwing an instance of 'XdmfError'
   what():  'Content' not found in itemProperties in 
XdmfArray::populateItem
Aborted

With PV4.0.1 + default XDMF reader (which should be XDMF2 if I 
understand correctly), I get :
Warning: In 
/scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, 
line 442
vtkLabeledDataMapper (0x97f2140): Could not find label array (CellVal) 
in input.
Warning: In 
/scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, 
line 442
vtkLabeledDataMapper (0x97d32d0): Could not find label array (NodeVal) 
in input.

Note : I tested with all point and cell values, only CellVal and 
NodeVal triggers error, NodesValues and CellValues are visualized 
correctly.

Franck

~> diff OK.xdmf KO.xdmf
48c48
<       <Attribute Name="NodeValues" AttributeType="Scalar" 
Center="Node">
---
>       <Attribute Name="NodeVal" AttributeType="Scalar" Center="Node">
52c52
<       <Attribute Name="CellValues" AttributeType="Scalar" 
Center="Cell">
---
>       <Attribute Name="CellVal" AttributeType="Scalar" Center="Cell">


Le 2016-05-17 13:57, Joachim Pouderoux a ?crit?:
> Houssen,
>
> Could you specify which reader you are using? xdmf2 or xdmf3?
> You mention PV5.0.0 - do you mean it used to work with previous
> releases?
>
> Best,
>
> JOACHIM POUDEROUX
>
>> _PhD, Technical Expert_
>
> 2016-05-16 16:55 GMT+02:00 houssen <houssen at ipgp.fr [6]>:
>
>> Hello,
>>
>> I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when
>> attribute names differ in grids, data can not be visualized : is
>> this intended ? If yes why ? If no, how to file a bug ?
>>
>> Thanks,
>>
>> Franck
>>
>> ~> diff OK.xdmf KO.xdmf
>> 48c48
>> <? ? ? ?<Attribute Name="NodeValues" AttributeType="Scalar"
>> Center="Node">
>> ---
>>
>>> ? ? ? <Attribute Name="NodeVal" AttributeType="Scalar"
>>> Center="Node">
>> 52c52
>> <? ? ? ?<Attribute Name="CellValues" AttributeType="Scalar"
>> Center="Cell">
>> ---
>>
>>> ? ? ? <Attribute Name="CellVal" AttributeType="Scalar"
>>> Center="Cell">
>>
>> _______________________________________________
>> Powered by www.kitware.com [1]
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html [2]
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView [3]
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=ParaView [4]
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview [5]
>
>
>
> Links:
> ------
> [1] http://www.kitware.com
> [2] http://www.kitware.com/opensource/opensource.html
> [3] http://paraview.org/Wiki/ParaView
> [4] http://markmail.org/search/?q=ParaView
> [5] http://public.kitware.com/mailman/listinfo/paraview
> [6] mailto:houssen at ipgp.fr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KO.xdmf
Type: application/xml
Size: 2022 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160517/6efd8cc0/attachment.wsdl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OK.xdmf
Type: application/xml
Size: 2028 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160517/6efd8cc0/attachment-0001.wsdl>

From u.utku.turuncoglu at be.itu.edu.tr  Wed May 18 05:22:38 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Wed, 18 May 2016 12:22:38 +0300
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
Message-ID: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>

Hi All,

I just wonder about the capability of ParaView, Catalyst in distributed 
computing environment. I have little bit experience in in-situ 
visualization but it is hard for me to see the big picture at this 
point. So, i decided to ask to the user list to get some suggestion from 
the experts. Hypothetically, lets assume that we have two simulation 
code that are coupled together (i.e. fluid-structure interaction) and 
both of them have their own MPI_COMM_WORLD and run on different 
processors (model1 runs on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). 
What is the correct design to create integrated in-situ visualization 
analysis (both model contributes to same visualization pipeline) in this 
case? Do you know any implementation that is similar to this design? At 
least, is it possible?

In this case, the adaptor code will need to access to two different 
MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its 
own MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation 
code have its own grid and field definitions (might be handled via 
defining different input ports). Does it create a problem in Paraview, 
Catalyst side, if the multiblock dataset is used to define the grids of 
the components in adaptor. I am asking because some MPI processes 
(belongs to adaptor code) will not have data for specific model 
component due to the domain decomposition implementation of the 
individual models. For example, MPI rank 4,5,6,7 will not have data for 
model1 (that runs on MPI rank 0,1,2,3) and 0,1,2,3 will not have data 
for model2 (that runs on MPI rank 4,5,6,7). To that end, do i need to 
collect all the data from the components? If this is the case, how can i 
handle 2d decomposition problem? Because, the adaptor code has no any 
common grid structure that fits for all the model components.

Regards,

Ufuk Turuncoglu

From danielbo17 at hotmail.com  Wed May 18 10:16:55 2016
From: danielbo17 at hotmail.com (Daniel Oliveira)
Date: Wed, 18 May 2016 11:16:55 -0300
Subject: [Paraview] Paraview Crash
Message-ID: <BLU181-W46E05AB83B894F351B12F1CF490@phx.gbl>

Hi all,
I need Paraview to view some vtk files generated by the finite element solver LIGGGTHS.I receive a problem when I try to execute the binary of ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.This is my error:
               
I click "OK" and "RENDER VIEW". After this Paraview crash.This is the error in console.

#------------------------------------------------------------------------------------------------------------------------------#ERROR: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 587vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4 extension is not supported by your graphics driver but is required for the new OpenGL rendering backend. Please update your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2.

ERROR: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 587vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4 extension is not supported by your graphics driver but is required for the new OpenGL rendering backend. Please update your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2.#------------------------------------------------------------------------------------------------------------------------------#

I thought that was mesa driver. I have compiled the newest mesa drivers and the problem persist.Can anyone help with this problem?
My system is a Debian 8.4.0 amd64 in a HP g42-330BR notebook.Please, tell what additional info I need to inform.Thank you.
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/345f5e73/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: snapshot1.png
Type: image/png
Size: 19582 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/345f5e73/attachment.png>

From utkarsh.ayachit at kitware.com  Wed May 18 10:26:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 18 May 2016 10:26:42 -0400
Subject: [Paraview] Paraview Crash
In-Reply-To: <BLU181-W46E05AB83B894F351B12F1CF490@phx.gbl>
References: <BLU181-W46E05AB83B894F351B12F1CF490@phx.gbl>
Message-ID: <CADHSJjDDjnK0OjxGBPUqL=ggyu5mSzq2d5mVQMQFO=Wh_KWzpg@mail.gmail.com>

You may need to rebuild mesa with drivers that support OpenGL 3.2 and newer.

See this post:
https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/

Alternatively, as the post mentions, try running the binary are
> paraview --mesa-llvm

That will use the packaged mesa libGL and hopefully circumvent the issue.

Utkarsh

On Wed, May 18, 2016 at 10:16 AM, Daniel Oliveira <danielbo17 at hotmail.com>
wrote:

> Hi all,
>
> I need Paraview to view some vtk files generated by the finite element
> solver LIGGGTHS.
> I receive a problem when I try to execute the binary of
> ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.
> This is my error:
>
>
>
>
>
> I click "OK" and "RENDER VIEW". After this Paraview crash.
> This is the error in console.
>
>
>
> #------------------------------------------------------------------------------------------------------------------------------#
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 587
> vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 587
> vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
> #------------------------------------------------------------------------------------------------------------------------------#
>
>
> I thought that was mesa driver. I have compiled the newest mesa drivers
> and the problem persist.
> Can anyone help with this problem?
>
> My system is a Debian 8.4.0 amd64 in a HP g42-330BR notebook.
> Please, tell what additional info I need to inform.
> Thank you.
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/58eb1910/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: snapshot1.png
Type: image/png
Size: 19582 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/58eb1910/attachment.png>

From andy.bauer at kitware.com  Wed May 18 10:52:20 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 18 May 2016 10:52:20 -0400
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>
Message-ID: <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>

Hi,

I'm a bit confused. MPI_COMM_WORLD is the global communicator and as far as
I'm aware, can't be modified which means there can't be two different
communicators.

Catalyst can be set to use a specific MPI communicator and that's been done
by at least one code (Code_Saturne). I think they have a multiphysics
simulation as well.

Cheers,
Andy

On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi All,
>
> I just wonder about the capability of ParaView, Catalyst in distributed
> computing environment. I have little bit experience in in-situ
> visualization but it is hard for me to see the big picture at this point.
> So, i decided to ask to the user list to get some suggestion from the
> experts. Hypothetically, lets assume that we have two simulation code that
> are coupled together (i.e. fluid-structure interaction) and both of them
> have their own MPI_COMM_WORLD and run on different processors (model1 runs
> on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct design
> to create integrated in-situ visualization analysis (both model contributes
> to same visualization pipeline) in this case? Do you know any
> implementation that is similar to this design? At least, is it possible?
>
> In this case, the adaptor code will need to access to two different
> MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its own
> MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation code
> have its own grid and field definitions (might be handled via defining
> different input ports). Does it create a problem in Paraview, Catalyst
> side, if the multiblock dataset is used to define the grids of the
> components in adaptor. I am asking because some MPI processes (belongs to
> adaptor code) will not have data for specific model component due to the
> domain decomposition implementation of the individual models. For example,
> MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank
> 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI rank
> 4,5,6,7). To that end, do i need to collect all the data from the
> components? If this is the case, how can i handle 2d decomposition problem?
> Because, the adaptor code has no any common grid structure that fits for
> all the model components.
>
> Regards,
>
> Ufuk Turuncoglu
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/f2a65fc8/attachment.html>

From utkarsh.ayachit at kitware.com  Wed May 18 10:54:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 18 May 2016 10:54:47 -0400
Subject: [Paraview] Vtp file calling other files
In-Reply-To: <BAY182-W563FEAEE93A16B5781B805D1480@phx.gbl>
References: <BAY182-W563FEAEE93A16B5781B805D1480@phx.gbl>
Message-ID: <CADHSJjBEPCbB1jzpUuT2MLZGNh3B-VBqUwhiNd4aU=uAY=HksQ@mail.gmail.com>

The vtp file format doesn't support xinclude.

Utkarsh

On Tue, May 17, 2016 at 5:26 AM, Marwen Gammar <mgammar at outlook.fr> wrote:
> Hello Miss, Mister,
> I want to combine lots of files for my animation so that i can save space in
> my computer, however i get messages of error about the fact that the file
> cannot be read, could you help me please?
> Here is an example with the cube:
>
> <?xml version="1.0"?>
> <VTKFile type="PolyData" version="0.1" byte_order="LittleEndian"
> xmlns:xi="http://www.w3.org/2003/XInclude">
>  <PolyData>
>    <Piece NumberOfPoints="8" NumberOfVerts="0" NumberOfLines="0"
>           NumberOfStrips="0" NumberOfPolys="6">
>     <Points>
>      <DataArray type="Float32" NumberOfComponents="3" format="XML">
>          <xi:include href="nodes.xml" parse="text"/>
>      </DataArray>
>     </Points>
>     <PointData Scalars="my_scalars">
>      <DataArray type="Float32" Name="my_scalars" format="ascii">
> 1 2 3 4 5 6 7 0
>      </DataArray>
>     </PointData>
>     <Polys>
>      <DataArray type="Int32" Name="connectivity" format="ascii">
> 0 1 2 3 4 5 6 7 0 1 5 4 2 3 7 6 0 4 7 3 1 2 6 5
>      </DataArray>
>      <DataArray type="Int32" Name="offsets" format="ascii">
>        4 8 12 16 20 24
>      </DataArray>
>     </Polys>
>    </Piece>
>   </PolyData>
> </VTKFile>
>
> The use of Xinclude works with xdmf but i have some trouble with the
> animation, so i want to use through vtp files.
>
> Thank you very much for your help!
> GAMMAR Marwen
>
> _______________________________________________
> 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
>

From u.utku.turuncoglu at be.itu.edu.tr  Wed May 18 11:17:11 2016
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Wed, 18 May 2016 18:17:11 +0300 (EEST)
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.ou
 tlook.com>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>,
 <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
 <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <62131.95.7.172.33.1463584631.squirrel@webmail.be.itu.edu.tr>

Yes, you are right. In this case, there will be two separate
MPI_COMM_WORLD. Plus, one that covers all the resources (let's say that
global MPI_COMM_WORLD). Actually, this kind of setup is very common for
multi-physics applications such as fluid-structure interaction. So, is it
possible to tight this kind of environment with Catalyst? I am not expert
about Catalyst but it seems that there might be a problem in the rendering
stage even underlying grids and fields are defined without any problem.

Regards,

--ufuk

> I'm not sure if this is exactly what the original user is referring to,
> but it is possible to have two separate codes communicate using MPI
> through the dynamic processes in MPI-2. Essentially, one program starts up
> on N processors and begins running and gets an MPI_COMM_WORLD. It then
> spawns another executable on M different processors and that new
> executable will call MPI_INIT and also get its own MPI_COMM_WORLD. So you
> have two, disjoint MPI_COMM_WORLD's that get linked together through a
> newly created intercommunicator.
>
>
> I've used this to couple a structural mechanics code to our fluid dynamics
> solver for example. It sounds like that is similar to what is being done
> here.
>
>
> How that would interact with coprocessing is beyond my knowledge though.
> It does sound like an interesting problem and one I would be very curious
> to find out the details.
>
>
> Tim
>
>
> ________________________________
> From: ParaView <paraview-bounces at paraview.org> on behalf of Andy Bauer
> <andy.bauer at kitware.com>
> Sent: Wednesday, May 18, 2016 10:52 AM
> To: Ufuk Utku Turuncoglu (BE)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] capability of ParaView, Catalyst in distributed
> computing environment ...
>
> Hi,
>
> I'm a bit confused. MPI_COMM_WORLD is the global communicator and as far
> as I'm aware, can't be modified which means there can't be two different
> communicators.
>
> Catalyst can be set to use a specific MPI communicator and that's been
> done by at least one code (Code_Saturne). I think they have a multiphysics
> simulation as well.
>
> Cheers,
> Andy
>
> On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE)
> <u.utku.turuncoglu at be.itu.edu.tr<mailto:u.utku.turuncoglu at be.itu.edu.tr>>
> wrote:
> Hi All,
>
> I just wonder about the capability of ParaView, Catalyst in distributed
> computing environment. I have little bit experience in in-situ
> visualization but it is hard for me to see the big picture at this point.
> So, i decided to ask to the user list to get some suggestion from the
> experts. Hypothetically, lets assume that we have two simulation code that
> are coupled together (i.e. fluid-structure interaction) and both of them
> have their own MPI_COMM_WORLD and run on different processors (model1 runs
> on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct
> design to create integrated in-situ visualization analysis (both model
> contributes to same visualization pipeline) in this case? Do you know any
> implementation that is similar to this design? At least, is it possible?
>
> In this case, the adaptor code will need to access to two different
> MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its own
> MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation code
> have its own grid and field definitions (might be handled via defining
> different input ports). Does it create a problem in Paraview, Catalyst
> side, if the multiblock dataset is used to define the grids of the
> components in adaptor. I am asking because some MPI processes (belongs to
> adaptor code) will not have data for specific model component due to the
> domain decomposition implementation of the individual models. For example,
> MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank
> 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI rank
> 4,5,6,7). To that end, do i need to collect all the data from the
> components? If this is the case, how can i handle 2d decomposition
> problem? Because, the adaptor code has no any common grid structure that
> fits for all the model components.
>
> Regards,
>
> Ufuk Turuncoglu
> _______________________________________________
> Powered by www.kitware.com<http://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
>
>


From tim.gallagher at gatech.edu  Wed May 18 11:05:40 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Wed, 18 May 2016 15:05:40 +0000
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>,
 <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
Message-ID: <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.outlook.com>

I'm not sure if this is exactly what the original user is referring to, but it is possible to have two separate codes communicate using MPI through the dynamic processes in MPI-2. Essentially, one program starts up on N processors and begins running and gets an MPI_COMM_WORLD. It then spawns another executable on M different processors and that new executable will call MPI_INIT and also get its own MPI_COMM_WORLD. So you have two, disjoint MPI_COMM_WORLD's that get linked together through a newly created intercommunicator.


I've used this to couple a structural mechanics code to our fluid dynamics solver for example. It sounds like that is similar to what is being done here.


How that would interact with coprocessing is beyond my knowledge though. It does sound like an interesting problem and one I would be very curious to find out the details.


Tim


________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Andy Bauer <andy.bauer at kitware.com>
Sent: Wednesday, May 18, 2016 10:52 AM
To: Ufuk Utku Turuncoglu (BE)
Cc: paraview at paraview.org
Subject: Re: [Paraview] capability of ParaView, Catalyst in distributed computing environment ...

Hi,

I'm a bit confused. MPI_COMM_WORLD is the global communicator and as far as I'm aware, can't be modified which means there can't be two different communicators.

Catalyst can be set to use a specific MPI communicator and that's been done by at least one code (Code_Saturne). I think they have a multiphysics simulation as well.

Cheers,
Andy

On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE) <u.utku.turuncoglu at be.itu.edu.tr<mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
Hi All,

I just wonder about the capability of ParaView, Catalyst in distributed computing environment. I have little bit experience in in-situ visualization but it is hard for me to see the big picture at this point. So, i decided to ask to the user list to get some suggestion from the experts. Hypothetically, lets assume that we have two simulation code that are coupled together (i.e. fluid-structure interaction) and both of them have their own MPI_COMM_WORLD and run on different processors (model1 runs on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct design to create integrated in-situ visualization analysis (both model contributes to same visualization pipeline) in this case? Do you know any implementation that is similar to this design? At least, is it possible?

In this case, the adaptor code will need to access to two different MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its own MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation code have its own grid and field definitions (might be handled via defining different input ports). Does it create a problem in Paraview, Catalyst side, if the multiblock dataset is used to define the grids of the components in adaptor. I am asking because some MPI processes (belongs to adaptor code) will not have data for specific model component due to the domain decomposition implementation of the individual models. For example, MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI rank 4,5,6,7). To that end, do i need to collect all the data from the components? If this is the case, how can i handle 2d decomposition problem? Because, the adaptor code has no any common grid structure that fits for all the model components.

Regards,

Ufuk Turuncoglu
_______________________________________________
Powered by www.kitware.com<http://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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/ce98254a/attachment.html>

From tim.gallagher at gatech.edu  Wed May 18 11:27:18 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Wed, 18 May 2016 15:27:18 +0000
Subject: [Paraview] Spanwise averaging onto a slice
Message-ID: <BN3PR07MB262760FBB90D3D0FDF41BCDC9D490@BN3PR07MB2627.namprd07.prod.outlook.com>

I'm fairly sure this has been discussed somewhere before, but my search engine skills are failing me right now.


I would like to take the spanwise average of a 3D dataset to create a 2D plane of the averaged data. In my case, things are (relatively) friendly -- it's a channel with a uniform, structured mesh in the Z direction and I would like to average the data in Z to create an X-Y plane of the averaged data. What complicates it for me is that it is a multiblock dataset with multiple blocks in that spanwise direction.


Is there a filter or set of filters that would compute the spanwise average and return a slice as a result?


Thanks,


Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/29496ad6/attachment.html>

From utkarsh.ayachit at kitware.com  Wed May 18 12:41:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 18 May 2016 12:41:38 -0400
Subject: [Paraview] Paraview Crash
In-Reply-To: <BLU181-W10C0623EDF4768577850A4CF490@phx.gbl>
References: <BLU181-W46E05AB83B894F351B12F1CF490@phx.gbl>
 <CADHSJjDDjnK0OjxGBPUqL=ggyu5mSzq2d5mVQMQFO=Wh_KWzpg@mail.gmail.com>
 <BLU181-W10C0623EDF4768577850A4CF490@phx.gbl>
Message-ID: <CADHSJjAbafy6YbnKQNV9E9GmmdY6wSWhY58sG6ZzX0BQEVnSUA@mail.gmail.com>

Awesome! Glad it's working.

On Wed, May 18, 2016 at 11:48 AM, Daniel Oliveira <danielbo17 at hotmail.com>
wrote:

> I resolved part of my problem with the command
>
> > paraview --mesa-llvm
>
> Now I can open Paraview to see my vtk files.
> I will try to compile my drivers with support to OpenGL 3.2 in the future.
> For now, problem solved.
>
> Thank you very much my friend.
>
> ------------------------------
> Date: Wed, 18 May 2016 10:26:42 -0400
> Subject: Re: [Paraview] Paraview Crash
> From: utkarsh.ayachit at kitware.com
> To: danielbo17 at hotmail.com
> CC: paraview at paraview.org
>
>
> You may need to rebuild mesa with drivers that support OpenGL 3.2 and
> newer.
>
> See this post:
> https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/
>
> Alternatively, as the post mentions, try running the binary are
> > paraview --mesa-llvm
>
> That will use the packaged mesa libGL and hopefully circumvent the issue.
>
> Utkarsh
>
> On Wed, May 18, 2016 at 10:16 AM, Daniel Oliveira <danielbo17 at hotmail.com>
> wrote:
>
> Hi all,
>
> I need Paraview to view some vtk files generated by the finite element
> solver LIGGGTHS.
> I receive a problem when I try to execute the binary of
> ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.
> This is my error:
>
>
>
>
>
> I click "OK" and "RENDER VIEW". After this Paraview crash.
> This is the error in console.
>
>
>
> #------------------------------------------------------------------------------------------------------------------------------#
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 587
> vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 587
> vtkXOpenGLRenderWindow (0x20bac10): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
> #------------------------------------------------------------------------------------------------------------------------------#
>
>
> I thought that was mesa driver. I have compiled the newest mesa drivers
> and the problem persist.
> Can anyone help with this problem?
>
> My system is a Debian 8.4.0 amd64 in a HP g42-330BR notebook.
> Please, tell what additional info I need to inform.
> Thank you.
>
>
> _______________________________________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/42281a60/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: snapshot1.png
Type: image/png
Size: 19582 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160518/42281a60/attachment.png>

From wascott at sandia.gov  Wed May 18 21:52:01 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 19 May 2016 01:52:01 +0000
Subject: [Paraview] How to copy "global variable" data to a variable in
	Python
Message-ID: <35b5b937b4bb4217b610848852421c27@ES01AMSNLNT.srn.sandia.gov>



If I want to get the numeric value of an "Annotate Global Variable" variable so that I can use it later in a python script, how do I do that? E.g. take the global variable, make it into a string, and display it as text

Thanks,

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/c51dfbd9/attachment.html>

From wascott at sandia.gov  Wed May 18 21:53:32 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 19 May 2016 01:53:32 +0000
Subject: [Paraview] Python question - ElementBlocks
Message-ID: <b6c717e56b7e45b986e96ff82f40e2d6@ES01AMSNLNT.srn.sandia.gov>

Is it necessary to include the list of blocks in the script similar to the line below or is it possible to say "all" to include all of the blocks all of the time or something similar?



o   activesourcefile.ElementBlocks = ['block_1', 'block_2', 'block_3']


Thanks,

Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/e2b45ef2/attachment.html>

From stephane at fujielectric.com  Thu May 19 00:54:13 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Thu, 19 May 2016 13:54:13 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
Message-ID: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>

Hello,
I've been trying to "superbuild" paraview 5.0 on Win7 without success.
I keep getting two errors:
1) the first one is related to szip at the beginning of the build
2) the second and last one is  ninja: build stopped: subcommand failed

nothing else.
I really need some help please...

Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/b591234d/attachment.html>
-------------- next part --------------
# This is the CMakeCache file.
# For build in directory: c:/superbuild
# It was generated by CMake: C:/Program Files (x86)/CMake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Path to a program.
7Z_EXE:FILEPATH=C:/Program Files/7-Zip/7z.exe

//Enable shared libraries
BUILD_SHARED_LIBS:BOOL=ON

//Build the testing tree.
BUILD_TESTING:BOOL=ON

//Path to a program.
BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND

//Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
// CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.
CMAKE_BUILD_TYPE:STRING=Debug

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/amd64/cl.exe

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3 /GR /EHsc

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG

//Libraries linked by default with all C++ applications.
CMAKE_CXX_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/amd64/cl.exe

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG

//Flags used by the compiler during release builds.
CMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING= /machine:x64

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/Program Files/ParaViewSuperBuild

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/amd64/link.exe

//Program used to build from build.ninja files.
CMAKE_MAKE_PROGRAM:FILEPATH=C:/superbuild/ninja.exe

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING= /machine:x64

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=ParaViewSuperBuild

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=C:/Strawberry/c/bin/windres.exe

//Flags for Windows Resource Compiler.
CMAKE_RC_FLAGS:STRING=' /DWIN32 '

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING= /machine:x64

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=OFF

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=OFF

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING= /machine:x64

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=OFF

//Path to the coverage program that CTest uses for performing coverage
// inspection
COVERAGE_COMMAND:FILEPATH=C:/Strawberry/c/bin/gcov.exe

//Extra command line flags to pass to the coverage tool
COVERAGE_EXTRA_FLAGS:STRING=-l

//Enable to build 7-Zip packages
CPACK_BINARY_7Z:BOOL=OFF

//Enable to build IFW packages
CPACK_BINARY_IFW:BOOL=OFF

//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=ON

//Enable to build WiX packages
CPACK_BINARY_WIX:BOOL=OFF

//Enable to build ZIP packages
CPACK_BINARY_ZIP:BOOL=OFF

//Enable to build 7-Zip source packages
CPACK_SOURCE_7Z:BOOL=ON

//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=ON

//Cross compilation stage: either HOST(ie no crosscompile)|TOOLS|CROSS
CROSS_BUILD_STAGE:STRING=HOST

//How many times to retry timed-out CTest submissions.
CTEST_SUBMIT_RETRY_COUNT:STRING=3

//How long to wait between timed-out CTest submissions.
CTEST_SUBMIT_RETRY_DELAY:STRING=5

//Path to a program.
CVSCOMMAND:FILEPATH=CVSCOMMAND-NOTFOUND

//Options passed to the cvs update command.
CVS_UPDATE_OPTIONS:STRING=-d -A -P

//Maximum time allowed before CTest will kill the test.
DART_TESTING_TIMEOUT:STRING=1500

//Path to a program.
DEVENV_PATH:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/Common7/IDE/devenv.com

//Request to build project bzip2
ENABLE_bzip2:BOOL=OFF

//Request to build project cgns
ENABLE_cgns:BOOL=ON

ENABLE_ffmpeg:BOOL=OFF

//Request to build project libxml2
ENABLE_libxml2:BOOL=OFF

//Request to build project manta
ENABLE_manta:BOOL=OFF

//Request to build project matplotlib
ENABLE_matplotlib:BOOL=ON

//Request to build project mpi
ENABLE_mpi:BOOL=ON

//Request to build project netcdf
ENABLE_netcdf:BOOL=OFF

//Request to build project numpy
ENABLE_numpy:BOOL=ON

//Request to build project paraview
ENABLE_paraview:BOOL=ON

//Request to build project png
ENABLE_png:BOOL=OFF

//Request to build project python
ENABLE_python:BOOL=ON

//Request to build project qt4
ENABLE_qt4:BOOL=ON

//Request to build Qt5. Enable this to build the user interface
// with Qt5.
ENABLE_qt5:BOOL=OFF

//Request to build project silo
ENABLE_silo:BOOL=ON

//Request to build project tbb
ENABLE_tbb:BOOL=ON

//Request to build project visitbridge
ENABLE_visitbridge:BOOL=OFF

//Request to build project vortexfinder2
ENABLE_vortexfinder2:BOOL=OFF

//Request to build project vrpn
ENABLE_vrpn:BOOL=OFF

//Request to build project xdmf3
ENABLE_xdmf3:BOOL=ON

FTJAM_EXECUTABLE:FILEPATH=C:/Users/2114122/Downloads/jam.exe

//Path to a program.
GITCOMMAND:FILEPATH=C:/Program Files/Git/cmd/git.exe

//Git command line client
GIT_EXECUTABLE:FILEPATH=C:/Program Files/Git/cmd/git.exe

//Path to a program.
HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND

//Command to build the project
MAKECOMMAND:STRING="C:\Program Files (x86)\CMake\bin\cmake.exe" --build . --config "${CTEST_CONFIGURATION_TYPE}"

//Path to the memory checking command, used for memory error detection.
MEMORYCHECK_COMMAND:FILEPATH=MEMORYCHECK_COMMAND-NOTFOUND

//File that contains suppressions for the memory checker
MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH=

//Executable for running MPI programs.
MPIEXEC:FILEPATH=C:/Program Files/Microsoft HPC Pack 2008 R2/Bin/mpiexec.exe

//Maximum number of processors available to run MPI applications.
MPIEXEC_MAX_NUMPROCS:STRING=24

//Flag used by MPI to specify the number of processes for MPIEXEC;
// the next option will be the number of processes.
MPIEXEC_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIEXEC.
MPIEXEC_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by MPIEXEC.
MPIEXEC_PREFLAGS:STRING=

//Path to a program.
MPI_CXX_COMPILER:FILEPATH=MPI_CXX_COMPILER-NOTFOUND

//MPI CXX compilation flags
MPI_CXX_COMPILE_FLAGS:STRING=

//MPI CXX include path
MPI_CXX_INCLUDE_PATH:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Inc

//MPI CXX libraries to link against
MPI_CXX_LIBRARIES:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Lib/amd64/msmpi.lib

//MPI CXX linking flags
MPI_CXX_LINK_FLAGS:STRING=

//Path to a program.
MPI_C_COMPILER:FILEPATH=MPI_C_COMPILER-NOTFOUND

//MPI C compilation flags
MPI_C_COMPILE_FLAGS:STRING=

//MPI C include path
MPI_C_INCLUDE_PATH:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Inc

//MPI C libraries to link against
MPI_C_LIBRARIES:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Lib/amd64/msmpi.lib

//MPI C linking flags
MPI_C_LINK_FLAGS:STRING=

//Extra MPI libraries to link against
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND

//MPI library to link against
MPI_LIBRARY:FILEPATH=C:/Program Files/Microsoft HPC Pack 2008 R2/Lib/amd64/msmpi.lib

//Path to a file.
MSVC12_REDIST_DIR:PATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/redist

//Path to a program.
NMAKE_PATH:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/nmake.exe

//Path to a program.
P4COMMAND:FILEPATH=P4COMMAND-NOTFOUND

//String to use as a suffix for generated packages
PACKAGE_SUFFIX:STRING=<default>

//GIT_REPOSITORY for project 'paraview'
PARAVIEW_GIT_REPOSITORY:STRING=https://gitlab.kitware.com/paraview/paraview.git

//GIT_TAG for project 'paraview'
PARAVIEW_GIT_TAG:STRING=master

//Rendering backend to use for ParaView
PARAVIEW_RENDERING_BACKEND:STRING=OpenGL

//Specify the version number for the package being generated e.g.
// 5.0.1
PARAVIEW_VERSION:STRING=5.0.1

//Provide the list of Projects that ParaView should additionally
// depends on
PV_EXTERNAL_PROJECTS:STRING=

//Extra arguments to be passed to ParaView when configuring.
PV_EXTRA_CMAKE_ARGS:STRING=

//Number of make jobs to use for compiling ParaView itself
PV_MAKE_NCPUS:STRING=5

//Value Computed by CMake
ParaViewSuperBuild_BINARY_DIR:STATIC=C:/superbuild

//Value Computed by CMake
ParaViewSuperBuild_SOURCE_DIR:STATIC=C:/Paraview

//If enabled then the repository is fetched from git
ParaView_FROM_GIT:BOOL=ON

//Which browser to use during testing, either chrome or firefox
REMOTE_PVWEB_TEST_BROWSER:STRING=firefox

//A list of urls against which to run a simple Web Visualizer test.
REMOTE_PVWEB_VISUALIZER_URLS:STRING=http://pvw-test.kitware.com/sbtest;http://pvw.kitware.com/sbtest;http://paraviewweb.kitware.com/sbtest

//Path to scp command, used by CTest for submitting results to
// a Dart server
SCPCOMMAND:FILEPATH=SCPCOMMAND-NOTFOUND

//Name of the computer/site where compile is being run
SITE:STRING=KFMV9893

//Path to the SLURM sbatch executable
SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND

//Path to the SLURM srun executable
SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND

//Path to a program.
SVNCOMMAND:FILEPATH=SVNCOMMAND-NOTFOUND

//When enabled, tests a live instance of ParaViewWeb.
TEST_REMOTE_PARAVIEW_WEB:BOOL=OFF

//Trust SVN certificates automatically
TRUST_SVN_CERTIFICATES_AUTOMATICALLY:BOOL=ON

//Enable the non-free parts of the superbuild
USE_NONFREE_COMPONENTS:BOOL=OFF

//Use system hdf5
USE_SYSTEM_hdf5:BOOL=OFF

//Use system qt4
USE_SYSTEM_qt4:BOOL=OFF

//Use system tbb
USE_SYSTEM_tbb:BOOL=OFF

//GIT_REPOSITORY for project 'vortexfinder2'
VORTEXFINDER2_GIT_REPOSITORY:STRING=https://github.com/tjcorona/vortexfinder2.git

//GIT_TAG for project 'vortexfinder2'
VORTEXFINDER2_GIT_TAG:STRING=master

//Location where source tar-balls are (to be) downloaded.
download_location:PATH=C:/superbuild/downloads

//Extra arguments to be passed to Qt when configuring.
qt_EXTRA_CONFIGURATION_OPTIONS:STRING=


########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: BZRCOMMAND
BZRCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=c:/superbuild
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=5
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=2
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/cpack.exe
//ADVANCED property for variable: CMAKE_CTEST_COMMAND
CMAKE_CTEST_COMMAND-ADVANCED:INTERNAL=1
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_STANDARD_LIBRARIES
CMAKE_CXX_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=C:/Paraview
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=2
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=C:/Program Files (x86)/CMake/share/cmake-3.5
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_COMMAND
COVERAGE_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_EXTRA_FLAGS
COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_7Z
CPACK_BINARY_7Z-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_IFW
CPACK_BINARY_IFW-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_NSIS
CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_WIX
CPACK_BINARY_WIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_ZIP
CPACK_BINARY_ZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_7Z
CPACK_SOURCE_7Z-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_ZIP
CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1
//STRINGS property for variable: CROSS_BUILD_STAGE
CROSS_BUILD_STAGE-STRINGS:INTERNAL=HOST;TOOLS;CROSS
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT
CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY
CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVSCOMMAND
CVSCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVS_UPDATE_OPTIONS
CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_TESTING_TIMEOUT
DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DEVENV_PATH
DEVENV_PATH-ADVANCED:INTERNAL=1
//Request to build project boost
ENABLE_boost:INTERNAL=OFF
//Request to build project freetype
ENABLE_freetype:INTERNAL=OFF
//Request to build project hdf5
ENABLE_hdf5:INTERNAL=OFF
//Request to build project szip
ENABLE_szip:INTERNAL=OFF
//Request to build project zlib
ENABLE_zlib:INTERNAL=OFF
//Details about finding MPI_C
FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[C:/Program Files/Microsoft HPC Pack 2008 R2/Lib/amd64/msmpi.lib][C:/Program Files/Microsoft HPC Pack 2008 R2/Inc][v()]
//Details about finding MPI_CXX
FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[C:/Program Files/Microsoft HPC Pack 2008 R2/Lib/amd64/msmpi.lib][C:/Program Files/Microsoft HPC Pack 2008 R2/Inc][v()]
//ADVANCED property for variable: GITCOMMAND
GITCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VOID_PTR_SIZE:INTERNAL=TRUE
//ADVANCED property for variable: HGCOMMAND
HGCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MAKECOMMAND
MAKECOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_COMMAND
MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE
MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC
MPIEXEC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS
MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG
MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_POSTFLAGS
MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_PREFLAGS
MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILER
MPI_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS
MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_INCLUDE_PATH
MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LIBRARIES
MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LINK_FLAGS
MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILER
MPI_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILE_FLAGS
MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_INCLUDE_PATH
MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_LIBRARIES
MPI_C_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_LINK_FLAGS
MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1
//Scratch variable for MPI header detection
MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND
//Scratch variable for MPI lib detection
MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND
//ADVANCED property for variable: MSVC12_REDIST_DIR
MSVC12_REDIST_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NMAKE_PATH
NMAKE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: P4COMMAND
P4COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PACKAGE_SUFFIX
PACKAGE_SUFFIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_FREEZE_PYTHON
PARAVIEW_FREEZE_PYTHON-ADVANCED:INTERNAL=1
//Freeze Python packages/modules into the application.
PARAVIEW_FREEZE_PYTHON:INTERNAL=OFF
//ADVANCED property for variable: PARAVIEW_GIT_REPOSITORY
PARAVIEW_GIT_REPOSITORY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_GIT_TAG
PARAVIEW_GIT_TAG-ADVANCED:INTERNAL=1
//STRINGS property for variable: PARAVIEW_RENDERING_BACKEND
PARAVIEW_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2
//ADVANCED property for variable: PARAVIEW_VERSION
PARAVIEW_VERSION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_EXTERNAL_PROJECTS
PV_EXTERNAL_PROJECTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_EXTRA_CMAKE_ARGS
PV_EXTRA_CMAKE_ARGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_MAKE_NCPUS
PV_MAKE_NCPUS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: REMOTE_PVWEB_TEST_BROWSER
REMOTE_PVWEB_TEST_BROWSER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: REMOTE_PVWEB_VISUALIZER_URLS
REMOTE_PVWEB_VISUALIZER_URLS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SCPCOMMAND
SCPCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SITE
SITE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SLURM_SBATCH_COMMAND
SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SLURM_SRUN_COMMAND
SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SVNCOMMAND
SVNCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TEST_REMOTE_PARAVIEW_WEB
TEST_REMOTE_PARAVIEW_WEB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TRUST_SVN_CERTIFICATES_AUTOMATICALLY
TRUST_SVN_CERTIFICATES_AUTOMATICALLY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: USE_NONFREE_COMPONENTS
USE_NONFREE_COMPONENTS-ADVANCED:INTERNAL=1
//Use system bzip2
USE_SYSTEM_bzip2:INTERNAL=OFF
//Use system libxml2
USE_SYSTEM_libxml2:INTERNAL=OFF
//Use system netcdf
USE_SYSTEM_netcdf:INTERNAL=OFF
//Use system png
USE_SYSTEM_png:INTERNAL=OFF
//Use system qt5
USE_SYSTEM_qt5:INTERNAL=OFF
//Use system zlib
USE_SYSTEM_zlib:INTERNAL=OFF
//CHECK_TYPE_SIZE: sizeof(void*)
VOID_PTR_SIZE:INTERNAL=8
//ADVANCED property for variable: VORTEXFINDER2_GIT_REPOSITORY
VORTEXFINDER2_GIT_REPOSITORY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VORTEXFINDER2_GIT_TAG
VORTEXFINDER2_GIT_TAG-ADVANCED:INTERNAL=1
boost_ENABLED:INTERNAL=TRUE
cgns_ENABLED:INTERNAL=TRUE
//ADVANCED property for variable: download_location
download_location-ADVANCED:INTERNAL=1
freetype_ENABLED:INTERNAL=TRUE
hdf5_ENABLED:INTERNAL=TRUE
matplotlib_ENABLED:INTERNAL=TRUE
mpi_ENABLED:INTERNAL=TRUE
numpy_ENABLED:INTERNAL=TRUE
paraview_ENABLED:INTERNAL=TRUE
python_ENABLED:INTERNAL=TRUE
qt4_ENABLED:INTERNAL=TRUE
silo_ENABLED:INTERNAL=TRUE
szip_ENABLED:INTERNAL=TRUE
tbb_ENABLED:INTERNAL=TRUE
xdmf3_ENABLED:INTERNAL=TRUE
zlib_ENABLED:INTERNAL=TRUE


From stephane at fujielectric.com  Thu May 19 01:49:10 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Thu, 19 May 2016 14:49:10 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
Message-ID: <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>

Hello,

I am sending a Log of the building process

Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394


On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
stephane at fujielectric.com> wrote:

> Hello,
> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
> I keep getting two errors:
> 1) the first one is related to szip at the beginning of the build
> 2) the second and last one is  ninja: build stopped: subcommand failed
>
> nothing else.
> I really need some help please...
>
> Ndong-Mefane Stephane, Dr.Eng
> Basic Design Sec.
> Steam Turbine Dept.
> Kawasaki Factory
>
> Fuji Electric Co., Ltd
> 1-1, Tanabeshinden, Kawasaki-ku,
> Kawasaki-city 210-9530, Japan
> Phone: +81-44-329-2155
> Fax: +81-44-329-2394
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/bfb5def1/attachment.html>
-------------- next part --------------
[1/123] Creating directories for 'zlib'
[2/123] Creating directories for 'mpi'
[3/123] Creating directories for 'qt4'
[4/123] Creating directories for 'python'
[5/123] Creating directories for 'szip'
[6/123] Creating directories for 'tbb'
[7/123] No download step for 'zlib'
[8/123] No download step for 'mpi'
[9/123] No update step for 'zlib'
[10/123] No patch step for 'zlib'
[11/123] No update step for 'mpi'
[12/123] No patch step for 'mpi'
[13/123] No configure step for 'mpi'
[14/123] No build step for 'mpi'
[15/123] No install step for 'mpi'
[16/123] Completed 'mpi'
[17/123] Performing download step (download, verify and extract) for 'szip'
-- downloading...

     src='http://paraview.org/files/dependencies/szip-2.1.tar.gz'

     dst='C:/superbuild/downloads/szip-2.1.tar.gz'

     timeout='none'

-- [download 100% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 27% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 41% complete]

-- [download 43% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 51% complete]

-- [download 55% complete]

-- [download 59% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 75% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/szip-2.1.tar.gz'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/szip-2.1.tar.gz'

     dst='C:/superbuild/szip/src/szip'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[18/123] No update step for 'szip'
[19/123] Performing patch_fix_install step for 'szip'
[20/123] Performing patch step for 'szip'
[21/123] Performing configure step for 'szip'
FAILED: szip/src/szip-stamp/szip-configure 
cmd.exe /C "cd /D C:\superbuild\szip\src\szip-build && "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=C:/superbuild/install -DCMAKE_PREFIX_PATH:PATH=C:/superbuild/install "-DCMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3" "-DCMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc" -DCMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64 -DCMAKE_BUILD_TYPE:STRING=Debug "-DCMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" -GNinja C:/superbuild/szip/src/szip && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/szip/src/szip-stamp/szip-configure"
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

[22/123] Performing download step (download, verify and extract) for 'tbb'
-- downloading...

     src='http://www.paraview.org/files/dependencies/tbb44_20150728oss_win.zip'

     dst='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

     timeout='none'

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

     dst='C:/superbuild/tbb/src/tbb'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[23/123] Performing download step (download, verify and extract) for 'python'
-- downloading...

     src='http://www.paraview.org/files/dependencies/python+deps.tar.bz2'

     dst='C:/superbuild/downloads/python+deps.tar.bz2'

     timeout='none'

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/python+deps.tar.bz2'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/python+deps.tar.bz2'

     dst='C:/superbuild/python/src/python'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[24/123] Performing download step (download, verify and extract) for 'qt4'
-- downloading...

     src='http://paraview.org/files/dependencies/qt-everywhere-opensource-src-4.8.4.tar.gz'

     dst='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

     timeout='none'

-- [download 100% complete]

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

     dst='C:/superbuild/qt4/src/qt4'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

ninja: build stopped: subcommand failed.

From jfavre at cscs.ch  Thu May 19 03:10:05 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Thu, 19 May 2016 07:10:05 +0000
Subject: [Paraview] Spanwise averaging onto a slice
In-Reply-To: <BN3PR07MB262760FBB90D3D0FDF41BCDC9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760FBB90D3D0FDF41BCDC9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684360EA77@MBX211.d.ethz.ch>


the following article discusses averaging techniques, such as a 3D longitudinal averaging, which is what you are looking for.

looping over your multi-blocks should be a rather simple extension.

https://blog.kitware.com/paraviews-python-programmable-filters-in-geophysics/

-----------------
Jean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/ba89099f/attachment.html>

From cgunases at gmail.com  Thu May 19 03:40:59 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Thu, 19 May 2016 13:10:59 +0530
Subject: [Paraview] How to get the object contour?
Message-ID: <CAJFKOL37vLsGmfoYdD-b013Uhh8trDRpZa40N+j97=uEUr8tGA@mail.gmail.com>

Hi ,

With the generated 3D model, i have 2 questions, as follows:

(1). i can only see separate slices instead of the contour of the object,
How to get the object contour?

Following is what i followed:
 [selected Filter--> alphabetical-->calculate-->scalars-->volume
scalars-->Apply--> coloring(Result)--> representation (volume) ]

(2) Is there a specific way to add Slice Thickness in Paraview?

Thank you in advance.

-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/cd462342/attachment.html>

From joachim.pouderoux at kitware.com  Thu May 19 03:42:13 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Thu, 19 May 2016 09:42:13 +0200
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
Message-ID: <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>

Hello,

Did you compiled ninja using your VS2013?
Do you start ninja from a Visual Studio 2013 command line (so that cmake
can find VS compiler in the environment)?

Regards,



*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:

> Hello,
>
> I am sending a Log of the building process
>
> Ndong-Mefane Stephane, Dr.Eng
> Basic Design Sec.
> Steam Turbine Dept.
> Kawasaki Factory
>
> Fuji Electric Co., Ltd
> 1-1, Tanabeshinden, Kawasaki-ku,
> Kawasaki-city 210-9530, Japan
> Phone: +81-44-329-2155
> Fax: +81-44-329-2394
>
>
> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
> stephane at fujielectric.com> wrote:
>
>> Hello,
>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>> I keep getting two errors:
>> 1) the first one is related to szip at the beginning of the build
>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>
>> nothing else.
>> I really need some help please...
>>
>> Ndong-Mefane Stephane, Dr.Eng
>> Basic Design Sec.
>> Steam Turbine Dept.
>> Kawasaki Factory
>>
>> Fuji Electric Co., Ltd
>> 1-1, Tanabeshinden, Kawasaki-ku,
>> Kawasaki-city 210-9530, Japan
>> Phone: +81-44-329-2155
>> Fax: +81-44-329-2394
>>
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/33b5c648/attachment.html>

From stephane at fujielectric.com  Thu May 19 04:05:36 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Thu, 19 May 2016 17:05:36 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
 <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
Message-ID: <CADLMsL4-YM-QCimhSqsqWA9DuH=VV5E-xgb3AUYcXABJ6fiSSg@mail.gmail.com>

Hello Joachim,

I downloaded ninja binary from here: https://ninja-build.org/
and I'm starting ninja as well as the cmake gui from the Visual Studio 2013
cross-platform command line

????
??????? ?????
????-???? ?????
????

????????
?210-9530??????????1-1
TEL 044-329-2155 FAX 044-329-2394

On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Hello,
>
> Did you compiled ninja using your VS2013?
> Do you start ninja from a Visual Studio 2013 command line (so that cmake
> can find VS compiler in the environment)?
>
> Regards,
>
>
>
> *Joachim Pouderoux*
>
> *PhD, Technical Expert*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:
>
>> Hello,
>>
>> I am sending a Log of the building process
>>
>> Ndong-Mefane Stephane, Dr.Eng
>> Basic Design Sec.
>> Steam Turbine Dept.
>> Kawasaki Factory
>>
>> Fuji Electric Co., Ltd
>> 1-1, Tanabeshinden, Kawasaki-ku,
>> Kawasaki-city 210-9530, Japan
>> Phone: +81-44-329-2155
>> Fax: +81-44-329-2394
>>
>>
>> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
>> stephane at fujielectric.com> wrote:
>>
>>> Hello,
>>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>>> I keep getting two errors:
>>> 1) the first one is related to szip at the beginning of the build
>>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>>
>>> nothing else.
>>> I really need some help please...
>>>
>>> Ndong-Mefane Stephane, Dr.Eng
>>> Basic Design Sec.
>>> Steam Turbine Dept.
>>> Kawasaki Factory
>>>
>>> Fuji Electric Co., Ltd
>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>> Kawasaki-city 210-9530, Japan
>>> Phone: +81-44-329-2155
>>> Fax: +81-44-329-2394
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/2c81ab90/attachment.html>

From stephane at fujielectric.com  Thu May 19 04:38:46 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Thu, 19 May 2016 17:38:46 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CADLMsL4-YM-QCimhSqsqWA9DuH=VV5E-xgb3AUYcXABJ6fiSSg@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
 <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
 <CADLMsL4-YM-QCimhSqsqWA9DuH=VV5E-xgb3AUYcXABJ6fiSSg@mail.gmail.com>
Message-ID: <CADLMsL6F75PwkYtJZkFg_D1KJYXdpZU4v4Xd8peDvfz3JjruSA@mail.gmail.com>

Hello,

I compiled a ninja binary from vs2013 command prompt and used it for the
superbuild but still the same problem.


Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394


On Thu, May 19, 2016 at 5:05 PM, stephane???? ???? <
stephane at fujielectric.com> wrote:

> Hello Joachim,
>
> I downloaded ninja binary from here: https://ninja-build.org/
> and I'm starting ninja as well as the cmake gui from the Visual Studio
> 2013 cross-platform command line
>
> ????
> ??????? ?????
> ????-???? ?????
> ????
>
> ????????
> ?210-9530??????????1-1
> TEL 044-329-2155 FAX 044-329-2394
>
> On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <
> joachim.pouderoux at kitware.com> wrote:
>
>> Hello,
>>
>> Did you compiled ninja using your VS2013?
>> Do you start ninja from a Visual Studio 2013 command line (so that cmake
>> can find VS compiler in the environment)?
>>
>> Regards,
>>
>>
>>
>> *Joachim Pouderoux*
>>
>> *PhD, Technical Expert*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:
>>
>>> Hello,
>>>
>>> I am sending a Log of the building process
>>>
>>> Ndong-Mefane Stephane, Dr.Eng
>>> Basic Design Sec.
>>> Steam Turbine Dept.
>>> Kawasaki Factory
>>>
>>> Fuji Electric Co., Ltd
>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>> Kawasaki-city 210-9530, Japan
>>> Phone: +81-44-329-2155
>>> Fax: +81-44-329-2394
>>>
>>>
>>> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
>>> stephane at fujielectric.com> wrote:
>>>
>>>> Hello,
>>>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>>>> I keep getting two errors:
>>>> 1) the first one is related to szip at the beginning of the build
>>>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>>>
>>>> nothing else.
>>>> I really need some help please...
>>>>
>>>> Ndong-Mefane Stephane, Dr.Eng
>>>> Basic Design Sec.
>>>> Steam Turbine Dept.
>>>> Kawasaki Factory
>>>>
>>>> Fuji Electric Co., Ltd
>>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>>> Kawasaki-city 210-9530, Japan
>>>> Phone: +81-44-329-2155
>>>> Fax: +81-44-329-2394
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/64cd5710/attachment.html>

From utkarsh.ayachit at kitware.com  Thu May 19 08:11:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 19 May 2016 08:11:38 -0400
Subject: [Paraview] Python question - ElementBlocks
In-Reply-To: <b6c717e56b7e45b986e96ff82f40e2d6@ES01AMSNLNT.srn.sandia.gov>
References: <b6c717e56b7e45b986e96ff82f40e2d6@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAyG_x9mN6yp5gs5ynDDeA_5c=jPFt=WAA8Sx-n1Y0b5w@mail.gmail.com>

The following should do the trick:

    activesourcefile.ElementBlocks.SelectAll()

Calling help(activesourcefile.ElementBlocks) will show info about all
available API (extract below):

  help(a.ElementBlocks)
  Help on ArrayListProperty in module paraview.servermanager object:

  class ArrayListProperty(VectorProperty)
   |  This property provides a simpler interface for selecting arrays.
   |  Simply assign a list of arrays that should be loaded by the reader.
   |  Use the Available property to get a list of available arrays.
   |
   ...
   |  Methods defined here:
   |
   |  DeselectAll(self)
   |      Deselects all arrays.
   |
   |  GetAvailable(self)
   |      Returns the list of available arrays
   |
   |  GetData(self)
   |      Returns all elements as a list.
   |
   |  SelectAll(self)
   |      Selects all arrays.
   |
   |  SetData(self, values)
   |      Allows setting of all values at once. Requires a single value,
   |      a tuple or list.
   ...
   |
   |  ----------------------------------------------------------------------
   |  Data descriptors defined here:
   |
   |  Available
   |      This read-only property contains the list of items that can
be read by a reader.
   |
   ...

Utkarsh

On Wed, May 18, 2016 at 9:53 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Is it necessary to include the list of blocks in the script similar to the
> line below or is it possible to say "all" to include all of the blocks all
> of the time or something similar?
>
>
>
> o   activesourcefile.ElementBlocks = ['block_1', 'block_2', 'block_3']
>
>
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
>
> _______________________________________________
> 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
>

From samuelkey at bresnan.net  Thu May 19 11:35:52 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Thu, 19 May 2016 09:35:52 -0600
Subject: [Paraview] How to get the object contour?
In-Reply-To: <CAJFKOL37vLsGmfoYdD-b013Uhh8trDRpZa40N+j97=uEUr8tGA@mail.gmail.com>
References: <CAJFKOL37vLsGmfoYdD-b013Uhh8trDRpZa40N+j97=uEUr8tGA@mail.gmail.com>
Message-ID: <652efbec-81c1-4514-e764-1606f570c0ba@bresnan.net>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/cee275bd/attachment.html>

From michalwozniak at live.ca  Thu May 19 13:11:30 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Thu, 19 May 2016 13:11:30 -0400
Subject: [Paraview] =?cp1256?q?Paraview_Web_5_show_Widget=FE?=
Message-ID: <BLU180-W1DC15AF30AC36C41FB35EAD4A0@phx.gbl>

Hi everyone,I have been trying for the past couple of day to replicate the show Widget (eg : show Plane, show Box display ) in ParaView web. In the desktop version, when you add a filter slice with Plane type, you get a red rectangle representing your widget with axes to easily move it. How do you enable this feature in ParaView web? In some old version of ParaView ( http://www.paraview.org/Wiki/ParaViewWeb_PWApp) it was possible. ThanksMichal  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/1d96ddcb/attachment.html>

From sebastien.jourdain at kitware.com  Thu May 19 13:22:31 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 19 May 2016 11:22:31 -0600
Subject: [Paraview] =?utf-8?q?Paraview_Web_5_show_Widget=E2=80=8F?=
In-Reply-To: <BLU180-W1DC15AF30AC36C41FB35EAD4A0@phx.gbl>
References: <BLU180-W1DC15AF30AC36C41FB35EAD4A0@phx.gbl>
Message-ID: <CABObKxd2weEPpBUkJymMhK+jEa1N0Sih6K1it57xha_=mgePcA@mail.gmail.com>

Hi Michal,

That feature is not currently available as a protocol on the Python side.

It is possible to add it back, but will take some time especially since we
have other focus regarding the Visualizer improvements...
Moreover, we dynamically generate the UI, which will make the 3D widget
toggle a little be more trickier compare to a adhoc UI like the one that
was done for PWApp.

Are you trying to enable it for a custom application, or are you looking
for having that feature in the ParaViewWeb Visualizer?

Seb





On Thu, May 19, 2016 at 11:11 AM, michal wozniak <michalwozniak at live.ca>
wrote:

> Hi everyone,
>
> I have been trying for the past couple of day to replicate the show Widget
> (eg : show Plane, show Box display ) in ParaView web. In the desktop
> version, when you add a filter slice with Plane type, you get a red
> rectangle representing your widget with axes to easily move it.
>
> How do you enable this feature in ParaView web? In some old version of
> ParaView ( http://www.paraview.org/Wiki/ParaViewWeb_PWApp) it was
> possible.
>
> Thanks
>
> Michal
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/140e7b85/attachment.html>

From svenkramer40 at gmail.com  Thu May 19 15:52:03 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Thu, 19 May 2016 21:52:03 +0200
Subject: [Paraview] Connect ParaViewWeb to Catalyst
Message-ID: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>

Hello,
I am looking for the recommended steps how to display an in-situ (live)
Catalyst simulation through ParaViewWeb.

After some efforts I am able to run ParaViewWeb successfully and I can view
a Catalyst-enabled simulation in paraview.

I hope, it is also possible to show the live Catalyst output via
ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
pvserver as mentioned at the end of
https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and giving
"--ds-host localhost --ds-port 11111" options to pv_web_visualizer.py, but
it doesn't help. I can't share anything to be displayed on the web.

Below you find the (not too detailed) steps I took to have a working
solution for either Catalyst-enabled simulations or a working web
visualizer:

Test connection from Catalyst simulation to paraview:
1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
http://www.paraview.org/download/)
2) Choose Catalyst->Connect in paraview
3) Run CFullExample from
https://github.com/Kitware/ParaViewCatalystExampleCode
4) Pipeline from CFullExample is shown in paraview.
Success!

Test ParaViewWeb:
1) Download ParaViewData-5.0.0.tar.gz from http://www.paraview.org/download/,
extract in /data
2) Run $ParaView_DIR/bin/pvpython
$ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
$ParaView_DIR/www  --data-dir /data --port 8080
3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
Success!

But how do I get Catalyst into the web visualizer? Is there any example how
to combine them? Anybody who can suggest the required steps?

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/79f4a44e/attachment.html>

From cgunases at gmail.com  Thu May 19 15:53:55 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Fri, 20 May 2016 01:23:55 +0530
Subject: [Paraview] How to get the object contour?
In-Reply-To: <652efbec-81c1-4514-e764-1606f570c0ba@bresnan.net>
References: <CAJFKOL37vLsGmfoYdD-b013Uhh8trDRpZa40N+j97=uEUr8tGA@mail.gmail.com>
 <652efbec-81c1-4514-e764-1606f570c0ba@bresnan.net>
Message-ID: <CAJFKOL0a-vuRWqESGvgGn0BK2sxMD+WgW82WQ_HFvOkyEmqpcw@mail.gmail.com>

Hi Samuel,

Thank you so much for your response.

Unfortunately, i have not used PV clip filters at all to generate slice
thickness. I am sorry to confuse you, but i need to add the slice thickness
to my 2D image instead

-- 
Warm regards,
Chathuri

On Thu, May 19, 2016 at 9:05 PM, Samuel Key <samuelkey at bresnan.net> wrote:

> Chathuri,
>
> I am not sure I understand what it is you are looking to display.
>
> If your "Slice with thickness" was generated with one or more PV Clip
> filters, then you have a 3-D volume.
>
> (1) PV's Contour filter can be used with scalar point data to give you 3-D
> iso-surfaces.
> (2) PV's Extract Surface filter will give you a 2-D surface "skin" of your
> "slice with thickness" volume. Applying PV's Contour filter to a surface
> with scalar point data will give you 2-D line contours.
>
> Hope this helps.
>
> Sam
>
>
> On 5/19/2016 1:40 AM, Chathuri Gunasekera wrote:
>
> Hi ,
>
> With the generated 3D model, i have 2 questions, as follows:
>
> (1). i can only see separate slices instead of the contour of the object,
> How to get the object contour?
>
> Following is what i followed:
>  [selected Filter--> alphabetical-->calculate-->scalars-->volume
> scalars-->Apply--> coloring(Result)--> representation (volume) ]
>
> (2) Is there a specific way to add Slice Thickness in Paraview?
>
> Thank you in advance.
>
> --
> Warm regards,
> Chathuri Gunasekera.
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/a88daf0f/attachment.html>

From ramrebol at gmail.com  Thu May 19 17:56:46 2016
From: ramrebol at gmail.com (Ramiro James Rebolledo Cormack)
Date: Thu, 19 May 2016 17:56:46 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in white
Message-ID: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>

Hi all.

I'm using paraview 4.0.1 on my ubuntu 14.04 64bits, the paraview version
coming from ubuntu 14.04 repositories.

The problem is: when I try to 'Export Scene' to pdf, it generates a white
pdf.

So, I compiled ParaView v5.0.1 from its source (without warnings or
errors), but I get the same problem.

I also have downloaded ParaView Binary Installers v5.0, but doesn't come
with 'Export Scene to pdf' option. That's why I'm trying to compile from
source code.

With ParaView Binary Installers v4.3 I have NO problem, but I want to use
the newer version.


So, how can I compile ParaView v5.0.1 to have the option for 'Export Scene'
to pdf?

Thanks in advance.

-- 
Ramiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/ad397932/attachment.html>

From utkarsh.ayachit at kitware.com  Thu May 19 18:01:36 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 19 May 2016 18:01:36 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
Message-ID: <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>

5.0.1 doesn't support export to PDF, I am afraid. However, "master"
does and so will "5.1"

(cc-ing Dave, just in case I am mistaken)

Utkarsh

On Thu, May 19, 2016 at 5:56 PM, Ramiro James Rebolledo Cormack
<ramrebol at gmail.com> wrote:
> Hi all.
>
> I'm using paraview 4.0.1 on my ubuntu 14.04 64bits, the paraview version
> coming from ubuntu 14.04 repositories.
>
> The problem is: when I try to 'Export Scene' to pdf, it generates a white
> pdf.
>
> So, I compiled ParaView v5.0.1 from its source (without warnings or errors),
> but I get the same problem.
>
> I also have downloaded ParaView Binary Installers v5.0, but doesn't come
> with 'Export Scene to pdf' option. That's why I'm trying to compile from
> source code.
>
> With ParaView Binary Installers v4.3 I have NO problem, but I want to use
> the newer version.
>
>
> So, how can I compile ParaView v5.0.1 to have the option for 'Export Scene'
> to pdf?
>
> Thanks in advance.
>
> --
> Ramiro
>
> _______________________________________________
> 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
>

From ramrebol at gmail.com  Thu May 19 18:08:29 2016
From: ramrebol at gmail.com (Ramiro James Rebolledo Cormack)
Date: Thu, 19 May 2016 18:08:29 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
 <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
Message-ID: <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>

Thanks Utkarsh. In my ubuntu 16.04 laptop I have installed ParaView 5.0.1
(from ubuntu repositories) and it has the option Export Scene to pdf, and
works perfect.
On the other hand, older paraview versions had the option, and worked.

I think that, maybe, I can get it using some spetial compilling option when
I use ccmake.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/23d81790/attachment.html>

From utkarsh.ayachit at kitware.com  Thu May 19 22:16:33 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 19 May 2016 22:16:33 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
 <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
 <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>
Message-ID: <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>

Ramiro,

A few things to note:

+ Not sure what's the deal with 4.0.1, but it's too old at this point
so let's ignore that.
+ When you downloaded ParaView 5.0.1 from paraview.org, starting with
5.0.1, we are using a new implementation of the rendering backend for
our binaries [1]. This rendering backend, let's call OpenGL2, doesn't
support exporting to PDF, at least, not in 5.0.1. It's been fixed in
git "master".
+ I suspect ParaView 5.0.1 from Ubuntu is using the old rendering
backend by default. The title bar should say something like "ParaView
5.0.1 (Legacy Rendering Backend)". This backend still support the old
export to PDF code and hence should have that option.
+ When you compiled 5.0.1 from source, I suspect you are getting the
old rendering backend too (unless you changed the CMake variable
VTK_RENDERING_BACKEND to OpenGL2). Not entirely sure why export would
fail in that case. There isn't any special flag to enable PDF export.

However, the best option to try out Export to PDF would be build the
latest "master" from source with VTK_RENDERING_BACKEND set to OpenGL2.

(Dave, do correct me if I am misspoke).

Utkarsh

[1] https://blog.kitware.com/kitware-unleashes-brand-new-rendering-backend-in-paraview-5-0/

On Thu, May 19, 2016 at 6:08 PM, Ramiro James Rebolledo Cormack
<ramrebol at gmail.com> wrote:
> Thanks Utkarsh. In my ubuntu 16.04 laptop I have installed ParaView 5.0.1
> (from ubuntu repositories) and it has the option Export Scene to pdf, and
> works perfect.
> On the other hand, older paraview versions had the option, and worked.
>
> I think that, maybe, I can get it using some spetial compilling option when
> I use ccmake.

From stephane at fujielectric.com  Fri May 20 01:42:31 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Fri, 20 May 2016 14:42:31 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CADLMsL5W57g_gjro=UkZ8T+Sm31rE8TyjbESGg4eF=8hBfSDaw@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
 <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
 <CADLMsL5W57g_gjro=UkZ8T+Sm31rE8TyjbESGg4eF=8hBfSDaw@mail.gmail.com>
Message-ID: <CADLMsL7HwUVW6mvu+dU33=t3S2QBJahyQf98bWxKFsBY=PBpJQ@mail.gmail.com>

Hello,

any idea on how to solve the following build error?



????
??????? ?????
????-???? ?????
????

????????
?210-9530??????????1-1
TEL 044-329-2155 FAX 044-329-2394

On Fri, May 20, 2016 at 8:33 AM, stephane???? ???? <
stephane at fujielectric.com> wrote:

> Hello,
> As stated in my previous e-mail, building ninja from vs2013did not solve
> the problem. I also noticed that re-sending the ninja command after the
> "subcommand failed" kind of resume the process to some point. I've attached
> the corresponding log files.
>
> Is it possible to build it with Visual Studio IDE instead of Ninja?
>
> ????
> ??????? ?????
> ????-???? ?????
> ????
>
> ????????
> ?210-9530??????????1-1
> TEL 044-329-2155 FAX 044-329-2394
>
> On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <
> joachim.pouderoux at kitware.com> wrote:
>
>> Hello,
>>
>> Did you compiled ninja using your VS2013?
>> Do you start ninja from a Visual Studio 2013 command line (so that cmake
>> can find VS compiler in the environment)?
>>
>> Regards,
>>
>>
>>
>> *Joachim Pouderoux*
>>
>> *PhD, Technical Expert*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:
>>
>>> Hello,
>>>
>>> I am sending a Log of the building process
>>>
>>> Ndong-Mefane Stephane, Dr.Eng
>>> Basic Design Sec.
>>> Steam Turbine Dept.
>>> Kawasaki Factory
>>>
>>> Fuji Electric Co., Ltd
>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>> Kawasaki-city 210-9530, Japan
>>> Phone: +81-44-329-2155
>>> Fax: +81-44-329-2394
>>>
>>>
>>> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
>>> stephane at fujielectric.com> wrote:
>>>
>>>> Hello,
>>>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>>>> I keep getting two errors:
>>>> 1) the first one is related to szip at the beginning of the build
>>>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>>>
>>>> nothing else.
>>>> I really need some help please...
>>>>
>>>> Ndong-Mefane Stephane, Dr.Eng
>>>> Basic Design Sec.
>>>> Steam Turbine Dept.
>>>> Kawasaki Factory
>>>>
>>>> Fuji Electric Co., Ltd
>>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>>> Kawasaki-city 210-9530, Japan
>>>> Phone: +81-44-329-2155
>>>> Fax: +81-44-329-2394
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/87a9ccac/attachment.html>

From stephane at fujielectric.com  Fri May 20 01:43:49 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Fri, 20 May 2016 14:43:49 +0900
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CADLMsL7HwUVW6mvu+dU33=t3S2QBJahyQf98bWxKFsBY=PBpJQ@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
 <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
 <CADLMsL5W57g_gjro=UkZ8T+Sm31rE8TyjbESGg4eF=8hBfSDaw@mail.gmail.com>
 <CADLMsL7HwUVW6mvu+dU33=t3S2QBJahyQf98bWxKFsBY=PBpJQ@mail.gmail.com>
Message-ID: <CADLMsL6tx-1kwHxqDD9h6caGVy35PDsNJFNP8eZOZOUe-YPvpw@mail.gmail.com>

Hello,

any idea on how to solve the following build error?

NMAKE : fatal error U1073: don't know how to make 'c:/Program\'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\bin\amd64\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
ninja: build stopped: subcommand failed.

Stephane

????
??????? ?????
????-???? ?????
????

????????
?210-9530??????????1-1
TEL 044-329-2155 FAX 044-329-2394

On Fri, May 20, 2016 at 2:42 PM, stephane???? ???? <
stephane at fujielectric.com> wrote:

> Hello,
>
> any idea on how to solve the following build error?
>
>
>
> ????
> ??????? ?????
> ????-???? ?????
> ????
>
> ????????
> ?210-9530??????????1-1
> TEL 044-329-2155 FAX 044-329-2394
>
> On Fri, May 20, 2016 at 8:33 AM, stephane???? ???? <
> stephane at fujielectric.com> wrote:
>
>> Hello,
>> As stated in my previous e-mail, building ninja from vs2013did not solve
>> the problem. I also noticed that re-sending the ninja command after the
>> "subcommand failed" kind of resume the process to some point. I've attached
>> the corresponding log files.
>>
>> Is it possible to build it with Visual Studio IDE instead of Ninja?
>>
>> ????
>> ??????? ?????
>> ????-???? ?????
>> ????
>>
>> ????????
>> ?210-9530??????????1-1
>> TEL 044-329-2155 FAX 044-329-2394
>>
>> On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <
>> joachim.pouderoux at kitware.com> wrote:
>>
>>> Hello,
>>>
>>> Did you compiled ninja using your VS2013?
>>> Do you start ninja from a Visual Studio 2013 command line (so that cmake
>>> can find VS compiler in the environment)?
>>>
>>> Regards,
>>>
>>>
>>>
>>> *Joachim Pouderoux*
>>>
>>> *PhD, Technical Expert*
>>> *Kitware SAS <http://www.kitware.fr>*
>>>
>>>
>>> 2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:
>>>
>>>> Hello,
>>>>
>>>> I am sending a Log of the building process
>>>>
>>>> Ndong-Mefane Stephane, Dr.Eng
>>>> Basic Design Sec.
>>>> Steam Turbine Dept.
>>>> Kawasaki Factory
>>>>
>>>> Fuji Electric Co., Ltd
>>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>>> Kawasaki-city 210-9530, Japan
>>>> Phone: +81-44-329-2155
>>>> Fax: +81-44-329-2394
>>>>
>>>>
>>>> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
>>>> stephane at fujielectric.com> wrote:
>>>>
>>>>> Hello,
>>>>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>>>>> I keep getting two errors:
>>>>> 1) the first one is related to szip at the beginning of the build
>>>>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>>>>
>>>>> nothing else.
>>>>> I really need some help please...
>>>>>
>>>>> Ndong-Mefane Stephane, Dr.Eng
>>>>> Basic Design Sec.
>>>>> Steam Turbine Dept.
>>>>> Kawasaki Factory
>>>>>
>>>>> Fuji Electric Co., Ltd
>>>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>>>> Kawasaki-city 210-9530, Japan
>>>>> Phone: +81-44-329-2155
>>>>> Fax: +81-44-329-2394
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/ad5fd7e4/attachment.html>

From lukasz.paluszek at airbus.com  Fri May 20 03:17:07 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Fri, 20 May 2016 07:17:07 +0000
Subject: [Paraview] Question about the ImageResampling Filter
Message-ID: <14587_1463728631_573EB9F7_14587_9088_1_cb3e4d95e06647d5949fd62b74b3f543@DE0-03DAG13-P03.central.mail.corp>

Hello All,

Is the Image Resampling filter applicable to all datasets or only VTK Images? Each time I try to use this filter on any other dataset than a uniform image file, Paraview crashes. In Paraview Help it is written: "Accepts input of following types: vtkDataSet vtkCompositeDataSet". I am using Paraview 5.0.0.

Regards,
Lukasz





[Beschreibung: Beschreibung: Description?: cid:image001.png at 01CF0B8F.DB7831F0]
?ukasz Paluszek
Airbus Helicopters
Aerodynamics Department (ETGA)
86607 Donauw?rth
Germany
Tel.: +49 (90) 671 8231
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>


AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauw?rth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?

<html><head></head><body><font color="black" face="arial" size="2">
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
</font>
</body>
</html>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/a4e3a210/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/a4e3a210/attachment.png>

From utkarsh.ayachit at kitware.com  Fri May 20 09:37:36 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 20 May 2016 09:37:36 -0400
Subject: [Paraview] Question about the ImageResampling Filter
In-Reply-To: <14587_1463728631_573EB9F7_14587_9088_1_cb3e4d95e06647d5949fd62b74b3f543@DE0-03DAG13-P03.central.mail.corp>
References: <14587_1463728631_573EB9F7_14587_9088_1_cb3e4d95e06647d5949fd62b74b3f543@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CADHSJjAA1zxk1Gs7=CE364QMg4zcBjNhO+xTNBi8CvGC7mfOLQ@mail.gmail.com>

Lukasz,

I'd suggest not to use 'ImageResampling' filter, it was a temporary fix and
clearly is buggy. A new filter has been added to ParaView "master", name
"Resample To Image". That would do what you want to do more reliably. What
platform are you running on? I can send you links to the nightly binaries
for the same.

Utkarsh

On Fri, May 20, 2016 at 3:17 AM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> Hello All,
>
>
>
> Is the Image Resampling filter applicable to all datasets or only VTK
> Images? Each time I try to use this filter on any other dataset than a
> uniform image file, Paraview crashes. In Paraview Help it is written:
> ?Accepts input of following types: vtkDataSet vtkCompositeDataSet?. I am
> using Paraview 5.0.0.
>
>
>
> Regards,
>
> Lukasz
>
>
>
>
>
>
>
>
>
>
>
> [image: Beschreibung: Beschreibung: Description :
> cid:image001.png at 01CF0B8F.DB7831F0]
>
> *?ukasz Paluszek*
>
> Airbus Helicopters
>
> Aerodynamics Department (ETGA)
>
> 86607 Donauw?rth
>
> Germany
>
> Tel.: +49 (90) 671 8231
>
> Fax.: +49 (90) 671 9122
>
> Lukasz.Paluszek at airbus.com
>
>
>
> AIRBUS HELICOPTERS DEUTSCHLAND GmbH
>
> Sitz der Gesellschaft / Registered Office: Donauw?rth
>
> Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508
>
> Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board:
> Guillaume Faury
>
> Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender
> / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin
> Sch?bel; Stefan Thom?
>
>
> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/12892ff7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/12892ff7/attachment.png>

From sebastien.jourdain at kitware.com  Fri May 20 09:42:13 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 20 May 2016 07:42:13 -0600
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
Message-ID: <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>

Hi Sven,

Live catalyst connection require a specific socket connection to the
in-situ process with some special handling.
We did not (yet) wrote the Python code to perform that specific action for
ParaViewWeb so it could be triggered by the web client or configured via an
argument at launch time.
I don't see any reason why this couldn't work, but as for now, I also don't
know an easy step to do it without spending time doing it myself.

Seb

On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Hello,
> I am looking for the recommended steps how to display an in-situ (live)
> Catalyst simulation through ParaViewWeb.
>
> After some efforts I am able to run ParaViewWeb successfully and I can
> view a Catalyst-enabled simulation in paraview.
>
> I hope, it is also possible to show the live Catalyst output via
> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
> pvserver as mentioned at the end of
> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
> giving "--ds-host localhost --ds-port 11111" options to
> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
> displayed on the web.
>
> Below you find the (not too detailed) steps I took to have a working
> solution for either Catalyst-enabled simulations or a working web
> visualizer:
>
> Test connection from Catalyst simulation to paraview:
> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
> http://www.paraview.org/download/)
> 2) Choose Catalyst->Connect in paraview
> 3) Run CFullExample from
> https://github.com/Kitware/ParaViewCatalystExampleCode
> 4) Pipeline from CFullExample is shown in paraview.
> Success!
>
> Test ParaViewWeb:
> 1) Download ParaViewData-5.0.0.tar.gz from
> http://www.paraview.org/download/, extract in /data
> 2) Run $ParaView_DIR/bin/pvpython
> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
> $ParaView_DIR/www  --data-dir /data --port 8080
> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
> Success!
>
> But how do I get Catalyst into the web visualizer? Is there any example
> how to combine them? Anybody who can suggest the required steps?
>
> Regards,
> Sven
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/657a967e/attachment.html>

From simon.m.su.civ at mail.mil  Fri May 20 09:44:04 2016
From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US))
Date: Fri, 20 May 2016 13:44:04 +0000
Subject: [Paraview] [Non-DoD Source] Re: paraview superbuild on Win7
 with ninja/vs2013/qt4/mpi (UNCLASSIFIED)
Message-ID: <D6C99B46E9329343B0566046C14828B81756A24B@uslshpli.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Stephane,

I am not sure about the superbuild process. But if your goal is to just build a ParaView for windows platform and not make a ParaView windows build using Superbuild, I can get you with all the dependencies library compiled with VS2013 express (which should be compatible with other VS 2013) that I used to build ParaView from source.

Let me know.

Best
-simon

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of stephane???? ????
Sent: Friday, May 20, 2016 1:44 AM
To: Joachim Pouderoux <joachim.pouderoux at kitware.com>
Cc: paraview <paraview at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. 


________________________________



Hello,

any idea on how to solve the following build error?

NMAKE : fatal error U1073: don't know how to make 'c:/Program\'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
ninja: build stopped: subcommand failed.

Stephane

????
?????????????
????-??????????
????

????????
?210-9530??????????1-1
TEL 044-329-2155 FAX 044-329-2394

On Fri, May 20, 2016 at 2:42 PM, stephane???? ???? <stephane at fujielectric.com < Caution-mailto:stephane at fujielectric.com > > wrote:


	Hello,

	any idea on how to solve the following build error?



	????
	?????????????
	????-??????????
	????
	
	????????
	?210-9530??????????1-1
	TEL 044-329-2155 FAX 044-329-2394

	On Fri, May 20, 2016 at 8:33 AM, stephane???? ???? <stephane at fujielectric.com < Caution-mailto:stephane at fujielectric.com > > wrote:
	

		Hello,
		As stated in my previous e-mail, building ninja from vs2013did not solve the problem. I also noticed that re-sending the ninja command after the "subcommand failed" kind of resume the process to some point. I've attached the corresponding log files.

		Is it possible to build it with Visual Studio IDE instead of Ninja?

		????
		?????????????
		????-??????????
		????
		
		????????
		?210-9530??????????1-1
		TEL 044-329-2155 FAX 044-329-2394

		On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <joachim.pouderoux at kitware.com < Caution-mailto:joachim.pouderoux at kitware.com > > wrote:
		

			Hello,
			
			
			Did you compiled ninja using your VS2013?
			
			Do you start ninja from a Visual Studio 2013 command line (so that cmake can find VS compiler in the environment)?
			
			
			Regards,
			



			Joachim Pouderoux
			

				PhD, Technical Expert
				Kitware SAS < Caution-http://www.kitware.fr > 
				


			2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com < Caution-mailto:stephane at fujielectric.com > >:
			

				Hello,

				I am sending a Log of the building process 
				
				
				Ndong-Mefane Stephane, Dr.Eng
				Basic Design Sec.
				Steam Turbine Dept.
				Kawasaki Factory
				
				Fuji Electric Co., Ltd
				1-1, Tanabeshinden, Kawasaki-ku,
				Kawasaki-city 210-9530, Japan
				Phone: +81-44-329-2155 < tel:%2B81-44-329-2155 > 
				Fax: +81-44-329-2394 < tel:%2B81-44-329-2394 > 
				
				

				On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <stephane at fujielectric.com < Caution-mailto:stephane at fujielectric.com > > wrote:
				

					Hello, 
					I've been trying to "superbuild" paraview 5.0 on Win7 without success.
					I keep getting two errors:
					1) the first one is related to szip at the beginning of the build
					2) the second and last one is  ninja: build stopped: subcommand failed

					nothing else.
					I really need some help please...

					Ndong-Mefane Stephane, Dr.Eng
					Basic Design Sec.
					Steam Turbine Dept.
					Kawasaki Factory
					
					Fuji Electric Co., Ltd
					1-1, Tanabeshinden, Kawasaki-ku,
					Kawasaki-city 210-9530, Japan
					Phone: +81-44-329-2155 < tel:%2B81-44-329-2155 > 
					Fax: +81-44-329-2394 < tel:%2B81-44-329-2394 > 
					
					



				_______________________________________________
				Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > 
				
				Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > 
				
				Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView > 
				
				Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView > 
				
				Follow this link to subscribe/unsubscribe:
				Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview > 
				
				






CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5567 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/345601c6/attachment.bin>

From ramrebol at gmail.com  Fri May 20 10:19:15 2016
From: ramrebol at gmail.com (Ramiro James Rebolledo Cormack)
Date: Fri, 20 May 2016 10:19:15 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
 <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
 <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>
 <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>
Message-ID: <CALsG1Z9d0S-cOCMD4whadWO1aRZLjUuS7Gh325k+aRt1aPZ_gQ@mail.gmail.com>

Thanks Utkarsh.


2016-05-19 22:16 GMT-04:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Ramiro,
>
> A few things to note:
>
> + Not sure what's the deal with 4.0.1, but it's too old at this point
> so let's ignore that.
>

I'm agree. I was just testing to understand what is happening.


> + When you downloaded ParaView 5.0.1 from paraview.org, starting with
> 5.0.1, we are using a new implementation of the rendering backend for
> our binaries [1]. This rendering backend, let's call OpenGL2, doesn't
> support exporting to PDF, at least, not in 5.0.1. It's been fixed in
> git "master".
>

In my laptop I have 3 options (pressing enter buttom) for
VTK_RENDERING_BACKEND:  OpenGL, OpenGL2 and None,
but in my desktop I have only one: OpenGL.

I compile paraview in my laptop (ubuntu 16.04) and my desktop (ubuntu
14.04) with exactly the same options in ccmake, in particular: OpenGL.
In my laptop 'Export to pdf' works perfect.
Is this related this the nvidia driver? In my desktop I have installed
nvidia driver, but in my destop I have not installed nvidia driver.


> + I suspect ParaView 5.0.1 from Ubuntu is using the old rendering
> backend by default. The title bar should say something like "ParaView
> 5.0.1 (Legacy Rendering Backend)". This backend still support the old
> export to PDF code and hence should have that option.
>

You are right: in the paraview version from ubuntu repository says
"ParaView 5.0.1 (Legacy Rendering Backend)" in the tittle bar.
Also, in my both compiled paraview 5.0.1 appears "ParaView 5.0.1 (Legacy
Rendering Backend)" in the tittle bar too.


> + When you compiled 5.0.1 from source, I suspect you are getting the
> old rendering backend too (unless you changed the CMake variable
> VTK_RENDERING_BACKEND to OpenGL2). Not entirely sure why export would
> fail in that case. There isn't any special flag to enable PDF export.
>

Now, in my desktop I'm trying compiling with OpenGL2 option (the option
doesn't comes hiting the enter button, instead of my laptop, but I chosed
writting it), and crossing my fingers.

I appreciate any ideas or suggestions (I don't have more), to find a way for
fix this 'little' problem: to have the export to pdf option.

Thanks again.


>
> However, the best option to try out Export to PDF would be build the
> latest "master" from source with VTK_RENDERING_BACKEND set to OpenGL2.
>
> (Dave, do correct me if I am misspoke).
>
> Utkarsh
>
> [1]
> https://blog.kitware.com/kitware-unleashes-brand-new-rendering-backend-in-paraview-5-0/
>
> On Thu, May 19, 2016 at 6:08 PM, Ramiro James Rebolledo Cormack
> <ramrebol at gmail.com> wrote:
> > Thanks Utkarsh. In my ubuntu 16.04 laptop I have installed ParaView 5.0.1
> > (from ubuntu repositories) and it has the option Export Scene to pdf, and
> > works perfect.
> > On the other hand, older paraview versions had the option, and worked.
> >
> > I think that, maybe, I can get it using some spetial compilling option
> when
> > I use ccmake.
>



-- 
Ramiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/cda3fd67/attachment.html>

From david.lonie at kitware.com  Fri May 20 10:19:51 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 20 May 2016 10:19:51 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
 <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
 <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>
 <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>
Message-ID: <CA+=e1ovpXuE5T3RMhrGE5r3EvEWVXKjF2ejhEJ8uknkpf6K9uw@mail.gmail.com>

On Thu, May 19, 2016 at 10:16 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> + Not sure what's the deal with 4.0.1, but it's too old at this point
> so let's ignore that.
> + When you downloaded ParaView 5.0.1 from paraview.org, starting with
> 5.0.1, we are using a new implementation of the rendering backend for
> our binaries [1]. This rendering backend, let's call OpenGL2, doesn't
> support exporting to PDF, at least, not in 5.0.1. It's been fixed in
> git "master".
> + I suspect ParaView 5.0.1 from Ubuntu is using the old rendering
> backend by default. The title bar should say something like "ParaView
> 5.0.1 (Legacy Rendering Backend)". This backend still support the old
> export to PDF code and hence should have that option.
> + When you compiled 5.0.1 from source, I suspect you are getting the
> old rendering backend too (unless you changed the CMake variable
> VTK_RENDERING_BACKEND to OpenGL2). Not entirely sure why export would
> fail in that case. There isn't any special flag to enable PDF export.
>
> However, the best option to try out Export to PDF would be build the
> latest "master" from source with VTK_RENDERING_BACKEND set to OpenGL2.
>
> (Dave, do correct me if I am misspoke).
>

This sounds about right. The gl2ps library we use to generate the pdfs was
not compatible with the new OpenGL2 backend, and I had to tweak it a bit to
get it working again. Looking at the git log, the modifications didn't make
it into the 5.0.1 release, so export would only work using the old backend
with that release.

The current development branch supports pdf export on both backends.

I'm curious about the white exported image, though. IIRC, the
vector-graphics export options shouldn't be shown on the versions of
paraview that don't support gl2ps, so if you're able to export, it should
be working. It sounds like you may have also brushed up against one of the
limitations of the gl2ps library -- for instance, it can't handle textured
objects (they'll just appear a solid color, rather than patterned). This
can be problematic as some of the color mapping techniques use textures.

If you're seeing incorrect output, try playing with the "rasterize 3D
geometry" and sort options to see if you can get a better representation of
the scene.

HTH,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/82f4cc76/attachment.html>

From lukasz.paluszek at airbus.com  Fri May 20 10:27:43 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Fri, 20 May 2016 14:27:43 +0000
Subject: [Paraview] Question about the ImageResampling Filter
In-Reply-To: <22163_1463751458_573F1322_22163_4816_1_CADHSJjAA1zxk1Gs7=CE364QMg4zcBjNhO+xTNBi8CvGC7mfOLQ@mail.gmail.com>
References: <14587_1463728631_573EB9F7_14587_9088_1_cb3e4d95e06647d5949fd62b74b3f543@DE0-03DAG13-P03.central.mail.corp>
 <22163_1463751458_573F1322_22163_4816_1_CADHSJjAA1zxk1Gs7=CE364QMg4zcBjNhO+xTNBi8CvGC7mfOLQ@mail.gmail.com>
Message-ID: <30086_1463754468_573F1EE4_30086_1155_1_e2c11cf091064a28bdc7fb1001dc6022@DE0-03DAG13-P03.central.mail.corp>

Hi Utkarsh,

I am always building Paraview from source on Linux with all the features I need, but there is no rush, I can wait for the next release or if I badly need this functionality I will pull it from the ?master?.

A little background:
I was actually playing around when I came across the issue, what I want to achieve is to do fast volume rendering on unstructured meshes. The volume rendering algorithms in Paraview are ultrafast with VTK image files but painfully slow with unstructured grids. I constantly have an idea in mind to map unstructured meshes to image files and then do the volume rendering. Simple as it sounds I could not find an automatic way to achieve this, in the end I had to manually generate image files in a text editor. I also tried with the Gaussian Resampling, but this filter fails in parallel, each process generates its own image file but there is no communication between them, it is not possible to resample data onto these images nor is it possible to save them (Paraview saves data from just one process). I am still hoping to find some smart way of generating image files, ideally automatically refined based on some flow variables of interest and then map the unstructured grid data on the generated VTK images for fast volume rendering.

Regards,
Lukasz


[Beschreibung: Beschreibung: Description?: cid:image001.png at 01CF0B8F.DB7831F0]
?ukasz Paluszek
Airbus Helicopters
Aerodynamics Department (ETGA)
86607 Donauw?rth
Germany
Tel.: +49 (90) 671 8231
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: 20 May 2016 15:38
To: Paluszek, Lukasz
Cc: paraview at paraview.org
Subject: Re: [Paraview] Question about the ImageResampling Filter

Lukasz,

I'd suggest not to use 'ImageResampling' filter, it was a temporary fix and clearly is buggy. A new filter has been added to ParaView "master", name "Resample To Image". That would do what you want to do more reliably. What platform are you running on? I can send you links to the nightly binaries for the same.

Utkarsh

On Fri, May 20, 2016 at 3:17 AM, Paluszek, Lukasz <lukasz.paluszek at airbus.com<mailto:lukasz.paluszek at airbus.com>> wrote:
Hello All,

Is the Image Resampling filter applicable to all datasets or only VTK Images? Each time I try to use this filter on any other dataset than a uniform image file, Paraview crashes. In Paraview Help it is written: ?Accepts input of following types: vtkDataSet vtkCompositeDataSet?. I am using Paraview 5.0.0.

Regards,
Lukasz





[Beschreibung: Beschreibung: Description?: cid:image001.png at 01CF0B8F.DB7831F0]
?ukasz Paluszek
Airbus Helicopters
Aerodynamics Department (ETGA)
86607 Donauw?rth
Germany
Tel.: +49 (90) 671 8231<tel:%2B49%20%2890%29%20671%208231>
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>


AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauw?rth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?



The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.

If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.

Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.

All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.







_______________________________________________
Powered by www.kitware.com<http://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


AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauw?rth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Thomas Hundt; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?

<html><head></head><body><font color="black" face="arial" size="2">
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
</font>
</body>
</html>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/51da8ec1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/51da8ec1/attachment.png>

From david.lonie at kitware.com  Fri May 20 10:27:40 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 20 May 2016 10:27:40 -0400
Subject: [Paraview] Paraview 5.0.1: Export Scene to pdf -- appears in
	white
In-Reply-To: <CALsG1Z9d0S-cOCMD4whadWO1aRZLjUuS7Gh325k+aRt1aPZ_gQ@mail.gmail.com>
References: <CALsG1Z_TQqXofOy-ke=N2SEo5CmdGm65J_9Tr7nLJtrnUBY2cA@mail.gmail.com>
 <CADHSJjAXF-UBuwczR_WUjmptth8c2yk7TSur1a1S+CR05e_5wA@mail.gmail.com>
 <CALsG1Z-xMkxFqyhdJhKU3ugx_ROL7P7L6=NL7idq93E4E-q3sQ@mail.gmail.com>
 <CADHSJjDbgWjd1FN819upwi_G9ZqTfxLdjFvCk2wfgqKaxhqdLA@mail.gmail.com>
 <CALsG1Z9d0S-cOCMD4whadWO1aRZLjUuS7Gh325k+aRt1aPZ_gQ@mail.gmail.com>
Message-ID: <CA+=e1ouNE+iJR24m4iQpc7wrYkxASPAk6YjtBjTctykHhpwy9w@mail.gmail.com>

On Fri, May 20, 2016 at 10:19 AM, Ramiro James Rebolledo Cormack <
ramrebol at gmail.com> wrote:
>
> I compile paraview in my laptop (ubuntu 16.04) and my desktop (ubuntu
> 14.04) with exactly the same options in ccmake, in particular: OpenGL.
> In my laptop 'Export to pdf' works perfect.
> Is this related this the nvidia driver? In my desktop I have installed
> nvidia driver, but in my destop I have not installed nvidia driver.
>

Hmm, the opengl driver shouldn't matter on the OpenGL1 backend, unless
there was a bug in their feedback rendering mode. Are you trying to export
the same scene on both systems?


> + When you compiled 5.0.1 from source, I suspect you are getting the
>> old rendering backend too (unless you changed the CMake variable
>> VTK_RENDERING_BACKEND to OpenGL2). Not entirely sure why export would
>> fail in that case. There isn't any special flag to enable PDF export.
>>
>
> Now, in my desktop I'm trying compiling with OpenGL2 option (the option
> doesn't comes hiting the enter button, instead of my laptop, but I chosed
> writting it), and crossing my fingers.
>
> I appreciate any ideas or suggestions (I don't have more), to find a way
> for fix this 'little' problem: to have the export to pdf option.
>

I'd suggest just playing with the export options and see if there's a
solution there. If you keep having trouble, send me a small state file that
reproduces the issue and I'll take a look. There are certain cases where
the gl2ps exporter will fail to capture all of the details in a scene,
though it should produce more than an empty white image.

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/dcd8b402/attachment.html>

From utkarsh.ayachit at kitware.com  Fri May 20 10:36:17 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 20 May 2016 10:36:17 -0400
Subject: [Paraview] Question about the ImageResampling Filter
In-Reply-To: <30086_1463754468_573F1EE4_30086_1155_1_e2c11cf091064a28bdc7fb1001dc6022@DE0-03DAG13-P03.central.mail.corp>
References: <14587_1463728631_573EB9F7_14587_9088_1_cb3e4d95e06647d5949fd62b74b3f543@DE0-03DAG13-P03.central.mail.corp>
 <22163_1463751458_573F1322_22163_4816_1_CADHSJjAA1zxk1Gs7=CE364QMg4zcBjNhO+xTNBi8CvGC7mfOLQ@mail.gmail.com>
 <30086_1463754468_573F1EE4_30086_1155_1_e2c11cf091064a28bdc7fb1001dc6022@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CADHSJjACy4AGuYaA4n3jC6ak+PK2vKp4x+sGFkZQzrvxpLgP_Q@mail.gmail.com>

Lukasz,

> The volume rendering algorithms in Paraview are ultrafast with VTK image files but painfully slow with unstructured grids. I constantly have an idea in mind to map unstructured meshes to image files and then do the volume rendering.

That's indeed the reason by the "Resample to Image" filter was created
:). And it's expected to work in parallel for composite datasets too.
Of course, if you spot a bug, do let us know.

Utkarsh

From andy.bauer at kitware.com  Fri May 20 10:39:39 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 20 May 2016 10:39:39 -0400
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <62131.95.7.172.33.1463584631.squirrel@webmail.be.itu.edu.tr>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>
 <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
 <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
 <62131.95.7.172.33.1463584631.squirrel@webmail.be.itu.edu.tr>
Message-ID: <CAMaOp+Ft3FoWrH9R-+hb8hB2PRNrLQ4cHn631sCEc8GkDmkrjA@mail.gmail.com>

It may be possible to do this with Catalyst. I would guess that nearly all
of the complex work would need to be done in the adaptor to integrate this
properly though.

On Wed, May 18, 2016 at 11:17 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Yes, you are right. In this case, there will be two separate
> MPI_COMM_WORLD. Plus, one that covers all the resources (let's say that
> global MPI_COMM_WORLD). Actually, this kind of setup is very common for
> multi-physics applications such as fluid-structure interaction. So, is it
> possible to tight this kind of environment with Catalyst? I am not expert
> about Catalyst but it seems that there might be a problem in the rendering
> stage even underlying grids and fields are defined without any problem.
>
> Regards,
>
> --ufuk
>
> > I'm not sure if this is exactly what the original user is referring to,
> > but it is possible to have two separate codes communicate using MPI
> > through the dynamic processes in MPI-2. Essentially, one program starts
> up
> > on N processors and begins running and gets an MPI_COMM_WORLD. It then
> > spawns another executable on M different processors and that new
> > executable will call MPI_INIT and also get its own MPI_COMM_WORLD. So you
> > have two, disjoint MPI_COMM_WORLD's that get linked together through a
> > newly created intercommunicator.
> >
> >
> > I've used this to couple a structural mechanics code to our fluid
> dynamics
> > solver for example. It sounds like that is similar to what is being done
> > here.
> >
> >
> > How that would interact with coprocessing is beyond my knowledge though.
> > It does sound like an interesting problem and one I would be very curious
> > to find out the details.
> >
> >
> > Tim
> >
> >
> > ________________________________
> > From: ParaView <paraview-bounces at paraview.org> on behalf of Andy Bauer
> > <andy.bauer at kitware.com>
> > Sent: Wednesday, May 18, 2016 10:52 AM
> > To: Ufuk Utku Turuncoglu (BE)
> > Cc: paraview at paraview.org
> > Subject: Re: [Paraview] capability of ParaView, Catalyst in distributed
> > computing environment ...
> >
> > Hi,
> >
> > I'm a bit confused. MPI_COMM_WORLD is the global communicator and as far
> > as I'm aware, can't be modified which means there can't be two different
> > communicators.
> >
> > Catalyst can be set to use a specific MPI communicator and that's been
> > done by at least one code (Code_Saturne). I think they have a
> multiphysics
> > simulation as well.
> >
> > Cheers,
> > Andy
> >
> > On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE)
> > <u.utku.turuncoglu at be.itu.edu.tr<mailto:u.utku.turuncoglu at be.itu.edu.tr
> >>
> > wrote:
> > Hi All,
> >
> > I just wonder about the capability of ParaView, Catalyst in distributed
> > computing environment. I have little bit experience in in-situ
> > visualization but it is hard for me to see the big picture at this point.
> > So, i decided to ask to the user list to get some suggestion from the
> > experts. Hypothetically, lets assume that we have two simulation code
> that
> > are coupled together (i.e. fluid-structure interaction) and both of them
> > have their own MPI_COMM_WORLD and run on different processors (model1
> runs
> > on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct
> > design to create integrated in-situ visualization analysis (both model
> > contributes to same visualization pipeline) in this case? Do you know any
> > implementation that is similar to this design? At least, is it possible?
> >
> > In this case, the adaptor code will need to access to two different
> > MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its own
> > MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation code
> > have its own grid and field definitions (might be handled via defining
> > different input ports). Does it create a problem in Paraview, Catalyst
> > side, if the multiblock dataset is used to define the grids of the
> > components in adaptor. I am asking because some MPI processes (belongs to
> > adaptor code) will not have data for specific model component due to the
> > domain decomposition implementation of the individual models. For
> example,
> > MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank
> > 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI rank
> > 4,5,6,7). To that end, do i need to collect all the data from the
> > components? If this is the case, how can i handle 2d decomposition
> > problem? Because, the adaptor code has no any common grid structure that
> > fits for all the model components.
> >
> > Regards,
> >
> > Ufuk Turuncoglu
> > _______________________________________________
> > Powered by www.kitware.com<http://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
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/a6fb8a67/attachment.html>

From svenkramer40 at gmail.com  Fri May 20 12:46:30 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Fri, 20 May 2016 18:46:30 +0200
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
Message-ID: <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>

Hello Seb,
glad to read your answer. So the problem is not only that I was unable to
find the relevant information.

You say, you have not (yet) written the required code. Does "not (yet)"
mean that it is on the agenda maybe within the next half year? Then I could
find a workaround and look forward to the next Paraview updates.

Otherwise I would try to work on the implementation for connecting
Paraviewweb to Catalyst output. Is there any developer documentation of
Catalysts "specific socket connection"? Or some general Catalyst developer
information? Those would be great to get started.
My first attempt would be to "wrap" the functionality of
Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
make it available to the web client. Or are the necessary steps much more
involved?

Thank you
Sven

2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
sebastien.jourdain at kitware.com>:

> Hi Sven,
>
> Live catalyst connection require a specific socket connection to the
> in-situ process with some special handling.
> We did not (yet) wrote the Python code to perform that specific action for
> ParaViewWeb so it could be triggered by the web client or configured via an
> argument at launch time.
> I don't see any reason why this couldn't work, but as for now, I also
> don't know an easy step to do it without spending time doing it myself.
>
> Seb
>
> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Hello,
>> I am looking for the recommended steps how to display an in-situ (live)
>> Catalyst simulation through ParaViewWeb.
>>
>> After some efforts I am able to run ParaViewWeb successfully and I can
>> view a Catalyst-enabled simulation in paraview.
>>
>> I hope, it is also possible to show the live Catalyst output via
>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>> pvserver as mentioned at the end of
>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
>> giving "--ds-host localhost --ds-port 11111" options to
>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>> displayed on the web.
>>
>> Below you find the (not too detailed) steps I took to have a working
>> solution for either Catalyst-enabled simulations or a working web
>> visualizer:
>>
>> Test connection from Catalyst simulation to paraview:
>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
>> http://www.paraview.org/download/)
>> 2) Choose Catalyst->Connect in paraview
>> 3) Run CFullExample from
>> https://github.com/Kitware/ParaViewCatalystExampleCode
>> 4) Pipeline from CFullExample is shown in paraview.
>> Success!
>>
>> Test ParaViewWeb:
>> 1) Download ParaViewData-5.0.0.tar.gz from
>> http://www.paraview.org/download/, extract in /data
>> 2) Run $ParaView_DIR/bin/pvpython
>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>> $ParaView_DIR/www  --data-dir /data --port 8080
>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>> Success!
>>
>> But how do I get Catalyst into the web visualizer? Is there any example
>> how to combine them? Anybody who can suggest the required steps?
>>
>> Regards,
>> Sven
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/23d8bde5/attachment.html>

From sebastien.jourdain at kitware.com  Fri May 20 12:59:29 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 20 May 2016 10:59:29 -0600
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
Message-ID: <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>

Hi Sven,

I am not aware on any specific developer documentation for Catalyst on the
ParaView side (but I haven't worked on that subject for years), although
Utkarsh or Andy might know.

Usually looking at the code and redoing it in the Python world is what is
required, but as I said, I'm not sure of what it means since I don't know
that code anymore. ;-)

For the timeframe, I can't tell (meaning I don't know), but we can still
try to help you or implement the missing piece via support contract if that
make sense on your end.

Thanks,

Seb

On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
wrote:

> Hello Seb,
> glad to read your answer. So the problem is not only that I was unable to
> find the relevant information.
>
> You say, you have not (yet) written the required code. Does "not (yet)"
> mean that it is on the agenda maybe within the next half year? Then I could
> find a workaround and look forward to the next Paraview updates.
>
> Otherwise I would try to work on the implementation for connecting
> Paraviewweb to Catalyst output. Is there any developer documentation of
> Catalysts "specific socket connection"? Or some general Catalyst developer
> information? Those would be great to get started.
> My first attempt would be to "wrap" the functionality of
> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
> make it available to the web client. Or are the necessary steps much more
> involved?
>
> Thank you
> Sven
>
>
> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Hi Sven,
>>
>> Live catalyst connection require a specific socket connection to the
>> in-situ process with some special handling.
>> We did not (yet) wrote the Python code to perform that specific action
>> for ParaViewWeb so it could be triggered by the web client or configured
>> via an argument at launch time.
>> I don't see any reason why this couldn't work, but as for now, I also
>> don't know an easy step to do it without spending time doing it myself.
>>
>> Seb
>>
>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Hello,
>>> I am looking for the recommended steps how to display an in-situ (live)
>>> Catalyst simulation through ParaViewWeb.
>>>
>>> After some efforts I am able to run ParaViewWeb successfully and I can
>>> view a Catalyst-enabled simulation in paraview.
>>>
>>> I hope, it is also possible to show the live Catalyst output via
>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>> pvserver as mentioned at the end of
>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
>>> giving "--ds-host localhost --ds-port 11111" options to
>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>> displayed on the web.
>>>
>>> Below you find the (not too detailed) steps I took to have a working
>>> solution for either Catalyst-enabled simulations or a working web
>>> visualizer:
>>>
>>> Test connection from Catalyst simulation to paraview:
>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
>>> http://www.paraview.org/download/)
>>> 2) Choose Catalyst->Connect in paraview
>>> 3) Run CFullExample from
>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>> 4) Pipeline from CFullExample is shown in paraview.
>>> Success!
>>>
>>> Test ParaViewWeb:
>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>> http://www.paraview.org/download/, extract in /data
>>> 2) Run $ParaView_DIR/bin/pvpython
>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>> Success!
>>>
>>> But how do I get Catalyst into the web visualizer? Is there any example
>>> how to combine them? Anybody who can suggest the required steps?
>>>
>>> Regards,
>>> Sven
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/8dcc031c/attachment.html>

From tim.gallagher at gatech.edu  Fri May 20 12:57:28 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Fri, 20 May 2016 16:57:28 +0000
Subject: [Paraview] Memory leak with Catalyst
Message-ID: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/ec9bb46e/attachment.html>

From michele.battistoni at unipg.it  Fri May 20 13:55:41 2016
From: michele.battistoni at unipg.it (Michele Battistoni)
Date: Fri, 20 May 2016 19:55:41 +0200
Subject: [Paraview] Slow with just 1M cells
Message-ID: <4A0C9ECE-56B5-4521-80FE-63B17C1C2ED4@unipg.it>

Paraview is awesome for lots of functionalities, however I find it extremely slow in processing data with any filter type, or in changing timestep as soon as the model size is around one million cells or above. I have experience with a commercial tool which on the same model and pc is 100x faster. Let's say a second vs. a min!

Is there any specific settings for ram of parallelization among cores?

Thanks 
Michele



From andy.bauer at kitware.com  Fri May 20 14:39:49 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 20 May 2016 14:39:49 -0400
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at
finding VTK objects that aren't deleted properly. You should be able to run
this with a small amount of calls to Catalyst as well. If you try this and
want help understanding the output (if an object like a vtkUnstructuredGrid
is leaked it will often give a whole bunch of false leaks that the
unstructured grid is just holding the references to), just share your
output file and I can take a look at it to try and narrow down the culprit.
That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any
Catalyst work to see what happens then. That may be a lot of compute cycles
but I'm not sure how else to try and bisect where the memory leak is
occurring.

Initializing and finalizing Catalyst every time you want output would
probably work but I'd think there may be significant overhead doing it like
this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <
tim.gallagher at gatech.edu> wrote:

> Hi,
>
>
> One of our users is running a very big simulation and writing out images
> of two slices (two different views) every 1000 iterations and writing out
> the data for the two slices (two different data writers) as VTK files every
> 5000 iterations. It is using Paraview 4.4.
>
>
> After 21000 iterations, the simulation is killed because the memory on the
> compute nodes fills up. I usually know how to track down memory problems in
> our code using valgrind and related tools, but is that the right way to go
> to try and find this problem?
>
>
> Are there any tips on how to isolate where the problem may be? I don't
> know if it is in the adapter, or in paraview itself. Has anybody
> encountered problems with runaway memory using Catalyst in 4.4 when writing
> images or VTK files?
>
>
> I know when we use pvpython to generate images and loop over many files,
> sometimes the memory also blows up and so we usually move the loop over the
> files outside the pvpython script and into a driver script that executes a
> new pvpython for each file. Is there a way to shut down/start up Catalyst
> each time it needs to write something? Is that advisable?
>
>
> Thanks,
>
>
> Tim
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/835e125e/attachment.html>

From tim.gallagher at gatech.edu  Fri May 20 14:56:49 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Fri, 20 May 2016 18:56:49 +0000
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
Message-ID: <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>

Hi Andy,


Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what it turns up.


The initialize/finalize every time is definitely a hack and not for long-term use. But, sponsors want a report on Monday and we need to be able to visualize things for that -- the simulation is too big to write data files and post-process later. So I modified the code to do that for now until I can find a proper fix.


I'll let you know if I get stuck with the log file.


Thanks again,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com>
Sent: Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding VTK objects that aren't deleted properly. You should be able to run this with a small amount of calls to Catalyst as well. If you try this and want help understanding the output (if an object like a vtkUnstructuredGrid is leaked it will often give a whole bunch of false leaks that the unstructured grid is just holding the references to), just share your output file and I can take a look at it to try and narrow down the culprit. That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any Catalyst work to see what happens then. That may be a lot of compute cycles but I'm not sure how else to try and bisect where the memory leak is occurring.

Initializing and finalizing Catalyst every time you want output would probably work but I'd think there may be significant overhead doing it like this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim

_______________________________________________
Powered by www.kitware.com<http://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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/2fd2ba15/attachment.html>

From burlen.loring at gmail.com  Fri May 20 15:46:34 2016
From: burlen.loring at gmail.com (Burlen Loring)
Date: Fri, 20 May 2016 12:46:34 -0700
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>

VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch 
all kinds of leaks. For example you can have leaks where data 
erroneously accumulates with each time step, but is deleted at program 
termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's 
probably better to use massif to profile your code on a small one node 
run. There's an excellent tool called massif visualizer to aid in 
exploring the data generated.


$0.02


On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:
>
> Hi Andy,
>
>
> Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and 
> see what it turns up.
>
>
> The initialize/finalize every time is definitely a hack and not for 
> long-term use. But, sponsors want a report on Monday and we need to be 
> able to visualize things for that -- the simulation is too big to 
> write data files and post-process later. So I modified the code to do 
> that for now until I can find a proper fix.
>
>
> I'll let you know if I get stuck with the log file.
>
>
> Thanks again,
>
>
> Tim
>
>
>
> ------------------------------------------------------------------------
> *From:* Andy Bauer <andy.bauer at kitware.com>
> *Sent:* Friday, May 20, 2016 2:39 PM
> *To:* Gallagher, Timothy P
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Memory leak with Catalyst
> Hi Tim,
>
> If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good 
> at finding VTK objects that aren't deleted properly. You should be 
> able to run this with a small amount of calls to Catalyst as well. If 
> you try this and want help understanding the output (if an object like 
> a vtkUnstructuredGrid is leaked it will often give a whole bunch of 
> false leaks that the unstructured grid is just holding the references 
> to), just share your output file and I can take a look at it to try 
> and narrow down the culprit. That may be slightly easier to use than 
> Valgrind.
>
> Beyond this, you could maybe try the same run but without doing any 
> Catalyst work to see what happens then. That may be a lot of compute 
> cycles but I'm not sure how else to try and bisect where the memory 
> leak is occurring.
>
> Initializing and finalizing Catalyst every time you want output would 
> probably work but I'd think there may be significant overhead doing it 
> like this. Plus, it's not really solving the problem -- just avoiding it.
>
> Best,
> Andy
>
>
> On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P 
> <tim.gallagher at gatech.edu <mailto:tim.gallagher at gatech.edu>> wrote:
>
>     Hi,
>
>
>     One of our users is running a very big simulation and writing out
>     images of two slices (two different views) every 1000 iterations
>     and writing out the data for the two slices (two different data
>     writers) as VTK files every 5000 iterations. It is using Paraview
>     4.4.
>
>
>     After 21000 iterations, the simulation is killed because the
>     memory on the compute nodes fills up. I usually know how to track
>     down memory problems in our code using valgrind and related tools,
>     but is that the right way to go to try and find this problem?
>
>
>     Are there any tips on how to isolate where the problem may be? I
>     don't know if it is in the adapter, or in paraview itself. Has
>     anybody encountered problems with runaway memory using Catalyst in
>     4.4 when writing images or VTK files?
>
>
>     I know when we use pvpython to generate images and loop over many
>     files, sometimes the memory also blows up and so we usually move
>     the loop over the files outside the pvpython script and into a
>     driver script that executes a new pvpython for each file. Is there
>     a way to shut down/start up Catalyst each time it needs to write
>     something? Is that advisable?
>
>
>     Thanks,
>
>
>     Tim
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>
>     Search the list archives at:
>     http://markmail.org/search/?q=ParaView
>     <http://markmail.org/search/?q=ParaView>
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/cea6395e/attachment.html>

From tim.gallagher at gatech.edu  Fri May 20 16:17:49 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Fri, 20 May 2016 20:17:49 +0000
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
Message-ID: <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>

Thanks for the advice Burlen -- I haven't used Massif before, so this is a good opportunity to give it a try.


The initialize/finalize each time approach doesn't work either. I am calling the Finalize() routine on the vtkCPProcessor class but then when it tries to initialize again, it throws:


Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line 50
vtkSocketController (0xa4342f0): Already initialized.


and then crashes. So, hopefully I can sort out the memory leak rather than trying to debug why a hacked fix doesn't work!


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com>
Sent: Friday, May 20, 2016 3:46 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst


VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all kinds of leaks. For example you can have leaks where data erroneously accumulates with each time step, but is deleted at program termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's probably better to use massif to profile your code on a small one node run. There's an excellent tool called massif visualizer to aid in exploring the data generated.


$0.02

On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:

Hi Andy,


Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what it turns up.


The initialize/finalize every time is definitely a hack and not for long-term use. But, sponsors want a report on Monday and we need to be able to visualize things for that -- the simulation is too big to write data files and post-process later. So I modified the code to do that for now until I can find a proper fix.


I'll let you know if I get stuck with the log file.


Thanks again,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com><mailto:andy.bauer at kitware.com>
Sent: Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding VTK objects that aren't deleted properly. You should be able to run this with a small amount of calls to Catalyst as well. If you try this and want help understanding the output (if an object like a vtkUnstructuredGrid is leaked it will often give a whole bunch of false leaks that the unstructured grid is just holding the references to), just share your output file and I can take a look at it to try and narrow down the culprit. That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any Catalyst work to see what happens then. That may be a lot of compute cycles but I'm not sure how else to try and bisect where the memory leak is occurring.

Initializing and finalizing Catalyst every time you want output would probably work but I'd think there may be significant overhead doing it like this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at <http://www.kitware.com/opensource/opensource.html> 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> http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview





_______________________________________________
Powered by www.kitware.com<http://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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/44615dc4/attachment.html>

From tim.gallagher at gatech.edu  Fri May 20 19:36:15 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Fri, 20 May 2016 23:36:15 +0000
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>,
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>

Well... not going so well.


If I run a small simulation with massif and the Release build of paraview, I don't see any growing memory in time. I also get my VTK files and images.


If I run the same simulation linked against a Debug build with VTK_DEBUG_LEAKS on, there is a segfault inside one of the libvtkRendering libraries (it says libvtkRenderingOp but the rest of the name is cut off). If I take the image rendering out of my pipeline (comment out the RegisterView call) and leave the VTK file writing, it runs fine and doesn't report any leaks. I tried to get the segfault to drop a core file, but it won't do it.


I'm thinking that there is an issue in the rendering part causing the leak. I have no idea what it could be though -- this is the 4.4.0 version, is anybody aware of any bug fixes between 4.4.0 and current versions that might be relevant?


Thanks for the help,


Tim




________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Gallagher, Timothy P <tim.gallagher at gatech.edu>
Sent: Friday, May 20, 2016 4:17 PM
To: Burlen Loring; Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst


Thanks for the advice Burlen -- I haven't used Massif before, so this is a good opportunity to give it a try.


The initialize/finalize each time approach doesn't work either. I am calling the Finalize() routine on the vtkCPProcessor class but then when it tries to initialize again, it throws:


Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line 50
vtkSocketController (0xa4342f0): Already initialized.


and then crashes. So, hopefully I can sort out the memory leak rather than trying to debug why a hacked fix doesn't work!


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com>
Sent: Friday, May 20, 2016 3:46 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst


VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all kinds of leaks. For example you can have leaks where data erroneously accumulates with each time step, but is deleted at program termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's probably better to use massif to profile your code on a small one node run. There's an excellent tool called massif visualizer to aid in exploring the data generated.


$0.02

On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:

Hi Andy,


Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what it turns up.


The initialize/finalize every time is definitely a hack and not for long-term use. But, sponsors want a report on Monday and we need to be able to visualize things for that -- the simulation is too big to write data files and post-process later. So I modified the code to do that for now until I can find a proper fix.


I'll let you know if I get stuck with the log file.


Thanks again,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com><mailto:andy.bauer at kitware.com>
Sent: Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding VTK objects that aren't deleted properly. You should be able to run this with a small amount of calls to Catalyst as well. If you try this and want help understanding the output (if an object like a vtkUnstructuredGrid is leaked it will often give a whole bunch of false leaks that the unstructured grid is just holding the references to), just share your output file and I can take a look at it to try and narrow down the culprit. That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any Catalyst work to see what happens then. That may be a lot of compute cycles but I'm not sure how else to try and bisect where the memory leak is occurring.

Initializing and finalizing Catalyst every time you want output would probably work but I'd think there may be significant overhead doing it like this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at <http://www.kitware.com/opensource/opensource.html> 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> http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview





_______________________________________________
Powered by www.kitware.com<http://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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/3eafa56d/attachment.html>

From kmorel at sandia.gov  Sat May 21 11:47:05 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Sat, 21 May 2016 15:47:05 +0000
Subject: [Paraview] Slow with just 1M cells
Message-ID: <C732BAF0-0404-4FF7-A3B3-0AFC9F69A7C5@sandia.gov>

Michele,

Taking over a minute to process a data set with 1 million cells does seem like an unreasonably long time, even for a moderately powered PC. Perhaps something odd is happening here. Can you describe in more detail what your data look like and what you are doing with them?

-Ken

On 5/20/16, 11:55 AM, "ParaView on behalf of Michele Battistoni" <paraview-bounces at paraview.org on behalf of michele.battistoni at unipg.it> wrote:

>Paraview is awesome for lots of functionalities, however I find it extremely slow in processing data with any filter type, or in changing timestep as soon as the model size is around one million cells or above. I have experience with a commercial tool which on the same model and pc is 100x faster. Let's say a second vs. a min!
>
>Is there any specific settings for ram of parallelization among cores?
>
>Thanks 
>Michele
>
>
>_______________________________________________
>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


From houssen at ipgp.fr  Sat May 21 12:57:14 2016
From: houssen at ipgp.fr (houssen)
Date: Sat, 21 May 2016 18:57:14 +0200
Subject: [Paraview] =?utf-8?q?Bug_in_XDMF_reader_=3F?=
In-Reply-To: <ebf4c9d96a628cea31d376c98435c2da@imap.ipgp.fr>
References: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
 <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>
 <ebf4c9d96a628cea31d376c98435c2da@imap.ipgp.fr>
Message-ID: <e1a6fcb6f8bede4cedb4fa97b0ef6156@imap.ipgp.fr>

I've just tried to visualize KO.xdmf with visit-2.10.2 : it works fine 
! So I guess it's a bug in paraview. How to file a bug ?

Franck

Le 2016-05-17 15:07, houssen a ?crit?:
> Just to clarify, the scenario that makes problem is : select all
> cells, go to selection inspector, visualize (in 3D viewer) values on
> cells and / or points (this triggers errors).
> My understanding is that both xdmf (OK and KO) are valid and should
> work. OK.xdmf works (whatever PV version), but, KO.xdmf do not
> (whatever PV version).
> The problem appears when attribute names differ on different grids :
> this looks (not sure) like a bug to me.
>
> With PV5.0.0 + default XDMF reader (which should be XDMF2 if I
> understand correctly), I get :
> Warning: In
> 
> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
> line 439
> vtkLabeledDataMapper (0x36cc600): Could not find label array
> (NodeValues) in input.
> Warning: In
> 
> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
> line 439
> vtkLabeledDataMapper (0x36cc600): Could not find label array
> (NodeVal) in input.
>
> Note : I tested with all point and cell values, only node values
> triggers error, cell values "do nothing".
>
> With PV5.0.0 + XDMF3 reader, I get:
> 'Content' not found in itemProperties in XdmfArray::populateItem
> Qt has caught an exception thrown from an event handler. Throwing
> exceptions from an event handler is not supported in Qt. You must
> reimplement QApplication::notify() and catch all exceptions there.
> terminate called after throwing an instance of 'XdmfError'
>   what():  'Content' not found in itemProperties in 
> XdmfArray::populateItem
> Aborted
>
> With PV4.0.1 + default XDMF reader (which should be XDMF2 if I
> understand correctly), I get :
> Warning: In
> 
> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
> line 442
> vtkLabeledDataMapper (0x97f2140): Could not find label array
> (CellVal) in input.
> Warning: In
> 
> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
> line 442
> vtkLabeledDataMapper (0x97d32d0): Could not find label array
> (NodeVal) in input.
>
> Note : I tested with all point and cell values, only CellVal and
> NodeVal triggers error, NodesValues and CellValues are visualized
> correctly.
>
> Franck
>
> ~> diff OK.xdmf KO.xdmf
> 48c48
> <       <Attribute Name="NodeValues" AttributeType="Scalar" 
> Center="Node">
> ---
>>       <Attribute Name="NodeVal" AttributeType="Scalar" 
>> Center="Node">
> 52c52
> <       <Attribute Name="CellValues" AttributeType="Scalar" 
> Center="Cell">
> ---
>>       <Attribute Name="CellVal" AttributeType="Scalar" 
>> Center="Cell">
>
>
> Le 2016-05-17 13:57, Joachim Pouderoux a ?crit?:
>> Houssen,
>>
>> Could you specify which reader you are using? xdmf2 or xdmf3?
>> You mention PV5.0.0 - do you mean it used to work with previous
>> releases?
>>
>> Best,
>>
>> JOACHIM POUDEROUX
>>
>>> _PhD, Technical Expert_
>>
>> 2016-05-16 16:55 GMT+02:00 houssen <houssen at ipgp.fr [6]>:
>>
>>> Hello,
>>>
>>> I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when
>>> attribute names differ in grids, data can not be visualized : is
>>> this intended ? If yes why ? If no, how to file a bug ?
>>>
>>> Thanks,
>>>
>>> Franck
>>>
>>> ~> diff OK.xdmf KO.xdmf
>>> 48c48
>>> <? ? ? ?<Attribute Name="NodeValues" AttributeType="Scalar"
>>> Center="Node">
>>> ---
>>>
>>>> ? ? ? <Attribute Name="NodeVal" AttributeType="Scalar"
>>>> Center="Node">
>>> 52c52
>>> <? ? ? ?<Attribute Name="CellValues" AttributeType="Scalar"
>>> Center="Cell">
>>> ---
>>>
>>>> ? ? ? <Attribute Name="CellVal" AttributeType="Scalar"
>>>> Center="Cell">
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com [1]
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html [2]
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView [3]
>>>
>>> Search the list archives at:
>>> http://markmail.org/search/?q=ParaView [4]
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview [5]
>>
>>
>>
>> Links:
>> ------
>> [1] http://www.kitware.com
>> [2] http://www.kitware.com/opensource/opensource.html
>> [3] http://paraview.org/Wiki/ParaView
>> [4] http://markmail.org/search/?q=ParaView
>> [5] http://public.kitware.com/mailman/listinfo/paraview
>> [6] mailto:houssen at ipgp.fr


From svenkramer40 at gmail.com  Sat May 21 13:53:23 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Sat, 21 May 2016 19:53:23 +0200
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
Message-ID: <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>

Thank you, Seb,
it seems like I am getting it to work. There are still some difficulties
because of my limited javascript experience, but with some quick&dirty
workarounds I do have the Catalyst output displayed from ParaViewWeb. As
you said, nothing else was required than wrapping the C functions in python.

Thanks
Sven


2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
sebastien.jourdain at kitware.com>:

> Hi Sven,
>
> I am not aware on any specific developer documentation for Catalyst on the
> ParaView side (but I haven't worked on that subject for years), although
> Utkarsh or Andy might know.
>
> Usually looking at the code and redoing it in the Python world is what is
> required, but as I said, I'm not sure of what it means since I don't know
> that code anymore. ;-)
>
> For the timeframe, I can't tell (meaning I don't know), but we can still
> try to help you or implement the missing piece via support contract if that
> make sense on your end.
>
> Thanks,
>
> Seb
>
> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Hello Seb,
>> glad to read your answer. So the problem is not only that I was unable to
>> find the relevant information.
>>
>> You say, you have not (yet) written the required code. Does "not (yet)"
>> mean that it is on the agenda maybe within the next half year? Then I could
>> find a workaround and look forward to the next Paraview updates.
>>
>> Otherwise I would try to work on the implementation for connecting
>> Paraviewweb to Catalyst output. Is there any developer documentation of
>> Catalysts "specific socket connection"? Or some general Catalyst developer
>> information? Those would be great to get started.
>> My first attempt would be to "wrap" the functionality of
>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>> make it available to the web client. Or are the necessary steps much more
>> involved?
>>
>> Thank you
>> Sven
>>
>>
>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>> sebastien.jourdain at kitware.com>:
>>
>>> Hi Sven,
>>>
>>> Live catalyst connection require a specific socket connection to the
>>> in-situ process with some special handling.
>>> We did not (yet) wrote the Python code to perform that specific action
>>> for ParaViewWeb so it could be triggered by the web client or configured
>>> via an argument at launch time.
>>> I don't see any reason why this couldn't work, but as for now, I also
>>> don't know an easy step to do it without spending time doing it myself.
>>>
>>> Seb
>>>
>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>> I am looking for the recommended steps how to display an in-situ (live)
>>>> Catalyst simulation through ParaViewWeb.
>>>>
>>>> After some efforts I am able to run ParaViewWeb successfully and I can
>>>> view a Catalyst-enabled simulation in paraview.
>>>>
>>>> I hope, it is also possible to show the live Catalyst output via
>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>> pvserver as mentioned at the end of
>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
>>>> giving "--ds-host localhost --ds-port 11111" options to
>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>> displayed on the web.
>>>>
>>>> Below you find the (not too detailed) steps I took to have a working
>>>> solution for either Catalyst-enabled simulations or a working web
>>>> visualizer:
>>>>
>>>> Test connection from Catalyst simulation to paraview:
>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
>>>> http://www.paraview.org/download/)
>>>> 2) Choose Catalyst->Connect in paraview
>>>> 3) Run CFullExample from
>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>> Success!
>>>>
>>>> Test ParaViewWeb:
>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>> http://www.paraview.org/download/, extract in /data
>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>> Success!
>>>>
>>>> But how do I get Catalyst into the web visualizer? Is there any example
>>>> how to combine them? Anybody who can suggest the required steps?
>>>>
>>>> Regards,
>>>> Sven
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160521/73a9b6bc/attachment.html>

From jfrx04 at gmail.com  Sun May 22 04:31:37 2016
From: jfrx04 at gmail.com (Feng Jiang)
Date: Sun, 22 May 2016 16:31:37 +0800
Subject: [Paraview] Problems about calculate the difference between two
	datasets
Message-ID: <CAGbDe5F+QasWTXGNk=t1hyfqFo=OTSn=x9z-ys9h0FxQmVeDuA@mail.gmail.com>

ParaView newbie here ,and sorry to interrupt you for some problems i met.

I have been using two vtk input files which named t1 and t2 for example,
both input files contained only one dataset for CellData may called flux1
and flux2.

Exactly the structure and the data t1 and t2 got were same and only make a
reflect from the surface of the center of x axis.

And I want to make the CellData flux1 to subtrack the flux2.
However I have tried Using the Group Datasets and the Calculator, or Using
the Python Calculator or Programmable filter, and all the result I got is
empty.

The results I tried seems the ParaView only subtracked the data basic on
the Cell ID.

So is there any way to solve it or some wrong operate I made I wondered, or
I must make the datasets reflect before I input ParaView ?

Thanks for any guidance,

Feng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160522/5bdabe06/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Sun May 22 07:59:41 2016
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Sun, 22 May 2016 14:59:41 +0300 (EEST)
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <CAMaOp+Ft3FoWrH9R-+hb8hB2PRNrLQ4cHn631sCEc8GkDmkrjA@mail.gmail.com>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>
 <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
 <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
 <62131.95.7.172.33.1463584631.squirrel@webmail.be.itu.edu.tr>
 <CAMaOp+Ft3FoWrH9R-+hb8hB2PRNrLQ4cHn631sCEc8GkDmkrjA@mail.gmail.com>
Message-ID: <61248.78.182.85.87.1463918381.squirrel@webmail.be.itu.edu.tr>

Thanks for the information. Currently, i am working on two component case
and the initial results show that grid and data information belong to each
model component must be accessible by all the MPI processes (defined in
global MPI_COMM_WORLD) in adaptor side. This makes the implementation very
complex when the 2d decomposition configuration of both model components
(which run in a specific subset of processors) are considered. In this
case, it seems that the easiest way is to interpolate/ redistribute the
data of both components into common grid or creating new 2d decomposition
in adaptor. Another possibility might be to implement MPI sections
specific for each model component (basically having two distinct
MPI_COMM_WORLD inside of global one) to access grid and fields in the
adaptor side but in this case i am not sure ParaView could handle these
kind of information or not. Anyway, it seems that it is a challanging
problem and probably it would be good to have this feature. I'll keep to
continue to try different implementations to test different ideas and keep
you posted about it. In the mean time, if you have any other idea, let me
know.

Regards,

--ufuk

> It may be possible to do this with Catalyst. I would guess that nearly all
> of the complex work would need to be done in the adaptor to integrate this
> properly though.
>
> On Wed, May 18, 2016 at 11:17 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Yes, you are right. In this case, there will be two separate
>> MPI_COMM_WORLD. Plus, one that covers all the resources (let's say that
>> global MPI_COMM_WORLD). Actually, this kind of setup is very common for
>> multi-physics applications such as fluid-structure interaction. So, is
>> it
>> possible to tight this kind of environment with Catalyst? I am not
>> expert
>> about Catalyst but it seems that there might be a problem in the
>> rendering
>> stage even underlying grids and fields are defined without any problem.
>>
>> Regards,
>>
>> --ufuk
>>
>> > I'm not sure if this is exactly what the original user is referring
>> to,
>> > but it is possible to have two separate codes communicate using MPI
>> > through the dynamic processes in MPI-2. Essentially, one program
>> starts
>> up
>> > on N processors and begins running and gets an MPI_COMM_WORLD. It then
>> > spawns another executable on M different processors and that new
>> > executable will call MPI_INIT and also get its own MPI_COMM_WORLD. So
>> you
>> > have two, disjoint MPI_COMM_WORLD's that get linked together through a
>> > newly created intercommunicator.
>> >
>> >
>> > I've used this to couple a structural mechanics code to our fluid
>> dynamics
>> > solver for example. It sounds like that is similar to what is being
>> done
>> > here.
>> >
>> >
>> > How that would interact with coprocessing is beyond my knowledge
>> though.
>> > It does sound like an interesting problem and one I would be very
>> curious
>> > to find out the details.
>> >
>> >
>> > Tim
>> >
>> >
>> > ________________________________
>> > From: ParaView <paraview-bounces at paraview.org> on behalf of Andy Bauer
>> > <andy.bauer at kitware.com>
>> > Sent: Wednesday, May 18, 2016 10:52 AM
>> > To: Ufuk Utku Turuncoglu (BE)
>> > Cc: paraview at paraview.org
>> > Subject: Re: [Paraview] capability of ParaView, Catalyst in
>> distributed
>> > computing environment ...
>> >
>> > Hi,
>> >
>> > I'm a bit confused. MPI_COMM_WORLD is the global communicator and as
>> far
>> > as I'm aware, can't be modified which means there can't be two
>> different
>> > communicators.
>> >
>> > Catalyst can be set to use a specific MPI communicator and that's been
>> > done by at least one code (Code_Saturne). I think they have a
>> multiphysics
>> > simulation as well.
>> >
>> > Cheers,
>> > Andy
>> >
>> > On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE)
>> > <u.utku.turuncoglu at be.itu.edu.tr<mailto:u.utku.turuncoglu at be.itu.edu.tr
>> >>
>> > wrote:
>> > Hi All,
>> >
>> > I just wonder about the capability of ParaView, Catalyst in
>> distributed
>> > computing environment. I have little bit experience in in-situ
>> > visualization but it is hard for me to see the big picture at this
>> point.
>> > So, i decided to ask to the user list to get some suggestion from the
>> > experts. Hypothetically, lets assume that we have two simulation code
>> that
>> > are coupled together (i.e. fluid-structure interaction) and both of
>> them
>> > have their own MPI_COMM_WORLD and run on different processors (model1
>> runs
>> > on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct
>> > design to create integrated in-situ visualization analysis (both model
>> > contributes to same visualization pipeline) in this case? Do you know
>> any
>> > implementation that is similar to this design? At least, is it
>> possible?
>> >
>> > In this case, the adaptor code will need to access to two different
>> > MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its
>> own
>> > MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation
>> code
>> > have its own grid and field definitions (might be handled via defining
>> > different input ports). Does it create a problem in Paraview, Catalyst
>> > side, if the multiblock dataset is used to define the grids of the
>> > components in adaptor. I am asking because some MPI processes (belongs
>> to
>> > adaptor code) will not have data for specific model component due to
>> the
>> > domain decomposition implementation of the individual models. For
>> example,
>> > MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank
>> > 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI
>> rank
>> > 4,5,6,7). To that end, do i need to collect all the data from the
>> > components? If this is the case, how can i handle 2d decomposition
>> > problem? Because, the adaptor code has no any common grid structure
>> that
>> > fits for all the model components.
>> >
>> > Regards,
>> >
>> > Ufuk Turuncoglu
>> > _______________________________________________
>> > Powered by www.kitware.com<http://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
>> >
>> >
>>
>>
>


From mathieu.westphal at kitware.com  Sun May 22 09:43:22 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Sun, 22 May 2016 15:43:22 +0200
Subject: [Paraview] Problems about calculate the difference between two
	datasets
In-Reply-To: <CAGbDe5F+QasWTXGNk=t1hyfqFo=OTSn=x9z-ys9h0FxQmVeDuA@mail.gmail.com>
References: <CAGbDe5F+QasWTXGNk=t1hyfqFo=OTSn=x9z-ys9h0FxQmVeDuA@mail.gmail.com>
Message-ID: <CAC2t4USDyT3SETn2QBZ0jpTFw2QawYjSiP+oARBzDaFecZ8tbg@mail.gmail.com>

Hello

Python calculator is the way to go here

inputs[0].PointData['flux1'] - inputs[1].PointData['flux2']

Beware of the order of the input, they will be ordered randomly by
paraview, but you can reorder them wia the python shell, or modify your
python-calculator script.


Mathieu Westphal

On Sun, May 22, 2016 at 10:31 AM, Feng Jiang <jfrx04 at gmail.com> wrote:

> ParaView newbie here ,and sorry to interrupt you for some problems i met.
>
> I have been using two vtk input files which named t1 and t2 for example,
> both input files contained only one dataset for CellData may called flux1
> and flux2.
>
> Exactly the structure and the data t1 and t2 got were same and only make a
> reflect from the surface of the center of x axis.
>
> And I want to make the CellData flux1 to subtrack the flux2.
> However I have tried Using the Group Datasets and the Calculator, or Using
> the Python Calculator or Programmable filter, and all the result I got is
> empty.
>
> The results I tried seems the ParaView only subtracked the data basic on
> the Cell ID.
>
> So is there any way to solve it or some wrong operate I made I wondered,
> or I must make the datasets reflect before I input ParaView ?
>
> Thanks for any guidance,
>
> Feng
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160522/2f5058f7/attachment.html>

From tim.gallagher at gatech.edu  Sun May 22 11:32:06 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Sun, 22 May 2016 15:32:06 +0000
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <61248.78.182.85.87.1463918381.squirrel@webmail.be.itu.edu.tr>
References: <e9768429-788d-e781-80cb-db20cfb863ec@be.itu.edu.tr>
 <CAMaOp+GCnpDtS1HmMBcyMCLg+HXnbsiR_kRjhtrvcP2iqbo0aQ@mail.gmail.com>
 <BN3PR07MB26278B7BD3424E0EC6463B7D9D490@BN3PR07MB2627.namprd07.prod.outlook.com>
 <62131.95.7.172.33.1463584631.squirrel@webmail.be.itu.edu.tr>
 <CAMaOp+Ft3FoWrH9R-+hb8hB2PRNrLQ4cHn631sCEc8GkDmkrjA@mail.gmail.com>,
 <61248.78.182.85.87.1463918381.squirrel@webmail.be.itu.edu.tr>
Message-ID: <BN3PR07MB2627380EC873573512619BD79D4D0@BN3PR07MB2627.namprd07.prod.outlook.com>

If you can control which communicator Paraview uses, you might want to look at using MPI_INTERCOMM_MERGE, which will take the union of the two disjoint sets described by an intercommunicator. So with that, you would create a new communicator that has all of your processors as members.

Paraview should be able to use that merged communicator seamlessly because it is a single communicator with all of the processor members attached. Meanwhile, your individual codes still use their own MPI_COMM_WORLD and the intercommunicator when they need to share information. 

That way, the codes do not need to change. Your adapter does the work of dealing with the merge process and the managing the merged communicator. 

I haven't tested anything like this of course. Just putting the idea out there.

Tim

________________________________________
From: u.utku.turuncoglu at be.itu.edu.tr <u.utku.turuncoglu at be.itu.edu.tr>
Sent: Sunday, May 22, 2016 7:59 AM
To: Andy Bauer
Cc: Ufuk Utku Turuncoglu; Gallagher, Timothy P; paraview at paraview.org
Subject: Re: [Paraview] capability of ParaView,      Catalyst in distributed computing environment ...

Thanks for the information. Currently, i am working on two component case
and the initial results show that grid and data information belong to each
model component must be accessible by all the MPI processes (defined in
global MPI_COMM_WORLD) in adaptor side. This makes the implementation very
complex when the 2d decomposition configuration of both model components
(which run in a specific subset of processors) are considered. In this
case, it seems that the easiest way is to interpolate/ redistribute the
data of both components into common grid or creating new 2d decomposition
in adaptor. Another possibility might be to implement MPI sections
specific for each model component (basically having two distinct
MPI_COMM_WORLD inside of global one) to access grid and fields in the
adaptor side but in this case i am not sure ParaView could handle these
kind of information or not. Anyway, it seems that it is a challanging
problem and probably it would be good to have this feature. I'll keep to
continue to try different implementations to test different ideas and keep
you posted about it. In the mean time, if you have any other idea, let me
know.

Regards,

--ufuk

> It may be possible to do this with Catalyst. I would guess that nearly all
> of the complex work would need to be done in the adaptor to integrate this
> properly though.
>
> On Wed, May 18, 2016 at 11:17 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Yes, you are right. In this case, there will be two separate
>> MPI_COMM_WORLD. Plus, one that covers all the resources (let's say that
>> global MPI_COMM_WORLD). Actually, this kind of setup is very common for
>> multi-physics applications such as fluid-structure interaction. So, is
>> it
>> possible to tight this kind of environment with Catalyst? I am not
>> expert
>> about Catalyst but it seems that there might be a problem in the
>> rendering
>> stage even underlying grids and fields are defined without any problem.
>>
>> Regards,
>>
>> --ufuk
>>
>> > I'm not sure if this is exactly what the original user is referring
>> to,
>> > but it is possible to have two separate codes communicate using MPI
>> > through the dynamic processes in MPI-2. Essentially, one program
>> starts
>> up
>> > on N processors and begins running and gets an MPI_COMM_WORLD. It then
>> > spawns another executable on M different processors and that new
>> > executable will call MPI_INIT and also get its own MPI_COMM_WORLD. So
>> you
>> > have two, disjoint MPI_COMM_WORLD's that get linked together through a
>> > newly created intercommunicator.
>> >
>> >
>> > I've used this to couple a structural mechanics code to our fluid
>> dynamics
>> > solver for example. It sounds like that is similar to what is being
>> done
>> > here.
>> >
>> >
>> > How that would interact with coprocessing is beyond my knowledge
>> though.
>> > It does sound like an interesting problem and one I would be very
>> curious
>> > to find out the details.
>> >
>> >
>> > Tim
>> >
>> >
>> > ________________________________
>> > From: ParaView <paraview-bounces at paraview.org> on behalf of Andy Bauer
>> > <andy.bauer at kitware.com>
>> > Sent: Wednesday, May 18, 2016 10:52 AM
>> > To: Ufuk Utku Turuncoglu (BE)
>> > Cc: paraview at paraview.org
>> > Subject: Re: [Paraview] capability of ParaView, Catalyst in
>> distributed
>> > computing environment ...
>> >
>> > Hi,
>> >
>> > I'm a bit confused. MPI_COMM_WORLD is the global communicator and as
>> far
>> > as I'm aware, can't be modified which means there can't be two
>> different
>> > communicators.
>> >
>> > Catalyst can be set to use a specific MPI communicator and that's been
>> > done by at least one code (Code_Saturne). I think they have a
>> multiphysics
>> > simulation as well.
>> >
>> > Cheers,
>> > Andy
>> >
>> > On Wed, May 18, 2016 at 5:22 AM, Ufuk Utku Turuncoglu (BE)
>> > <u.utku.turuncoglu at be.itu.edu.tr<mailto:u.utku.turuncoglu at be.itu.edu.tr
>> >>
>> > wrote:
>> > Hi All,
>> >
>> > I just wonder about the capability of ParaView, Catalyst in
>> distributed
>> > computing environment. I have little bit experience in in-situ
>> > visualization but it is hard for me to see the big picture at this
>> point.
>> > So, i decided to ask to the user list to get some suggestion from the
>> > experts. Hypothetically, lets assume that we have two simulation code
>> that
>> > are coupled together (i.e. fluid-structure interaction) and both of
>> them
>> > have their own MPI_COMM_WORLD and run on different processors (model1
>> runs
>> > on MPI rank 0,1,2,3 and model2 runs on 4,5,6,7). What is the correct
>> > design to create integrated in-situ visualization analysis (both model
>> > contributes to same visualization pipeline) in this case? Do you know
>> any
>> > implementation that is similar to this design? At least, is it
>> possible?
>> >
>> > In this case, the adaptor code will need to access to two different
>> > MPI_COMM_WORLD and it could run on all processor (from 0 to 7) or its
>> own
>> > MPI_COMM_WORLD (i.e. MPI ranks 8,9,10,11). Also, the both simulation
>> code
>> > have its own grid and field definitions (might be handled via defining
>> > different input ports). Does it create a problem in Paraview, Catalyst
>> > side, if the multiblock dataset is used to define the grids of the
>> > components in adaptor. I am asking because some MPI processes (belongs
>> to
>> > adaptor code) will not have data for specific model component due to
>> the
>> > domain decomposition implementation of the individual models. For
>> example,
>> > MPI rank 4,5,6,7 will not have data for model1 (that runs on MPI rank
>> > 0,1,2,3) and 0,1,2,3 will not have data for model2 (that runs on MPI
>> rank
>> > 4,5,6,7). To that end, do i need to collect all the data from the
>> > components? If this is the case, how can i handle 2d decomposition
>> > problem? Because, the adaptor code has no any common grid structure
>> that
>> > fits for all the model components.
>> >
>> > Regards,
>> >
>> > Ufuk Turuncoglu
>> > _______________________________________________
>> > Powered by www.kitware.com<http://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
>> >
>> >
>>
>>
>


From burlen.loring at gmail.com  Sun May 22 22:30:43 2016
From: burlen.loring at gmail.com (Burlen Loring)
Date: Sun, 22 May 2016 19:30:43 -0700
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <57426B53.2060700@gmail.com>

btw, we just had similar problem that was entirely explained by vtk 
writer attempting to gather a bunch of arrays to the root node. Utkarsh 
found a way to disable that behavior. I wonder if you are hitting the same.

On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:
>
> Well... not going so well.
>
>
> If I run a small simulation with massif and the Release build of 
> paraview, I don't see any growing memory in time. I also get my VTK 
> files and images.
>
>
> If I run the same simulation linked against a Debug build with 
> VTK_DEBUG_LEAKS on, there is a segfault inside one of the 
> libvtkRendering libraries (it says libvtkRenderingOp but the rest of 
> the name is cut off). If I take the image rendering out of my pipeline 
> (comment out the RegisterView call) and leave the VTK file writing, it 
> runs fine and doesn't report any leaks. I tried to get the segfault to 
> drop a core file, but it won't do it.
>
>
> I'm thinking that there is an issue in the rendering part causing the 
> leak. I have no idea what it could be though -- this is the 4.4.0 
> version, is anybody aware of any bug fixes between 4.4.0 and current 
> versions that might be relevant?
>
>
> Thanks for the help,
>
>
> Tim
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* ParaView <paraview-bounces at paraview.org> on behalf of 
> Gallagher, Timothy P <tim.gallagher at gatech.edu>
> *Sent:* Friday, May 20, 2016 4:17 PM
> *To:* Burlen Loring; Andy Bauer
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Memory leak with Catalyst
>
> Thanks for the advice Burlen -- I haven't used Massif before, so this 
> is a good opportunity to give it a try.
>
>
> The initialize/finalize each time approach doesn't work either. I am 
> calling the Finalize() routine on the vtkCPProcessor class but then 
> when it tries to initialize again, it throws:
>
>
> Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, 
> line 50
> vtkSocketController (0xa4342f0): Already initialized.
>
>
> and then crashes. So, hopefully I can sort out the memory leak rather 
> than trying to debug why a hacked fix doesn't work!
>
>
> Tim
>
>
>
> ------------------------------------------------------------------------
> *From:* Burlen Loring <burlen.loring at gmail.com>
> *Sent:* Friday, May 20, 2016 3:46 PM
> *To:* Gallagher, Timothy P; Andy Bauer
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Memory leak with Catalyst
>
> VTK_DEBUG_LEAKS, although will catch some serious errors, will not 
> catch all kinds of leaks. For example you can have leaks where data 
> erroneously accumulates with each time step, but is deleted at program 
> termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's 
> probably better to use massif to profile your code on a small one node 
> run. There's an excellent tool called massif visualizer to aid in 
> exploring the data generated.
>
>
> $0.02
>
>
> On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:
>>
>> Hi Andy,
>>
>>
>> Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now 
>> and see what it turns up.
>>
>>
>> The initialize/finalize every time is definitely a hack and not for 
>> long-term use. But, sponsors want a report on Monday and we need to 
>> be able to visualize things for that -- the simulation is too big to 
>> write data files and post-process later. So I modified the code to do 
>> that for now until I can find a proper fix.
>>
>>
>> I'll let you know if I get stuck with the log file.
>>
>>
>> Thanks again,
>>
>>
>> Tim
>>
>>
>>
>> ------------------------------------------------------------------------
>> *From:* Andy Bauer <andy.bauer at kitware.com>
>> *Sent:* Friday, May 20, 2016 2:39 PM
>> *To:* Gallagher, Timothy P
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Memory leak with Catalyst
>> Hi Tim,
>>
>> If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good 
>> at finding VTK objects that aren't deleted properly. You should be 
>> able to run this with a small amount of calls to Catalyst as well. If 
>> you try this and want help understanding the output (if an object 
>> like a vtkUnstructuredGrid is leaked it will often give a whole bunch 
>> of false leaks that the unstructured grid is just holding the 
>> references to), just share your output file and I can take a look at 
>> it to try and narrow down the culprit. That may be slightly easier to 
>> use than Valgrind.
>>
>> Beyond this, you could maybe try the same run but without doing any 
>> Catalyst work to see what happens then. That may be a lot of compute 
>> cycles but I'm not sure how else to try and bisect where the memory 
>> leak is occurring.
>>
>> Initializing and finalizing Catalyst every time you want output would 
>> probably work but I'd think there may be significant overhead doing 
>> it like this. Plus, it's not really solving the problem -- just 
>> avoiding it.
>>
>> Best,
>> Andy
>>
>>
>> On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P 
>> <tim.gallagher at gatech.edu <mailto:tim.gallagher at gatech.edu>> wrote:
>>
>>     Hi,
>>
>>
>>     One of our users is running a very big simulation and writing out
>>     images of two slices (two different views) every 1000 iterations
>>     and writing out the data for the two slices (two different data
>>     writers) as VTK files every 5000 iterations. It is using Paraview
>>     4.4.
>>
>>
>>     After 21000 iterations, the simulation is killed because the
>>     memory on the compute nodes fills up. I usually know how to track
>>     down memory problems in our code using valgrind and related
>>     tools, but is that the right way to go to try and find this problem?
>>
>>
>>     Are there any tips on how to isolate where the problem may be? I
>>     don't know if it is in the adapter, or in paraview itself. Has
>>     anybody encountered problems with runaway memory using Catalyst
>>     in 4.4 when writing images or VTK files?
>>
>>
>>     I know when we use pvpython to generate images and loop over many
>>     files, sometimes the memory also blows up and so we usually move
>>     the loop over the files outside the pvpython script and into a
>>     driver script that executes a new pvpython for each file. Is
>>     there a way to shut down/start up Catalyst each time it needs to
>>     write something? Is that advisable?
>>
>>
>>     Thanks,
>>
>>
>>     Tim
>>
>>
>>     _______________________________________________
>>     Powered by www.kitware.com <http://www.kitware.com>
>>
>>     Visit other Kitware open-source projects at
>>     <http://www.kitware.com/opensource/opensource.html>http://www.kitware.com/opensource/opensource.html
>>
>>     Please keep messages on-topic and check the ParaView Wiki at:
>>     http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>
>>     Search the list archives at:
>>     <http://markmail.org/search/?q=ParaView>http://markmail.org/search/?q=ParaView
>>
>>     Follow this link to subscribe/unsubscribe:
>>     http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>>
>>
>> _______________________________________________
>> Powered bywww.kitware.com
>>
>> Visit other Kitware open-source projects athttp://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
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160522/8b578a42/attachment.html>

From sebastien.jourdain at kitware.com  Mon May 23 01:22:37 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Sun, 22 May 2016 23:22:37 -0600
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
Message-ID: <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>

Glad to ear that you managed to get something going. If you feel like
sharing your code, we might be able to provide some integration into
ParaView and/or ParaViewWeb proper.

Seb

On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
wrote:

> Thank you, Seb,
> it seems like I am getting it to work. There are still some difficulties
> because of my limited javascript experience, but with some quick&dirty
> workarounds I do have the Catalyst output displayed from ParaViewWeb. As
> you said, nothing else was required than wrapping the C functions in python.
>
> Thanks
> Sven
>
>
> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Hi Sven,
>>
>> I am not aware on any specific developer documentation for Catalyst on
>> the ParaView side (but I haven't worked on that subject for years),
>> although Utkarsh or Andy might know.
>>
>> Usually looking at the code and redoing it in the Python world is what is
>> required, but as I said, I'm not sure of what it means since I don't know
>> that code anymore. ;-)
>>
>> For the timeframe, I can't tell (meaning I don't know), but we can still
>> try to help you or implement the missing piece via support contract if that
>> make sense on your end.
>>
>> Thanks,
>>
>> Seb
>>
>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Hello Seb,
>>> glad to read your answer. So the problem is not only that I was unable
>>> to find the relevant information.
>>>
>>> You say, you have not (yet) written the required code. Does "not (yet)"
>>> mean that it is on the agenda maybe within the next half year? Then I could
>>> find a workaround and look forward to the next Paraview updates.
>>>
>>> Otherwise I would try to work on the implementation for connecting
>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>> information? Those would be great to get started.
>>> My first attempt would be to "wrap" the functionality of
>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>> make it available to the web client. Or are the necessary steps much more
>>> involved?
>>>
>>> Thank you
>>> Sven
>>>
>>>
>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com>:
>>>
>>>> Hi Sven,
>>>>
>>>> Live catalyst connection require a specific socket connection to the
>>>> in-situ process with some special handling.
>>>> We did not (yet) wrote the Python code to perform that specific action
>>>> for ParaViewWeb so it could be triggered by the web client or configured
>>>> via an argument at launch time.
>>>> I don't see any reason why this couldn't work, but as for now, I also
>>>> don't know an easy step to do it without spending time doing it myself.
>>>>
>>>> Seb
>>>>
>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>> I am looking for the recommended steps how to display an in-situ
>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>
>>>>> After some efforts I am able to run ParaViewWeb successfully and I can
>>>>> view a Catalyst-enabled simulation in paraview.
>>>>>
>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>> pvserver as mentioned at the end of
>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
>>>>> giving "--ds-host localhost --ds-port 11111" options to
>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>> displayed on the web.
>>>>>
>>>>> Below you find the (not too detailed) steps I took to have a working
>>>>> solution for either Catalyst-enabled simulations or a working web
>>>>> visualizer:
>>>>>
>>>>> Test connection from Catalyst simulation to paraview:
>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz (from
>>>>> http://www.paraview.org/download/)
>>>>> 2) Choose Catalyst->Connect in paraview
>>>>> 3) Run CFullExample from
>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>> Success!
>>>>>
>>>>> Test ParaViewWeb:
>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>> http://www.paraview.org/download/, extract in /data
>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>> Success!
>>>>>
>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>
>>>>> Regards,
>>>>> Sven
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160522/e47acc3d/attachment.html>

From jfavre at cscs.ch  Mon May 23 02:19:07 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Mon, 23 May 2016 06:19:07 +0000
Subject: [Paraview] Problems about calculate the difference between
	two	datasets
In-Reply-To: <CAC2t4USDyT3SETn2QBZ0jpTFw2QawYjSiP+oARBzDaFecZ8tbg@mail.gmail.com>
References: <CAGbDe5F+QasWTXGNk=t1hyfqFo=OTSn=x9z-ys9h0FxQmVeDuA@mail.gmail.com>,
 <CAC2t4USDyT3SETn2QBZ0jpTFw2QawYjSiP+oARBzDaFecZ8tbg@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684360FC9E@MBX211.d.ethz.ch>

>> Beware of the order of the input, they will be ordered randomly by paraview,

Mathieu,

could you please comment on that statement, "randomly"? I was always under the understanding that the order used by ParaView reflects the order of selection (a series of ctrl-right mouse clicks in the pipeline browser)

Jean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/e661190d/attachment.html>

From mathieu.westphal at kitware.com  Mon May 23 03:41:14 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Mon, 23 May 2016 09:41:14 +0200
Subject: [Paraview] Problems about calculate the difference between two
	datasets
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684360FC9E@MBX211.d.ethz.ch>
References: <CAGbDe5F+QasWTXGNk=t1hyfqFo=OTSn=x9z-ys9h0FxQmVeDuA@mail.gmail.com>
 <CAC2t4USDyT3SETn2QBZ0jpTFw2QawYjSiP+oARBzDaFecZ8tbg@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F684360FC9E@MBX211.d.ethz.ch>
Message-ID: <CAC2t4UQH3kmrpxHFJEXZzBGouu7_g-ELZFAVoqn0WK9JpuohHA@mail.gmail.com>

Hello

Actually no, it is actually ordered by proxy global id order, wich is
basically random from a user point of view.
This is not a wanted behavior but ordering using the order of selection
would need some refactoring.

Regards,

Mathieu Westphal

On Mon, May 23, 2016 at 8:19 AM, Favre Jean <jfavre at cscs.ch> wrote:

> >> Beware of the order of the input, they will be ordered randomly by
> paraview,
>
> Mathieu,
>
> could you please comment on that statement, "randomly"? I was always under
> the understanding that the order used by ParaView reflects the order of
> selection (a series of ctrl-right mouse clicks in the pipeline browser)
>
> Jean
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/c86226c0/attachment.html>

From apeczak at ara.co.uk  Mon May 23 06:16:32 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Mon, 23 May 2016 10:16:32 +0000
Subject: [Paraview] Custom panel widget
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>

Hello,

Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.

Andrzej


**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From grothausmann.roman at mh-hannover.de  Mon May 23 07:26:27 2016
From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.)
Date: Mon, 23 May 2016 13:26:27 +0200
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <548070F4.4070508@gmx.net>
References: <548070F4.4070508@gmx.net>
Message-ID: <5742E8E3.40800@mh-hannover.de>

Dear mailing list members,


When I export scenes to X3D then load the mesh into blender or a browser the 
mesh is colour wrong. The colours are there but apparently assigned to random 
cells/vertices. This happens with either PV5 or PV4, especially for category 
colouring. When using e.g. WebGL exporter all is fine.
Is there anything to do special for exporting to X3D? When I use plain VTK, the 
exported colours seemed OK so far.

Any help or hints are very much appreciated
Roman


On 04/12/14 15:34, Michael Nolde wrote:
> works perfectly, thank you!
>
> On 03.12.2014 19:49, Sebastien Jourdain wrote:
> View is not valid at the point you get it.
>
> from paraview.simple import *
> exporters=servermanager.createModule("exporters")
> source=Cone()
> Show()
> render=Render()
> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
> x3dExporter.SetView(render)
> x3dExporter.Write()
>
> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__> wrote:
> Dear mailing list members,
>
> I have some trouble exporting a scene to a X3D file via pvpython.
> I tried to execute to code found in
> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
> (see below). It is executed without any errors, but no output file is created.
> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
> What I want to achieve is to convert .ply files to .x3d via pvpython.
> Could someone give me a hint?
>
> Thanks in advance,
> Michael
>
> from paraview.simple import *
> exporters=servermanager.createModule("exporters")
> source=Cone()
> view = GetActiveView()
> Show(view)
> render=Render()
> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
> x3dExporter.SetView(view)
> x3dExporter.Write()
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview__
>
>
>
>
>

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-2900

From utkarsh.ayachit at kitware.com  Mon May 23 09:57:34 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 09:57:34 -0400
Subject: [Paraview] Custom panel widget
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>
Message-ID: <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>

> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.

There are several ways of skinning this cat. Can you elaborate of what
exactly is your use-case? Do you want the default values for this
double-vector-property (DVP) set using some values provided by the VTK
filter, but allow user to override using UI?

From tim.gallagher at gatech.edu  Mon May 23 09:57:37 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 23 May 2016 13:57:37 +0000
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <57426B53.2060700@gmail.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <57426B53.2060700@gmail.com>
Message-ID: <BN3PR07MB2627F93DC800BA34D03EF05F9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>

Interesting -- I'd be willing to try it out if you have more details (commit hashtag, ticket, etc.), even if I have to figure out how to backport it from a newer version.


Thanks,


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com>
Sent: Sunday, May 22, 2016 10:30 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst

btw, we just had similar problem that was entirely explained by vtk writer attempting to gather a bunch of arrays to the root node. Utkarsh found a way to disable that behavior. I wonder if you are hitting the same.

On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:

Well... not going so well.


If I run a small simulation with massif and the Release build of paraview, I don't see any growing memory in time. I also get my VTK files and images.


If I run the same simulation linked against a Debug build with VTK_DEBUG_LEAKS on, there is a segfault inside one of the libvtkRendering libraries (it says libvtkRenderingOp but the rest of the name is cut off). If I take the image rendering out of my pipeline (comment out the RegisterView call) and leave the VTK file writing, it runs fine and doesn't report any leaks. I tried to get the segfault to drop a core file, but it won't do it.


I'm thinking that there is an issue in the rendering part causing the leak. I have no idea what it could be though -- this is the 4.4.0 version, is anybody aware of any bug fixes between 4.4.0 and current versions that might be relevant?


Thanks for the help,


Tim




________________________________
From: ParaView <paraview-bounces at paraview.org><mailto:paraview-bounces at paraview.org> on behalf of Gallagher, Timothy P <tim.gallagher at gatech.edu><mailto:tim.gallagher at gatech.edu>
Sent: Friday, May 20, 2016 4:17 PM
To: Burlen Loring; Andy Bauer
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst


Thanks for the advice Burlen -- I haven't used Massif before, so this is a good opportunity to give it a try.


The initialize/finalize each time approach doesn't work either. I am calling the Finalize() routine on the vtkCPProcessor class but then when it tries to initialize again, it throws:


Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line 50
vtkSocketController (0xa4342f0): Already initialized.


and then crashes. So, hopefully I can sort out the memory leak rather than trying to debug why a hacked fix doesn't work!


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com><mailto:burlen.loring at gmail.com>
Sent: Friday, May 20, 2016 3:46 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst


VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all kinds of leaks. For example you can have leaks where data erroneously accumulates with each time step, but is deleted at program termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's probably better to use massif to profile your code on a small one node run. There's an excellent tool called massif visualizer to aid in exploring the data generated.


$0.02

On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:

Hi Andy,


Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what it turns up.


The initialize/finalize every time is definitely a hack and not for long-term use. But, sponsors want a report on Monday and we need to be able to visualize things for that -- the simulation is too big to write data files and post-process later. So I modified the code to do that for now until I can find a proper fix.


I'll let you know if I get stuck with the log file.


Thanks again,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com><mailto:andy.bauer at kitware.com>
Sent: Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding VTK objects that aren't deleted properly. You should be able to run this with a small amount of calls to Catalyst as well. If you try this and want help understanding the output (if an object like a vtkUnstructuredGrid is leaked it will often give a whole bunch of false leaks that the unstructured grid is just holding the references to), just share your output file and I can take a look at it to try and narrow down the culprit. That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any Catalyst work to see what happens then. That may be a lot of compute cycles but I'm not sure how else to try and bisect where the memory leak is occurring.

Initializing and finalizing Catalyst every time you want output would probably work but I'd think there may be significant overhead doing it like this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at <http://www.kitware.com/opensource/opensource.html> http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: <http://paraview.org/Wiki/ParaView> http://paraview.org/Wiki/ParaView

Search the list archives at: <http://markmail.org/search/?q=ParaView> http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview





_______________________________________________
Powered by www.kitware.com<http://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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/7b3cb529/attachment.html>

From utkarsh.ayachit at kitware.com  Mon May 23 10:06:04 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 10:06:04 -0400
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <5742E8E3.40800@mh-hannover.de>
References: <548070F4.4070508@gmx.net>
	<5742E8E3.40800@mh-hannover.de>
Message-ID: <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>

Roman,

Can you post an example? When I tried the same with a simple sphere
color by "Normals X", it seems to work as expected. I used
"view3dscene" to view the X3d file.

On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
<grothausmann.roman at mh-hannover.de> wrote:
> Dear mailing list members,
>
>
> When I export scenes to X3D then load the mesh into blender or a browser the
> mesh is colour wrong. The colours are there but apparently assigned to
> random cells/vertices. This happens with either PV5 or PV4, especially for
> category colouring. When using e.g. WebGL exporter all is fine.
> Is there anything to do special for exporting to X3D? When I use plain VTK,
> the exported colours seemed OK so far.
>
> Any help or hints are very much appreciated
> Roman
>
>
> On 04/12/14 15:34, Michael Nolde wrote:
>>
>> works perfectly, thank you!
>>
>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>> View is not valid at the point you get it.
>>
>> from paraview.simple import *
>> exporters=servermanager.createModule("exporters")
>> source=Cone()
>> Show()
>> render=Render()
>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>> x3dExporter.SetView(render)
>> x3dExporter.Write()
>>
>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__> wrote:
>> Dear mailing list members,
>>
>> I have some trouble exporting a scene to a X3D file via pvpython.
>> I tried to execute to code found in
>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>> (see below). It is executed without any errors, but no output file is
>> created.
>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>> Could someone give me a hint?
>>
>> Thanks in advance,
>> Michael
>>
>> from paraview.simple import *
>> exporters=servermanager.createModule("exporters")
>> source=Cone()
>> view = GetActiveView()
>> Show(view)
>> render=Render()
>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>> x3dExporter.SetView(view)
>> x3dExporter.Write()
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview__
>>
>>
>>
>>
>>
>
> --
> Dr. Roman Grothausmann
>
> Tomographie und Digitale Bildverarbeitung
> Tomography and Digital Image Analysis
>
> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
> Medizinische Hochschule Hannover
> Carl-Neuberg-Str. 1
> D-30625 Hannover
>
> Tel. +49 511 532-2900
> _______________________________________________
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-05-23 10:04:56.png
Type: image/png
Size: 195595 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/ea61ea42/attachment-0001.png>

From utkarsh.ayachit at kitware.com  Mon May 23 10:10:44 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 10:10:44 -0400
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
Message-ID: <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>

And same with categorical colors. I did notice, however, it fails when
coloring with "Field Data" arrays. Is that what you're seeing? That
I'd expected would fail in VTK too. That's indeed a missing feature in
the exporter.

On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Roman,
>
> Can you post an example? When I tried the same with a simple sphere
> color by "Normals X", it seems to work as expected. I used
> "view3dscene" to view the X3d file.
>
> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
> <grothausmann.roman at mh-hannover.de> wrote:
>> Dear mailing list members,
>>
>>
>> When I export scenes to X3D then load the mesh into blender or a browser the
>> mesh is colour wrong. The colours are there but apparently assigned to
>> random cells/vertices. This happens with either PV5 or PV4, especially for
>> category colouring. When using e.g. WebGL exporter all is fine.
>> Is there anything to do special for exporting to X3D? When I use plain VTK,
>> the exported colours seemed OK so far.
>>
>> Any help or hints are very much appreciated
>> Roman
>>
>>
>> On 04/12/14 15:34, Michael Nolde wrote:
>>>
>>> works perfectly, thank you!
>>>
>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>> View is not valid at the point you get it.
>>>
>>> from paraview.simple import *
>>> exporters=servermanager.createModule("exporters")
>>> source=Cone()
>>> Show()
>>> render=Render()
>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>> x3dExporter.SetView(render)
>>> x3dExporter.Write()
>>>
>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__> wrote:
>>> Dear mailing list members,
>>>
>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>> I tried to execute to code found in
>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>> (see below). It is executed without any errors, but no output file is
>>> created.
>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>>> Could someone give me a hint?
>>>
>>> Thanks in advance,
>>> Michael
>>>
>>> from paraview.simple import *
>>> exporters=servermanager.createModule("exporters")
>>> source=Cone()
>>> view = GetActiveView()
>>> Show(view)
>>> render=Render()
>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>> x3dExporter.SetView(view)
>>> x3dExporter.Write()
>>>
>>>
>>> _______________________________________________
>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Dr. Roman Grothausmann
>>
>> Tomographie und Digitale Bildverarbeitung
>> Tomography and Digital Image Analysis
>>
>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>> Medizinische Hochschule Hannover
>> Carl-Neuberg-Str. 1
>> D-30625 Hannover
>>
>> Tel. +49 511 532-2900
>> _______________________________________________
>> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-05-23 10:09:05.png
Type: image/png
Size: 143337 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/e473bed7/attachment.png>

From utkarsh.ayachit at kitware.com  Mon May 23 11:42:00 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 11:42:00 -0400
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <57431EAD.4010209@mh-hannover.de>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
 <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>
 <57431EAD.4010209@mh-hannover.de>
Message-ID: <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>

Ah okay. Looks like there's another bug with cell-data coloring and
x3d. I've spotted the bug (I think) and am working on a fix. Not sure
how this could have worked in VTK example, however. I'll send you a
patch shortly.

On Mon, May 23, 2016 at 11:15 AM, Grothausmann, Roman Dr.
<grothausmann.roman at mh-hannover.de> wrote:
> Many thanks Utkarsh for Your quick reply.
> Attached is an example VTP (generated by
> https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.pvsm)
> coloured with KAAMS cat. on FacetIds (cell data) and then exported as X3D
> from PV5. The PNG is a comparison view of PV and view3dscene.
> The WebGL output (from make test) is great:
> http://htmlpreview.github.io/?https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.html
>
>
> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>
>> And same with categorical colors. I did notice, however, it fails when
>> coloring with "Field Data" arrays. Is that what you're seeing? That
>> I'd expected would fail in VTK too. That's indeed a missing feature in
>> the exporter.
>>
>> On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>>
>>> Roman,
>>>
>>> Can you post an example? When I tried the same with a simple sphere
>>> color by "Normals X", it seems to work as expected. I used
>>> "view3dscene" to view the X3d file.
>>>
>>> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>
>>>> Dear mailing list members,
>>>>
>>>>
>>>> When I export scenes to X3D then load the mesh into blender or a browser
>>>> the
>>>> mesh is colour wrong. The colours are there but apparently assigned to
>>>> random cells/vertices. This happens with either PV5 or PV4, especially
>>>> for
>>>> category colouring. When using e.g. WebGL exporter all is fine.
>>>> Is there anything to do special for exporting to X3D? When I use plain
>>>> VTK,
>>>> the exported colours seemed OK so far.
>>>>
>>>> Any help or hints are very much appreciated
>>>> Roman
>>>>
>>>>
>>>> On 04/12/14 15:34, Michael Nolde wrote:
>>>>>
>>>>>
>>>>> works perfectly, thank you!
>>>>>
>>>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>>>> View is not valid at the point you get it.
>>>>>
>>>>> from paraview.simple import *
>>>>> exporters=servermanager.createModule("exporters")
>>>>> source=Cone()
>>>>> Show()
>>>>> render=Render()
>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>> x3dExporter.SetView(render)
>>>>> x3dExporter.Write()
>>>>>
>>>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__>
>>>>> wrote:
>>>>> Dear mailing list members,
>>>>>
>>>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>>>> I tried to execute to code found in
>>>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>>>> (see below). It is executed without any errors, but no output file is
>>>>> created.
>>>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>>>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>>>>> Could someone give me a hint?
>>>>>
>>>>> Thanks in advance,
>>>>> Michael
>>>>>
>>>>> from paraview.simple import *
>>>>> exporters=servermanager.createModule("exporters")
>>>>> source=Cone()
>>>>> view = GetActiveView()
>>>>> Show(view)
>>>>> render=Render()
>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>> x3dExporter.SetView(view)
>>>>> x3dExporter.Write()
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Dr. Roman Grothausmann
>>>>
>>>> Tomographie und Digitale Bildverarbeitung
>>>> Tomography and Digital Image Analysis
>>>>
>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>> Medizinische Hochschule Hannover
>>>> Carl-Neuberg-Str. 1
>>>> D-30625 Hannover
>>>>
>>>> Tel. +49 511 532-2900
>>>> _______________________________________________
>>>> 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
>
>
> --
> Dr. Roman Grothausmann
>
> Tomographie und Digitale Bildverarbeitung
> Tomography and Digital Image Analysis
>
> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
> Medizinische Hochschule Hannover
> Carl-Neuberg-Str. 1
> D-30625 Hannover
>
> Tel. +49 511 532-2900

From svenkramer40 at gmail.com  Mon May 23 12:44:22 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Mon, 23 May 2016 18:44:22 +0200
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
 <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
Message-ID: <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>

Sure, I would share the code. But as I said, I haven't done anything more
than wrapping pqCatalystConnectReaction::connect() and hacking several
lines in the python rpc server, which are probably not done right.
If it helps, I can try to reconstruct all the lines I have modified and
clean up the stuff. However, you'll probably find a cleaner solution to
invoke pqCatalystConnectReaction::connect() from the web client.

Sven

2016-05-23 7:22 GMT+02:00 Sebastien Jourdain <sebastien.jourdain at kitware.com
>:

> Glad to ear that you managed to get something going. If you feel like
> sharing your code, we might be able to provide some integration into
> ParaView and/or ParaViewWeb proper.
>
> Seb
>
> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
> wrote:
>
>> Thank you, Seb,
>> it seems like I am getting it to work. There are still some difficulties
>> because of my limited javascript experience, but with some quick&dirty
>> workarounds I do have the Catalyst output displayed from ParaViewWeb. As
>> you said, nothing else was required than wrapping the C functions in python.
>>
>> Thanks
>> Sven
>>
>>
>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
>> sebastien.jourdain at kitware.com>:
>>
>>> Hi Sven,
>>>
>>> I am not aware on any specific developer documentation for Catalyst on
>>> the ParaView side (but I haven't worked on that subject for years),
>>> although Utkarsh or Andy might know.
>>>
>>> Usually looking at the code and redoing it in the Python world is what
>>> is required, but as I said, I'm not sure of what it means since I don't
>>> know that code anymore. ;-)
>>>
>>> For the timeframe, I can't tell (meaning I don't know), but we can still
>>> try to help you or implement the missing piece via support contract if that
>>> make sense on your end.
>>>
>>> Thanks,
>>>
>>> Seb
>>>
>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>>> wrote:
>>>
>>>> Hello Seb,
>>>> glad to read your answer. So the problem is not only that I was unable
>>>> to find the relevant information.
>>>>
>>>> You say, you have not (yet) written the required code. Does "not (yet)"
>>>> mean that it is on the agenda maybe within the next half year? Then I could
>>>> find a workaround and look forward to the next Paraview updates.
>>>>
>>>> Otherwise I would try to work on the implementation for connecting
>>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>>> information? Those would be great to get started.
>>>> My first attempt would be to "wrap" the functionality of
>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>>> make it available to the web client. Or are the necessary steps much more
>>>> involved?
>>>>
>>>> Thank you
>>>> Sven
>>>>
>>>>
>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com>:
>>>>
>>>>> Hi Sven,
>>>>>
>>>>> Live catalyst connection require a specific socket connection to the
>>>>> in-situ process with some special handling.
>>>>> We did not (yet) wrote the Python code to perform that specific action
>>>>> for ParaViewWeb so it could be triggered by the web client or configured
>>>>> via an argument at launch time.
>>>>> I don't see any reason why this couldn't work, but as for now, I also
>>>>> don't know an easy step to do it without spending time doing it myself.
>>>>>
>>>>> Seb
>>>>>
>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>> I am looking for the recommended steps how to display an in-situ
>>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>>
>>>>>> After some efforts I am able to run ParaViewWeb successfully and I
>>>>>> can view a Catalyst-enabled simulation in paraview.
>>>>>>
>>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>>> pvserver as mentioned at the end of
>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ and
>>>>>> giving "--ds-host localhost --ds-port 11111" options to
>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>>> displayed on the web.
>>>>>>
>>>>>> Below you find the (not too detailed) steps I took to have a working
>>>>>> solution for either Catalyst-enabled simulations or a working web
>>>>>> visualizer:
>>>>>>
>>>>>> Test connection from Catalyst simulation to paraview:
>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz
>>>>>> (from http://www.paraview.org/download/)
>>>>>> 2) Choose Catalyst->Connect in paraview
>>>>>> 3) Run CFullExample from
>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>>> Success!
>>>>>>
>>>>>> Test ParaViewWeb:
>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>>> http://www.paraview.org/download/, extract in /data
>>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>>> Success!
>>>>>>
>>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>>
>>>>>> Regards,
>>>>>> Sven
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/b0825106/attachment.html>

From sebastien.jourdain at kitware.com  Mon May 23 12:51:17 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 23 May 2016 10:51:17 -0600
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
 <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
 <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
Message-ID: <CABObKxfAMy6qFzyh94Q2PxaUoY1Wsyr5aGszyBXygeH7e8n9TQ@mail.gmail.com>

Hi Sven,

What you did is what I was planning to do. Maybe cleaner, but that's it. So
the end integration could be slightly different, but the core will be the
same.

On a side note, we will never call a "Qt" code from Python. As we are note
expecting the GUI to be build for ParaViewWeb.

Seb


On Mon, May 23, 2016 at 10:44 AM, Sven Kramer <svenkramer40 at gmail.com>
wrote:

> Sure, I would share the code. But as I said, I haven't done anything more
> than wrapping pqCatalystConnectReaction::connect() and hacking several
> lines in the python rpc server, which are probably not done right.
> If it helps, I can try to reconstruct all the lines I have modified and
> clean up the stuff. However, you'll probably find a cleaner solution to
> invoke pqCatalystConnectReaction::connect() from the web client.
>
> Sven
>
> 2016-05-23 7:22 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Glad to ear that you managed to get something going. If you feel like
>> sharing your code, we might be able to provide some integration into
>> ParaView and/or ParaViewWeb proper.
>>
>> Seb
>>
>> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Thank you, Seb,
>>> it seems like I am getting it to work. There are still some difficulties
>>> because of my limited javascript experience, but with some quick&dirty
>>> workarounds I do have the Catalyst output displayed from ParaViewWeb. As
>>> you said, nothing else was required than wrapping the C functions in python.
>>>
>>> Thanks
>>> Sven
>>>
>>>
>>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com>:
>>>
>>>> Hi Sven,
>>>>
>>>> I am not aware on any specific developer documentation for Catalyst on
>>>> the ParaView side (but I haven't worked on that subject for years),
>>>> although Utkarsh or Andy might know.
>>>>
>>>> Usually looking at the code and redoing it in the Python world is what
>>>> is required, but as I said, I'm not sure of what it means since I don't
>>>> know that code anymore. ;-)
>>>>
>>>> For the timeframe, I can't tell (meaning I don't know), but we can
>>>> still try to help you or implement the missing piece via support contract
>>>> if that make sense on your end.
>>>>
>>>> Thanks,
>>>>
>>>> Seb
>>>>
>>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Seb,
>>>>> glad to read your answer. So the problem is not only that I was unable
>>>>> to find the relevant information.
>>>>>
>>>>> You say, you have not (yet) written the required code. Does "not
>>>>> (yet)" mean that it is on the agenda maybe within the next half year? Then
>>>>> I could find a workaround and look forward to the next Paraview updates.
>>>>>
>>>>> Otherwise I would try to work on the implementation for connecting
>>>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>>>> information? Those would be great to get started.
>>>>> My first attempt would be to "wrap" the functionality of
>>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>>>> make it available to the web client. Or are the necessary steps much more
>>>>> involved?
>>>>>
>>>>> Thank you
>>>>> Sven
>>>>>
>>>>>
>>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com>:
>>>>>
>>>>>> Hi Sven,
>>>>>>
>>>>>> Live catalyst connection require a specific socket connection to the
>>>>>> in-situ process with some special handling.
>>>>>> We did not (yet) wrote the Python code to perform that specific
>>>>>> action for ParaViewWeb so it could be triggered by the web client or
>>>>>> configured via an argument at launch time.
>>>>>> I don't see any reason why this couldn't work, but as for now, I also
>>>>>> don't know an easy step to do it without spending time doing it myself.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>> I am looking for the recommended steps how to display an in-situ
>>>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>>>
>>>>>>> After some efforts I am able to run ParaViewWeb successfully and I
>>>>>>> can view a Catalyst-enabled simulation in paraview.
>>>>>>>
>>>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>>>> pvserver as mentioned at the end of
>>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/
>>>>>>> and giving "--ds-host localhost --ds-port 11111" options to
>>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>>>> displayed on the web.
>>>>>>>
>>>>>>> Below you find the (not too detailed) steps I took to have a working
>>>>>>> solution for either Catalyst-enabled simulations or a working web
>>>>>>> visualizer:
>>>>>>>
>>>>>>> Test connection from Catalyst simulation to paraview:
>>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz
>>>>>>> (from http://www.paraview.org/download/)
>>>>>>> 2) Choose Catalyst->Connect in paraview
>>>>>>> 3) Run CFullExample from
>>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>>>> Success!
>>>>>>>
>>>>>>> Test ParaViewWeb:
>>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>>>> http://www.paraview.org/download/, extract in /data
>>>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>>>> Success!
>>>>>>>
>>>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Sven
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/bcc5aa01/attachment.html>

From utkarsh.ayachit at kitware.com  Mon May 23 13:08:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 13:08:30 -0400
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
 <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>
 <57431EAD.4010209@mh-hannover.de>
 <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>
Message-ID: <CADHSJjDt+S-6FaYb71UA_aHKwX7X9zV8vZPZP4TenSX_Gj38cQ@mail.gmail.com>

Here's a fix for the same:

https://gitlab.kitware.com/vtk/vtk/merge_requests/1517

Utkarsh

On Mon, May 23, 2016 at 11:42 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Ah okay. Looks like there's another bug with cell-data coloring and
> x3d. I've spotted the bug (I think) and am working on a fix. Not sure
> how this could have worked in VTK example, however. I'll send you a
> patch shortly.
>
> On Mon, May 23, 2016 at 11:15 AM, Grothausmann, Roman Dr.
> <grothausmann.roman at mh-hannover.de> wrote:
>> Many thanks Utkarsh for Your quick reply.
>> Attached is an example VTP (generated by
>> https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.pvsm)
>> coloured with KAAMS cat. on FacetIds (cell data) and then exported as X3D
>> from PV5. The PNG is a comparison view of PV and view3dscene.
>> The WebGL output (from make test) is great:
>> http://htmlpreview.github.io/?https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.html
>>
>>
>> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>>
>>> And same with categorical colors. I did notice, however, it fails when
>>> coloring with "Field Data" arrays. Is that what you're seeing? That
>>> I'd expected would fail in VTK too. That's indeed a missing feature in
>>> the exporter.
>>>
>>> On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>
>>>> Roman,
>>>>
>>>> Can you post an example? When I tried the same with a simple sphere
>>>> color by "Normals X", it seems to work as expected. I used
>>>> "view3dscene" to view the X3d file.
>>>>
>>>> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>
>>>>> Dear mailing list members,
>>>>>
>>>>>
>>>>> When I export scenes to X3D then load the mesh into blender or a browser
>>>>> the
>>>>> mesh is colour wrong. The colours are there but apparently assigned to
>>>>> random cells/vertices. This happens with either PV5 or PV4, especially
>>>>> for
>>>>> category colouring. When using e.g. WebGL exporter all is fine.
>>>>> Is there anything to do special for exporting to X3D? When I use plain
>>>>> VTK,
>>>>> the exported colours seemed OK so far.
>>>>>
>>>>> Any help or hints are very much appreciated
>>>>> Roman
>>>>>
>>>>>
>>>>> On 04/12/14 15:34, Michael Nolde wrote:
>>>>>>
>>>>>>
>>>>>> works perfectly, thank you!
>>>>>>
>>>>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>>>>> View is not valid at the point you get it.
>>>>>>
>>>>>> from paraview.simple import *
>>>>>> exporters=servermanager.createModule("exporters")
>>>>>> source=Cone()
>>>>>> Show()
>>>>>> render=Render()
>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>> x3dExporter.SetView(render)
>>>>>> x3dExporter.Write()
>>>>>>
>>>>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__>
>>>>>> wrote:
>>>>>> Dear mailing list members,
>>>>>>
>>>>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>>>>> I tried to execute to code found in
>>>>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>>>>> (see below). It is executed without any errors, but no output file is
>>>>>> created.
>>>>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>>>>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>>>>>> Could someone give me a hint?
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Michael
>>>>>>
>>>>>> from paraview.simple import *
>>>>>> exporters=servermanager.createModule("exporters")
>>>>>> source=Cone()
>>>>>> view = GetActiveView()
>>>>>> Show(view)
>>>>>> render=Render()
>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>> x3dExporter.SetView(view)
>>>>>> x3dExporter.Write()
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Dr. Roman Grothausmann
>>>>>
>>>>> Tomographie und Digitale Bildverarbeitung
>>>>> Tomography and Digital Image Analysis
>>>>>
>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>>> Medizinische Hochschule Hannover
>>>>> Carl-Neuberg-Str. 1
>>>>> D-30625 Hannover
>>>>>
>>>>> Tel. +49 511 532-2900
>>>>> _______________________________________________
>>>>> 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
>>
>>
>> --
>> Dr. Roman Grothausmann
>>
>> Tomographie und Digitale Bildverarbeitung
>> Tomography and Digital Image Analysis
>>
>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>> Medizinische Hochschule Hannover
>> Carl-Neuberg-Str. 1
>> D-30625 Hannover
>>
>> Tel. +49 511 532-2900

From CBaumann at slb.com  Mon May 23 14:40:28 2016
From: CBaumann at slb.com (Carlos Baumann)
Date: Mon, 23 May 2016 18:40:28 +0000
Subject: [Paraview] How to Annotate time steps when using VTK files ?
Message-ID: <32D0A6E400786141A9A2CB170C1CF1EC01DD4723F2@NL0230MBX07N1.DIR.slb.com>

Hello ParaView !

I would like to annotate the actual Time using a series of .vtk files,
However it appears that with .vtk files ParaView is creating the time from the time step number, not from the T####.vtk part of the filename.
I also included  a "TIME" array with one entry as shown in the snapshot below, because Visit uses this data to track the time, but this is not recognized by Paraview.

What can I do to annotate the time based on the filename string suffix T####.vtk, in this case time would be for me in milliseconds,
or to use the data TIME in each time step as shown below  (time in seconds)

Thanks in advance.
Carlos

ParaView Snapshot with all the available data:
[cid:image001.jpg at 01D1B4F8.A9FEEB40]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/646f9c12/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 27457 bytes
Desc: image001.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/646f9c12/attachment.jpg>

From utkarsh.ayachit at kitware.com  Mon May 23 15:28:16 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 23 May 2016 15:28:16 -0400
Subject: [Paraview] How to Annotate time steps when using VTK files ?
In-Reply-To: <32D0A6E400786141A9A2CB170C1CF1EC01DD4723F2@NL0230MBX07N1.DIR.slb.com>
References: <32D0A6E400786141A9A2CB170C1CF1EC01DD4723F2@NL0230MBX07N1.DIR.slb.com>
Message-ID: <CADHSJjBNyFO7gGq=S1CTLyWfuM3JNtbbvJyQxm-6f_Da7_jOGQ@mail.gmail.com>

Try using the "Annotate Global Data" filter instead. You can then choose to
use the value from the field data array TIME.

On Mon, May 23, 2016 at 2:40 PM, Carlos Baumann <CBaumann at slb.com> wrote:

> Hello ParaView !
>
>
>
> I would like to annotate the actual Time using a series of .vtk files,
>
> However it appears that with .vtk files ParaView is creating the time from
> the time step number, not from the T####.vtk part of the filename.
>
> I also included  a ?TIME? array with one entry as shown in the snapshot
> below, because Visit uses this data to track the time, but this is not
> recognized by Paraview.
>
>
>
> What can I do to annotate the time based on the filename string suffix
> T####.vtk, in this case time would be for me in milliseconds,
>
> or to use the data TIME in each time step as shown below  (time in seconds)
>
>
>
> Thanks in advance.
>
> Carlos
>
>
>
> ParaView Snapshot with all the available data:
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/c8d75c31/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 27457 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/c8d75c31/attachment.jpg>

From burlen.loring at gmail.com  Mon May 23 15:30:22 2016
From: burlen.loring at gmail.com (Burlen Loring)
Date: Mon, 23 May 2016 12:30:22 -0700
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB2627F93DC800BA34D03EF05F9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <57426B53.2060700@gmail.com>
 <BN3PR07MB2627F93DC800BA34D03EF05F9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <037583dd-c272-2556-af65-d2b1965fceaf@gmail.com>

I think there is an api in the multi-block writer to disable writing 
metadata. Utkarsh knows, he's the one that figured it out. not sure how 
it applies to your use case. you may not even be using multi-block format...


On 05/23/2016 06:57 AM, Gallagher, Timothy P wrote:
>
> Interesting -- I'd be willing to try it out if you have more details 
> (commit hashtag, ticket, etc.), even if I have to figure out how to 
> backport it from a newer version.
>
>
> Thanks,
>
>
> Tim
>
>
>
> ------------------------------------------------------------------------
> *From:* Burlen Loring <burlen.loring at gmail.com>
> *Sent:* Sunday, May 22, 2016 10:30 PM
> *To:* Gallagher, Timothy P; Andy Bauer
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Memory leak with Catalyst
> btw, we just had similar problem that was entirely explained by vtk 
> writer attempting to gather a bunch of arrays to the root node. 
> Utkarsh found a way to disable that behavior. I wonder if you are 
> hitting the same.
>
> On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:
>>
>> Well... not going so well.
>>
>>
>> If I run a small simulation with massif and the Release build of 
>> paraview, I don't see any growing memory in time. I also get my VTK 
>> files and images.
>>
>>
>> If I run the same simulation linked against a Debug build with 
>> VTK_DEBUG_LEAKS on, there is a segfault inside one of the 
>> libvtkRendering libraries (it says libvtkRenderingOp but the rest of 
>> the name is cut off). If I take the image rendering out of my 
>> pipeline (comment out the RegisterView call) and leave the VTK file 
>> writing, it runs fine and doesn't report any leaks. I tried to get 
>> the segfault to drop a core file, but it won't do it.
>>
>>
>> I'm thinking that there is an issue in the rendering part causing the 
>> leak. I have no idea what it could be though -- this is the 4.4.0 
>> version, is anybody aware of any bug fixes between 4.4.0 and current 
>> versions that might be relevant?
>>
>>
>> Thanks for the help,
>>
>>
>> Tim
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>> *From:* ParaView <paraview-bounces at paraview.org> on behalf of 
>> Gallagher, Timothy P <tim.gallagher at gatech.edu>
>> *Sent:* Friday, May 20, 2016 4:17 PM
>> *To:* Burlen Loring; Andy Bauer
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Memory leak with Catalyst
>>
>> Thanks for the advice Burlen -- I haven't used Massif before, so this 
>> is a good opportunity to give it a try.
>>
>>
>> The initialize/finalize each time approach doesn't work either. I am 
>> calling the Finalize() routine on the vtkCPProcessor class but then 
>> when it tries to initialize again, it throws:
>>
>>
>> Warning: In 
>> /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line 50
>> vtkSocketController (0xa4342f0): Already initialized.
>>
>>
>> and then crashes. So, hopefully I can sort out the memory leak rather 
>> than trying to debug why a hacked fix doesn't work!
>>
>>
>> Tim
>>
>>
>>
>> ------------------------------------------------------------------------
>> *From:* Burlen Loring <burlen.loring at gmail.com>
>> *Sent:* Friday, May 20, 2016 3:46 PM
>> *To:* Gallagher, Timothy P; Andy Bauer
>> *Cc:* paraview at paraview.org
>> *Subject:* Re: [Paraview] Memory leak with Catalyst
>>
>> VTK_DEBUG_LEAKS, although will catch some serious errors, will not 
>> catch all kinds of leaks. For example you can have leaks where data 
>> erroneously accumulates with each time step, but is deleted at 
>> program termination. VTK_DEBUG_LEAKS will not catch that kind of 
>> error. It's probably better to use massif to profile your code on a 
>> small one node run. There's an excellent tool called massif 
>> visualizer to aid in exploring the data generated.
>>
>>
>> $0.02
>>
>>
>> On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:
>>>
>>> Hi Andy,
>>>
>>>
>>> Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now 
>>> and see what it turns up.
>>>
>>>
>>> The initialize/finalize every time is definitely a hack and not for 
>>> long-term use. But, sponsors want a report on Monday and we need to 
>>> be able to visualize things for that -- the simulation is too big to 
>>> write data files and post-process later. So I modified the code to 
>>> do that for now until I can find a proper fix.
>>>
>>>
>>> I'll let you know if I get stuck with the log file.
>>>
>>>
>>> Thanks again,
>>>
>>>
>>> Tim
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>> *From:* Andy Bauer <andy.bauer at kitware.com>
>>> *Sent:* Friday, May 20, 2016 2:39 PM
>>> *To:* Gallagher, Timothy P
>>> *Cc:* paraview at paraview.org
>>> *Subject:* Re: [Paraview] Memory leak with Catalyst
>>> Hi Tim,
>>>
>>> If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good 
>>> at finding VTK objects that aren't deleted properly. You should be 
>>> able to run this with a small amount of calls to Catalyst as well. 
>>> If you try this and want help understanding the output (if an object 
>>> like a vtkUnstructuredGrid is leaked it will often give a whole 
>>> bunch of false leaks that the unstructured grid is just holding the 
>>> references to), just share your output file and I can take a look at 
>>> it to try and narrow down the culprit. That may be slightly easier 
>>> to use than Valgrind.
>>>
>>> Beyond this, you could maybe try the same run but without doing any 
>>> Catalyst work to see what happens then. That may be a lot of compute 
>>> cycles but I'm not sure how else to try and bisect where the memory 
>>> leak is occurring.
>>>
>>> Initializing and finalizing Catalyst every time you want output 
>>> would probably work but I'd think there may be significant overhead 
>>> doing it like this. Plus, it's not really solving the problem -- 
>>> just avoiding it.
>>>
>>> Best,
>>> Andy
>>>
>>>
>>> On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P 
>>> <tim.gallagher at gatech.edu <mailto:tim.gallagher at gatech.edu>> wrote:
>>>
>>>     Hi,
>>>
>>>
>>>     One of our users is running a very big simulation and writing
>>>     out images of two slices (two different views) every 1000
>>>     iterations and writing out the data for the two slices (two
>>>     different data writers) as VTK files every 5000 iterations. It
>>>     is using Paraview 4.4.
>>>
>>>
>>>     After 21000 iterations, the simulation is killed because the
>>>     memory on the compute nodes fills up. I usually know how to
>>>     track down memory problems in our code using valgrind and
>>>     related tools, but is that the right way to go to try and find
>>>     this problem?
>>>
>>>
>>>     Are there any tips on how to isolate where the problem may be? I
>>>     don't know if it is in the adapter, or in paraview itself. Has
>>>     anybody encountered problems with runaway memory using Catalyst
>>>     in 4.4 when writing images or VTK files?
>>>
>>>
>>>     I know when we use pvpython to generate images and loop over
>>>     many files, sometimes the memory also blows up and so we usually
>>>     move the loop over the files outside the pvpython script and
>>>     into a driver script that executes a new pvpython for each file.
>>>     Is there a way to shut down/start up Catalyst each time it needs
>>>     to write something? Is that advisable?
>>>
>>>
>>>     Thanks,
>>>
>>>
>>>     Tim
>>>
>>>
>>>     _______________________________________________
>>>     Powered by www.kitware.com <http://www.kitware.com>
>>>
>>>     Visit other Kitware open-source projects at
>>>     <http://www.kitware.com/opensource/opensource.html>http://www.kitware.com/opensource/opensource.html
>>>
>>>     Please keep messages on-topic and check the ParaView Wiki at:
>>>     <http://paraview.org/Wiki/ParaView>http://paraview.org/Wiki/ParaView
>>>
>>>     Search the list archives at:
>>>     <http://markmail.org/search/?q=ParaView>http://markmail.org/search/?q=ParaView
>>>
>>>     Follow this link to subscribe/unsubscribe:
>>>     http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered bywww.kitware.com
>>>
>>> Visit other Kitware open-source projects athttp://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
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/e92cb149/attachment.html>

From tim.gallagher at gatech.edu  Mon May 23 16:13:36 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 23 May 2016 20:13:36 +0000
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <037583dd-c272-2556-af65-d2b1965fceaf@gmail.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <57426B53.2060700@gmail.com>
 <BN3PR07MB2627F93DC800BA34D03EF05F9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>,
 <037583dd-c272-2556-af65-d2b1965fceaf@gmail.com>
Message-ID: <BN3PR07MB2627B84D2EBE88BA3E96CEEB9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>

I am using the multiblock format, so I am definitely interested in the solution. Hopefully Utkarsh sees this and can chime in.


Thanks!


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com>
Sent: Monday, May 23, 2016 3:30 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst


I think there is an api in the multi-block writer to disable writing metadata. Utkarsh knows, he's the one that figured it out. not sure how it applies to your use case. you may not even be using multi-block format...

On 05/23/2016 06:57 AM, Gallagher, Timothy P wrote:

Interesting -- I'd be willing to try it out if you have more details (commit hashtag, ticket, etc.), even if I have to figure out how to backport it from a newer version.


Thanks,


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com><mailto:burlen.loring at gmail.com>
Sent: Sunday, May 22, 2016 10:30 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst

btw, we just had similar problem that was entirely explained by vtk writer attempting to gather a bunch of arrays to the root node. Utkarsh found a way to disable that behavior. I wonder if you are hitting the same.

On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:

Well... not going so well.


If I run a small simulation with massif and the Release build of paraview, I don't see any growing memory in time. I also get my VTK files and images.


If I run the same simulation linked against a Debug build with VTK_DEBUG_LEAKS on, there is a segfault inside one of the libvtkRendering libraries (it says libvtkRenderingOp but the rest of the name is cut off). If I take the image rendering out of my pipeline (comment out the RegisterView call) and leave the VTK file writing, it runs fine and doesn't report any leaks. I tried to get the segfault to drop a core file, but it won't do it.


I'm thinking that there is an issue in the rendering part causing the leak. I have no idea what it could be though -- this is the 4.4.0 version, is anybody aware of any bug fixes between 4.4.0 and current versions that might be relevant?


Thanks for the help,


Tim




________________________________
From: ParaView <paraview-bounces at paraview.org><mailto:paraview-bounces at paraview.org> on behalf of Gallagher, Timothy P <tim.gallagher at gatech.edu><mailto:tim.gallagher at gatech.edu>
Sent: Friday, May 20, 2016 4:17 PM
To: Burlen Loring; Andy Bauer
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst


Thanks for the advice Burlen -- I haven't used Massif before, so this is a good opportunity to give it a try.


The initialize/finalize each time approach doesn't work either. I am calling the Finalize() routine on the vtkCPProcessor class but then when it tries to initialize again, it throws:


Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line 50
vtkSocketController (0xa4342f0): Already initialized.


and then crashes. So, hopefully I can sort out the memory leak rather than trying to debug why a hacked fix doesn't work!


Tim


________________________________
From: Burlen Loring <burlen.loring at gmail.com><mailto:burlen.loring at gmail.com>
Sent: Friday, May 20, 2016 3:46 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst


VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all kinds of leaks. For example you can have leaks where data erroneously accumulates with each time step, but is deleted at program termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's probably better to use massif to profile your code on a small one node run. There's an excellent tool called massif visualizer to aid in exploring the data generated.


$0.02

On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:

Hi Andy,


Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what it turns up.


The initialize/finalize every time is definitely a hack and not for long-term use. But, sponsors want a report on Monday and we need to be able to visualize things for that -- the simulation is too big to write data files and post-process later. So I modified the code to do that for now until I can find a proper fix.


I'll let you know if I get stuck with the log file.


Thanks again,


Tim


________________________________
From: Andy Bauer <andy.bauer at kitware.com><mailto:andy.bauer at kitware.com>
Sent: Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: <mailto:paraview at paraview.org> paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Memory leak with Catalyst

Hi Tim,

If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding VTK objects that aren't deleted properly. You should be able to run this with a small amount of calls to Catalyst as well. If you try this and want help understanding the output (if an object like a vtkUnstructuredGrid is leaked it will often give a whole bunch of false leaks that the unstructured grid is just holding the references to), just share your output file and I can take a look at it to try and narrow down the culprit. That may be slightly easier to use than Valgrind.

Beyond this, you could maybe try the same run but without doing any Catalyst work to see what happens then. That may be a lot of compute cycles but I'm not sure how else to try and bisect where the memory leak is occurring.

Initializing and finalizing Catalyst every time you want output would probably work but I'd think there may be significant overhead doing it like this. Plus, it's not really solving the problem -- just avoiding it.

Best,
Andy


On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P <tim.gallagher at gatech.edu<mailto:tim.gallagher at gatech.edu>> wrote:

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim

_______________________________________________
Powered by <http://www.kitware.com> www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at <http://www.kitware.com/opensource/opensource.html> http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: <http://paraview.org/Wiki/ParaView> http://paraview.org/Wiki/ParaView

Search the list archives at: <http://markmail.org/search/?q=ParaView> http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview





_______________________________________________
Powered by www.kitware.com<http://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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/a408d64c/attachment.html>

From CBaumann at slb.com  Mon May 23 16:13:39 2016
From: CBaumann at slb.com (Carlos Baumann)
Date: Mon, 23 May 2016 20:13:39 +0000
Subject: [Paraview] Thanks ! => RE: [Ext] Re: How to Annotate time steps
 when using VTK files ?
Message-ID: <32D0A6E400786141A9A2CB170C1CF1EC01DD47243C@NL0230MBX07N1.DIR.slb.com>

Utkarsh,

Thanks a lot, this is exactly what I needed !

Regards,
Carlos

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Monday, May 23, 2016 2:28 PM
To: Carlos Baumann <CBaumann at slb.com>
Cc: paraview at paraview.org
Subject: [Ext] Re: [Paraview] How to Annotate time steps when using VTK files ?

Try using the "Annotate Global Data" filter instead. You can then choose to use the value from the field data array TIME.

On Mon, May 23, 2016 at 2:40 PM, Carlos Baumann <CBaumann at slb.com<mailto:CBaumann at slb.com>> wrote:
Hello ParaView !

I would like to annotate the actual Time using a series of .vtk files,
However it appears that with .vtk files ParaView is creating the time from the time step number, not from the T####.vtk part of the filename.
I also included  a ?TIME? array with one entry as shown in the snapshot below, because Visit uses this data to track the time, but this is not recognized by Paraview.

What can I do to annotate the time based on the filename string suffix T####.vtk, in this case time would be for me in milliseconds,
or to use the data TIME in each time step as shown below  (time in seconds)

Thanks in advance.
Carlos

ParaView Snapshot with all the available data:
[cid:image001.jpg at 01D1B505.AE8CEBF0]


_______________________________________________
Powered by www.kitware.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=CwMFaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=QWWPsaveDbm9Z1Al2MxeLA&m=TDtMLKa7oYug7veLpYJCvV5Ifuw0NWvno_LSSAlKmsE&s=HNcuw1c3GZzDlW_Dn6ifa3Q1AKJ7onmcS7KJMP97Ims&e=>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=CwMFaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=QWWPsaveDbm9Z1Al2MxeLA&m=TDtMLKa7oYug7veLpYJCvV5Ifuw0NWvno_LSSAlKmsE&s=NtDFOhHI2jokpXFSidJRXH1d4eOtrhrIJEvd-rbD5XE&e=>

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=CwMFaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=QWWPsaveDbm9Z1Al2MxeLA&m=TDtMLKa7oYug7veLpYJCvV5Ifuw0NWvno_LSSAlKmsE&s=m1uIYMl4Lt9wtNNLxPqdG3g73RHBiun-Qxr75Idzt0E&e=>

Search the list archives at: http://markmail.org/search/?q=ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=CwMFaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=QWWPsaveDbm9Z1Al2MxeLA&m=TDtMLKa7oYug7veLpYJCvV5Ifuw0NWvno_LSSAlKmsE&s=UDeU4WCt09zFmNlBAVEMR48zzsNMGqR_u8xllB3DYSY&e=>

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview<https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=CwMFaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=QWWPsaveDbm9Z1Al2MxeLA&m=TDtMLKa7oYug7veLpYJCvV5Ifuw0NWvno_LSSAlKmsE&s=pqswTIxanc-_0289PaEJWRi6R0O2lB55spLIPCp0lUY&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/6a60cb21/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 27457 bytes
Desc: image001.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160523/6a60cb21/attachment.jpg>

From thomas.faribault-menard at mail.mcgill.ca  Mon May 23 22:19:50 2016
From: thomas.faribault-menard at mail.mcgill.ca (=?iso-8859-1?Q?Thomas_Faribault-M=E9nard?=)
Date: Tue, 24 May 2016 02:19:50 +0000
Subject: [Paraview] Programmable filter - script for mean of two input
	PointSources
Message-ID: <CY1PR03MB213801685E6D927BF70DB1349D4F0@CY1PR03MB2138.namprd03.prod.outlook.com>

Hi,

I'm a beginner in ParaView. I have two Point Source as my inputs. My output is a third point source that has to be located at the mean of the coordinates of my inputs.

I would prefer the solution to be in the form of a programmable python filter but I need a little help.

Could you point me in the right direction please ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160524/6ef65d8c/attachment.html>

From wollherr at geophysik.uni-muenchen.de  Tue May 24 03:36:24 2016
From: wollherr at geophysik.uni-muenchen.de (Stephanie Wollherr)
Date: Tue, 24 May 2016 09:36:24 +0200
Subject: [Paraview] using contour plot with xdmf input
In-Reply-To: <57440005.5080106@geophysik.uni-muenchen.de>
References: <57440005.5080106@geophysik.uni-muenchen.de>
Message-ID: <57440478.9030308@geophysik.uni-muenchen.de>


Hi all,


I'm using a xdmf input file to visualize my data output from a
simulation. Before, the output format was vtk. I could easily do contour
plots using
CellDataToPointData and than apply the Contour button.
However with the xdmf format this is no longer possible.
There is no error but it just does not display anything.

I came across this
https://cmake.org/pipermail/paraview/2015-December/035852.html
where another user run into this problem, but it seems that there was no
answer on this.

I was wondering if there is already a solution or if someone can help me
with this?
Thank you already in advance!

Stephanie

ps:
I'm using paraview 4.3 on linux.
My xdmf file looks like that:
<?xml version="1.0" ?>
<!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
<Xdmf Version="2.0">
 <Domain>
  <Topology TopologyType="Triangle" NumberOfElements="147104">
   <DataItem NumberType="Int" Precision="8" Format="HDF"
Dimensions="147104 3">data-fault.h5:/connect</DataItem>
  </Topology>
  <Geometry name="geo" GeometryType="XYZ" NumberOfElements="441312">
   <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="441312 3">data-fault.h5:/geometry</DataItem>
  </Geometry>
  <DataItem NumberType="UInt" Precision="4" Format="HDF"
Dimensions="147104">data-fault.h5:/partition</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/SRs</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/SRd</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/T_s</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/T_d</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/P_n</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/u_n</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Ts0</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Td0</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Pn0</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Sls</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Sld</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/Vr</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/ASl</DataItem>
  <DataItem NumberType="Float" Precision="8" Format="HDF"
Dimensions="         133 147104">data-fault.h5:/PSR</DataItem>
  <Grid Name="TimeSeries" GridType="Collection" CollectionType="Temporal">
   <Grid Name="step_000000000000" GridType="Uniform">
    <Topology Reference="/Xdmf/Domain/Topology[1]"/>
    <Geometry Reference="/Xdmf/Domain/Geometry[1]"/>
    <Time Value="0.000608937"/>
    <Attribute Name="partition" Center="Cell">
     <DataItem Reference="/Xdmf/Domain/DataItem[1]" Dimensions="147104"/>
    </Attribute>
    <Attribute Name="SRs" Center="Cell">
     <DataItem ItemType="HyperSlab" Dimensions="147104">
      <DataItem NumberType="UInt" Precision="8" Format="XML"
Dimensions="3 2">0 0 1 1 1 147104</DataItem>
      <DataItem Reference="/Xdmf/Domain/DataItem[2]"/>
     </DataItem>
    </Attribute>
    <Attribute Name="SRd" Center="Cell">
     <DataItem ItemType="HyperSlab" Dimensions="147104">
      <DataItem NumberType="UInt" Precision="8" Format="XML"
Dimensions="3 2">0 0 1 1 1 147104</DataItem>
      <DataItem Reference="/Xdmf/Domain/DataItem[3]"/>
     </DataItem>
    </Attribute>
    <Attribute Name="T_s" Center="Cell">
     <DataItem ItemType="HyperSlab" Dimensions="147104">
      <DataItem NumberType="UInt" Precision="8" Format="XML"
Dimensions="3 2">0 0 1 1 1 147104</DataItem>
      <DataItem Reference="/Xdmf/Domain/DataItem[4]"/>
     </DataItem>
    </Attribute>
.......





From grothausmann.roman at mh-hannover.de  Tue May 24 08:52:27 2016
From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.)
Date: Tue, 24 May 2016 14:52:27 +0200
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <CADHSJjDt+S-6FaYb71UA_aHKwX7X9zV8vZPZP4TenSX_Gj38cQ@mail.gmail.com>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
 <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>
 <57431EAD.4010209@mh-hannover.de>
 <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>
 <CADHSJjDt+S-6FaYb71UA_aHKwX7X9zV8vZPZP4TenSX_Gj38cQ@mail.gmail.com>
Message-ID: <57444E8B.1070805@mh-hannover.de>

Many, many thanks Utkarsh for that quick fix!
Yes, You are right, my VTK test was using point data, so the problem didn't appear.
Thanks again for the great support.

On 23/05/16 19:08, Utkarsh Ayachit wrote:
> Here's a fix for the same:
>
> https://gitlab.kitware.com/vtk/vtk/merge_requests/1517
>
> Utkarsh
>
> On Mon, May 23, 2016 at 11:42 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Ah okay. Looks like there's another bug with cell-data coloring and
>> x3d. I've spotted the bug (I think) and am working on a fix. Not sure
>> how this could have worked in VTK example, however. I'll send you a
>> patch shortly.
>>
>> On Mon, May 23, 2016 at 11:15 AM, Grothausmann, Roman Dr.
>> <grothausmann.roman at mh-hannover.de> wrote:
>>> Many thanks Utkarsh for Your quick reply.
>>> Attached is an example VTP (generated by
>>> https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.pvsm)
>>> coloured with KAAMS cat. on FacetIds (cell data) and then exported as X3D
>>> from PV5. The PNG is a comparison view of PV and view3dscene.
>>> The WebGL output (from make test) is great:
>>> http://htmlpreview.github.io/?https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.html
>>>
>>>
>>> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>>>
>>>> And same with categorical colors. I did notice, however, it fails when
>>>> coloring with "Field Data" arrays. Is that what you're seeing? That
>>>> I'd expected would fail in VTK too. That's indeed a missing feature in
>>>> the exporter.
>>>>
>>>> On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>
>>>>> Roman,
>>>>>
>>>>> Can you post an example? When I tried the same with a simple sphere
>>>>> color by "Normals X", it seems to work as expected. I used
>>>>> "view3dscene" to view the X3d file.
>>>>>
>>>>> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
>>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>>
>>>>>> Dear mailing list members,
>>>>>>
>>>>>>
>>>>>> When I export scenes to X3D then load the mesh into blender or a browser
>>>>>> the
>>>>>> mesh is colour wrong. The colours are there but apparently assigned to
>>>>>> random cells/vertices. This happens with either PV5 or PV4, especially
>>>>>> for
>>>>>> category colouring. When using e.g. WebGL exporter all is fine.
>>>>>> Is there anything to do special for exporting to X3D? When I use plain
>>>>>> VTK,
>>>>>> the exported colours seemed OK so far.
>>>>>>
>>>>>> Any help or hints are very much appreciated
>>>>>> Roman
>>>>>>
>>>>>>
>>>>>> On 04/12/14 15:34, Michael Nolde wrote:
>>>>>>>
>>>>>>>
>>>>>>> works perfectly, thank you!
>>>>>>>
>>>>>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>>>>>> View is not valid at the point you get it.
>>>>>>>
>>>>>>> from paraview.simple import *
>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>> source=Cone()
>>>>>>> Show()
>>>>>>> render=Render()
>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>> x3dExporter.SetView(render)
>>>>>>> x3dExporter.Write()
>>>>>>>
>>>>>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__>
>>>>>>> wrote:
>>>>>>> Dear mailing list members,
>>>>>>>
>>>>>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>>>>>> I tried to execute to code found in
>>>>>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>>>>>> (see below). It is executed without any errors, but no output file is
>>>>>>> created.
>>>>>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>>>>>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>>>>>>> Could someone give me a hint?
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>> Michael
>>>>>>>
>>>>>>> from paraview.simple import *
>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>> source=Cone()
>>>>>>> view = GetActiveView()
>>>>>>> Show(view)
>>>>>>> render=Render()
>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>> x3dExporter.SetView(view)
>>>>>>> x3dExporter.Write()
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Dr. Roman Grothausmann
>>>>>>
>>>>>> Tomographie und Digitale Bildverarbeitung
>>>>>> Tomography and Digital Image Analysis
>>>>>>
>>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>>>> Medizinische Hochschule Hannover
>>>>>> Carl-Neuberg-Str. 1
>>>>>> D-30625 Hannover
>>>>>>
>>>>>> Tel. +49 511 532-2900
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>>
>>> --
>>> Dr. Roman Grothausmann
>>>
>>> Tomographie und Digitale Bildverarbeitung
>>> Tomography and Digital Image Analysis
>>>
>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>> Medizinische Hochschule Hannover
>>> Carl-Neuberg-Str. 1
>>> D-30625 Hannover
>>>
>>> Tel. +49 511 532-2900

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-2900

From utkarsh.ayachit at kitware.com  Tue May 24 09:16:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 24 May 2016 09:16:42 -0400
Subject: [Paraview] Programmable filter - script for mean of two input
	PointSources
In-Reply-To: <CY1PR03MB213801685E6D927BF70DB1349D4F0@CY1PR03MB2138.namprd03.prod.outlook.com>
References: <CY1PR03MB213801685E6D927BF70DB1349D4F0@CY1PR03MB2138.namprd03.prod.outlook.com>
Message-ID: <CADHSJjBwu1igu6gU+RJ2jiuPSuNOgEC1OMnC004ek7ZxKRXUxA@mail.gmail.com>

Here's a simple trick:

1. Select both point sources in pipeline browser and then create the
"Python Calculator".
2. Use the expression "(inputs[0].Points + inputs[1].Points)/2.0", and
hit "Apply"
3. Next, create the "Calculator" filter connect to the "Python
Calculator" with expression "result" and also check the "Coordinate
Results" checkbox. Hit "Apply".

That should do it.

Example state file attached.



On Mon, May 23, 2016 at 10:19 PM, Thomas Faribault-M?nard
<thomas.faribault-menard at mail.mcgill.ca> wrote:
> Hi,
>
> I?m a beginner in ParaView. I have two Point Source as my inputs. My output
> is a third point source that has to be located at the mean of the
> coordinates of my inputs.
>
> I would prefer the solution to be in the form of a programmable python
> filter but I need a little help.
>
> Could you point me in the right direction please ?
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: meanpoints.pvsm
Type: application/octet-stream
Size: 185653 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160524/91ea2eed/attachment-0001.obj>

From utkarsh.ayachit at kitware.com  Tue May 24 09:18:14 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 24 May 2016 09:18:14 -0400
Subject: [Paraview] using contour plot with xdmf input
In-Reply-To: <57440478.9030308@geophysik.uni-muenchen.de>
References: <57440005.5080106@geophysik.uni-muenchen.de>
 <57440478.9030308@geophysik.uni-muenchen.de>
Message-ID: <CADHSJjB=S=Zyt094cgqa2eY0w_XsMDN2AwYato++eazmK9ehJA@mail.gmail.com>

Stephanie,

Is it possible to share the full dataset to reproduce this issue? That
will make things easier.

Thanks,
Ukarsh

On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
<wollherr at geophysik.uni-muenchen.de> wrote:
>
> Hi all,
>
>
> I'm using a xdmf input file to visualize my data output from a
> simulation. Before, the output format was vtk. I could easily do contour
> plots using
> CellDataToPointData and than apply the Contour button.
> However with the xdmf format this is no longer possible.
> There is no error but it just does not display anything.
>
> I came across this
> https://cmake.org/pipermail/paraview/2015-December/035852.html
> where another user run into this problem, but it seems that there was no
> answer on this.
>
> I was wondering if there is already a solution or if someone can help me
> with this?
> Thank you already in advance!
>
> Stephanie
>
> ps:
> I'm using paraview 4.3 on linux.
> My xdmf file looks like that:
> <?xml version="1.0" ?>
> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
> <Xdmf Version="2.0">
>  <Domain>
>   <Topology TopologyType="Triangle" NumberOfElements="147104">
>    <DataItem NumberType="Int" Precision="8" Format="HDF"
> Dimensions="147104 3">data-fault.h5:/connect</DataItem>
>   </Topology>
>   <Geometry name="geo" GeometryType="XYZ" NumberOfElements="441312">
>    <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="441312 3">data-fault.h5:/geometry</DataItem>
>   </Geometry>
>   <DataItem NumberType="UInt" Precision="4" Format="HDF"
> Dimensions="147104">data-fault.h5:/partition</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/SRs</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/SRd</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/T_s</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/T_d</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/P_n</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/u_n</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Ts0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Td0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Pn0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Sls</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Sld</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Vr</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/ASl</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/PSR</DataItem>
>   <Grid Name="TimeSeries" GridType="Collection" CollectionType="Temporal">
>    <Grid Name="step_000000000000" GridType="Uniform">
>     <Topology Reference="/Xdmf/Domain/Topology[1]"/>
>     <Geometry Reference="/Xdmf/Domain/Geometry[1]"/>
>     <Time Value="0.000608937"/>
>     <Attribute Name="partition" Center="Cell">
>      <DataItem Reference="/Xdmf/Domain/DataItem[1]" Dimensions="147104"/>
>     </Attribute>
>     <Attribute Name="SRs" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[2]"/>
>      </DataItem>
>     </Attribute>
>     <Attribute Name="SRd" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[3]"/>
>      </DataItem>
>     </Attribute>
>     <Attribute Name="T_s" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[4]"/>
>      </DataItem>
>     </Attribute>
> .......
>
>
>
>
> _______________________________________________
> 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

From utkarsh.ayachit at kitware.com  Tue May 24 13:33:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 24 May 2016 13:33:53 -0400
Subject: [Paraview] using contour plot with xdmf input
In-Reply-To: <57440478.9030308@geophysik.uni-muenchen.de>
References: <57440005.5080106@geophysik.uni-muenchen.de>
 <57440478.9030308@geophysik.uni-muenchen.de>
Message-ID: <CADHSJjDQ0PrUvWTtU2MqND_9JzHjoW13ptzfZT_6NKKrNnA8rg@mail.gmail.com>

Stephanie,

This is indeed weird, looks like I can apply the Contour filter but it
doesn't produce any output. Did you say you were writing out VTK files
before and it used to work then? Can you also share the VTK file that
was working?

Thanks
Utkarsh

On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
<wollherr at geophysik.uni-muenchen.de> wrote:
>
> Hi all,
>
>
> I'm using a xdmf input file to visualize my data output from a
> simulation. Before, the output format was vtk. I could easily do contour
> plots using
> CellDataToPointData and than apply the Contour button.
> However with the xdmf format this is no longer possible.
> There is no error but it just does not display anything.
>
> I came across this
> https://cmake.org/pipermail/paraview/2015-December/035852.html
> where another user run into this problem, but it seems that there was no
> answer on this.
>
> I was wondering if there is already a solution or if someone can help me
> with this?
> Thank you already in advance!
>
> Stephanie
>
> ps:
> I'm using paraview 4.3 on linux.
> My xdmf file looks like that:
> <?xml version="1.0" ?>
> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
> <Xdmf Version="2.0">
>  <Domain>
>   <Topology TopologyType="Triangle" NumberOfElements="147104">
>    <DataItem NumberType="Int" Precision="8" Format="HDF"
> Dimensions="147104 3">data-fault.h5:/connect</DataItem>
>   </Topology>
>   <Geometry name="geo" GeometryType="XYZ" NumberOfElements="441312">
>    <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="441312 3">data-fault.h5:/geometry</DataItem>
>   </Geometry>
>   <DataItem NumberType="UInt" Precision="4" Format="HDF"
> Dimensions="147104">data-fault.h5:/partition</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/SRs</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/SRd</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/T_s</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/T_d</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/P_n</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/u_n</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Ts0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Td0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Pn0</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Sls</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Sld</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/Vr</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/ASl</DataItem>
>   <DataItem NumberType="Float" Precision="8" Format="HDF"
> Dimensions="         133 147104">data-fault.h5:/PSR</DataItem>
>   <Grid Name="TimeSeries" GridType="Collection" CollectionType="Temporal">
>    <Grid Name="step_000000000000" GridType="Uniform">
>     <Topology Reference="/Xdmf/Domain/Topology[1]"/>
>     <Geometry Reference="/Xdmf/Domain/Geometry[1]"/>
>     <Time Value="0.000608937"/>
>     <Attribute Name="partition" Center="Cell">
>      <DataItem Reference="/Xdmf/Domain/DataItem[1]" Dimensions="147104"/>
>     </Attribute>
>     <Attribute Name="SRs" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[2]"/>
>      </DataItem>
>     </Attribute>
>     <Attribute Name="SRd" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[3]"/>
>      </DataItem>
>     </Attribute>
>     <Attribute Name="T_s" Center="Cell">
>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>       <DataItem NumberType="UInt" Precision="8" Format="XML"
> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>       <DataItem Reference="/Xdmf/Domain/DataItem[4]"/>
>      </DataItem>
>     </Attribute>
> .......
>
>
>
>
> _______________________________________________
> 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

From utkarsh.ayachit at kitware.com  Tue May 24 17:25:06 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 24 May 2016 17:25:06 -0400
Subject: [Paraview] Memory leak with Catalyst
In-Reply-To: <BN3PR07MB2627B84D2EBE88BA3E96CEEB9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>
References: <BN3PR07MB262760F2E2ADAA4B8A3A132A9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <CAMaOp+HnbA4kW0Xx8QBr5tXfj9t2gNXHO4erg9rMq1wEYXXJWw@mail.gmail.com>
 <BN3PR07MB26277FD855CE401B78A5807D9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <d39f9b34-7f98-6cba-7fcb-f272ad0f5f36@gmail.com>
 <BN3PR07MB2627C1BD71C3772434B7E5BD9D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <BN3PR07MB2627F2820BAB540B8488B8239D4B0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <57426B53.2060700@gmail.com>
 <BN3PR07MB2627F93DC800BA34D03EF05F9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>
 <037583dd-c272-2556-af65-d2b1965fceaf@gmail.com>
 <BN3PR07MB2627B84D2EBE88BA3E96CEEB9D4E0@BN3PR07MB2627.namprd07.prod.outlook.com>
Message-ID: <CADHSJjBj9Hmc4jiwPyWv5xsEt8dNZDCLr6mkb3q_p4pXXqNn1Q@mail.gmail.com>

Guys,

The multiblock writer issue is unrelated -- as far as I can tell. Esp
since "If I take the image rendering out of my pipeline (comment out
the RegisterView call) and leave the VTK file writing, it runs fine
and doesn't report any leaks.".


Here's the MR if you're interested in checking it out in any case:
https://gitlab.kitware.com/vtk/vtk/merge_requests/1393


Utkarsh

On Mon, May 23, 2016 at 4:13 PM, Gallagher, Timothy P
<tim.gallagher at gatech.edu> wrote:
> I am using the multiblock format, so I am definitely interested in the
> solution. Hopefully Utkarsh sees this and can chime in.
>
>
> Thanks!
>
>
> Tim
>
>
>
> ________________________________
> From: Burlen Loring <burlen.loring at gmail.com>
> Sent: Monday, May 23, 2016 3:30 PM
>
> To: Gallagher, Timothy P; Andy Bauer
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Memory leak with Catalyst
>
>
> I think there is an api in the multi-block writer to disable writing
> metadata. Utkarsh knows, he's the one that figured it out. not sure how it
> applies to your use case. you may not even be using multi-block format...
>
>
> On 05/23/2016 06:57 AM, Gallagher, Timothy P wrote:
>
> Interesting -- I'd be willing to try it out if you have more details (commit
> hashtag, ticket, etc.), even if I have to figure out how to backport it from
> a newer version.
>
>
> Thanks,
>
>
> Tim
>
>
>
> ________________________________
> From: Burlen Loring <burlen.loring at gmail.com>
> Sent: Sunday, May 22, 2016 10:30 PM
> To: Gallagher, Timothy P; Andy Bauer
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Memory leak with Catalyst
>
> btw, we just had similar problem that was entirely explained by vtk writer
> attempting to gather a bunch of arrays to the root node. Utkarsh found a way
> to disable that behavior. I wonder if you are hitting the same.
>
> On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:
>
> Well... not going so well.
>
>
> If I run a small simulation with massif and the Release build of paraview, I
> don't see any growing memory in time. I also get my VTK files and images.
>
>
> If I run the same simulation linked against a Debug build with
> VTK_DEBUG_LEAKS on, there is a segfault inside one of the libvtkRendering
> libraries (it says libvtkRenderingOp but the rest of the name is cut off).
> If I take the image rendering out of my pipeline (comment out the
> RegisterView call) and leave the VTK file writing, it runs fine and doesn't
> report any leaks. I tried to get the segfault to drop a core file, but it
> won't do it.
>
>
> I'm thinking that there is an issue in the rendering part causing the leak.
> I have no idea what it could be though -- this is the 4.4.0 version, is
> anybody aware of any bug fixes between 4.4.0 and current versions that might
> be relevant?
>
>
> Thanks for the help,
>
>
> Tim
>
>
>
>
>
> ________________________________
> From: ParaView <paraview-bounces at paraview.org> on behalf of Gallagher,
> Timothy P <tim.gallagher at gatech.edu>
> Sent: Friday, May 20, 2016 4:17 PM
> To: Burlen Loring; Andy Bauer
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Memory leak with Catalyst
>
>
> Thanks for the advice Burlen -- I haven't used Massif before, so this is a
> good opportunity to give it a try.
>
>
> The initialize/finalize each time approach doesn't work either. I am calling
> the Finalize() routine on the vtkCPProcessor class but then when it tries to
> initialize again, it throws:
>
>
> Warning: In /data4/ParaView/VTK/Parallel/Core/vtkSocketController.cxx, line
> 50
> vtkSocketController (0xa4342f0): Already initialized.
>
>
> and then crashes. So, hopefully I can sort out the memory leak rather than
> trying to debug why a hacked fix doesn't work!
>
>
> Tim
>
>
>
> ________________________________
> From: Burlen Loring <burlen.loring at gmail.com>
> Sent: Friday, May 20, 2016 3:46 PM
> To: Gallagher, Timothy P; Andy Bauer
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Memory leak with Catalyst
>
>
> VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all
> kinds of leaks. For example you can have leaks where data erroneously
> accumulates with each time step, but is deleted at program termination.
> VTK_DEBUG_LEAKS will not catch that kind of error. It's probably better to
> use massif to profile your code on a small one node run. There's an
> excellent tool called massif visualizer to aid in exploring the data
> generated.
>
>
> $0.02
>
>
> On 05/20/2016 11:56 AM, Gallagher, Timothy P wrote:
>
> Hi Andy,
>
>
> Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see
> what it turns up.
>
>
> The initialize/finalize every time is definitely a hack and not for
> long-term use. But, sponsors want a report on Monday and we need to be able
> to visualize things for that -- the simulation is too big to write data
> files and post-process later. So I modified the code to do that for now
> until I can find a proper fix.
>
>
> I'll let you know if I get stuck with the log file.
>
>
> Thanks again,
>
>
> Tim
>
>
>
> ________________________________
> From: Andy Bauer <andy.bauer at kitware.com>
> Sent: Friday, May 20, 2016 2:39 PM
> To: Gallagher, Timothy P
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Memory leak with Catalyst
>
> Hi Tim,
>
> If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at
> finding VTK objects that aren't deleted properly. You should be able to run
> this with a small amount of calls to Catalyst as well. If you try this and
> want help understanding the output (if an object like a vtkUnstructuredGrid
> is leaked it will often give a whole bunch of false leaks that the
> unstructured grid is just holding the references to), just share your output
> file and I can take a look at it to try and narrow down the culprit. That
> may be slightly easier to use than Valgrind.
>
> Beyond this, you could maybe try the same run but without doing any Catalyst
> work to see what happens then. That may be a lot of compute cycles but I'm
> not sure how else to try and bisect where the memory leak is occurring.
>
> Initializing and finalizing Catalyst every time you want output would
> probably work but I'd think there may be significant overhead doing it like
> this. Plus, it's not really solving the problem -- just avoiding it.
>
> Best,
> Andy
>
>
> On Fri, May 20, 2016 at 12:57 PM, Gallagher, Timothy P
> <tim.gallagher at gatech.edu> wrote:
>>
>> Hi,
>>
>>
>> One of our users is running a very big simulation and writing out images
>> of two slices (two different views) every 1000 iterations and writing out
>> the data for the two slices (two different data writers) as VTK files every
>> 5000 iterations. It is using Paraview 4.4.
>>
>>
>> After 21000 iterations, the simulation is killed because the memory on the
>> compute nodes fills up. I usually know how to track down memory problems in
>> our code using valgrind and related tools, but is that the right way to go
>> to try and find this problem?
>>
>>
>> Are there any tips on how to isolate where the problem may be? I don't
>> know if it is in the adapter, or in paraview itself. Has anybody encountered
>> problems with runaway memory using Catalyst in 4.4 when writing images or
>> VTK files?
>>
>>
>> I know when we use pvpython to generate images and loop over many files,
>> sometimes the memory also blows up and so we usually move the loop over the
>> files outside the pvpython script and into a driver script that executes a
>> new pvpython for each file. Is there a way to shut down/start up Catalyst
>> each time it needs to write something? Is that advisable?
>>
>>
>> Thanks,
>>
>>
>> Tim
>>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> _______________________________________________
> 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
>
>
>
>
>
> _______________________________________________
> 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
>

From utkarsh.ayachit at kitware.com  Wed May 25 09:29:57 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 25 May 2016 09:29:57 -0400
Subject: [Paraview] using contour plot with xdmf input
In-Reply-To: <CADHSJjB=S=Zyt094cgqa2eY0w_XsMDN2AwYato++eazmK9ehJA@mail.gmail.com>
References: <57440005.5080106@geophysik.uni-muenchen.de>
 <57440478.9030308@geophysik.uni-muenchen.de>
 <CADHSJjB=S=Zyt094cgqa2eY0w_XsMDN2AwYato++eazmK9ehJA@mail.gmail.com>
Message-ID: <CADHSJjDLwVGacpXV25dG63uN8_TOWsEEcOTet28r3Du2RUC=gw@mail.gmail.com>

Stephanie,

The issue seems to be the fact that in the XDMF file you have a whole
lot of duplicated points. Here's my pipeline:

   fault.xmdf -> Clean To Grid -> Cell Data To Point Data

Now I can contour as expected. Clean To Grid will merge duplicate points.


On Tue, May 24, 2016 at 9:18 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Stephanie,
>
> Is it possible to share the full dataset to reproduce this issue? That
> will make things easier.
>
> Thanks,
> Ukarsh
>
> On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
> <wollherr at geophysik.uni-muenchen.de> wrote:
>>
>> Hi all,
>>
>>
>> I'm using a xdmf input file to visualize my data output from a
>> simulation. Before, the output format was vtk. I could easily do contour
>> plots using
>> CellDataToPointData and than apply the Contour button.
>> However with the xdmf format this is no longer possible.
>> There is no error but it just does not display anything.
>>
>> I came across this
>> https://cmake.org/pipermail/paraview/2015-December/035852.html
>> where another user run into this problem, but it seems that there was no
>> answer on this.
>>
>> I was wondering if there is already a solution or if someone can help me
>> with this?
>> Thank you already in advance!
>>
>> Stephanie
>>
>> ps:
>> I'm using paraview 4.3 on linux.
>> My xdmf file looks like that:
>> <?xml version="1.0" ?>
>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>> <Xdmf Version="2.0">
>>  <Domain>
>>   <Topology TopologyType="Triangle" NumberOfElements="147104">
>>    <DataItem NumberType="Int" Precision="8" Format="HDF"
>> Dimensions="147104 3">data-fault.h5:/connect</DataItem>
>>   </Topology>
>>   <Geometry name="geo" GeometryType="XYZ" NumberOfElements="441312">
>>    <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="441312 3">data-fault.h5:/geometry</DataItem>
>>   </Geometry>
>>   <DataItem NumberType="UInt" Precision="4" Format="HDF"
>> Dimensions="147104">data-fault.h5:/partition</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/SRs</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/SRd</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/T_s</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/T_d</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/P_n</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/u_n</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Ts0</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Td0</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Pn0</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Sls</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Sld</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/Vr</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/ASl</DataItem>
>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>> Dimensions="         133 147104">data-fault.h5:/PSR</DataItem>
>>   <Grid Name="TimeSeries" GridType="Collection" CollectionType="Temporal">
>>    <Grid Name="step_000000000000" GridType="Uniform">
>>     <Topology Reference="/Xdmf/Domain/Topology[1]"/>
>>     <Geometry Reference="/Xdmf/Domain/Geometry[1]"/>
>>     <Time Value="0.000608937"/>
>>     <Attribute Name="partition" Center="Cell">
>>      <DataItem Reference="/Xdmf/Domain/DataItem[1]" Dimensions="147104"/>
>>     </Attribute>
>>     <Attribute Name="SRs" Center="Cell">
>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>       <DataItem Reference="/Xdmf/Domain/DataItem[2]"/>
>>      </DataItem>
>>     </Attribute>
>>     <Attribute Name="SRd" Center="Cell">
>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>       <DataItem Reference="/Xdmf/Domain/DataItem[3]"/>
>>      </DataItem>
>>     </Attribute>
>>     <Attribute Name="T_s" Center="Cell">
>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>       <DataItem Reference="/Xdmf/Domain/DataItem[4]"/>
>>      </DataItem>
>>     </Attribute>
>> .......
>>
>>
>>
>>
>> _______________________________________________
>> 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

From wollherr at geophysik.uni-muenchen.de  Wed May 25 10:27:09 2016
From: wollherr at geophysik.uni-muenchen.de (Stephanie Wollherr)
Date: Wed, 25 May 2016 16:27:09 +0200
Subject: [Paraview] using contour plot with xdmf input
In-Reply-To: <CADHSJjDLwVGacpXV25dG63uN8_TOWsEEcOTet28r3Du2RUC=gw@mail.gmail.com>
References: <57440005.5080106@geophysik.uni-muenchen.de>
 <57440478.9030308@geophysik.uni-muenchen.de>
 <CADHSJjB=S=Zyt094cgqa2eY0w_XsMDN2AwYato++eazmK9ehJA@mail.gmail.com>
 <CADHSJjDLwVGacpXV25dG63uN8_TOWsEEcOTet28r3Du2RUC=gw@mail.gmail.com>
Message-ID: <5745B63D.20409@geophysik.uni-muenchen.de>

Dear Ukarsh,

thank you for solving this problem! It works perfectly fine now!

Kind regards,
Stephanie

On 25/05/16 15:29, Utkarsh Ayachit wrote:
> Stephanie,
>
> The issue seems to be the fact that in the XDMF file you have a whole
> lot of duplicated points. Here's my pipeline:
>
>    fault.xmdf -> Clean To Grid -> Cell Data To Point Data
>
> Now I can contour as expected. Clean To Grid will merge duplicate points.
>
>
> On Tue, May 24, 2016 at 9:18 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Stephanie,
>>
>> Is it possible to share the full dataset to reproduce this issue? That
>> will make things easier.
>>
>> Thanks,
>> Ukarsh
>>
>> On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
>> <wollherr at geophysik.uni-muenchen.de> wrote:
>>> Hi all,
>>>
>>>
>>> I'm using a xdmf input file to visualize my data output from a
>>> simulation. Before, the output format was vtk. I could easily do contour
>>> plots using
>>> CellDataToPointData and than apply the Contour button.
>>> However with the xdmf format this is no longer possible.
>>> There is no error but it just does not display anything.
>>>
>>> I came across this
>>> https://cmake.org/pipermail/paraview/2015-December/035852.html
>>> where another user run into this problem, but it seems that there was no
>>> answer on this.
>>>
>>> I was wondering if there is already a solution or if someone can help me
>>> with this?
>>> Thank you already in advance!
>>>
>>> Stephanie
>>>
>>> ps:
>>> I'm using paraview 4.3 on linux.
>>> My xdmf file looks like that:
>>> <?xml version="1.0" ?>
>>> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
>>> <Xdmf Version="2.0">
>>>  <Domain>
>>>   <Topology TopologyType="Triangle" NumberOfElements="147104">
>>>    <DataItem NumberType="Int" Precision="8" Format="HDF"
>>> Dimensions="147104 3">data-fault.h5:/connect</DataItem>
>>>   </Topology>
>>>   <Geometry name="geo" GeometryType="XYZ" NumberOfElements="441312">
>>>    <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="441312 3">data-fault.h5:/geometry</DataItem>
>>>   </Geometry>
>>>   <DataItem NumberType="UInt" Precision="4" Format="HDF"
>>> Dimensions="147104">data-fault.h5:/partition</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/SRs</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/SRd</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/T_s</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/T_d</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/P_n</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/u_n</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Ts0</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Td0</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Pn0</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Sls</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Sld</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/Vr</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/ASl</DataItem>
>>>   <DataItem NumberType="Float" Precision="8" Format="HDF"
>>> Dimensions="         133 147104">data-fault.h5:/PSR</DataItem>
>>>   <Grid Name="TimeSeries" GridType="Collection" CollectionType="Temporal">
>>>    <Grid Name="step_000000000000" GridType="Uniform">
>>>     <Topology Reference="/Xdmf/Domain/Topology[1]"/>
>>>     <Geometry Reference="/Xdmf/Domain/Geometry[1]"/>
>>>     <Time Value="0.000608937"/>
>>>     <Attribute Name="partition" Center="Cell">
>>>      <DataItem Reference="/Xdmf/Domain/DataItem[1]" Dimensions="147104"/>
>>>     </Attribute>
>>>     <Attribute Name="SRs" Center="Cell">
>>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>>       <DataItem Reference="/Xdmf/Domain/DataItem[2]"/>
>>>      </DataItem>
>>>     </Attribute>
>>>     <Attribute Name="SRd" Center="Cell">
>>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>>       <DataItem Reference="/Xdmf/Domain/DataItem[3]"/>
>>>      </DataItem>
>>>     </Attribute>
>>>     <Attribute Name="T_s" Center="Cell">
>>>      <DataItem ItemType="HyperSlab" Dimensions="147104">
>>>       <DataItem NumberType="UInt" Precision="8" Format="XML"
>>> Dimensions="3 2">0 0 1 1 1 147104</DataItem>
>>>       <DataItem Reference="/Xdmf/Domain/DataItem[4]"/>
>>>      </DataItem>
>>>     </Attribute>
>>> .......
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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

-- 
Stephanie Wollherr
Geophysics
Department of Earth and Environmental Sciences
LMU Munich

From houssen at ipgp.fr  Wed May 25 10:33:43 2016
From: houssen at ipgp.fr (houssen)
Date: Wed, 25 May 2016 16:33:43 +0200
Subject: [Paraview] =?utf-8?q?Bug_in_XDMF_reader_=3F?=
In-Reply-To: <e1a6fcb6f8bede4cedb4fa97b0ef6156@imap.ipgp.fr>
References: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
 <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>
 <ebf4c9d96a628cea31d376c98435c2da@imap.ipgp.fr>
 <e1a6fcb6f8bede4cedb4fa97b0ef6156@imap.ipgp.fr>
Message-ID: <4636617c4bb2a48183815a5a0f10364f@imap.ipgp.fr>

Got no news. Should I file a bug ? If yes, how ?

Franck

Le 2016-05-21 18:57, houssen a ?crit?:
> I've just tried to visualize KO.xdmf with visit-2.10.2 : it works
> fine ! So I guess it's a bug in paraview. How to file a bug ?
>
> Franck
>
> Le 2016-05-17 15:07, houssen a ?crit?:
>> Just to clarify, the scenario that makes problem is : select all
>> cells, go to selection inspector, visualize (in 3D viewer) values on
>> cells and / or points (this triggers errors).
>> My understanding is that both xdmf (OK and KO) are valid and should
>> work. OK.xdmf works (whatever PV version), but, KO.xdmf do not
>> (whatever PV version).
>> The problem appears when attribute names differ on different grids :
>> this looks (not sure) like a bug to me.
>>
>> With PV5.0.0 + default XDMF reader (which should be XDMF2 if I
>> understand correctly), I get :
>> Warning: In
>> 
>> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>> line 439
>> vtkLabeledDataMapper (0x36cc600): Could not find label array
>> (NodeValues) in input.
>> Warning: In
>> 
>> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>> line 439
>> vtkLabeledDataMapper (0x36cc600): Could not find label array
>> (NodeVal) in input.
>>
>> Note : I tested with all point and cell values, only node values
>> triggers error, cell values "do nothing".
>>
>> With PV5.0.0 + XDMF3 reader, I get:
>> 'Content' not found in itemProperties in XdmfArray::populateItem
>> Qt has caught an exception thrown from an event handler. Throwing
>> exceptions from an event handler is not supported in Qt. You must
>> reimplement QApplication::notify() and catch all exceptions there.
>> terminate called after throwing an instance of 'XdmfError'
>>   what():  'Content' not found in itemProperties in 
>> XdmfArray::populateItem
>> Aborted
>>
>> With PV4.0.1 + default XDMF reader (which should be XDMF2 if I
>> understand correctly), I get :
>> Warning: In
>> 
>> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>> line 442
>> vtkLabeledDataMapper (0x97f2140): Could not find label array
>> (CellVal) in input.
>> Warning: In
>> 
>> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>> line 442
>> vtkLabeledDataMapper (0x97d32d0): Could not find label array
>> (NodeVal) in input.
>>
>> Note : I tested with all point and cell values, only CellVal and
>> NodeVal triggers error, NodesValues and CellValues are visualized
>> correctly.
>>
>> Franck
>>
>> ~> diff OK.xdmf KO.xdmf
>> 48c48
>> <       <Attribute Name="NodeValues" AttributeType="Scalar" 
>> Center="Node">
>> ---
>>>       <Attribute Name="NodeVal" AttributeType="Scalar" 
>>> Center="Node">
>> 52c52
>> <       <Attribute Name="CellValues" AttributeType="Scalar" 
>> Center="Cell">
>> ---
>>>       <Attribute Name="CellVal" AttributeType="Scalar" 
>>> Center="Cell">
>>
>>
>> Le 2016-05-17 13:57, Joachim Pouderoux a ?crit?:
>>> Houssen,
>>>
>>> Could you specify which reader you are using? xdmf2 or xdmf3?
>>> You mention PV5.0.0 - do you mean it used to work with previous
>>> releases?
>>>
>>> Best,
>>>
>>> JOACHIM POUDEROUX
>>>
>>>> _PhD, Technical Expert_
>>>
>>> 2016-05-16 16:55 GMT+02:00 houssen <houssen at ipgp.fr [6]>:
>>>
>>>> Hello,
>>>>
>>>> I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when
>>>> attribute names differ in grids, data can not be visualized : is
>>>> this intended ? If yes why ? If no, how to file a bug ?
>>>>
>>>> Thanks,
>>>>
>>>> Franck
>>>>
>>>> ~> diff OK.xdmf KO.xdmf
>>>> 48c48
>>>> <? ? ? ?<Attribute Name="NodeValues" AttributeType="Scalar"
>>>> Center="Node">
>>>> ---
>>>>
>>>>> ? ? ? <Attribute Name="NodeVal" AttributeType="Scalar"
>>>>> Center="Node">
>>>> 52c52
>>>> <? ? ? ?<Attribute Name="CellValues" AttributeType="Scalar"
>>>> Center="Cell">
>>>> ---
>>>>
>>>>> ? ? ? <Attribute Name="CellVal" AttributeType="Scalar"
>>>>> Center="Cell">
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com [1]
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html [2]
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView [3]
>>>>
>>>> Search the list archives at:
>>>> http://markmail.org/search/?q=ParaView [4]
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview [5]
>>>
>>>
>>>
>>> Links:
>>> ------
>>> [1] http://www.kitware.com
>>> [2] http://www.kitware.com/opensource/opensource.html
>>> [3] http://paraview.org/Wiki/ParaView
>>> [4] http://markmail.org/search/?q=ParaView
>>> [5] http://public.kitware.com/mailman/listinfo/paraview
>>> [6] mailto:houssen at ipgp.fr


From joachim.pouderoux at kitware.com  Wed May 25 11:57:43 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Wed, 25 May 2016 17:57:43 +0200
Subject: [Paraview] Bug in XDMF reader ?
In-Reply-To: <4636617c4bb2a48183815a5a0f10364f@imap.ipgp.fr>
References: <422f2e4d208ac9f23f738e444abdf90a@imap.ipgp.fr>
 <CACJ=gTjz4ArDwN5mQwxwdpJiKkCoDVKjiFhFaWdCLsmjRwY=1g@mail.gmail.com>
 <ebf4c9d96a628cea31d376c98435c2da@imap.ipgp.fr>
 <e1a6fcb6f8bede4cedb4fa97b0ef6156@imap.ipgp.fr>
 <4636617c4bb2a48183815a5a0f10364f@imap.ipgp.fr>
Message-ID: <CACJ=gThRbCaRGh2mbpaMtNrLB=TBTFv-EXVtB3Kk2cDT5y730w@mail.gmail.com>

Franck,

Feel free to fill a bug on ParaView bug tracker here:
http://www.paraview.org/Bug

Best,
Joachim

*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2016-05-25 16:33 GMT+02:00 houssen <houssen at ipgp.fr>:

> Got no news. Should I file a bug ? If yes, how ?
>
> Franck
>
>
> Le 2016-05-21 18:57, houssen a ?crit :
>
>> I've just tried to visualize KO.xdmf with visit-2.10.2 : it works
>> fine ! So I guess it's a bug in paraview. How to file a bug ?
>>
>> Franck
>>
>> Le 2016-05-17 15:07, houssen a ?crit :
>>
>>> Just to clarify, the scenario that makes problem is : select all
>>> cells, go to selection inspector, visualize (in 3D viewer) values on
>>> cells and / or points (this triggers errors).
>>> My understanding is that both xdmf (OK and KO) are valid and should
>>> work. OK.xdmf works (whatever PV version), but, KO.xdmf do not
>>> (whatever PV version).
>>> The problem appears when attribute names differ on different grids :
>>> this looks (not sure) like a bug to me.
>>>
>>> With PV5.0.0 + default XDMF reader (which should be XDMF2 if I
>>> understand correctly), I get :
>>> Warning: In
>>>
>>>
>>> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>>> line 439
>>> vtkLabeledDataMapper (0x36cc600): Could not find label array
>>> (NodeValues) in input.
>>> Warning: In
>>>
>>>
>>> /scratch/ParaView-v5.0.0-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>>> line 439
>>> vtkLabeledDataMapper (0x36cc600): Could not find label array
>>> (NodeVal) in input.
>>>
>>> Note : I tested with all point and cell values, only node values
>>> triggers error, cell values "do nothing".
>>>
>>> With PV5.0.0 + XDMF3 reader, I get:
>>> 'Content' not found in itemProperties in XdmfArray::populateItem
>>> Qt has caught an exception thrown from an event handler. Throwing
>>> exceptions from an event handler is not supported in Qt. You must
>>> reimplement QApplication::notify() and catch all exceptions there.
>>> terminate called after throwing an instance of 'XdmfError'
>>>   what():  'Content' not found in itemProperties in
>>> XdmfArray::populateItem
>>> Aborted
>>>
>>> With PV4.0.1 + default XDMF reader (which should be XDMF2 if I
>>> understand correctly), I get :
>>> Warning: In
>>>
>>>
>>> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>>> line 442
>>> vtkLabeledDataMapper (0x97f2140): Could not find label array
>>> (CellVal) in input.
>>> Warning: In
>>>
>>>
>>> /scratch/ParaView-v4.0.1-source/VTK/Rendering/Label/vtkLabeledDataMapper.cxx,
>>> line 442
>>> vtkLabeledDataMapper (0x97d32d0): Could not find label array
>>> (NodeVal) in input.
>>>
>>> Note : I tested with all point and cell values, only CellVal and
>>> NodeVal triggers error, NodesValues and CellValues are visualized
>>> correctly.
>>>
>>> Franck
>>>
>>> ~> diff OK.xdmf KO.xdmf
>>> 48c48
>>> <       <Attribute Name="NodeValues" AttributeType="Scalar"
>>> Center="Node">
>>> ---
>>>
>>>>       <Attribute Name="NodeVal" AttributeType="Scalar" Center="Node">
>>>>
>>> 52c52
>>> <       <Attribute Name="CellValues" AttributeType="Scalar"
>>> Center="Cell">
>>> ---
>>>
>>>>       <Attribute Name="CellVal" AttributeType="Scalar" Center="Cell">
>>>>
>>>
>>>
>>> Le 2016-05-17 13:57, Joachim Pouderoux a ?crit :
>>>
>>>> Houssen,
>>>>
>>>> Could you specify which reader you are using? xdmf2 or xdmf3?
>>>> You mention PV5.0.0 - do you mean it used to work with previous
>>>> releases?
>>>>
>>>> Best,
>>>>
>>>> JOACHIM POUDEROUX
>>>>
>>>> _PhD, Technical Expert_
>>>>>
>>>>
>>>> 2016-05-16 16:55 GMT+02:00 houssen <houssen at ipgp.fr [6]>:
>>>>
>>>> Hello,
>>>>>
>>>>> I have 2 grids (sharing the same nodes). On ParaView-5.0.0, when
>>>>> attribute names differ in grids, data can not be visualized : is
>>>>> this intended ? If yes why ? If no, how to file a bug ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Franck
>>>>>
>>>>> ~> diff OK.xdmf KO.xdmf
>>>>> 48c48
>>>>> <       <Attribute Name="NodeValues" AttributeType="Scalar"
>>>>> Center="Node">
>>>>> ---
>>>>>
>>>>>       <Attribute Name="NodeVal" AttributeType="Scalar"
>>>>>> Center="Node">
>>>>>>
>>>>> 52c52
>>>>> <       <Attribute Name="CellValues" AttributeType="Scalar"
>>>>> Center="Cell">
>>>>> ---
>>>>>
>>>>>       <Attribute Name="CellVal" AttributeType="Scalar"
>>>>>> Center="Cell">
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com [1]
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html [2]
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> http://paraview.org/Wiki/ParaView [3]
>>>>>
>>>>> Search the list archives at:
>>>>> http://markmail.org/search/?q=ParaView [4]
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview [5]
>>>>>
>>>>
>>>>
>>>>
>>>> Links:
>>>> ------
>>>> [1] http://www.kitware.com
>>>> [2] http://www.kitware.com/opensource/opensource.html
>>>> [3] http://paraview.org/Wiki/ParaView
>>>> [4] http://markmail.org/search/?q=ParaView
>>>> [5] http://public.kitware.com/mailman/listinfo/paraview
>>>> [6] mailto:houssen at ipgp.fr
>>>>
>>>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160525/bad7c2bb/attachment.html>

From jonathan.borduas at caboma.com  Wed May 25 10:50:05 2016
From: jonathan.borduas at caboma.com (Jonathan Borduas)
Date: Wed, 25 May 2016 14:50:05 +0000
Subject: [Paraview] Programmable filter - script for mean of two
	input	PointSources
In-Reply-To: <CADHSJjBwu1igu6gU+RJ2jiuPSuNOgEC1OMnC004ek7ZxKRXUxA@mail.gmail.com>
References: <CY1PR03MB213801685E6D927BF70DB1349D4F0@CY1PR03MB2138.namprd03.prod.outlook.com>
 <CADHSJjBwu1igu6gU+RJ2jiuPSuNOgEC1OMnC004ek7ZxKRXUxA@mail.gmail.com>
Message-ID: <BY2PR15MB05209DD92F75D14CF7EE7111FD400@BY2PR15MB0520.namprd15.prod.outlook.com>

Hi, 

What is the best way to proceed if someone wants to use the new coordinate (mean of the two dots) in another filter using a Link. For instance, I would like to use the coordinate as the Origin of a Clip filter. 

Thank you,


-----Message d'origine-----
De?: ParaView [mailto:paraview-bounces at paraview.org] De la part de Utkarsh Ayachit
Envoy??: 24 mai 2016 09:17
??: Thomas Faribault-M?nard <thomas.faribault-menard at mail.mcgill.ca>
Cc?: paraview at paraview.org
Objet?: Re: [Paraview] Programmable filter - script for mean of two input PointSources

Here's a simple trick:

1. Select both point sources in pipeline browser and then create the "Python Calculator".
2. Use the expression "(inputs[0].Points + inputs[1].Points)/2.0", and hit "Apply"
3. Next, create the "Calculator" filter connect to the "Python Calculator" with expression "result" and also check the "Coordinate Results" checkbox. Hit "Apply".

That should do it.

Example state file attached.



On Mon, May 23, 2016 at 10:19 PM, Thomas Faribault-M?nard <thomas.faribault-menard at mail.mcgill.ca> wrote:
> Hi,
>
> I?m a beginner in ParaView. I have two Point Source as my inputs. My 
> output is a third point source that has to be located at the mean of 
> the coordinates of my inputs.
>
> I would prefer the solution to be in the form of a programmable python 
> filter but I need a little help.
>
> Could you point me in the right direction please ?
>
>
> _______________________________________________
> 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
>

From kmorel at sandia.gov  Wed May 25 14:05:25 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 25 May 2016 18:05:25 +0000
Subject: [Paraview] Slow with just 1M cells
In-Reply-To: <C732BAF0-0404-4FF7-A3B3-0AFC9F69A7C5@sandia.gov>
References: <C732BAF0-0404-4FF7-A3B3-0AFC9F69A7C5@sandia.gov>
Message-ID: <A49F5253-951C-4F62-B7DB-0CD73C3DD57C@sandia.gov>

Michele,

I took a look at the data you sent me. I experienced many of the issues you brought up.

After taking a closer look at the data, I realized that many of the cells in your data are of the general polyhedral type. Unlike the standard cell shapes like tetrahedron and hexahedron, polyhedral shapes are general polyhedra formed by specifying the face polygons. They allow you to specify any flat faceted shape, but computing basic operations on them such as interpolations, derivatives, and location finding is very expensive. This is why operations like streamlines are going so slowly.

If the cells are represented as standard shapes, things go much faster. For example, if you tetrahedralize the data, streamlines takes well under 10 seconds. That gets the operations to about the range where your nameless commercial product is running. I suspect, but cannot verify, that this other visualization package is probably downgrading the cells to something like hexahedra, which makes it run faster.

I don?t recommend running the tetrahedralization filter all the time on your data. It is also slow and really bloats the data. If you could write out an alternate form of the data that wrote hexahedra instead of polyhedra, I suspect things would run much faster. You would probably have a problem with faces not being aligned, though.

One final note, although the clip filter is taking a long time, I found the slice filter to be much faster. Generally, when dealing with large data, you should favor slice over clip. It?s much faster, uses much less memory, and usually gives you the same information.

-Ken

On 5/21/16, 9:47 AM, "Moreland, Kenneth" <kmorel at sandia.gov> wrote:

>Michele,
>
>Taking over a minute to process a data set with 1 million cells does seem like an unreasonably long time, even for a moderately powered PC. Perhaps something odd is happening here. Can you describe in more detail what your data look like and what you are doing with them?
>
>-Ken
>
>On 5/20/16, 11:55 AM, "ParaView on behalf of Michele Battistoni" <paraview-bounces at paraview.org on behalf of michele.battistoni at unipg.it> wrote:
>
>>Paraview is awesome for lots of functionalities, however I find it extremely slow in processing data with any filter type, or in changing timestep as soon as the model size is around one million cells or above. I have experience with a commercial tool which on the same model and pc is 100x faster. Let's say a second vs. a min!
>>
>>Is there any specific settings for ram of parallelization among cores?
>>
>>Thanks 
>>Michele
>>
>>
>>_______________________________________________
>>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
>


From brownm12 at vt.edu  Wed May 25 14:04:47 2016
From: brownm12 at vt.edu (Matthew Brown)
Date: Wed, 25 May 2016 14:04:47 -0400
Subject: [Paraview] PV 5.0.1 client-server crashing for some datasets
Message-ID: <CAHM0Tbxr0JxDETtDGa56-L-N=qKw=gmVjFxCxOA_rE6t9duwdw@mail.gmail.com>

I have recently built and installed ParaView 5.0.1 on one of our clusters
and am having issues when loading most datasets that I have tried.

1. remote rendering seems to work with no issues:  I can make spheres and
cylinders and move them around and color their sections according the core
doing the processing
2. the ParaView tutorial dataset (from
http://www.paraview.org/Wiki/The_ParaView_Tutorial) named headsq.vti can
load and render remotely with no problems
3. loading either of the other two tutorial datasets (can.ex2 or
disk_out_ref.ex2) causes the application to crash
4. The remote client machine (running ParaView5.0.1) can open all of these
datasets with no problem

Crash details:
a. data set variables show up correctly in the Properties pane, but
Information seems unavailable: all the fields under statistics and data
arrays have values "NA", but time indices look correct
b. clicking "Apply" causes the client application on the remote machine and
pvserver on the cluster to die
c. client-side standard output:
####################-begin-####################
$ ./paraview
AutoMPI: SUCCESS: command is:
 "/Applications/paraview.app/Contents/MacOS/mpiexec" "-np" "2"
"/Applications/paraview.app/Contents/bin/pvserver" "--server-port=56934"
AutoMPI: starting process server
-------------- server output --------------
Waiting for client...
AutoMPI: server successfully started.
ERROR: In
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
line 310
vtkSIProxy (0x7f93f3a2ead0): Failed to create vtkHAVSVolumeMapper. Aborting
for debugging purposes.


Abort trap: 6
####################-end-####################

d. cluster-side standard output:
####################-begin-####################
[brownm12 at nr019 ~]$ mpirun -n 2 pvserver
Waiting for client...
Connection URL: cs://nr019:11111
Accepting connection(s): nr019:11111
Client connected.
ERROR: In
/opt/build/BUILD/ParaView-5.0.1-Source/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 809
vtkSocketCommunicator (0x2f81200): Could not receive tag. 1

Exiting...
Exiting...
####################-end-####################

Build information:
cluster: CentOS 7, gcc-4.7.2, openmpi-1.8.5, python 2.7.10, ParaView 5.0.1.
I can provide more details if needed, but I'm not sure what would be most
relevant

It seems to me that the issue may be with how the cluster is opening the
datasets.  I would like some advice or ideas on how to resolve or continue
troubleshooting the problem.

Thanks,

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160525/af827091/attachment.html>

From utkarsh.ayachit at kitware.com  Wed May 25 14:55:10 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 25 May 2016 14:55:10 -0400
Subject: [Paraview] PV 5.0.1 client-server crashing for some datasets
In-Reply-To: <CAHM0Tbxr0JxDETtDGa56-L-N=qKw=gmVjFxCxOA_rE6t9duwdw@mail.gmail.com>
References: <CAHM0Tbxr0JxDETtDGa56-L-N=qKw=gmVjFxCxOA_rE6t9duwdw@mail.gmail.com>
Message-ID: <CADHSJjDZ+goj6DppYXYzxD7WwpYN-fD5uPppgmF7hxE3HUZ3MA@mail.gmail.com>

Matt,

Can you confirm that both the client and server are using the same
rendering backend? Unfortunately, there's no clean way to do that
except to look at the CMakeCache.txt used to build to two. Confirm
that the VTK_RENDERING_BACKEND CMake flag is set to the same value on
both. I suspect one is "OpenGL" and other is "OpenGL2".

Utkarsh

On Wed, May 25, 2016 at 2:04 PM, Matthew Brown <brownm12 at vt.edu> wrote:
> I have recently built and installed ParaView 5.0.1 on one of our clusters
> and am having issues when loading most datasets that I have tried.
>
> 1. remote rendering seems to work with no issues:  I can make spheres and
> cylinders and move them around and color their sections according the core
> doing the processing
> 2. the ParaView tutorial dataset (from
> http://www.paraview.org/Wiki/The_ParaView_Tutorial) named headsq.vti can
> load and render remotely with no problems
> 3. loading either of the other two tutorial datasets (can.ex2 or
> disk_out_ref.ex2) causes the application to crash
> 4. The remote client machine (running ParaView5.0.1) can open all of these
> datasets with no problem
>
> Crash details:
> a. data set variables show up correctly in the Properties pane, but
> Information seems unavailable: all the fields under statistics and data
> arrays have values "NA", but time indices look correct
> b. clicking "Apply" causes the client application on the remote machine and
> pvserver on the cluster to die
> c. client-side standard output:
> ####################-begin-####################
> $ ./paraview
> AutoMPI: SUCCESS: command is:
>  "/Applications/paraview.app/Contents/MacOS/mpiexec" "-np" "2"
> "/Applications/paraview.app/Contents/bin/pvserver" "--server-port=56934"
> AutoMPI: starting process server
> -------------- server output --------------
> Waiting for client...
> AutoMPI: server successfully started.
> ERROR: In
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7f93f3a2ead0): Failed to create vtkHAVSVolumeMapper. Aborting
> for debugging purposes.
>
>
> Abort trap: 6
> ####################-end-####################
>
> d. cluster-side standard output:
> ####################-begin-####################
> [brownm12 at nr019 ~]$ mpirun -n 2 pvserver
> Waiting for client...
> Connection URL: cs://nr019:11111
> Accepting connection(s): nr019:11111
> Client connected.
> ERROR: In
> /opt/build/BUILD/ParaView-5.0.1-Source/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 809
> vtkSocketCommunicator (0x2f81200): Could not receive tag. 1
>
> Exiting...
> Exiting...
> ####################-end-####################
>
> Build information:
> cluster: CentOS 7, gcc-4.7.2, openmpi-1.8.5, python 2.7.10, ParaView 5.0.1.
> I can provide more details if needed, but I'm not sure what would be most
> relevant
>
> It seems to me that the issue may be with how the cluster is opening the
> datasets.  I would like some advice or ideas on how to resolve or continue
> troubleshooting the problem.
>
> Thanks,
>
> Matt
>
>
>
> _______________________________________________
> 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
>

From brownm12 at vt.edu  Wed May 25 15:45:25 2016
From: brownm12 at vt.edu (Matthew Brown)
Date: Wed, 25 May 2016 15:45:25 -0400
Subject: [Paraview] PV 5.0.1 client-server crashing for some datasets
In-Reply-To: <CADHSJjDZ+goj6DppYXYzxD7WwpYN-fD5uPppgmF7hxE3HUZ3MA@mail.gmail.com>
References: <CAHM0Tbxr0JxDETtDGa56-L-N=qKw=gmVjFxCxOA_rE6t9duwdw@mail.gmail.com>
 <CADHSJjDZ+goj6DppYXYzxD7WwpYN-fD5uPppgmF7hxE3HUZ3MA@mail.gmail.com>
Message-ID: <CAHM0TbyD-J=+kCYFW724SdtrKjwkJFAh4UQZ=-6YsmCkR4g-2Q@mail.gmail.com>

Thank you for the quick reply.

On the client, I used a superbuild for MacOS X which I take it is built
with OpenGL2.  On the cluster, I accepted the default flag which (upon
rerunning ccmake) appears to be OpenGL on this system.

So, the client and server are almost certainly built to use different
rendering backends.  I take it that they must be the same for full
functionality, is that correct?  What functionality would you expect to
fail if rendering backends are mismatched between the client and server?

Matt

On Wed, May 25, 2016 at 2:55 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Matt,
>
> Can you confirm that both the client and server are using the same
> rendering backend? Unfortunately, there's no clean way to do that
> except to look at the CMakeCache.txt used to build to two. Confirm
> that the VTK_RENDERING_BACKEND CMake flag is set to the same value on
> both. I suspect one is "OpenGL" and other is "OpenGL2".
>
> Utkarsh
>
> On Wed, May 25, 2016 at 2:04 PM, Matthew Brown <brownm12 at vt.edu> wrote:
> > I have recently built and installed ParaView 5.0.1 on one of our clusters
> > and am having issues when loading most datasets that I have tried.
> >
> > 1. remote rendering seems to work with no issues:  I can make spheres and
> > cylinders and move them around and color their sections according the
> core
> > doing the processing
> > 2. the ParaView tutorial dataset (from
> > http://www.paraview.org/Wiki/The_ParaView_Tutorial) named headsq.vti can
> > load and render remotely with no problems
> > 3. loading either of the other two tutorial datasets (can.ex2 or
> > disk_out_ref.ex2) causes the application to crash
> > 4. The remote client machine (running ParaView5.0.1) can open all of
> these
> > datasets with no problem
> >
> > Crash details:
> > a. data set variables show up correctly in the Properties pane, but
> > Information seems unavailable: all the fields under statistics and data
> > arrays have values "NA", but time indices look correct
> > b. clicking "Apply" causes the client application on the remote machine
> and
> > pvserver on the cluster to die
> > c. client-side standard output:
> > ####################-begin-####################
> > $ ./paraview
> > AutoMPI: SUCCESS: command is:
> >  "/Applications/paraview.app/Contents/MacOS/mpiexec" "-np" "2"
> > "/Applications/paraview.app/Contents/bin/pvserver" "--server-port=56934"
> > AutoMPI: starting process server
> > -------------- server output --------------
> > Waiting for client...
> > AutoMPI: server successfully started.
> > ERROR: In
> >
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
> > line 310
> > vtkSIProxy (0x7f93f3a2ead0): Failed to create vtkHAVSVolumeMapper.
> Aborting
> > for debugging purposes.
> >
> >
> > Abort trap: 6
> > ####################-end-####################
> >
> > d. cluster-side standard output:
> > ####################-begin-####################
> > [brownm12 at nr019 ~]$ mpirun -n 2 pvserver
> > Waiting for client...
> > Connection URL: cs://nr019:11111
> > Accepting connection(s): nr019:11111
> > Client connected.
> > ERROR: In
> >
> /opt/build/BUILD/ParaView-5.0.1-Source/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> > line 809
> > vtkSocketCommunicator (0x2f81200): Could not receive tag. 1
> >
> > Exiting...
> > Exiting...
> > ####################-end-####################
> >
> > Build information:
> > cluster: CentOS 7, gcc-4.7.2, openmpi-1.8.5, python 2.7.10, ParaView
> 5.0.1.
> > I can provide more details if needed, but I'm not sure what would be most
> > relevant
> >
> > It seems to me that the issue may be with how the cluster is opening the
> > datasets.  I would like some advice or ideas on how to resolve or
> continue
> > troubleshooting the problem.
> >
> > Thanks,
> >
> > Matt
> >
> >
> >
> > _______________________________________________
> > 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
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160525/5c374d03/attachment.html>

From lyon at fnal.gov  Wed May 25 15:53:04 2016
From: lyon at fnal.gov (Adam Lyon)
Date: Wed, 25 May 2016 14:53:04 -0500
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
 <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
 <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
Message-ID: <CANjddW19=BozzpOaNErw5bQzqf_9GPXRWGha=odnYFu_fsyj6A@mail.gmail.com>

Hi Sven - I'm very interested in how you got catalyst to work with
paraviewweb.  Can you post your code somewhere (or send me a tar file or
something)? I would very much appreciate that. Thanks very much! -- Adam

*------*

*Adam L. Lyon*
*Scientist; Associate Division Head for Systems for Scientific Applications*

Scientific Computing Division & Muon g-2 Experiment
Fermi National Accelerator Laboratory
630 840 5522 office
www.fnal.gov
lyon at fnal.gov

Connect with us!
News <http://news.fnal.gov/>  |  Facebook
<https://www.facebook.com/Fermilab>  |  Twitter
<https://twitter.com/Fermilab>

On Mon, May 23, 2016 at 11:44 AM, Sven Kramer <svenkramer40 at gmail.com>
wrote:

> Sure, I would share the code. But as I said, I haven't done anything more
> than wrapping pqCatalystConnectReaction::connect() and hacking several
> lines in the python rpc server, which are probably not done right.
> If it helps, I can try to reconstruct all the lines I have modified and
> clean up the stuff. However, you'll probably find a cleaner solution to
> invoke pqCatalystConnectReaction::connect() from the web client.
>
> Sven
>
> 2016-05-23 7:22 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Glad to ear that you managed to get something going. If you feel like
>> sharing your code, we might be able to provide some integration into
>> ParaView and/or ParaViewWeb proper.
>>
>> Seb
>>
>> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Thank you, Seb,
>>> it seems like I am getting it to work. There are still some difficulties
>>> because of my limited javascript experience, but with some quick&dirty
>>> workarounds I do have the Catalyst output displayed from ParaViewWeb. As
>>> you said, nothing else was required than wrapping the C functions in python.
>>>
>>> Thanks
>>> Sven
>>>
>>>
>>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com>:
>>>
>>>> Hi Sven,
>>>>
>>>> I am not aware on any specific developer documentation for Catalyst on
>>>> the ParaView side (but I haven't worked on that subject for years),
>>>> although Utkarsh or Andy might know.
>>>>
>>>> Usually looking at the code and redoing it in the Python world is what
>>>> is required, but as I said, I'm not sure of what it means since I don't
>>>> know that code anymore. ;-)
>>>>
>>>> For the timeframe, I can't tell (meaning I don't know), but we can
>>>> still try to help you or implement the missing piece via support contract
>>>> if that make sense on your end.
>>>>
>>>> Thanks,
>>>>
>>>> Seb
>>>>
>>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Seb,
>>>>> glad to read your answer. So the problem is not only that I was unable
>>>>> to find the relevant information.
>>>>>
>>>>> You say, you have not (yet) written the required code. Does "not
>>>>> (yet)" mean that it is on the agenda maybe within the next half year? Then
>>>>> I could find a workaround and look forward to the next Paraview updates.
>>>>>
>>>>> Otherwise I would try to work on the implementation for connecting
>>>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>>>> information? Those would be great to get started.
>>>>> My first attempt would be to "wrap" the functionality of
>>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>>>> make it available to the web client. Or are the necessary steps much more
>>>>> involved?
>>>>>
>>>>> Thank you
>>>>> Sven
>>>>>
>>>>>
>>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com>:
>>>>>
>>>>>> Hi Sven,
>>>>>>
>>>>>> Live catalyst connection require a specific socket connection to the
>>>>>> in-situ process with some special handling.
>>>>>> We did not (yet) wrote the Python code to perform that specific
>>>>>> action for ParaViewWeb so it could be triggered by the web client or
>>>>>> configured via an argument at launch time.
>>>>>> I don't see any reason why this couldn't work, but as for now, I also
>>>>>> don't know an easy step to do it without spending time doing it myself.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>> I am looking for the recommended steps how to display an in-situ
>>>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>>>
>>>>>>> After some efforts I am able to run ParaViewWeb successfully and I
>>>>>>> can view a Catalyst-enabled simulation in paraview.
>>>>>>>
>>>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>>>> pvserver as mentioned at the end of
>>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/
>>>>>>> and giving "--ds-host localhost --ds-port 11111" options to
>>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>>>> displayed on the web.
>>>>>>>
>>>>>>> Below you find the (not too detailed) steps I took to have a working
>>>>>>> solution for either Catalyst-enabled simulations or a working web
>>>>>>> visualizer:
>>>>>>>
>>>>>>> Test connection from Catalyst simulation to paraview:
>>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz
>>>>>>> (from http://www.paraview.org/download/)
>>>>>>> 2) Choose Catalyst->Connect in paraview
>>>>>>> 3) Run CFullExample from
>>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>>>> Success!
>>>>>>>
>>>>>>> Test ParaViewWeb:
>>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>>>> http://www.paraview.org/download/, extract in /data
>>>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>>>> Success!
>>>>>>>
>>>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Sven
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160525/c3e7ebb4/attachment.html>

From brownm12 at vt.edu  Wed May 25 16:57:08 2016
From: brownm12 at vt.edu (Matthew Brown)
Date: Wed, 25 May 2016 16:57:08 -0400
Subject: [Paraview] PV 5.0.1 client-server crashing for some datasets
In-Reply-To: <CAHM0TbyD-J=+kCYFW724SdtrKjwkJFAh4UQZ=-6YsmCkR4g-2Q@mail.gmail.com>
References: <CAHM0Tbxr0JxDETtDGa56-L-N=qKw=gmVjFxCxOA_rE6t9duwdw@mail.gmail.com>
 <CADHSJjDZ+goj6DppYXYzxD7WwpYN-fD5uPppgmF7hxE3HUZ3MA@mail.gmail.com>
 <CAHM0TbyD-J=+kCYFW724SdtrKjwkJFAh4UQZ=-6YsmCkR4g-2Q@mail.gmail.com>
Message-ID: <CAHM0TbzETwAbJorTVErzceKgC9dPYi-FycT25eyd+u0+eU+aQg@mail.gmail.com>

I rebuilt the cluster's installation of Paraview 5.0.1 making sure to set
VTK_RENDERING_BACKEND=OpenGL2 since this will be most compatible with the
superbuild binaries.  The datasets I originally could not load now seem to
load and render correctly.  I will have more users test the installation
and report back here if I hear of any problems.

Thanks again,

Matt

On Wed, May 25, 2016 at 3:45 PM, Matthew Brown <brownm12 at vt.edu> wrote:

> Thank you for the quick reply.
>
> On the client, I used a superbuild for MacOS X which I take it is built
> with OpenGL2.  On the cluster, I accepted the default flag which (upon
> rerunning ccmake) appears to be OpenGL on this system.
>
> So, the client and server are almost certainly built to use different
> rendering backends.  I take it that they must be the same for full
> functionality, is that correct?  What functionality would you expect to
> fail if rendering backends are mismatched between the client and server?
>
> Matt
>
> On Wed, May 25, 2016 at 2:55 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Matt,
>>
>> Can you confirm that both the client and server are using the same
>> rendering backend? Unfortunately, there's no clean way to do that
>> except to look at the CMakeCache.txt used to build to two. Confirm
>> that the VTK_RENDERING_BACKEND CMake flag is set to the same value on
>> both. I suspect one is "OpenGL" and other is "OpenGL2".
>>
>> Utkarsh
>>
>> On Wed, May 25, 2016 at 2:04 PM, Matthew Brown <brownm12 at vt.edu> wrote:
>> > I have recently built and installed ParaView 5.0.1 on one of our
>> clusters
>> > and am having issues when loading most datasets that I have tried.
>> >
>> > 1. remote rendering seems to work with no issues:  I can make spheres
>> and
>> > cylinders and move them around and color their sections according the
>> core
>> > doing the processing
>> > 2. the ParaView tutorial dataset (from
>> > http://www.paraview.org/Wiki/The_ParaView_Tutorial) named headsq.vti
>> can
>> > load and render remotely with no problems
>> > 3. loading either of the other two tutorial datasets (can.ex2 or
>> > disk_out_ref.ex2) causes the application to crash
>> > 4. The remote client machine (running ParaView5.0.1) can open all of
>> these
>> > datasets with no problem
>> >
>> > Crash details:
>> > a. data set variables show up correctly in the Properties pane, but
>> > Information seems unavailable: all the fields under statistics and data
>> > arrays have values "NA", but time indices look correct
>> > b. clicking "Apply" causes the client application on the remote machine
>> and
>> > pvserver on the cluster to die
>> > c. client-side standard output:
>> > ####################-begin-####################
>> > $ ./paraview
>> > AutoMPI: SUCCESS: command is:
>> >  "/Applications/paraview.app/Contents/MacOS/mpiexec" "-np" "2"
>> > "/Applications/paraview.app/Contents/bin/pvserver" "--server-port=56934"
>> > AutoMPI: starting process server
>> > -------------- server output --------------
>> > Waiting for client...
>> > AutoMPI: server successfully started.
>> > ERROR: In
>> >
>> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
>> > line 310
>> > vtkSIProxy (0x7f93f3a2ead0): Failed to create vtkHAVSVolumeMapper.
>> Aborting
>> > for debugging purposes.
>> >
>> >
>> > Abort trap: 6
>> > ####################-end-####################
>> >
>> > d. cluster-side standard output:
>> > ####################-begin-####################
>> > [brownm12 at nr019 ~]$ mpirun -n 2 pvserver
>> > Waiting for client...
>> > Connection URL: cs://nr019:11111
>> > Accepting connection(s): nr019:11111
>> > Client connected.
>> > ERROR: In
>> >
>> /opt/build/BUILD/ParaView-5.0.1-Source/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
>> > line 809
>> > vtkSocketCommunicator (0x2f81200): Could not receive tag. 1
>> >
>> > Exiting...
>> > Exiting...
>> > ####################-end-####################
>> >
>> > Build information:
>> > cluster: CentOS 7, gcc-4.7.2, openmpi-1.8.5, python 2.7.10, ParaView
>> 5.0.1.
>> > I can provide more details if needed, but I'm not sure what would be
>> most
>> > relevant
>> >
>> > It seems to me that the issue may be with how the cluster is opening the
>> > datasets.  I would like some advice or ideas on how to resolve or
>> continue
>> > troubleshooting the problem.
>> >
>> > Thanks,
>> >
>> > Matt
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160525/f1fe156b/attachment.html>

From apeczak at ara.co.uk  Thu May 26 07:30:31 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Thu, 26 May 2016 11:30:31 +0000
Subject: [Paraview] Custom panel widget
In-Reply-To: <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara> 
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara>

Hi Utkarsh

Our use-case scenario is that we have our own filter based on vtkCpCutter (both vtkPolyData on the input and output port) . We use this filter to generate a set of slices on surface geometry. We then process the obtained contours with vtkPlotEdges. For each contour (slice) we would like to compute a scalar value, say max distance between two points in the contour and output the values to the scalar list widget. Of course we also would like to modify the distances and send it back to the filters. These values will be used to update the output of the filter.

Andrzej


-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 23 May 2016 14:58
To: Andrzej Peczak
Cc: ParaView
Subject: Re: [Paraview] Custom panel widget

> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.

There are several ways of skinning this cat. Can you elaborate of what exactly is your use-case? Do you want the default values for this double-vector-property (DVP) set using some values provided by the VTK filter, but allow user to override using UI?

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From ryan.abernathey at gmail.com  Thu May 26 10:47:33 2016
From: ryan.abernathey at gmail.com (Ryan Abernathey)
Date: Thu, 26 May 2016 10:47:33 -0400
Subject: [Paraview] texture dropdown disabled,
	can't set texture on polygonal mesh
Message-ID: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>

Hello,

I am trying to put a texture (png file) onto the surface of a polygonal
mesh.

I go to the properties tab, enabled Advanced, go to Miscellaneous...

Right after "pickable" is the texture dropdown. But it is disabled. I can't
figure out how to load my texture. See attached screenshot.

Thanks in advance for your help.

-Ryan

[image: Inline image 1]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/7175ea03/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/7175ea03/attachment-0001.png>

From dave.demarle at kitware.com  Thu May 26 10:52:24 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 26 May 2016 10:52:24 -0400
Subject: [Paraview] texture dropdown disabled,
 can't set texture on polygonal mesh
In-Reply-To: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
References: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
Message-ID: <CANjZAi8-MHs258L3kJNBChJzHEr-RE8EOKGceHVcWmXctJO7_A@mail.gmail.com>

Check the Information tab for a "Texture Coordinates" point aligned array.
If not present it would explain why you can't apply a Texture.
In that case, try the "Texture to Sphere" filter to generate some.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, May 26, 2016 at 10:47 AM, Ryan Abernathey <ryan.abernathey at gmail.com
> wrote:

> Hello,
>
> I am trying to put a texture (png file) onto the surface of a polygonal
> mesh.
>
> I go to the properties tab, enabled Advanced, go to Miscellaneous...
>
> Right after "pickable" is the texture dropdown. But it is disabled. I
> can't figure out how to load my texture. See attached screenshot.
>
> Thanks in advance for your help.
>
> -Ryan
>
> [image: Inline image 1]
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/6b7542e5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/6b7542e5/attachment.png>

From utkarsh.ayachit at kitware.com  Thu May 26 13:09:04 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 26 May 2016 13:09:04 -0400
Subject: [Paraview] Temporarily moratorium on new accounts for ParaView and
	VTK bug tracker
Message-ID: <CADHSJjC17in7dRUpZtEhGW-eQkUbpdmZkzFxZsddUPyXP4rzAQ@mail.gmail.com>

Folks,

Due to a recent spam-a-geddon, we are temporarily disabling new
account signing up on VTK/ParaView bug trackers while we figure out
how best to deal with this in the long term.

Thanks for patience,
VTK/ParaView Team

From nico.schloemer at gmail.com  Fri May 27 04:25:40 2016
From: nico.schloemer at gmail.com (=?UTF-8?Q?Nico_Schl=C3=B6mer?=)
Date: Fri, 27 May 2016 08:25:40 +0000
Subject: [Paraview] include could not find load file: vtkModuleAPI
Message-ID: <CAK6Z60fQb7tsPuJTJAJYjqzwCGEC2ZtmPbkPiXXLmkY0+g+RCw@mail.gmail.com>

When configuring ParaView with
```
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -Wno-dev -DBUILD_DOCUMENTATION=ON
-DCMAKE_INSTALL_RPATH=/usr/lib/paraview
-DCMAKE_INSTALL_RPATH_USE_LINK_PATH=OFF -DCMAKE_SKIP_RPATH=OFF
-DPARAVIEW_ENABLE_FFMPEG=ON -DPARAVIEW_ENABLE_WEB=OFF
-DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=OFF -DVTK_USE_MPEG2_ENCODER=OFF
-DVTK_USE_FFMPEG_ENCODER=ON -DVTK_USE_OGGTHEORA_ENCODER=ON
-DVTK_USE_SYSTEM_FREETYPE=ON -DVTK_USE_SYSTEM_GL2PS=ON
-DVTK_USE_SYSTEM_JPEG=ON -DVTK_USE_SYSTEM_JSONCPP=ON
-DVTK_USE_SYSTEM_NETCDF=ON -DVTK_USE_SYSTEM_GLEW=ON -DVTK_USE_SYSTEM_PNG=ON
-DVTK_USE_SYSTEM_OGGTHEORA=ON -DVTK_USE_SYSTEM_TIFF=ON
-DVTK_USE_SYSTEM_ZLIB=ON -DVTK_USE_SYSTEM_LIBXML2=ON
-DVTK_USE_SYSTEM_EXPAT=ON -DVTK_USE_SYSTEM_HDF5=ON
-DVTK_INSTALL_LIBRARY_DIR=lib/paraview
-DVTK_INSTALL_ARCHIVE_DIR=lib/paraview
-DVTK_INSTALL_INCLUDE_DIR=include/paraview
-DVTK_INSTALL_DATA_DIR=share/paraview
-DVTK_INSTALL_DOC_DIR=share/doc/paraview
-DVTK_INSTALL_PACKAGE_DIR=lib/cmake/paraview -DVTK_CUSTOM_LIBRARY_SUFFIX=
-DBUILD_EXAMPLES=OFF -DDOCUMENTATION_HTML_HELP=ON
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DBUILD_DOCUMENTATION=ON
-DPARAVIEW_USE_MPI=ON -DMPI_INCLUDE_PATH=/usr/include/mpi
-DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=ON
-DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON
-DPARAVIEW_BUILD_PLUGIN_MobileRemoteControl=OFF
-DEigen_DIR=/usr/include/eigen3 -DPARAVIEW_BUILD_WEB_DOCUMENTATION=ON
-DPARAVIEW_QT_VERSION=4
```
I'm getting the configuration error
```
CMake Error at CMakeLists.txt:618 (include): include could not find load
file: vtkModuleAPI
```
What might be the cause for this?

Cheers,
Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160527/9725b98b/attachment.html>

From mathieu.westphal at kitware.com  Fri May 27 04:37:36 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 27 May 2016 10:37:36 +0200
Subject: [Paraview] include could not find load file: vtkModuleAPI
In-Reply-To: <CAK6Z60fQb7tsPuJTJAJYjqzwCGEC2ZtmPbkPiXXLmkY0+g+RCw@mail.gmail.com>
References: <CAK6Z60fQb7tsPuJTJAJYjqzwCGEC2ZtmPbkPiXXLmkY0+g+RCw@mail.gmail.com>
Message-ID: <CAC2t4URZ+1epS7JyFPf7kwhrf4sOS-Dkccz44kCHRHwqZKo1WA@mail.gmail.com>

Hi

You probably forgot to "git submodule update --init"

Regards

Mathieu Westphal

On Fri, May 27, 2016 at 10:25 AM, Nico Schl?mer <nico.schloemer at gmail.com>
wrote:

> When configuring ParaView with
> ```
> cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -Wno-dev -DBUILD_DOCUMENTATION=ON
> -DCMAKE_INSTALL_RPATH=/usr/lib/paraview
> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=OFF -DCMAKE_SKIP_RPATH=OFF
> -DPARAVIEW_ENABLE_FFMPEG=ON -DPARAVIEW_ENABLE_WEB=OFF
> -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=OFF -DVTK_USE_MPEG2_ENCODER=OFF
> -DVTK_USE_FFMPEG_ENCODER=ON -DVTK_USE_OGGTHEORA_ENCODER=ON
> -DVTK_USE_SYSTEM_FREETYPE=ON -DVTK_USE_SYSTEM_GL2PS=ON
> -DVTK_USE_SYSTEM_JPEG=ON -DVTK_USE_SYSTEM_JSONCPP=ON
> -DVTK_USE_SYSTEM_NETCDF=ON -DVTK_USE_SYSTEM_GLEW=ON -DVTK_USE_SYSTEM_PNG=ON
> -DVTK_USE_SYSTEM_OGGTHEORA=ON -DVTK_USE_SYSTEM_TIFF=ON
> -DVTK_USE_SYSTEM_ZLIB=ON -DVTK_USE_SYSTEM_LIBXML2=ON
> -DVTK_USE_SYSTEM_EXPAT=ON -DVTK_USE_SYSTEM_HDF5=ON
> -DVTK_INSTALL_LIBRARY_DIR=lib/paraview
> -DVTK_INSTALL_ARCHIVE_DIR=lib/paraview
> -DVTK_INSTALL_INCLUDE_DIR=include/paraview
> -DVTK_INSTALL_DATA_DIR=share/paraview
> -DVTK_INSTALL_DOC_DIR=share/doc/paraview
> -DVTK_INSTALL_PACKAGE_DIR=lib/cmake/paraview -DVTK_CUSTOM_LIBRARY_SUFFIX=
> -DBUILD_EXAMPLES=OFF -DDOCUMENTATION_HTML_HELP=ON
> -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DBUILD_DOCUMENTATION=ON
> -DPARAVIEW_USE_MPI=ON -DMPI_INCLUDE_PATH=/usr/include/mpi
> -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=ON
> -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON
> -DPARAVIEW_BUILD_PLUGIN_MobileRemoteControl=OFF
> -DEigen_DIR=/usr/include/eigen3 -DPARAVIEW_BUILD_WEB_DOCUMENTATION=ON
> -DPARAVIEW_QT_VERSION=4
> ```
> I'm getting the configuration error
> ```
> CMake Error at CMakeLists.txt:618 (include): include could not find load
> file: vtkModuleAPI
> ```
> What might be the cause for this?
>
> Cheers,
> Nico
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160527/98e7a0e9/attachment.html>

From utkarsh.ayachit at kitware.com  Fri May 27 08:50:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 27 May 2016 08:50:47 -0400
Subject: [Paraview] Custom panel widget
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara>
Message-ID: <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com>

Andrzej,

Just to make sure I understand:

vtkCpCutter calculates slices aka contours on surface and also outputs
an array of  "max-distance"s. You want the user to be able to see
these values on the panel for this filter and then change them which
in turn affects some execution logic in vtkCpCutter. Is that correct?

Utkarsh

On Thu, May 26, 2016 at 7:30 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Hi Utkarsh
>
> Our use-case scenario is that we have our own filter based on vtkCpCutter (both vtkPolyData on the input and output port) . We use this filter to generate a set of slices on surface geometry. We then process the obtained contours with vtkPlotEdges. For each contour (slice) we would like to compute a scalar value, say max distance between two points in the contour and output the values to the scalar list widget. Of course we also would like to modify the distances and send it back to the filters. These values will be used to update the output of the filter.
>
> Andrzej
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 23 May 2016 14:58
> To: Andrzej Peczak
> Cc: ParaView
> Subject: Re: [Paraview] Custom panel widget
>
>> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.
>
> There are several ways of skinning this cat. Can you elaborate of what exactly is your use-case? Do you want the default values for this double-vector-property (DVP) set using some values provided by the VTK filter, but allow user to override using UI?
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by someone other than the recipient, for
> system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************

From apeczak at ara.co.uk  Fri May 27 11:58:18 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Fri, 27 May 2016 15:58:18 +0000
Subject: [Paraview] Custom panel widget
In-Reply-To: <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara> 
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com> 
 <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara> 
 <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B583E60@sooty3.win.ara>

Yes, this is what I want Utkarsh. 

The filter does not necessary has to output the distances on the output port (which I presumably would do by assigning a field array to the output geometry)  but I definitely would like them to display and modify in the panel widget to affect the execution logic of the filter.

Andrzej

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 27 May 2016 13:51
To: Andrzej Peczak
Cc: ParaView
Subject: Re: [Paraview] Custom panel widget

Andrzej,

Just to make sure I understand:

vtkCpCutter calculates slices aka contours on surface and also outputs an array of  "max-distance"s. You want the user to be able to see these values on the panel for this filter and then change them which in turn affects some execution logic in vtkCpCutter. Is that correct?
	
Utkarsh

On Thu, May 26, 2016 at 7:30 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Hi Utkarsh
>
> Our use-case scenario is that we have our own filter based on vtkCpCutter (both vtkPolyData on the input and output port) . We use this filter to generate a set of slices on surface geometry. We then process the obtained contours with vtkPlotEdges. For each contour (slice) we would like to compute a scalar value, say max distance between two points in the contour and output the values to the scalar list widget. Of course we also would like to modify the distances and send it back to the filters. These values will be used to update the output of the filter.
>
> Andrzej
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 23 May 2016 14:58
> To: Andrzej Peczak
> Cc: ParaView
> Subject: Re: [Paraview] Custom panel widget
>
>> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.
>
> There are several ways of skinning this cat. Can you elaborate of what exactly is your use-case? Do you want the default values for this double-vector-property (DVP) set using some values provided by the VTK filter, but allow user to override using UI?
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by 
> someone other than the recipient, for system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From apeczak at ara.co.uk  Fri May 27 12:50:18 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Fri, 27 May 2016 16:50:18 +0000
Subject: [Paraview] Python question
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B583E89@sooty3.win.ara>

One of my colleagues asked me to forward the question he has regarding use of a python script.

Andrzej

From: Andrea Ciarella 
Sent: 25 May 2016 16:10
To: Andrzej Peczak
Subject: Support request

Hi,

I create filter in Paraview using the python_filter_generator.py to create an xml file from a python script.
It works fine but I would like to have the ability to select the required variable from a drop list.
If I do it the modified xml causes Paraview to crash or the variable(Pressure) is not send to the python script. Do you know what I am getting wrong.
Please find attached the xml filter I am using

Thank you
Kind regards
Andrea Ciarella
Project Scientist 
Aerodynamics Capability
Aircraft Research Association Ltd

Tel: +44 (0) 1234 324632
Email: aciarella at ara.co.uk


**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BladeCp.zip
Type: application/x-zip-compressed
Size: 1440 bytes
Desc: BladeCp.zip
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160527/bbc98d20/attachment.bin>

From richard.c.angelini.civ at mail.mil  Fri May 27 14:08:53 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 27 May 2016 18:08:53 +0000
Subject: [Paraview] 5.0.1/Exodus Reader
Message-ID: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>

We?re seeing an issue with the Exodus reader in version 5.0.1.      We can read any particular Exodus dataset when running ParaView 5.0.1 locally ? read the data on the same machine where the client is running.   However, when we try to load any of the Exodus datasets in client-server mode,   ParaView 5.0.1 immediately crashes.    Crash happens when the client is run on either a Mac or Linux workstation.


Accepting connection(s): my_Mac:52994
ERROR: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 310
vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper. Aborting for debugging purposes.


Accepting connection(s): my_Linux:35227
ERROR: In /usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 310
vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting for debugging purposes.

This same dataset works in client-server mode using ParaView 4.3.1.
We seem to be able to load up other data types using ParaView 5.0.1 ? so far, it *appears* that only Exodus files are failing.


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160527/0de14f68/attachment.html>

From utkarsh.ayachit at kitware.com  Fri May 27 14:24:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 27 May 2016 14:24:53 -0400
Subject: [Paraview] 5.0.1/Exodus Reader
In-Reply-To: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>

Rick,

I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL and other to OpenGL2. You need them to match.

Utkarsh

On Fri, May 27, 2016 at 2:08 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> We?re seeing an issue with the Exodus reader in version 5.0.1.      We can
> read any particular Exodus dataset when running ParaView 5.0.1 locally ?
> read the data on the same machine where the client is running.   However,
> when we try to load any of the Exodus datasets in client-server mode,
> ParaView 5.0.1 immediately crashes.    Crash happens when the client is run
> on either a Mac or Linux workstation.
>
>
> Accepting connection(s): my_Mac:52994
> ERROR: In
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper. Aborting
> for debugging purposes.
>
>
> Accepting connection(s): my_Linux:35227
> ERROR: In
> /usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting for
> debugging purposes.
>
> This same dataset works in client-server mode using ParaView 4.3.1.
> We seem to be able to load up other data types using ParaView 5.0.1 ? so
> far, it *appears* that only Exodus files are failing.
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> _______________________________________________
> 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
>

From utkarsh.ayachit at kitware.com  Fri May 27 14:37:08 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 27 May 2016 14:37:08 -0400
Subject: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
In-Reply-To: <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>

> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?    Is there some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh

From richard.c.angelini.civ at mail.mil  Fri May 27 14:29:50 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 27 May 2016 18:29:50 +0000
Subject: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
In-Reply-To: <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
Message-ID: <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>


Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
pre-built Mac/Linux binaries were both built with OpenGL?    Is there some
way to check to see which OpenGL the client was built with?

________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Friday, May 27, 2016 at 2:24 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Rick,

I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL and other to OpenGL2. You need them to match.

Utkarsh

On Fri, May 27, 2016 at 2:08 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> We?re seeing an issue with the Exodus reader in version 5.0.1.      We
>can
> read any particular Exodus dataset when running ParaView 5.0.1 locally ?
> read the data on the same machine where the client is running.   However,
> when we try to load any of the Exodus datasets in client-server mode,
> ParaView 5.0.1 immediately crashes.    Crash happens when the client is
>run
> on either a Mac or Linux workstation.
>
>
> Accepting connection(s): my_Mac:52994
> ERROR: In
> 
>/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_o
>sx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImple
>mentation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper.
>Aborting
> for debugging purposes.
>
>
> Accepting connection(s): my_Linux:35227
> ERROR: In
> 
>/usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCo
>re/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting
>for
> debugging purposes.
>
> This same dataset works in client-server mode using ParaView 4.3.1.
> We seem to be able to load up other data types using ParaView 5.0.1 ? so
> far, it *appears* that only Exodus files are failing.
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>


From richard.c.angelini.civ at mail.mil  Fri May 27 14:42:09 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 27 May 2016 18:42:09 +0000
Subject: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
In-Reply-To: <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
Message-ID: <D36E0CEC.2B78C%Richard.C.Angelini.CIV@mail.mil>

Utkarsh - thanks for the info.  I believe that you?re right that the build
didn?t go as intended.
________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh


From svenkramer40 at gmail.com  Sat May 28 03:25:08 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Sat, 28 May 2016 09:25:08 +0200
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
 <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
 <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
Message-ID: <CAJZHu4Tv2nH6HGn8hV09jXy=dAKwAZ17Tnx-vTASCdWyhku_4A@mail.gmail.com>

Dear catalyst users,
I am sorry I cannot document the detailed steps how to set up the catalyst
to paraviewweb connection, bescause I am only experimenting how to get it
right at the moment. I have received several emails asking for guidance,
but I would like to ask you to pose your questions on this mailing list so
that others may contribute who have more experience.
Again, the essential step is happening in
pqCatalystConnectReaction::connect(). You don't need any Qt calls, but if
you follow that method, you find that a vtkSMLiveInsituManager is created,
which can be used for the further client-server communication. I could
receive a rendered image from catalyst in the web client, but a real "live"
connection is not yet working. I cannot answer questions like "How did you
do it", because my setup is a big mess, and I would have to go through all
steps again if I wanted to document this mess. If you describe instead what
you did and what doesn't work, we may be able to find a solution together.

If you study the contents of pv_web_catalyst.py and
Web/Javascript/Widgets/CatalystBrower it seems like all this has already
been solved one year ago.

Regards
Sven

2016-05-23 18:44 GMT+02:00 Sven Kramer <svenkramer40 at gmail.com>:

> Sure, I would share the code. But as I said, I haven't done anything more
> than wrapping pqCatalystConnectReaction::connect() and hacking several
> lines in the python rpc server, which are probably not done right.
> If it helps, I can try to reconstruct all the lines I have modified and
> clean up the stuff. However, you'll probably find a cleaner solution to
> invoke pqCatalystConnectReaction::connect() from the web client.
>
> Sven
>
> 2016-05-23 7:22 GMT+02:00 Sebastien Jourdain <
> sebastien.jourdain at kitware.com>:
>
>> Glad to ear that you managed to get something going. If you feel like
>> sharing your code, we might be able to provide some integration into
>> ParaView and/or ParaViewWeb proper.
>>
>> Seb
>>
>> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
>> wrote:
>>
>>> Thank you, Seb,
>>> it seems like I am getting it to work. There are still some difficulties
>>> because of my limited javascript experience, but with some quick&dirty
>>> workarounds I do have the Catalyst output displayed from ParaViewWeb. As
>>> you said, nothing else was required than wrapping the C functions in python.
>>>
>>> Thanks
>>> Sven
>>>
>>>
>>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com>:
>>>
>>>> Hi Sven,
>>>>
>>>> I am not aware on any specific developer documentation for Catalyst on
>>>> the ParaView side (but I haven't worked on that subject for years),
>>>> although Utkarsh or Andy might know.
>>>>
>>>> Usually looking at the code and redoing it in the Python world is what
>>>> is required, but as I said, I'm not sure of what it means since I don't
>>>> know that code anymore. ;-)
>>>>
>>>> For the timeframe, I can't tell (meaning I don't know), but we can
>>>> still try to help you or implement the missing piece via support contract
>>>> if that make sense on your end.
>>>>
>>>> Thanks,
>>>>
>>>> Seb
>>>>
>>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Seb,
>>>>> glad to read your answer. So the problem is not only that I was unable
>>>>> to find the relevant information.
>>>>>
>>>>> You say, you have not (yet) written the required code. Does "not
>>>>> (yet)" mean that it is on the agenda maybe within the next half year? Then
>>>>> I could find a workaround and look forward to the next Paraview updates.
>>>>>
>>>>> Otherwise I would try to work on the implementation for connecting
>>>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>>>> information? Those would be great to get started.
>>>>> My first attempt would be to "wrap" the functionality of
>>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>>>> make it available to the web client. Or are the necessary steps much more
>>>>> involved?
>>>>>
>>>>> Thank you
>>>>> Sven
>>>>>
>>>>>
>>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com>:
>>>>>
>>>>>> Hi Sven,
>>>>>>
>>>>>> Live catalyst connection require a specific socket connection to the
>>>>>> in-situ process with some special handling.
>>>>>> We did not (yet) wrote the Python code to perform that specific
>>>>>> action for ParaViewWeb so it could be triggered by the web client or
>>>>>> configured via an argument at launch time.
>>>>>> I don't see any reason why this couldn't work, but as for now, I also
>>>>>> don't know an easy step to do it without spending time doing it myself.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>> I am looking for the recommended steps how to display an in-situ
>>>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>>>
>>>>>>> After some efforts I am able to run ParaViewWeb successfully and I
>>>>>>> can view a Catalyst-enabled simulation in paraview.
>>>>>>>
>>>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>>>> pvserver as mentioned at the end of
>>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/
>>>>>>> and giving "--ds-host localhost --ds-port 11111" options to
>>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>>>> displayed on the web.
>>>>>>>
>>>>>>> Below you find the (not too detailed) steps I took to have a working
>>>>>>> solution for either Catalyst-enabled simulations or a working web
>>>>>>> visualizer:
>>>>>>>
>>>>>>> Test connection from Catalyst simulation to paraview:
>>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz
>>>>>>> (from http://www.paraview.org/download/)
>>>>>>> 2) Choose Catalyst->Connect in paraview
>>>>>>> 3) Run CFullExample from
>>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>>>> Success!
>>>>>>>
>>>>>>> Test ParaViewWeb:
>>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>>>> http://www.paraview.org/download/, extract in /data
>>>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>>>> Success!
>>>>>>>
>>>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Sven
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160528/f9b31659/attachment.html>

From cory.quammen at kitware.com  Sun May 29 10:47:05 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 29 May 2016 16:47:05 +0200
Subject: [Paraview] Python question
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B583E89@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B583E89@sooty3.win.ara>
Message-ID: <CAB5Fpx4MpJZOnaMDiTQdyJCd1efiogk+5z97VsUMEOjRkkqkvQ@mail.gmail.com>

Hi Andrzej,

The problem is in this section:

<StringVectorProperty
    name="Pressure"
    command="SetParameter"
    initial_string="Pressure"
    number_of_elements="5"
    element_types="0 0 0 0 2"
    animateable="1"
    default_values="0 0 0 0 0">

        <ArrayListDomain name="array_list"
                         attribute_type="Scalars"
                         input_domain_name="inputs_array">
          <RequiredProperties>
            <Property name="Input"
                      function="Input" />
          </RequiredProperties>
                  </ArrayListDomain>

<Documentation></Documentation></StringVectorProperty>

The "SetParameter" member function exists in the
vtkPythonProgrammableFilter, but with this declaration, you are saying
the member function takes 5 arguments. The crash occurs with an error
message saying

ERROR: In /Users/cory.quammen/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx,
line 390
vtkPVSessionCore (0x7fd583c415d0): Object type:
vtkPythonProgrammableFilter, could not find requested method:
"SetParameter"
or the method was called with incorrect arguments.
while processing

Message 0 = Invoke
  Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter (0x7fd58b623310)}
  Argument 1 = string_value {SetParameter}
  Argument 2 = string_value {Pressure}
  Argument 3 = int32_value {0}
  Argument 4 = int32_value {0}
  Argument 5 = int32_value {0}
  Argument 6 = int32_value {0}
  Argument 7 = string_value {}

Try this XML to replace the problematic XML

The problem is in this section:

<StringVectorProperty
    name="Pressure"
    command="SetParameter"
    initial_string="Pressure"
    number_of_elements="1"
    animateable="1"
    default_values="0">

        <ArrayListDomain name="array_list"
                         attribute_type="Scalars"
                         input_domain_name="inputs_array">
          <RequiredProperties>
            <Property name="Input"
                      function="Input" />
          </RequiredProperties>
                  </ArrayListDomain>

<Documentation>
</Documentation>
</StringVectorProperty>

This works in local tests for me.

HTH,
Cory

On Fri, May 27, 2016 at 6:50 PM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> One of my colleagues asked me to forward the question he has regarding use of a python script.
>
> Andrzej
>
> From: Andrea Ciarella
> Sent: 25 May 2016 16:10
> To: Andrzej Peczak
> Subject: Support request
>
> Hi,
>
> I create filter in Paraview using the python_filter_generator.py to create an xml file from a python script.
> It works fine but I would like to have the ability to select the required variable from a drop list.
> If I do it the modified xml causes Paraview to crash or the variable(Pressure) is not send to the python script. Do you know what I am getting wrong.
> Please find attached the xml filter I am using
>
> Thank you
> Kind regards
> Andrea Ciarella
> Project Scientist
> Aerodynamics Capability
> Aircraft Research Association Ltd
>
> Tel: +44 (0) 1234 324632
> Email: aciarella at ara.co.uk
>
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by someone other than the recipient, for
> system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From peterdebuchev at gmail.com  Sun May 29 13:09:12 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Sun, 29 May 2016 19:09:12 +0200
Subject: [Paraview] basics of paraview client server programming
Message-ID: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>

Dear Paraview programmers,
I am looking for some information about the basic principles of Paraviews
client-server model, the setup of client proxies and the communication
design.

I think that I have seen a chapter with a short introduction on these
topics some years ago. It was in one of the VTK books or in the Paraview
User's Guide. Now I cannot find this chapter again. Has it been removed in
the latest edition of these books? Or is it described in a different book
which I don't remember?

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160529/f830fbd3/attachment.html>

From michalwozniak at live.ca  Sun May 29 13:37:19 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Sun, 29 May 2016 13:37:19 -0400
Subject: [Paraview] Save State/adding custom property
Message-ID: <BLU180-W628B6367E1B9193BE06014AD440@phx.gbl>

Hi everyone,
I am trying to add a custom property to the state xml. 
For eg: 
I loaded object.stl and did a slice on it. Then, I saved the state and went to look at the XML. 
<ProxyCollection name="sources">      <Item id="4031" name="Slice1"/>      <Item id="3783" name="object.stl"/> </ProxyCollection>
I want to add an extra property called "user" 
<ProxyCollection name="sources">      <Item id="4031" name="Slice1" user="dev"/>      <Item id="3783" name="object.stl" user="basic"/> </ProxyCollection>
the extra property will be added during the saving of the state. I will be changing user property using a widget. I just want to know how to send the value of my variable user to be printed in the xml. 
I have been looking at a couple of classes  vtkSMStateVersionController, vtkSMStateLoader, vtkSMProperty. I got confused after looking at so many classes related to this.  Do i need to register my variable or send it using a specific function?Is there some documentation/tutorial for this?
thanks 
Michal Wozniak


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160529/4278a3f5/attachment.html>

From sebastien.jourdain at kitware.com  Sun May 29 18:40:17 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Sun, 29 May 2016 16:40:17 -0600
Subject: [Paraview] Connect ParaViewWeb to Catalyst
In-Reply-To: <CAJZHu4Tv2nH6HGn8hV09jXy=dAKwAZ17Tnx-vTASCdWyhku_4A@mail.gmail.com>
References: <CAJZHu4SGdhWKB4bALZL47ykt3LhHEhZuv20eyGs81aG2=35ctw@mail.gmail.com>
 <CABObKxf2brHQn9OV8SRjxyPq38nRJW+skB5Dcd43wcB1Dzde8w@mail.gmail.com>
 <CAJZHu4Q8y6iwB2ZV2za72w2uzuzODDkNp1JG8xCbjBuMHuQHdw@mail.gmail.com>
 <CABObKxekM5AM6jXXM6z5t=eWJL1GhiHL0femzB9F6Fwtc_OHqw@mail.gmail.com>
 <CAJZHu4TY5HRe1XYecKO9SQqNRTyNzgJb8tu=bSatF9sWFP_8ZQ@mail.gmail.com>
 <CABObKxc=s+DdsjD8615pMrpKxaYy6=mksANPmYvYFgh5Zkh8zQ@mail.gmail.com>
 <CAJZHu4QJ1G-BfUeE_OgbApxzpMc7zzYSj-+6hn-aF4UbQ9inDg@mail.gmail.com>
 <CAJZHu4Tv2nH6HGn8hV09jXy=dAKwAZ17Tnx-vTASCdWyhku_4A@mail.gmail.com>
Message-ID: <CABObKxdOPA8isPysOu1chH1YkObdsE2sYdaHL6vFPdFBaWtaGA@mail.gmail.com>

Hi Sven,

Thanks for your feedback. I'm even surprised to see my name on that Python
file. I definitely forget about it and I'm not even sure to know what it is
doing, but it is probably a good start.

Regrading your comment on ./VTK/Web/Javascript/Widgets/CatalystBrower/*, it
is not meant to be used for that purpose.
It was written to build some visualization tools of data generated via
Catalyst. (https://datascience.lanl.gov/data/papers/SC14.pdf)

If you want to see some progress on that web code you can look at
http://kitware.github.io/paraviewweb/ and
http://kitware.github.io/arctic-viewer/ for concrete application.

Seb

On Sat, May 28, 2016 at 1:25 AM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Dear catalyst users,
> I am sorry I cannot document the detailed steps how to set up the catalyst
> to paraviewweb connection, bescause I am only experimenting how to get it
> right at the moment. I have received several emails asking for guidance,
> but I would like to ask you to pose your questions on this mailing list so
> that others may contribute who have more experience.
> Again, the essential step is happening in
> pqCatalystConnectReaction::connect(). You don't need any Qt calls, but if
> you follow that method, you find that a vtkSMLiveInsituManager is created,
> which can be used for the further client-server communication. I could
> receive a rendered image from catalyst in the web client, but a real "live"
> connection is not yet working. I cannot answer questions like "How did you
> do it", because my setup is a big mess, and I would have to go through all
> steps again if I wanted to document this mess. If you describe instead what
> you did and what doesn't work, we may be able to find a solution together.
>
> If you study the contents of pv_web_catalyst.py and
> Web/Javascript/Widgets/CatalystBrower it seems like all this has already
> been solved one year ago.
>
> Regards
> Sven
>
> 2016-05-23 18:44 GMT+02:00 Sven Kramer <svenkramer40 at gmail.com>:
>
>> Sure, I would share the code. But as I said, I haven't done anything more
>> than wrapping pqCatalystConnectReaction::connect() and hacking several
>> lines in the python rpc server, which are probably not done right.
>> If it helps, I can try to reconstruct all the lines I have modified and
>> clean up the stuff. However, you'll probably find a cleaner solution to
>> invoke pqCatalystConnectReaction::connect() from the web client.
>>
>> Sven
>>
>> 2016-05-23 7:22 GMT+02:00 Sebastien Jourdain <
>> sebastien.jourdain at kitware.com>:
>>
>>> Glad to ear that you managed to get something going. If you feel like
>>> sharing your code, we might be able to provide some integration into
>>> ParaView and/or ParaViewWeb proper.
>>>
>>> Seb
>>>
>>> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkramer40 at gmail.com>
>>> wrote:
>>>
>>>> Thank you, Seb,
>>>> it seems like I am getting it to work. There are still some
>>>> difficulties because of my limited javascript experience, but with some
>>>> quick&dirty workarounds I do have the Catalyst output displayed from
>>>> ParaViewWeb. As you said, nothing else was required than wrapping the C
>>>> functions in python.
>>>>
>>>> Thanks
>>>> Sven
>>>>
>>>>
>>>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com>:
>>>>
>>>>> Hi Sven,
>>>>>
>>>>> I am not aware on any specific developer documentation for Catalyst on
>>>>> the ParaView side (but I haven't worked on that subject for years),
>>>>> although Utkarsh or Andy might know.
>>>>>
>>>>> Usually looking at the code and redoing it in the Python world is what
>>>>> is required, but as I said, I'm not sure of what it means since I don't
>>>>> know that code anymore. ;-)
>>>>>
>>>>> For the timeframe, I can't tell (meaning I don't know), but we can
>>>>> still try to help you or implement the missing piece via support contract
>>>>> if that make sense on your end.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Seb
>>>>>
>>>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkramer40 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello Seb,
>>>>>> glad to read your answer. So the problem is not only that I was
>>>>>> unable to find the relevant information.
>>>>>>
>>>>>> You say, you have not (yet) written the required code. Does "not
>>>>>> (yet)" mean that it is on the agenda maybe within the next half year? Then
>>>>>> I could find a workaround and look forward to the next Paraview updates.
>>>>>>
>>>>>> Otherwise I would try to work on the implementation for connecting
>>>>>> Paraviewweb to Catalyst output. Is there any developer documentation of
>>>>>> Catalysts "specific socket connection"? Or some general Catalyst developer
>>>>>> information? Those would be great to get started.
>>>>>> My first attempt would be to "wrap" the functionality of
>>>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and
>>>>>> make it available to the web client. Or are the necessary steps much more
>>>>>> involved?
>>>>>>
>>>>>> Thank you
>>>>>> Sven
>>>>>>
>>>>>>
>>>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com>:
>>>>>>
>>>>>>> Hi Sven,
>>>>>>>
>>>>>>> Live catalyst connection require a specific socket connection to the
>>>>>>> in-situ process with some special handling.
>>>>>>> We did not (yet) wrote the Python code to perform that specific
>>>>>>> action for ParaViewWeb so it could be triggered by the web client or
>>>>>>> configured via an argument at launch time.
>>>>>>> I don't see any reason why this couldn't work, but as for now, I
>>>>>>> also don't know an easy step to do it without spending time doing it myself.
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkramer40 at gmail.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> I am looking for the recommended steps how to display an in-situ
>>>>>>>> (live) Catalyst simulation through ParaViewWeb.
>>>>>>>>
>>>>>>>> After some efforts I am able to run ParaViewWeb successfully and I
>>>>>>>> can view a Catalyst-enabled simulation in paraview.
>>>>>>>>
>>>>>>>> I hope, it is also possible to show the live Catalyst output via
>>>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting a
>>>>>>>> pvserver as mentioned at the end of
>>>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/
>>>>>>>> and giving "--ds-host localhost --ds-port 11111" options to
>>>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be
>>>>>>>> displayed on the web.
>>>>>>>>
>>>>>>>> Below you find the (not too detailed) steps I took to have a
>>>>>>>> working solution for either Catalyst-enabled simulations or a working web
>>>>>>>> visualizer:
>>>>>>>>
>>>>>>>> Test connection from Catalyst simulation to paraview:
>>>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz
>>>>>>>> (from http://www.paraview.org/download/)
>>>>>>>> 2) Choose Catalyst->Connect in paraview
>>>>>>>> 3) Run CFullExample from
>>>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>>>>>> 4) Pipeline from CFullExample is shown in paraview.
>>>>>>>> Success!
>>>>>>>>
>>>>>>>> Test ParaViewWeb:
>>>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from
>>>>>>>> http://www.paraview.org/download/, extract in /data
>>>>>>>> 2) Run $ParaView_DIR/bin/pvpython
>>>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py --content
>>>>>>>> $ParaView_DIR/www  --data-dir /data --port 8080
>>>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/
>>>>>>>> Success!
>>>>>>>>
>>>>>>>> But how do I get Catalyst into the web visualizer? Is there any
>>>>>>>> example how to combine them? Anybody who can suggest the required steps?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Sven
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160529/c3e36f0a/attachment.html>

From utkarsh.ayachit at kitware.com  Mon May 30 08:10:48 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 30 May 2016 08:10:48 -0400
Subject: [Paraview] Save State/adding custom property
In-Reply-To: <BLU180-W628B6367E1B9193BE06014AD440@phx.gbl>
References: <BLU180-W628B6367E1B9193BE06014AD440@phx.gbl>
Message-ID: <CADHSJjB1KCoA52P3JQSrxO4U7_Lp6TTNw1N+ng+hvi38REOHXA@mail.gmail.com>

There's a preexisting feature called "annotation" that vtkSMProxy
supports via the following API. Seems to me that'd map well to what
you're trying to do with the "user" property.

void SetAnnotation (const char *key, const char *value)
const char * GetAnnotation (const char *key)
void RemoveAnnotation (const char *key)
void RemoveAllAnnotations ()
bool HasAnnotation (const char *key)
int GetNumberOfAnnotations ()
const char * GetAnnotationKeyAt (int index)

Utkarsh

On Sun, May 29, 2016 at 1:37 PM, michal wozniak <michalwozniak at live.ca> wrote:
> Hi everyone,
>
> I am trying to add a custom property to the state xml.
>
> For eg:
>
> I loaded object.stl and did a slice on it. Then, I saved the state and went
> to look at the XML.
>
> <ProxyCollection name="sources">
>       <Item id="4031" name="Slice1"/>
>       <Item id="3783" name="object.stl"/>
>  </ProxyCollection>
>
> I want to add an extra property called "user"
>
> <ProxyCollection name="sources">
>       <Item id="4031" name="Slice1" user="dev"/>
>       <Item id="3783" name="object.stl" user="basic"/>
>  </ProxyCollection>
>
> the extra property will be added during the saving of the state. I will be
> changing user property using a widget.
> I just want to know how to send the value of my variable user to be printed
> in the xml.
>
> I have been looking at a couple of classes  vtkSMStateVersionController,
> vtkSMStateLoader, vtkSMProperty.
> I got confused after looking at so many classes related to this.  Do i need
> to register my variable or send it using a specific function?
> Is there some documentation/tutorial for this?
>
> thanks
>
> Michal Wozniak
>
>
>
>
> _______________________________________________
> 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
>

From grothausmann.roman at mh-hannover.de  Tue May 31 07:59:08 2016
From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.)
Date: Tue, 31 May 2016 13:59:08 +0200
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <57444E8B.1070805@mh-hannover.de>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
 <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>
 <57431EAD.4010209@mh-hannover.de>
 <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>
 <CADHSJjDt+S-6FaYb71UA_aHKwX7X9zV8vZPZP4TenSX_Gj38cQ@mail.gmail.com>
 <57444E8B.1070805@mh-hannover.de>
Message-ID: <574D7C8C.1040305@mh-hannover.de>

Just a quick note that Your fix went into VTK after the newest VTK was synched 
into PV, so I had to do a pull in the VTK subdirectory of PV to get it.
Works like a charm now and together with X3dToX3dom.xslt yields a zoom-able HTML:
http://romangrothausmann.github.io/FacetAnalyser/demos/X3D/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.xhtml

On 24/05/16 14:52, Grothausmann, Roman Dr. wrote:
> Many, many thanks Utkarsh for that quick fix!
> Yes, You are right, my VTK test was using point data, so the problem didn't appear.
> Thanks again for the great support.
>
> On 23/05/16 19:08, Utkarsh Ayachit wrote:
>> Here's a fix for the same:
>>
>> https://gitlab.kitware.com/vtk/vtk/merge_requests/1517
>>
>> Utkarsh
>>
>> On Mon, May 23, 2016 at 11:42 AM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>> Ah okay. Looks like there's another bug with cell-data coloring and
>>> x3d. I've spotted the bug (I think) and am working on a fix. Not sure
>>> how this could have worked in VTK example, however. I'll send you a
>>> patch shortly.
>>>
>>> On Mon, May 23, 2016 at 11:15 AM, Grothausmann, Roman Dr.
>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>> Many thanks Utkarsh for Your quick reply.
>>>> Attached is an example VTP (generated by
>>>> https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.pvsm)
>>>>
>>>> coloured with KAAMS cat. on FacetIds (cell data) and then exported as X3D
>>>> from PV5. The PNG is a comparison view of PV and view3dscene.
>>>> The WebGL output (from make test) is great:
>>>> http://htmlpreview.github.io/?https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.html
>>>>
>>>>
>>>>
>>>> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>>>>
>>>>> And same with categorical colors. I did notice, however, it fails when
>>>>> coloring with "Field Data" arrays. Is that what you're seeing? That
>>>>> I'd expected would fail in VTK too. That's indeed a missing feature in
>>>>> the exporter.
>>>>>
>>>>> On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>>
>>>>>> Roman,
>>>>>>
>>>>>> Can you post an example? When I tried the same with a simple sphere
>>>>>> color by "Normals X", it seems to work as expected. I used
>>>>>> "view3dscene" to view the X3d file.
>>>>>>
>>>>>> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
>>>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>>>
>>>>>>> Dear mailing list members,
>>>>>>>
>>>>>>>
>>>>>>> When I export scenes to X3D then load the mesh into blender or a browser
>>>>>>> the
>>>>>>> mesh is colour wrong. The colours are there but apparently assigned to
>>>>>>> random cells/vertices. This happens with either PV5 or PV4, especially
>>>>>>> for
>>>>>>> category colouring. When using e.g. WebGL exporter all is fine.
>>>>>>> Is there anything to do special for exporting to X3D? When I use plain
>>>>>>> VTK,
>>>>>>> the exported colours seemed OK so far.
>>>>>>>
>>>>>>> Any help or hints are very much appreciated
>>>>>>> Roman
>>>>>>>
>>>>>>>
>>>>>>> On 04/12/14 15:34, Michael Nolde wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> works perfectly, thank you!
>>>>>>>>
>>>>>>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>>>>>>> View is not valid at the point you get it.
>>>>>>>>
>>>>>>>> from paraview.simple import *
>>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>>> source=Cone()
>>>>>>>> Show()
>>>>>>>> render=Render()
>>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>>> x3dExporter.SetView(render)
>>>>>>>> x3dExporter.Write()
>>>>>>>>
>>>>>>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__>
>>>>>>>> wrote:
>>>>>>>> Dear mailing list members,
>>>>>>>>
>>>>>>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>>>>>>> I tried to execute to code found in
>>>>>>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>>>>>>> (see below). It is executed without any errors, but no output file is
>>>>>>>> created.
>>>>>>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>>>>>>> What I want to achieve is to convert .ply files to .x3d via pvpython.
>>>>>>>> Could someone give me a hint?
>>>>>>>>
>>>>>>>> Thanks in advance,
>>>>>>>> Michael
>>>>>>>>
>>>>>>>> from paraview.simple import *
>>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>>> source=Cone()
>>>>>>>> view = GetActiveView()
>>>>>>>> Show(view)
>>>>>>>> render=Render()
>>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>>> x3dExporter.SetView(view)
>>>>>>>> x3dExporter.Write()
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Dr. Roman Grothausmann
>>>>>>>
>>>>>>> Tomographie und Digitale Bildverarbeitung
>>>>>>> Tomography and Digital Image Analysis
>>>>>>>
>>>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>>>>> Medizinische Hochschule Hannover
>>>>>>> Carl-Neuberg-Str. 1
>>>>>>> D-30625 Hannover
>>>>>>>
>>>>>>> Tel. +49 511 532-2900
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>
>>>>
>>>> --
>>>> Dr. Roman Grothausmann
>>>>
>>>> Tomographie und Digitale Bildverarbeitung
>>>> Tomography and Digital Image Analysis
>>>>
>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>> Medizinische Hochschule Hannover
>>>> Carl-Neuberg-Str. 1
>>>> D-30625 Hannover
>>>>
>>>> Tel. +49 511 532-2900
>

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-2900

From utkarsh.ayachit at kitware.com  Tue May 31 08:04:26 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 31 May 2016 08:04:26 -0400
Subject: [Paraview] X3DExporter false mesh colouring?
In-Reply-To: <574D7C8C.1040305@mh-hannover.de>
References: <548070F4.4070508@gmx.net> <5742E8E3.40800@mh-hannover.de>
 <CADHSJjB=zGd+piy0bQ_GUa-Hy=2_x9VMO0Q+iNQfaf_2ZahPfw@mail.gmail.com>
 <CADHSJjAjYLjSRaFJ5pihkpQTHmCxXo+YVt4C07SyP4NkQWxp7w@mail.gmail.com>
 <57431EAD.4010209@mh-hannover.de>
 <CADHSJjAvD=RVGz6e86BTndej23+1FYmrCptueNgzy96RnbYU4Q@mail.gmail.com>
 <CADHSJjDt+S-6FaYb71UA_aHKwX7X9zV8vZPZP4TenSX_Gj38cQ@mail.gmail.com>
 <57444E8B.1070805@mh-hannover.de> <574D7C8C.1040305@mh-hannover.de>
Message-ID: <CADHSJjB6MF=Ba7a2GQJ2pMFdRtAFxeBCjxSKuMQawKT8RMqL4g@mail.gmail.com>

Nice!

On Tue, May 31, 2016 at 7:59 AM, Grothausmann, Roman Dr.
<grothausmann.roman at mh-hannover.de> wrote:
> Just a quick note that Your fix went into VTK after the newest VTK was
> synched into PV, so I had to do a pull in the VTK subdirectory of PV to get
> it.
> Works like a charm now and together with X3dToX3dom.xslt yields a zoom-able
> HTML:
> http://romangrothausmann.github.io/FacetAnalyser/demos/X3D/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.xhtml
>
>
> On 24/05/16 14:52, Grothausmann, Roman Dr. wrote:
>>
>> Many, many thanks Utkarsh for that quick fix!
>> Yes, You are right, my VTK test was using point data, so the problem
>> didn't appear.
>> Thanks again for the great support.
>>
>> On 23/05/16 19:08, Utkarsh Ayachit wrote:
>>>
>>> Here's a fix for the same:
>>>
>>> https://gitlab.kitware.com/vtk/vtk/merge_requests/1517
>>>
>>> Utkarsh
>>>
>>> On Mon, May 23, 2016 at 11:42 AM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>
>>>> Ah okay. Looks like there's another bug with cell-data coloring and
>>>> x3d. I've spotted the bug (I think) and am working on a fix. Not sure
>>>> how this could have worked in VTK example, however. I'll send you a
>>>> patch shortly.
>>>>
>>>> On Mon, May 23, 2016 at 11:15 AM, Grothausmann, Roman Dr.
>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>
>>>>> Many thanks Utkarsh for Your quick reply.
>>>>> Attached is an example VTP (generated by
>>>>>
>>>>> https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.pvsm)
>>>>>
>>>>> coloured with KAAMS cat. on FacetIds (cell data) and then exported as
>>>>> X3D
>>>>> from PV5. The PNG is a comparison view of PV and view3dscene.
>>>>> The WebGL output (from make test) is great:
>>>>>
>>>>> http://htmlpreview.github.io/?https://github.com/romangrothausmann/FacetAnalyser/blob/master/demos/8faced-rhombic-dodecahedron_twinned_simp%2Bdef.html
>>>>>
>>>>>
>>>>>
>>>>> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>>>>>
>>>>>>
>>>>>> And same with categorical colors. I did notice, however, it fails when
>>>>>> coloring with "Field Data" arrays. Is that what you're seeing? That
>>>>>> I'd expected would fail in VTK too. That's indeed a missing feature in
>>>>>> the exporter.
>>>>>>
>>>>>> On Mon, May 23, 2016 at 10:06 AM, Utkarsh Ayachit
>>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Roman,
>>>>>>>
>>>>>>> Can you post an example? When I tried the same with a simple sphere
>>>>>>> color by "Normals X", it seems to work as expected. I used
>>>>>>> "view3dscene" to view the X3d file.
>>>>>>>
>>>>>>> On Mon, May 23, 2016 at 7:26 AM, Grothausmann, Roman Dr.
>>>>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Dear mailing list members,
>>>>>>>>
>>>>>>>>
>>>>>>>> When I export scenes to X3D then load the mesh into blender or a
>>>>>>>> browser
>>>>>>>> the
>>>>>>>> mesh is colour wrong. The colours are there but apparently assigned
>>>>>>>> to
>>>>>>>> random cells/vertices. This happens with either PV5 or PV4,
>>>>>>>> especially
>>>>>>>> for
>>>>>>>> category colouring. When using e.g. WebGL exporter all is fine.
>>>>>>>> Is there anything to do special for exporting to X3D? When I use
>>>>>>>> plain
>>>>>>>> VTK,
>>>>>>>> the exported colours seemed OK so far.
>>>>>>>>
>>>>>>>> Any help or hints are very much appreciated
>>>>>>>> Roman
>>>>>>>>
>>>>>>>>
>>>>>>>> On 04/12/14 15:34, Michael Nolde wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> works perfectly, thank you!
>>>>>>>>>
>>>>>>>>> On 03.12.2014 19:49, Sebastien Jourdain wrote:
>>>>>>>>> View is not valid at the point you get it.
>>>>>>>>>
>>>>>>>>> from paraview.simple import *
>>>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>>>> source=Cone()
>>>>>>>>> Show()
>>>>>>>>> render=Render()
>>>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>>>> x3dExporter.SetView(render)
>>>>>>>>> x3dExporter.Write()
>>>>>>>>>
>>>>>>>>> On Wed, Dec 3, 2014 at 10:01 AM, Michael Nolde <__mnolde at gmx.net__>
>>>>>>>>> wrote:
>>>>>>>>> Dear mailing list members,
>>>>>>>>>
>>>>>>>>> I have some trouble exporting a scene to a X3D file via pvpython.
>>>>>>>>> I tried to execute to code found in
>>>>>>>>>
>>>>>>>>> __http://public.kitware.com/pipermail/paraview/2012-May/024924.html__
>>>>>>>>> (see below). It is executed without any errors, but no output file
>>>>>>>>> is
>>>>>>>>> created.
>>>>>>>>> My Paraview version is 4.0.1 64-bit (on a Ubuntu 14.04 machine).
>>>>>>>>> What I want to achieve is to convert .ply files to .x3d via
>>>>>>>>> pvpython.
>>>>>>>>> Could someone give me a hint?
>>>>>>>>>
>>>>>>>>> Thanks in advance,
>>>>>>>>> Michael
>>>>>>>>>
>>>>>>>>> from paraview.simple import *
>>>>>>>>> exporters=servermanager.createModule("exporters")
>>>>>>>>> source=Cone()
>>>>>>>>> view = GetActiveView()
>>>>>>>>> Show(view)
>>>>>>>>> render=Render()
>>>>>>>>> x3dExporter=exporters.X3DExporter(FileName="foo.x3d")
>>>>>>>>> x3dExporter.SetView(view)
>>>>>>>>> x3dExporter.Write()
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview__
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Dr. Roman Grothausmann
>>>>>>>>
>>>>>>>> Tomographie und Digitale Bildverarbeitung
>>>>>>>> Tomography and Digital Image Analysis
>>>>>>>>
>>>>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>>>>>> Medizinische Hochschule Hannover
>>>>>>>> Carl-Neuberg-Str. 1
>>>>>>>> D-30625 Hannover
>>>>>>>>
>>>>>>>> Tel. +49 511 532-2900
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dr. Roman Grothausmann
>>>>>
>>>>> Tomographie und Digitale Bildverarbeitung
>>>>> Tomography and Digital Image Analysis
>>>>>
>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
>>>>> Medizinische Hochschule Hannover
>>>>> Carl-Neuberg-Str. 1
>>>>> D-30625 Hannover
>>>>>
>>>>> Tel. +49 511 532-2900
>>
>>
>
> --
> Dr. Roman Grothausmann
>
> Tomographie und Digitale Bildverarbeitung
> Tomography and Digital Image Analysis
>
> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
> Medizinische Hochschule Hannover
> Carl-Neuberg-Str. 1
> D-30625 Hannover
>
> Tel. +49 511 532-2900

From richard.c.angelini.civ at mail.mil  Tue May 31 08:09:47 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Tue, 31 May 2016 12:09:47 +0000
Subject: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
In-Reply-To: <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
Message-ID: <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>

Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
resolved the problem!


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh


From utkarsh.ayachit at kitware.com  Tue May 31 11:21:06 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 31 May 2016 11:21:06 -0400
Subject: [Paraview] Custom panel widget
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B583E60@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara>
 <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B583E60@sooty3.win.ara>
Message-ID: <CADHSJjDct6nAa=AEO8bSYrYMrpH4LPfa0zqS3o1Bm7MWJjAWhw@mail.gmail.com>

Andrzej,

Here's a possible approach:

Add a "information_only" property to the proxy to retrieve the values
for  max_distance computed by the filter. You can create a custom
SIProperty [1] subclass to support arbitrary API to get the values
from your filter and communicate that to the SMProperty. Your widget
that can explicitly monitor this property to update view of "current
values" as appropriate.

What I am not sure if whether the information_property will get
updates every time the filter re-executes, e.g. when time changes. If
it doesn't, we may have to explicitly monitor the
vtkCommand::UpdateDataEvent fired by the proxy and call
vtkSMProxy::UpdatePropertyInformation() explicitly.

[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSIProperty.html

On Fri, May 27, 2016 at 11:58 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Yes, this is what I want Utkarsh.
>
> The filter does not necessary has to output the distances on the output port (which I presumably would do by assigning a field array to the output geometry)  but I definitely would like them to display and modify in the panel widget to affect the execution logic of the filter.
>
> Andrzej
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 27 May 2016 13:51
> To: Andrzej Peczak
> Cc: ParaView
> Subject: Re: [Paraview] Custom panel widget
>
> Andrzej,
>
> Just to make sure I understand:
>
> vtkCpCutter calculates slices aka contours on surface and also outputs an array of  "max-distance"s. You want the user to be able to see these values on the panel for this filter and then change them which in turn affects some execution logic in vtkCpCutter. Is that correct?
>
> Utkarsh
>
> On Thu, May 26, 2016 at 7:30 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
>> Hi Utkarsh
>>
>> Our use-case scenario is that we have our own filter based on vtkCpCutter (both vtkPolyData on the input and output port) . We use this filter to generate a set of slices on surface geometry. We then process the obtained contours with vtkPlotEdges. For each contour (slice) we would like to compute a scalar value, say max distance between two points in the contour and output the values to the scalar list widget. Of course we also would like to modify the distances and send it back to the filters. These values will be used to update the output of the filter.
>>
>> Andrzej
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: 23 May 2016 14:58
>> To: Andrzej Peczak
>> Cc: ParaView
>> Subject: Re: [Paraview] Custom panel widget
>>
>>> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.
>>
>> There are several ways of skinning this cat. Can you elaborate of what exactly is your use-case? Do you want the default values for this double-vector-property (DVP) set using some values provided by the VTK filter, but allow user to override using UI?
>>
>> **********************************************************************
>> Please consider the environment. Only print this email if absolutely necessary.
>>
>> This email contains information that is private and confidential and is intended only for the addressee.
>> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
>> Note: All email sent to or from this address may be accessed by
>> someone other than the recipient, for system management and security reasons.
>> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
>> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>>
>> **********************************************************************
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by someone other than the recipient, for
> system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************

From utkarsh.ayachit at kitware.com  Tue May 31 11:39:28 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 31 May 2016 11:39:28 -0400
Subject: [Paraview] How to copy "global variable" data to a variable in
	Python
In-Reply-To: <35b5b937b4bb4217b610848852421c27@ES01AMSNLNT.srn.sandia.gov>
References: <35b5b937b4bb4217b610848852421c27@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjDzjHBCEU8Xj846TTL2T++6+_jxEY2uYtQGB7m_==dR_w@mail.gmail.com>

Alan,

I am not sure I follow, but attached is a script that fetches "global
arrays" to the client side so you can do whatever you want with it. Is
that what you're looking for?

Utkarsh

On Wed, May 18, 2016 at 9:52 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>
>
> If I want to get the numeric value of an "Annotate Global Variable" variable
> so that I can use it later in a python script, how do I do that? E.g. take
> the global variable, make it into a string, and display it as text
>
>
>
> Thanks,
>
>
>
> Alan
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fetch_global_data.py
Type: text/x-python
Size: 981 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160531/d1050f95/attachment.py>

From michalwozniak at live.ca  Tue May 31 11:50:35 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Tue, 31 May 2016 11:50:35 -0400
Subject: [Paraview] Save State/adding custom property
In-Reply-To: <CADHSJjB1KCoA52P3JQSrxO4U7_Lp6TTNw1N+ng+hvi38REOHXA@mail.gmail.com>
References: <BLU180-W628B6367E1B9193BE06014AD440@phx.gbl>,
 <CADHSJjB1KCoA52P3JQSrxO4U7_Lp6TTNw1N+ng+hvi38REOHXA@mail.gmail.com>
Message-ID: <BLU180-W1403BD7F1AB9AF20DCAAA4AD460@phx.gbl>

That's exactly what I was looking for.
thanks a lot for the great support !!!

> Date: Mon, 30 May 2016 08:10:48 -0400
> Subject: Re: [Paraview] Save State/adding custom property
> From: utkarsh.ayachit at kitware.com
> To: michalwozniak at live.ca
> CC: paraview at paraview.org
> 
> There's a preexisting feature called "annotation" that vtkSMProxy
> supports via the following API. Seems to me that'd map well to what
> you're trying to do with the "user" property.
> 
> void SetAnnotation (const char *key, const char *value)
> const char * GetAnnotation (const char *key)
> void RemoveAnnotation (const char *key)
> void RemoveAllAnnotations ()
> bool HasAnnotation (const char *key)
> int GetNumberOfAnnotations ()
> const char * GetAnnotationKeyAt (int index)
> 
> Utkarsh
> 
> On Sun, May 29, 2016 at 1:37 PM, michal wozniak <michalwozniak at live.ca> wrote:
> > Hi everyone,
> >
> > I am trying to add a custom property to the state xml.
> >
> > For eg:
> >
> > I loaded object.stl and did a slice on it. Then, I saved the state and went
> > to look at the XML.
> >
> > <ProxyCollection name="sources">
> >       <Item id="4031" name="Slice1"/>
> >       <Item id="3783" name="object.stl"/>
> >  </ProxyCollection>
> >
> > I want to add an extra property called "user"
> >
> > <ProxyCollection name="sources">
> >       <Item id="4031" name="Slice1" user="dev"/>
> >       <Item id="3783" name="object.stl" user="basic"/>
> >  </ProxyCollection>
> >
> > the extra property will be added during the saving of the state. I will be
> > changing user property using a widget.
> > I just want to know how to send the value of my variable user to be printed
> > in the xml.
> >
> > I have been looking at a couple of classes  vtkSMStateVersionController,
> > vtkSMStateLoader, vtkSMProperty.
> > I got confused after looking at so many classes related to this.  Do i need
> > to register my variable or send it using a specific function?
> > Is there some documentation/tutorial for this?
> >
> > thanks
> >
> > Michal Wozniak
> >
> >
> >
> >
> > _______________________________________________
> > 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
> >
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160531/cc8593a5/attachment.html>

From utkarsh.ayachit at kitware.com  Tue May 31 13:23:27 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 31 May 2016 13:23:27 -0400
Subject: [Paraview] ISAV2016: Call for Participation
Message-ID: <CADHSJjCnomO9mSq-46_SSTGThRRRFZXNizu_eYhnbRfVmyYe9A@mail.gmail.com>

Call for Participation: ISAV 2016
=========================

ISAV2016: In Situ Infrastructures for Enabling Extreme-Scale Analysis
and Visualization

In cooperation with SIGHPC and held in conjunction with SC16: The
International Conference on High Performance Computing, Networking,
Storage and Analysis, Salt Lake City, Utah, U.S.A.

Full-day Sunday November 13th, 2016

ISAV 2016 Web Site: http://vis.lbl.gov/Events/ISAV-2016/

Workshop Theme
------------------------

The considerable interest in the HPC community regarding in situ
analysis and visualization is  due to several factors. First is an I/O
cost savings, where data is analyzed/visualized while  being
generated, without first storing to a file system. Second is the
potential for increased  accuracy, where fine temporal sampling of
transient analysis might expose some complex behavior missed in coarse
temporal sampling. Third is the ability to use all available
resources, CPU?s and accelerators, in the computation of analysis
products.

The workshop brings together researchers, developers and practitioners
from industry, academia, and government laboratories developing,
applying, and deploying in situ methods in extreme-scale, high
performance computing. The goal is to present research findings,
lessons learned, and insights related to developing and applying in
situ methods and infrastructure across a range of science and
engineering applications in HPC environments; to discuss topics like
opportunities presented by new architectures, existing infrastructure
needs, requirements, and gaps, and experiences to foster and enable in
situ analysis and visualization; to serve as a ?center of gravity? for
researchers, practitioners, and users/consumers of in situ methods and
infrastructure in the HPC space.

Participation/Call for Papers and Oral Presentations
---------------------------------------------------------------------

We invite two types of submissions to ISAV 2016: (1) short, 4-page
papers that present research results, that identify opportunities or
challenges, and that present case studies/best practices for in situ
methods/infrastructure in the areas of data management, analysis and
visualization; (2) lightning presentation submission, consisting of a
1- or 2-page submission, for a brief oral presentation at the
workshop. Short papers will appear in the workshop proceedings and
will be invited to give an oral presentation of 15 to 20 minutes;
lightning round submissions that are invited to present at the
workshop will have author names and titles included as part of the
proceedings. Submissions of both types are welcome that fall within
one or more areas of interest, as follows:

Areas of interest for ISAV, include, but are not limited to:

In situ infrastructures
        * Current Systems: production quality, research prototypes
        * Opportunities
        * Gaps

System resources, hardware, and emerging architectures
        * Enabling Hardware
        * Hardware and architectures that provide opportunities for In situ
          processing, such as burst buffers, staging computations on I/O nodes,
          sharing cores within a node for both simulation and in situ processing

Methods/algorithms/applications/Case studies
        * Best practices
        * Analysis: feature detection, statistical methods, temporal methods,
          geometric methods
        * Visualization: information visualization, scientific
visualization, time-
          varying methods
        * Data reduction/compression
        * Examples/case studies of solving a specific science
challenge with in situ
          methods/infrastructure.

Simulation
        * Integration:data modeling, software-engineering
        * Resilience: error detection, fault recovery
        * Workflows for supporting complex in situ processing pipelines

Requirements
        * Preserve important elements
        * Significantly reduce the data size
        * Flexibility for post-processing exploration

Review Process
----------------------

All submissions will undergo a peer-review process consisting of three
reviews by experts in the field, and evaluated according to relevance
to the workshop theme, technical soundness, creativity, originality,
and impactfulness of method/results. Lightning round submissions will
be evaluated primarily for relevance to the workshop.

Submission Process
----------------------------

Authors are invited to submit papers of at most 4 pages in PDF format,
excluding references, and lightning presentations of at most 2 pages
in PDF format, excluding references. Papers should be formatted in the
ACM Proceedings Style (templates available at
https://www.acm.org/publications/proceedings-template) and submitted
via EasyChair (https://easychair.org/conferences/?conf=isav2016). No
changes to the margins, spacing, or font sizes as specified by the
style file are allowed.

Papers must be self-contained and provide the technical substance
required for the program committee to evaluate their contributions.
Submitted papers must be original work that has not appeared in and is
not under consideration for another conference or a journal. See the
ACM Prior Publication Policy for more details. Papers can be submitted
at https://easychair.org/conferences/?conf=isav2016.

Publication in proceedings, presentation at the workshop
---------------------------------------------------------------------------

All paper submissions that receive favorable reviews will be included
as part of the workshop proceedings, which will be published through
SIGHPC along with other SC16 workshop proceedings in the ACM Digital
Library and IEEE Xplore. Lightning round submissions will not be
included as part of the proceedings.

Subject to the constraints of workshop length, some subset of the
accepted publications will be invited to give a brief oral
presentation at the workshop. The exact number of such presentations
and their length will be determined after the review process has been
completed.

Timeline/Important Dates
-----------------------------------

        15 August 2016              Paper submission deadline
        15 September 2016        Author notification
        30 September 2016        Camera ready copy due
        15 October 2016             Final program posted to ISAV web page
        13 November 2016         ISAV 2016 workshop at SC16

From richard.c.angelini.civ at mail.mil  Tue May 31 16:07:49 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Tue, 31 May 2016 20:07:49 +0000
Subject: [Paraview] ParaView 5.0.1 on an older Mac
Message-ID: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>

I have the following message from one of my local ParaView users:

Following is the message I am getting with the Paraview 5 client on the Mac. It appears to work in spite of this warning.

Warning: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx, line 2856
vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant memory and performance impacts. Your hardware has been identified as vendor ATI Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and version 4.1 ATI-1.24.39

About this Mac has the following information about my system:
Graphics  ATI Radeon HD 5770 1024 MB


The user does not see this error running ParaView 4.x.x ? so ? presumably this warning message is related to OpenGL2 running on an older graphics card???    Is this something we should be worried about in the short-term?  I?m not sure how much longer this older Mac will be in service ? but will we run in to issues with OpenGL2 which will preclude it from working on these older systems?




________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160531/8dc9d959/attachment.html>

From mike.jackson at bluequartz.net  Tue May 31 16:31:52 2016
From: mike.jackson at bluequartz.net (Michael Jackson)
Date: Tue, 31 May 2016 16:31:52 -0400
Subject: [Paraview] ParaView 5.0.1 on an older Mac
In-Reply-To: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
References: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <574DF4B8.1080203@bluequartz.net>

Richard,
    You will get this warning/error message on any OS X machine using 
ATI/AMD graphics hardware running OS X 10.10 or earlier. OS X 10.11 
corrected an OpenGL driver issue that this error is reporting. It is 
down in the VTK stack. I do not know if we should be worried or not 
about the warning/error.

-- 
Mike Jackson  [mike.jackson at bluequartz.net]
> Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
> <mailto:richard.c.angelini.civ at mail.mil>
> May 31, 2016 at 4:07 PM
> I have the following message from one of my local ParaView users:
>
> Following is the message I am getting with the Paraview 5 client on 
> the Mac. It appears to work in spite of this warning.
>
> Warning: In 
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx, 
> line 2856
> vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug 
> in Apple-AMD hardware related to gl_PrimitiveID.  This may cause 
> significant memory and performance impacts. Your hardware has been 
> identified as vendor ATI Technologies Inc. with renderer of ATI Radeon 
> HD 5770 OpenGL Engine and version 4.1 ATI-1.24.39
>
> About this Mac has the following information about my system:
> *Graphics*  ATI Radeon HD 5770 1024 MB
>
>
> The user does not see this error running ParaView 4.x.x ? 
> so ? presumably this warning message is related to OpenGL2 running on 
> an older graphics card???    Is this something we should be worried 
> about in the short-term?  I?m not sure how much longer this older Mac 
> will be in service ? but will we run in to issues with OpenGL2 which 
> will preclude it from working on these older systems?
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160531/546954df/attachment.html>

From cory.quammen at kitware.com  Tue May 31 17:22:01 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 31 May 2016 23:22:01 +0200
Subject: [Paraview] ParaView 5.0.1 on an older Mac
In-Reply-To: <574DF4B8.1080203@bluequartz.net>
References: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
 <574DF4B8.1080203@bluequartz.net>
Message-ID: <CAB5Fpx5-ekgosFdP3HhPcSY9z71AdEECn3HPMNs53XA8RUjAgQ@mail.gmail.com>

Rick,

There is a test in VTK - vtkRenderingOpenGL2Cxx-TestAppleBug - that
will fail if the ATI bug workaround is used but not needed. If you
have VTK built with testing on on the old Mac system and this test
fails, we would know the bug workaround is not needed for this system
and we could suppress this warning in the VTK version that goes into
ParaView 5.1.

Thanks,
Cory

On Tue, May 31, 2016 at 10:31 PM, Michael Jackson
<mike.jackson at bluequartz.net> wrote:
> Richard,
>    You will get this warning/error message on any OS X machine using ATI/AMD
> graphics hardware running OS X 10.10 or earlier. OS X 10.11 corrected an
> OpenGL driver issue that this error is reporting. It is down in the VTK
> stack. I do not know if we should be worried or not about the warning/error.
>
> --
> Mike Jackson  [mike.jackson at bluequartz.net]
>
> Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> May 31, 2016 at 4:07 PM
> I have the following message from one of my local ParaView users:
>
> Following is the message I am getting with the Paraview 5 client on the Mac.
> It appears to work in spite of this warning.
>
> Warning: In
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx,
> line 2856
> vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in
> Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant
> memory and performance impacts. Your hardware has been identified as vendor
> ATI Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and
> version 4.1 ATI-1.24.39
>
> About this Mac has the following information about my system:
> Graphics  ATI Radeon HD 5770 1024 MB
>
>
> The user does not see this error running ParaView 4.x.x ? so ? presumably
> this warning message is related to OpenGL2 running on an older graphics
> card???    Is this something we should be worried about in the short-term?
> I?m not sure how much longer this older Mac will be in service ? but will we
> run in to issues with OpenGL2 which will preclude it from working on these
> older systems?
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From asaad.sellmann at rwth-aachen.de  Tue May  3 07:32:58 2016
From: asaad.sellmann at rwth-aachen.de (Sellmann, Kai Asaad)
Date: Tue, 03 May 2016 11:32:58 -0000
Subject: [Paraview] Visualizing load paths
Message-ID: <1462274379341.43274@rwth-aachen.de>

Dear people,

I am currently trying to find a way to visualize load paths with results from static finite element analysis within solid structures. For this FE-analysis I use Altairs software suite (Hypermesh/Optistruct/Hyperview).

>From reading several different publications I know that there is an easy way to visualize the load path with the attached file with the use of TecPlot.
I received the attached file from Herbert Moldenhauer who relys on D.W. Kellys methods for visulaizing the load path within structures.

It would really help a lot to get more information about the background of the stream tracer filters, because I am currently struggeling to format the input properly. As far as I know I need a field of vectors ("The dataset must contain a field array with 3 Components. An Array of vectors (point-centered) is required"), but with the attached file for example I am not able to use the stream tracer filter.

Your help would be greatly appreciated!!!
Thank you very much in advance!

Asaad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160503/572562f7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TecplotDataLoader.dat
Type: application/octet-stream
Size: 568583 bytes
Desc: TecplotDataLoader.dat
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160503/572562f7/attachment-0001.obj>

From lackodan at outlook.com  Tue May 24 14:06:51 2016
From: lackodan at outlook.com (D L)
Date: Tue, 24 May 2016 18:06:51 -0000
Subject: [Paraview] Error opening specific STL-files on specific computer
 ("unable to read point")
Message-ID: <DUB126-W836C7C7500CBA3C22FFF1CDD4F0@phx.gbl>

Hi everyone,

I've been using Paraview for a couple of years now and it's been great. However, I've now encountered a weird problem that I cannot solve. A couple of years ago, I used VTK (and Python) to automatically segment the skin layer surface out of MRI scans. I've always been able to view the resulting surface meshes in Paraview and other 3D visualization programs such as Meshlab. 

I would now like to work with this dataset again, but I cannot get the surfaces -which are stored as STL-files- to open on my computer. When I try to open them in Paraview (I've tried both 4.1.0 and 5.0.1), I get the following error:


ERROR: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/IO/Geometry/vtkSTLReader.cxx, line 461
vtkSTLReader (0x41dcc90): STLReader: error while reading file /media/daniel/Data/PhyT/Data/ICBM surfaces/F/MNI_0111/db_MNI_0111_scalp_final.stl at line 3: unable to read point.


ERROR: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x6045af0): Algorithm vtkFileSeriesReader(0x534fef0) returned failure for request: vtkInformation (0x4919ff0)
  Debug: Off
  Modified Time: 1061902
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  FROM_OUTPUT_PORT: 0
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0


When I try to open them in Meshlab, I get an error message about "Premature End of file". Other STL-files, however, do open. I'm working on Ubuntu 15.10 64-bit. At first I assumed that the STL-files had somehow all gotten corrupted, but they open perfectly on a colleague's computer (Paraview 5.0.0 running on OpenSuse) and on my Windows 8.1 laptop (both in Paraview 5.0.0 and in Meshlab 1.3.3).

I'm not sure what's wrong. Could anybody please offer some insight? 

I've attached an example file to this e-mail.

Kind regards,

Daniel 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160524/7c201685/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: db_MNI_0111_scalp_final.stl
Type: application/sla
Size: 14162390 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160524/7c201685/attachment-0001.stl>

From ryan.abernathey at gmail.com  Thu May 26 11:13:48 2016
From: ryan.abernathey at gmail.com (Ryan Abernathey)
Date: Thu, 26 May 2016 15:13:48 -0000
Subject: [Paraview] Fwd:  texture dropdown disabled,
 can't set texture on polygonal mesh
In-Reply-To: <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
References: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
 <CANjZAi8-MHs258L3kJNBChJzHEr-RE8EOKGceHVcWmXctJO7_A@mail.gmail.com>
 <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
Message-ID: <CAJAZx5CdOwkgbtzzS3AvUH_3VkYqLGMh+4tk-BaZ8pCk3MH7Zw@mail.gmail.com>

Thanks for the tip David!

I used the "Texture Map To Sphere" filter, which kind of worked. However,
the texture mapping is not happening correctly, as you can see from the
attached screenshot. The image is mangled.

Here is the image I am using:
http://eoimages.gsfc.nasa.gov/images/imagerecords/57000/57730/land_ocean_ice_2048.png

I also tried one with the coordinates shifted, as in this tutorial (
http://www.earthmodels.org/data-and-tools/topography/paraview-topography-by-texture-mapping),
but it didn't make a difference, still mangled.
http://www.earthmodels.org/data-and-tools/topography/texture_land_ocean_ice_8192.png

Do you have any suggestions on how to overcome this?

Thanks,
Ryan


[image: Inline image 1]

On Thu, May 26, 2016 at 10:52 AM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Check the Information tab for a "Texture Coordinates" point aligned array.
> If not present it would explain why you can't apply a Texture.
> In that case, try the "Texture to Sphere" filter to generate some.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, May 26, 2016 at 10:47 AM, Ryan Abernathey <
> ryan.abernathey at gmail.com> wrote:
>
>> Hello,
>>
>> I am trying to put a texture (png file) onto the surface of a polygonal
>> mesh.
>>
>> I go to the properties tab, enabled Advanced, go to Miscellaneous...
>>
>> Right after "pickable" is the texture dropdown. But it is disabled. I
>> can't figure out how to load my texture. See attached screenshot.
>>
>> Thanks in advance for your help.
>>
>> -Ryan
>>
>> [image: Inline image 1]
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/845a001a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/845a001a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot2.png
Type: image/png
Size: 754163 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/845a001a/attachment-0003.png>

From ryan.abernathey at gmail.com  Thu May 26 11:14:49 2016
From: ryan.abernathey at gmail.com (Ryan Abernathey)
Date: Thu, 26 May 2016 15:14:49 -0000
Subject: [Paraview] texture dropdown disabled,
 can't set texture on polygonal mesh
In-Reply-To: <CAJAZx5CdOwkgbtzzS3AvUH_3VkYqLGMh+4tk-BaZ8pCk3MH7Zw@mail.gmail.com>
References: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
 <CANjZAi8-MHs258L3kJNBChJzHEr-RE8EOKGceHVcWmXctJO7_A@mail.gmail.com>
 <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
 <CAJAZx5CdOwkgbtzzS3AvUH_3VkYqLGMh+4tk-BaZ8pCk3MH7Zw@mail.gmail.com>
Message-ID: <CAJAZx5C65p-dP4r0F9eMVMrmKSCyTt49Q3PnO_9C3Np93e=cuQ@mail.gmail.com>

To clarify, the problem is that the image is being "doubled", i.e. wrapped
twice around the sphere in a mirrored fashion.

This happens even if I resize the image to be 1x1 aspect ratio.

-Ryan

On Thu, May 26, 2016 at 11:13 AM, Ryan Abernathey <ryan.abernathey at gmail.com
> wrote:

> Thanks for the tip David!
>
> I used the "Texture Map To Sphere" filter, which kind of worked. However,
> the texture mapping is not happening correctly, as you can see from the
> attached screenshot. The image is mangled.
>
> Here is the image I am using:
>
> http://eoimages.gsfc.nasa.gov/images/imagerecords/57000/57730/land_ocean_ice_2048.png
>
> I also tried one with the coordinates shifted, as in this tutorial (
> http://www.earthmodels.org/data-and-tools/topography/paraview-topography-by-texture-mapping),
> but it didn't make a difference, still mangled.
>
> http://www.earthmodels.org/data-and-tools/topography/texture_land_ocean_ice_8192.png
>
> Do you have any suggestions on how to overcome this?
>
> Thanks,
> Ryan
>
>
> [image: Inline image 1]
>
> On Thu, May 26, 2016 at 10:52 AM, David E DeMarle <
> dave.demarle at kitware.com> wrote:
>
>> Check the Information tab for a "Texture Coordinates" point aligned
>> array. If not present it would explain why you can't apply a Texture.
>> In that case, try the "Texture to Sphere" filter to generate some.
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Thu, May 26, 2016 at 10:47 AM, Ryan Abernathey <
>> ryan.abernathey at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am trying to put a texture (png file) onto the surface of a polygonal
>>> mesh.
>>>
>>> I go to the properties tab, enabled Advanced, go to Miscellaneous...
>>>
>>> Right after "pickable" is the texture dropdown. But it is disabled. I
>>> can't figure out how to load my texture. See attached screenshot.
>>>
>>> Thanks in advance for your help.
>>>
>>> -Ryan
>>>
>>> [image: Inline image 1]
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f9104793/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot2.png
Type: image/png
Size: 754163 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f9104793/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f9104793/attachment-0003.png>

From dave.demarle at kitware.com  Thu May 26 11:16:36 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 26 May 2016 15:16:36 -0000
Subject: [Paraview] texture dropdown disabled,
 can't set texture on polygonal mesh
In-Reply-To: <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
References: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
 <CANjZAi8-MHs258L3kJNBChJzHEr-RE8EOKGceHVcWmXctJO7_A@mail.gmail.com>
 <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
Message-ID: <CANjZAi-Z6WU1DcYcw_5sbkAtOr433zFUKv8jz78t86tfBca=-Q@mail.gmail.com>

uncheck "Prevent seam" on the T2S filter.

note: cc'ing paraview list back in so all can contribute/benefit from the
discussion.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, May 26, 2016 at 11:08 AM, Ryan Abernathey <ryan.abernathey at gmail.com
> wrote:

> Thanks for the tip David!
>
> I used the "Texture Map To Sphere" filter, which kind of worked. However,
> the texture mapping is not happening correctly, as you can see from the
> attached screenshot. The image is mangled.
>
> Here is the image I am using:
>
> http://eoimages.gsfc.nasa.gov/images/imagerecords/57000/57730/land_ocean_ice_2048.png
>
> I also tried one with the coordinates shifted, as in this tutorial (
> http://www.earthmodels.org/data-and-tools/topography/paraview-topography-by-texture-mapping),
> but it didn't make a difference, still mangled.
>
> http://www.earthmodels.org/data-and-tools/topography/texture_land_ocean_ice_8192.png
>
> Do you have any suggestions on how to overcome this?
>
> Thanks,
> Ryan
>
>
> [image: Inline image 1]
>
> On Thu, May 26, 2016 at 10:52 AM, David E DeMarle <
> dave.demarle at kitware.com> wrote:
>
>> Check the Information tab for a "Texture Coordinates" point aligned
>> array. If not present it would explain why you can't apply a Texture.
>> In that case, try the "Texture to Sphere" filter to generate some.
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Thu, May 26, 2016 at 10:47 AM, Ryan Abernathey <
>> ryan.abernathey at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am trying to put a texture (png file) onto the surface of a polygonal
>>> mesh.
>>>
>>> I go to the properties tab, enabled Advanced, go to Miscellaneous...
>>>
>>> Right after "pickable" is the texture dropdown. But it is disabled. I
>>> can't figure out how to load my texture. See attached screenshot.
>>>
>>> Thanks in advance for your help.
>>>
>>> -Ryan
>>>
>>> [image: Inline image 1]
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f2484eae/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot2.png
Type: image/png
Size: 754163 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f2484eae/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/f2484eae/attachment-0003.png>

From ryan.abernathey at gmail.com  Thu May 26 11:26:29 2016
From: ryan.abernathey at gmail.com (Ryan Abernathey)
Date: Thu, 26 May 2016 15:26:29 -0000
Subject: [Paraview] texture dropdown disabled,
 can't set texture on polygonal mesh
In-Reply-To: <CANjZAi-Z6WU1DcYcw_5sbkAtOr433zFUKv8jz78t86tfBca=-Q@mail.gmail.com>
References: <CAJAZx5BNN8=xDGCo38OVDWATQzyUDtmoKcQ8mbeEXPpFkxFZBA@mail.gmail.com>
 <CANjZAi8-MHs258L3kJNBChJzHEr-RE8EOKGceHVcWmXctJO7_A@mail.gmail.com>
 <CAJAZx5AEc9Q71VHbnft3XMJyHVrtXQqpo6F+pRG99Cj=QCQ82A@mail.gmail.com>
 <CANjZAi-Z6WU1DcYcw_5sbkAtOr433zFUKv8jz78t86tfBca=-Q@mail.gmail.com>
Message-ID: <CAJAZx5AKmqXum5VEdPifMzLAKGSw9u0Q2jbbcKh_+Xjdc-_uOg@mail.gmail.com>

Thanks so much! It works!

On Thu, May 26, 2016 at 11:16 AM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> uncheck "Prevent seam" on the T2S filter.
>
> note: cc'ing paraview list back in so all can contribute/benefit from the
> discussion.
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Thu, May 26, 2016 at 11:08 AM, Ryan Abernathey <
> ryan.abernathey at gmail.com> wrote:
>
>> Thanks for the tip David!
>>
>> I used the "Texture Map To Sphere" filter, which kind of worked. However,
>> the texture mapping is not happening correctly, as you can see from the
>> attached screenshot. The image is mangled.
>>
>> Here is the image I am using:
>>
>> http://eoimages.gsfc.nasa.gov/images/imagerecords/57000/57730/land_ocean_ice_2048.png
>>
>> I also tried one with the coordinates shifted, as in this tutorial (
>> http://www.earthmodels.org/data-and-tools/topography/paraview-topography-by-texture-mapping),
>> but it didn't make a difference, still mangled.
>>
>> http://www.earthmodels.org/data-and-tools/topography/texture_land_ocean_ice_8192.png
>>
>> Do you have any suggestions on how to overcome this?
>>
>> Thanks,
>> Ryan
>>
>>
>> [image: Inline image 1]
>>
>> On Thu, May 26, 2016 at 10:52 AM, David E DeMarle <
>> dave.demarle at kitware.com> wrote:
>>
>>> Check the Information tab for a "Texture Coordinates" point aligned
>>> array. If not present it would explain why you can't apply a Texture.
>>> In that case, try the "Texture to Sphere" filter to generate some.
>>>
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 21 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-881-4909
>>>
>>> On Thu, May 26, 2016 at 10:47 AM, Ryan Abernathey <
>>> ryan.abernathey at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am trying to put a texture (png file) onto the surface of a polygonal
>>>> mesh.
>>>>
>>>> I go to the properties tab, enabled Advanced, go to Miscellaneous...
>>>>
>>>> Right after "pickable" is the texture dropdown. But it is disabled. I
>>>> can't figure out how to load my texture. See attached screenshot.
>>>>
>>>> Thanks in advance for your help.
>>>>
>>>> -Ryan
>>>>
>>>> [image: Inline image 1]
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/244975ea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot2.png
Type: image/png
Size: 754163 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/244975ea/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraview_screenshot.png
Type: image/png
Size: 206963 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160526/244975ea/attachment-0003.png>

From stephane at fujielectric.com  Thu May 19 19:37:07 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Thu, 19 May 2016 23:37:07 -0000
Subject: [Paraview] paraview superbuild on Win7 with ninja/vs2013/qt4/mpi
In-Reply-To: <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
References: <CADLMsL4YfC63L-sTCFmfYd64y+jTq5Wkgnjhv-wH=qnY+JnskQ@mail.gmail.com>
 <CADLMsL5giUL6ST+-2n++e2SPr7DS6B3PfvHHkd6+Xxm0pqqJig@mail.gmail.com>
 <CACJ=gTje+gMGBeZGW96AcOyoG9syowAD4VmTEasosG6WHXUW3A@mail.gmail.com>
Message-ID: <CADLMsL5W57g_gjro=UkZ8T+Sm31rE8TyjbESGg4eF=8hBfSDaw@mail.gmail.com>

Hello,
As stated in my previous e-mail, building ninja from vs2013did not solve
the problem. I also noticed that re-sending the ninja command after the
"subcommand failed" kind of resume the process to some point. I've attached
the corresponding log files.

Is it possible to build it with Visual Studio IDE instead of Ninja?

????
??????? ?????
????-???? ?????
????

????????
?210-9530??????????1-1
TEL 044-329-2155 FAX 044-329-2394

On Thu, May 19, 2016 at 4:42 PM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Hello,
>
> Did you compiled ninja using your VS2013?
> Do you start ninja from a Visual Studio 2013 command line (so that cmake
> can find VS compiler in the environment)?
>
> Regards,
>
>
>
> *Joachim Pouderoux*
>
> *PhD, Technical Expert*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2016-05-19 7:49 GMT+02:00 stephane???? ???? <stephane at fujielectric.com>:
>
>> Hello,
>>
>> I am sending a Log of the building process
>>
>> Ndong-Mefane Stephane, Dr.Eng
>> Basic Design Sec.
>> Steam Turbine Dept.
>> Kawasaki Factory
>>
>> Fuji Electric Co., Ltd
>> 1-1, Tanabeshinden, Kawasaki-ku,
>> Kawasaki-city 210-9530, Japan
>> Phone: +81-44-329-2155
>> Fax: +81-44-329-2394
>>
>>
>> On Thu, May 19, 2016 at 1:54 PM, stephane???? ???? <
>> stephane at fujielectric.com> wrote:
>>
>>> Hello,
>>> I've been trying to "superbuild" paraview 5.0 on Win7 without success.
>>> I keep getting two errors:
>>> 1) the first one is related to szip at the beginning of the build
>>> 2) the second and last one is  ninja: build stopped: subcommand failed
>>>
>>> nothing else.
>>> I really need some help please...
>>>
>>> Ndong-Mefane Stephane, Dr.Eng
>>> Basic Design Sec.
>>> Steam Turbine Dept.
>>> Kawasaki Factory
>>>
>>> Fuji Electric Co., Ltd
>>> 1-1, Tanabeshinden, Kawasaki-ku,
>>> Kawasaki-city 210-9530, Japan
>>> Phone: +81-44-329-2155
>>> Fax: +81-44-329-2394
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160519/134d9632/attachment.html>
-------------- next part --------------
[1/123] Creating directories for 'mpi'
[2/123] Creating directories for 'qt4'
[3/123] Creating directories for 'tbb'
[4/123] Creating directories for 'szip'
[5/123] Creating directories for 'python'
[6/123] Creating directories for 'zlib'
[7/123] No download step for 'mpi'
[8/123] No download step for 'zlib'
[9/123] No patch step for 'mpi'
[10/123] No update step for 'mpi'
[11/123] No patch step for 'zlib'
[12/123] No update step for 'zlib'
[13/123] No configure step for 'mpi'
[14/123] No build step for 'mpi'
[15/123] No install step for 'mpi'
[16/123] Completed 'mpi'
[17/123] Performing download step (download, verify and extract) for 'szip'
-- downloading...

     src='http://paraview.org/files/dependencies/szip-2.1.tar.gz'

     dst='C:/superbuild/downloads/szip-2.1.tar.gz'

     timeout='none'

-- [download 100% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 88% complete]

-- [download 92% complete]

-- [download 96% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/szip-2.1.tar.gz'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/szip-2.1.tar.gz'

     dst='C:/superbuild/szip/src/szip'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[18/123] No update step for 'szip'
[19/123] Performing patch_fix_install step for 'szip'
[20/123] Performing patch step for 'szip'
[21/123] Performing configure step for 'szip'
FAILED: szip/src/szip-stamp/szip-configure 
cmd.exe /C "cd /D C:\superbuild\szip\src\szip-build && "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=C:/superbuild/install -DCMAKE_PREFIX_PATH:PATH=C:/superbuild/install "-DCMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3" "-DCMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc" -DCMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64 -DCMAKE_BUILD_TYPE:STRING=Debug "-DCMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" -GNinja C:/superbuild/szip/src/szip && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/szip/src/szip-stamp/szip-configure"
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

[22/123] Performing download step (download, verify and extract) for 'tbb'
-- downloading...

     src='http://www.paraview.org/files/dependencies/tbb44_20150728oss_win.zip'

     dst='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

     timeout='none'

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/tbb44_20150728oss_win.zip'

     dst='C:/superbuild/tbb/src/tbb'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[23/123] Performing download step (download, verify and extract) for 'python'
-- downloading...

     src='http://www.paraview.org/files/dependencies/python+deps.tar.bz2'

     dst='C:/superbuild/downloads/python+deps.tar.bz2'

     timeout='none'

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/python+deps.tar.bz2'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/python+deps.tar.bz2'

     dst='C:/superbuild/python/src/python'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

[24/123] Performing download step (download, verify and extract) for 'qt4'
-- downloading...

     src='http://paraview.org/files/dependencies/qt-everywhere-opensource-src-4.8.4.tar.gz'

     dst='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

     timeout='none'

-- [download 100% complete]

-- [download 0% complete]

-- [download 1% complete]

-- [download 2% complete]

-- [download 3% complete]

-- [download 4% complete]

-- [download 5% complete]

-- [download 6% complete]

-- [download 7% complete]

-- [download 8% complete]

-- [download 9% complete]

-- [download 10% complete]

-- [download 11% complete]

-- [download 12% complete]

-- [download 13% complete]

-- [download 14% complete]

-- [download 15% complete]

-- [download 16% complete]

-- [download 17% complete]

-- [download 18% complete]

-- [download 19% complete]

-- [download 20% complete]

-- [download 21% complete]

-- [download 22% complete]

-- [download 23% complete]

-- [download 24% complete]

-- [download 25% complete]

-- [download 26% complete]

-- [download 27% complete]

-- [download 28% complete]

-- [download 29% complete]

-- [download 30% complete]

-- [download 31% complete]

-- [download 32% complete]

-- [download 33% complete]

-- [download 34% complete]

-- [download 35% complete]

-- [download 36% complete]

-- [download 37% complete]

-- [download 38% complete]

-- [download 39% complete]

-- [download 40% complete]

-- [download 41% complete]

-- [download 42% complete]

-- [download 43% complete]

-- [download 44% complete]

-- [download 45% complete]

-- [download 46% complete]

-- [download 47% complete]

-- [download 48% complete]

-- [download 49% complete]

-- [download 50% complete]

-- [download 51% complete]

-- [download 52% complete]

-- [download 53% complete]

-- [download 54% complete]

-- [download 55% complete]

-- [download 56% complete]

-- [download 57% complete]

-- [download 58% complete]

-- [download 59% complete]

-- [download 60% complete]

-- [download 61% complete]

-- [download 62% complete]

-- [download 63% complete]

-- [download 64% complete]

-- [download 65% complete]

-- [download 66% complete]

-- [download 67% complete]

-- [download 68% complete]

-- [download 69% complete]

-- [download 70% complete]

-- [download 71% complete]

-- [download 72% complete]

-- [download 73% complete]

-- [download 74% complete]

-- [download 75% complete]

-- [download 76% complete]

-- [download 77% complete]

-- [download 78% complete]

-- [download 79% complete]

-- [download 80% complete]

-- [download 81% complete]

-- [download 82% complete]

-- [download 83% complete]

-- [download 84% complete]

-- [download 85% complete]

-- [download 86% complete]

-- [download 87% complete]

-- [download 88% complete]

-- [download 89% complete]

-- [download 90% complete]

-- [download 91% complete]

-- [download 92% complete]

-- [download 93% complete]

-- [download 94% complete]

-- [download 95% complete]

-- [download 96% complete]

-- [download 97% complete]

-- [download 98% complete]

-- [download 99% complete]

-- [download 100% complete]

-- downloading... done

-- verifying file...

     file='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

-- verifying file... done

-- extracting...

     src='C:/superbuild/downloads/qt-everywhere-opensource-src-4.8.4.tar.gz'

     dst='C:/superbuild/qt4/src/qt4'

-- extracting... [tar xfz]

-- extracting... [analysis]

-- extracting... [rename]

-- extracting... [clean up]

-- extracting... done

ninja: build stopped: subcommand failed.
-------------- next part --------------
[1/100] No patch step for 'tbb'
[2/100] No patch step for 'python'
[3/100] No update step for 'python'
[4/100] No patch step for 'qt4'
[5/100] No update step for 'qt4'
[6/100] No update step for 'tbb'
[7/100] Performing configure step for 'szip'
FAILED: szip/src/szip-stamp/szip-configure 
cmd.exe /C "cd /D C:\superbuild\szip\src\szip-build && "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=C:/superbuild/install -DCMAKE_PREFIX_PATH:PATH=C:/superbuild/install "-DCMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3" "-DCMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc" -DCMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64 -DCMAKE_BUILD_TYPE:STRING=Debug "-DCMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" -GNinja C:/superbuild/szip/src/szip && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/szip/src/szip-stamp/szip-configure"
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

[8/100] No configure step for 'python'
[9/100] No configure step for 'tbb'
[10/100] Performing configure step for 'qt4'


This is the Qt for Windows Open Source Edition.



You have already accepted the terms of the license.



Environment:

    INCLUDE=


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\ATLMFC\INCLUDE


      C:\Program Files (x86)\Windows Kits\8.1\include\shared


      C:\Program Files (x86)\Windows Kits\8.1\include\um


      C:\Program Files (x86)\Windows Kits\8.1\include\winrt


      C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include

    LIB=


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\LIB\amd64


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\ATLMFC\LIB\amd64


      C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x64


      

    PATH=


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow


      C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\


      C:\Program Files (x86)\MSBuild\12.0\bin


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\x86_amd64


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools


      C:\Windows\Microsoft.NET\Framework\v4.0.30319


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages


      C:\Program Files (x86)\HTML Help Workshop


      C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools


      C:\Program Files (x86)\Windows Kits\8.1\bin\x86


      C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\


      C:\ProgramData\Oracle\Java\javapath


      C:\Perl64\site\bin


      C:\Perl64\bin


      C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\


      C:\ptc2\MKSTOO~1\bin64


      C:\ptc2\MKSTOO~1\bin


      C:\ptc2\MKSTOO~1\bin\X11


      C:\ptc2\MKSTOO~1\mksnt


      C:\KST\STUTY


      C:\mchelix\HDD


      C:\MCHelix\HDTools\Mcserver


      C:\MCHelix\HDTools


      C:\Program Files (x86)\Intel\iCLS Client\


      C:\Program Files\Intel\iCLS Client\


      C:\Windows\system32


      C:\Windows


      C:\Windows\System32\Wbem


      C:\Windows\System32\WindowsPowerShell\v1.0\


      C:\Program Files\Intel\Intel(R) Management Engine Components\DAL


      C:\Program Files\Intel\Intel(R) Management Engine Components\IPT


      C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL


      C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT


      C:\Dakota\bin


      C:\Dakota\test


      C:\ptc\ANSYS_Inc\v150\CFX\bin


      C:\Perl64\bin\perl.exe


      C:\Program Files (x86)\Microsoft Office\Office14\Library\xlStm32.xll


      C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\


      C:\Program Files\Microsoft SQL Server\110\Tools\Binn\


      C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\


      C:\Program Files\Microsoft SQL Server\120\Tools\Binn\


      C:\Program Files (x86)\CMake\bin\cmake.exe


      C:\Anaconda2


      C:\Anaconda2\Scripts


      C:\Anaconda2\Library\bin


      C:\Cast3M\PCW_15\bin


      C:\Tcl\bin


      C:\Strawberry\c\bin


      C:\Strawberry\perl\site\bin


      C:\Strawberry\perl\bin


      C:\Program Files (x86)\CMake\bin


      C:\Program Files\Git\cmd


      p??


      C:\MikTex\miktex\bin\x64\

You are licensed to use this software under the terms of the GNU GPL version 3.You are licensed to use this software under the terms of the Lesser GNU LGPL version 2.1.

See C:/superbuild/qt4/src/qt43



 or C:/superbuild/qt4/src/qt4L



Configuration:

    minimal-config


    small-config


    medium-config


    large-config


    full-config


    release

Qt Configuration:

    release


    zlib


    png


    accessibility


    qt3support


    opengl


    s60


    ipv6


    xmlpatterns


    native-gestures


    svg


    concurrent


    minimal-config


    small-config


    medium-config


    large-config


    full-config



QMAKESPEC...................win32-g++ (detected)

Architecture................windows

Maketool....................mingw32-make

Debug symbols...............no

Link Time Code Generation...no

Accessibility support.......yes

STL support.................yes

Exception support...........yes

RTTI support................yes

MMX support.................yes

3DNOW support...............yes

SSE support.................yes

SSE2 support................yes

IWMMXT support..............no

NEON support................no

OpenGL support..............yes

OpenVG support..............no

OpenSSL support.............no

QtDBus support..............no

QtXmlPatterns support.......yes

Phonon support..............no

QtMultimedia support........no

Large File support..........no

NIS support.................no

Iconv support...............

WebKit support..............no

Declarative support.........no

QtScript support............no

QtScriptTools support.......no

Graphics System.............raster

Qt3 compatibility...........yes

DirectWrite support.........no

Use system proxies..........no



Third Party Libraries:

    ZLIB support............qt

    GIF support.............plugin

    TIFF support............plugin

    JPEG support............plugin

    PNG support.............yes

    MNG support.............plugin

    FreeType support........no



Styles:

    Windows.................yes

    Windows XP..............yes

    Windows Vista...........yes

    Plastique...............yes

    Cleanlooks..............yes

    Motif...................yes

    CDE.....................yes

    Windows CE..............no

    Windows Mobile..........no

    S60.....................no



Sql Drivers:

    ODBC....................no

    MySQL...................no

    OCI.....................no

    PostgreSQL..............no

    TDS.....................no

    DB2.....................no

    SQLite..................plugin (qt)

    SQLite2.................no

    InterBase...............no



Sources are in..............C:\superbuild\qt4\src\qt4

Build is done in............C:\superbuild\qt4\src\qt4

Install prefix..............C:/superbuild/install

Headers installed to........C:/superbuild/install/include

Libraries installed to......C:/superbuild/install/lib

Plugins installed to........C:/superbuild/install/plugins

Imports installed to........C:/superbuild/install/imports

Binaries installed to.......C:/superbuild/install/bin

Docs installed to...........C:/superbuild/install/doc

Data installed to...........C:/superbuild/install

Translations installed to...C:/superbuild/install/translations

Examples installed to.......C:/superbuild/install/examples

Demos installed to..........C:/superbuild/install/demos



Include paths...............C:/superbuild/install/include 

Additional libraries........-LC:/superbuild/install/lib 

Creating qmake...

g++ -c -oproject.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION project.cpp

g++ -c -omain.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION main.cpp

g++ -c -omakefile.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/makefile.cpp

g++ -c -ounixmake.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/unix/unixmake.cpp

g++ -c -ounixmake2.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/unix/unixmake2.cpp

g++ -c -omingw_make.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/mingw_make.cpp

g++ -c -ooption.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION option.cpp

g++ -c -owinmakefile.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/winmakefile.cpp

g++ -c -oprojectgenerator.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/projectgenerator.cpp

g++ -c -oproperty.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION property.cpp

g++ -c -ometa.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION meta.cpp

g++ -c -omakefiledeps.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/makefiledeps.cpp

g++ -c -ometamakefile.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/metamakefile.cpp

g++ -c -oxmloutput.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/xmloutput.cpp

g++ -c -opbuilder_pbx.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/mac/pbuilder_pbx.cpp

g++ -c -oborland_bmake.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/borland_bmake.cpp

g++ -c -omsvc_nmake.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/msvc_nmake.cpp

g++ -c -omsvc_vcproj.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/msvc_vcproj.cpp

generators/win32/msvc_vcproj.cpp:77:15: warning: anonymous type with no linkage used to declare variable '<anonymous struct> dotNetCombo []' with linkage [enabled by default]

g++ -c -omsvc_vcxproj.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/msvc_vcxproj.cpp

g++ -c -omsvc_objectmodel.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/msvc_objectmodel.cpp

g++ -c -omsbuild_objectmodel.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/win32/msbuild_objectmodel.cpp

g++ -c -osymmake.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/symbian/symmake.cpp

g++ -c -oinitprojectdeploy_symbian.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/symbian/initprojectdeploy_symbian.cpp

g++ -c -osymmake_abld.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/symbian/symmake_abld.cpp

g++ -c -osymmake_sbsv2.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/symbian/symmake_sbsv2.cpp

g++ -c -osymbiancommon.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/symbian/symbiancommon.cpp

g++ -c -oregistry.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/tools/shared/windows/registry.cpp

g++ -c -oepocroot.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/tools/shared/symbian/epocroot.cpp

g++ -c -ogbuild.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION generators/integrity/gbuild.cpp

g++ -c -oqbitarray.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qbitarray.cpp

g++ -c -oqbuffer.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qbuffer.cpp

g++ -c -oqbytearray.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qbytearray.cpp

g++ -c -oqcryptographichash.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qcryptographichash.cpp

g++ -c -oqvsnprintf.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qvsnprintf.cpp

g++ -c -oqbytearraymatcher.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qbytearraymatcher.cpp

g++ -c -oqconfig.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/global/qconfig.cpp

g++ -c -oqdatetime.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qdatetime.cpp

g++ -c -oqdir.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qdir.cpp

g++ -c -oqdiriterator.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qdiriterator.cpp

g++ -c -oqfile.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfile.cpp

g++ -c -oqtemporaryfile.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qtemporaryfile.cpp

g++ -c -oqfileinfo.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfileinfo.cpp

g++ -c -oqabstractfileengine.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qabstractfileengine.cpp

g++ -c -oqfilesystementry.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfilesystementry.cpp

g++ -c -oqfilesystemengine.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfilesystemengine.cpp

g++ -c -oqfilesystemengine_win.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfilesystemengine_win.cpp

g++ -c -oqfilesystemiterator_win.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfilesystemiterator_win.cpp

g++ -c -oqfsfileengine.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfsfileengine.cpp

g++ -c -oqfsfileengine_iterator.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfsfileengine_iterator.cpp

g++ -c -oqfsfileengine_win.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qfsfileengine_win.cpp

g++ -c -oqglobal.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/global/qglobal.cpp

g++ -c -oqhash.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qhash.cpp

g++ -c -oqiodevice.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qiodevice.cpp

g++ -c -oqlibraryinfo.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/global/qlibraryinfo.cpp

g++ -c -oqlist.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qlist.cpp

g++ -c -oqlinkedlist.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qlinkedlist.cpp

g++ -c -oqlocale.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qlocale.cpp

g++ -c -oqlocale_tools.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qlocale_tools.cpp

g++ -c -oqlocale_win.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qlocale_win.cpp

g++ -c -oqmalloc.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/global/qmalloc.cpp

g++ -c -oqmap.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qmap.cpp

g++ -c -oqregexp.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qregexp.cpp

g++ -c -oqtextcodec.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/codecs/qtextcodec.cpp

g++ -c -oqutfcodec.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/codecs/qutfcodec.cpp

g++ -c -oqstring.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qstring.cpp

g++ -c -oqstringlist.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qstringlist.cpp

g++ -c -oqsystemerror.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/kernel/qsystemerror.cpp

g++ -c -oqsystemlibrary.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/plugin/qsystemlibrary.cpp

g++ -c -oqtextstream.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qtextstream.cpp

g++ -c -oquuid.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/plugin/quuid.cpp

g++ -c -oqvector.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/tools/qvector.cpp

g++ -c -oqsettings.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qsettings.cpp

g++ -c -oqsettings_win.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/io/qsettings_win.cpp

g++ -c -oqvariant.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/kernel/qvariant.cpp

g++ -c -oqmetatype.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/kernel/qmetatype.cpp

g++ -c -oqxmlstream.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/xml/qxmlstream.cpp

g++ -c -oqxmlutils.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/xml/qxmlutils.cpp

g++ -c -oqnumeric.o -O -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -Igenerators/integrity -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/include -IC:\superbuild\qt4\src\qt4/include/QtCore -IC:\superbuild\qt4\src\qt4/src/corelib/global -IC:\superbuild\qt4\src\qt4/src/corelib/xml -IC:\superbuild\qt4\src\qt4/mkspecs/win32-g++ -IC:\superbuild\qt4\src\qt4/tools/shared -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_PCRE -DQT_NODLL -DQT_NO_STL -DQT_NO_COMPRESS -DUNICODE -DHAVE_QCONFIG_CPP -DQT_BUILD_QMAKE -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -DQT_NO_DATASTREAM -DQT_BOOTSTRAPPED -DQLIBRARYINFO_EPOCROOT -DQMAKE_OPENSOURCE_EDITION C:\superbuild\qt4\src\qt4/src/corelib/global/qnumeric.cpp

g++ -static-libgcc -s -o qmake.exe project.o main.o makefile.o unixmake.o unixmake2.o mingw_make.o option.o winmakefile.o projectgenerator.o property.o meta.o makefiledeps.o metamakefile.o xmloutput.o pbuilder_pbx.o borland_bmake.o msvc_nmake.o msvc_vcproj.o msvc_vcxproj.o msvc_objectmodel.o msbuild_objectmodel.o symmake.o initprojectdeploy_symbian.o symmake_abld.o symmake_sbsv2.o symbiancommon.o registry.o epocroot.o gbuild.o qbitarray.o qbuffer.o qbytearray.o qcryptographichash.o qvsnprintf.o qbytearraymatcher.o qconfig.o qdatetime.o qdir.o qdiriterator.o qfile.o qtemporaryfile.o qfileinfo.o qabstractfileengine.o qfilesystementry.o qfilesystemengine.o qfilesystemengine_win.o qfilesystemiterator_win.o qfsfileengine.o qfsfileengine_iterator.o qfsfileengine_win.o qglobal.o qhash.o qiodevice.o qlibraryinfo.o qlist.o qlinkedlist.o qlocale.o qlocale_tools.o qlocale_win.o qmalloc.o qmap.o qregexp.o qtextcodec.o qutfcodec.o qstring.o qstringlist.o qsystemerror.o qsystemlibrary.o qtextstream.o quuid.o qvector.o qsettings.o qsettings_win.o qvariant.o qmetatype.o qxmlstream.o qxmlutils.o qnumeric.o -lole32 -luuid -ladvapi32 -lkernel32

copy qmake.exe C:\superbuild\qt4\src\qt4\bin\qmake.exe

        1 ???????????????

Creating makefiles in src...

Reading C:/superbuild/qt4/src/qt4/src/tools/bootstrap/bootstrap.pro

Reading C:/superbuild/qt4/src/qt4/src/tools/moc/moc.pro

Reading C:/superbuild/qt4/src/qt4/src/tools/rcc/rcc.pro

Reading C:/superbuild/qt4/src/qt4/src/tools/uic/uic.pro

Reading C:/superbuild/qt4/src/qt4/src/winmain/winmain.pro

Reading C:/superbuild/qt4/src/qt4/src/corelib/corelib.pro

Reading C:/superbuild/qt4/src/qt4/src/xml/xml.pro

Reading C:/superbuild/qt4/src/qt4/src/network/network.pro

Reading C:/superbuild/qt4/src/qt4/src/sql/sql.pro

Reading C:/superbuild/qt4/src/qt4/src/testlib/testlib.pro

Reading C:/superbuild/qt4/src/qt4/src/gui/gui.pro

Reading C:/superbuild/qt4/src/qt4/src/qt3support/qt3support.pro

Reading C:/superbuild/qt4/src/qt4/src/tools/uic3/uic3.pro

Reading C:/superbuild/qt4/src/qt4/src/activeqt/activeqt.pro

 Reading C:/superbuild/qt4/src/qt4/src/activeqt/container/container.pro

 Reading C:/superbuild/qt4/src/qt4/src/activeqt/control/control.pro

Reading C:/superbuild/qt4/src/qt4/src/opengl/opengl.pro

Reading C:/superbuild/qt4/src/qt4/src/xmlpatterns/xmlpatterns.pro

Reading C:/superbuild/qt4/src/qt4/src/svg/svg.pro

Reading C:/superbuild/qt4/src/qt4/src/plugins/plugins.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/sqldrivers/sqldrivers.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/sqldrivers/sqlite/sqlite.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/script/script.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/bearer/bearer.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/bearer/generic/generic.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/bearer/nativewifi/nativewifi.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/codecs/codecs.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/codecs/cn/cn.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/codecs/jp/jp.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/codecs/tw/tw.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/codecs/kr/kr.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/imageformats.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/jpeg/jpeg.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/gif/gif.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/mng/mng.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/svg/svg.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/tiff/tiff.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/ico/ico.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/imageformats/tga/tga.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/iconengines/iconengines.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/iconengines/svgiconengine/svgiconengine.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/graphicssystems/graphicssystems.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/graphicssystems/trace/trace.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/graphicssystems/opengl/opengl.pro

 Reading C:/superbuild/qt4/src/qt4/src/plugins/accessible/accessible.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/accessible/widgets/widgets.pro

  Reading C:/superbuild/qt4/src/qt4/src/plugins/accessible/compat/compat.pro

Reading C:/superbuild/qt4/src/qt4/tools/tools.pro

 Reading C:/superbuild/qt4/src/qt4/tools/assistant/assistant.pro

  Reading C:/superbuild/qt4/src/qt4/tools/assistant/lib/fulltextsearch/fulltextsearch.pro

  Reading C:/superbuild/qt4/src/qt4/tools/assistant/lib/lib.pro

  Reading C:/superbuild/qt4/src/qt4/tools/assistant/tools/tools.pro

   Reading C:/superbuild/qt4/src/qt4/tools/assistant/tools/assistant/assistant.pro

   Reading C:/superbuild/qt4/src/qt4/tools/assistant/tools/qhelpgenerator/qhelpgenerator.pro

   Reading C:/superbuild/qt4/src/qt4/tools/assistant/tools/qcollectiongenerator/qcollectiongenerator.pro

   Reading C:/superbuild/qt4/src/qt4/tools/assistant/tools/qhelpconverter/qhelpconverter.pro

 Reading C:/superbuild/qt4/src/qt4/tools/pixeltool/pixeltool.pro

 Reading C:/superbuild/qt4/src/qt4/tools/porting/porting.pro

  Reading C:/superbuild/qt4/src/qt4/tools/porting/src/src.pro

 Reading C:/superbuild/qt4/src/qt4/tools/qtestlib/qtestlib.pro

  Reading C:/superbuild/qt4/src/qt4/tools/qtestlib/updater/updater.pro

 Reading C:/superbuild/qt4/src/qt4/tools/qttracereplay/qttracereplay.pro

 Reading C:/superbuild/qt4/src/qt4/tools/designer/designer.pro

  Reading C:/superbuild/qt4/src/qt4/tools/designer/src/src.pro

   Reading C:/superbuild/qt4/src/qt4/tools/designer/src/uitools/uitools.pro

   Reading C:/superbuild/qt4/src/qt4/tools/designer/src/lib/lib.pro

   Reading C:/superbuild/qt4/src/qt4/tools/designer/src/components/components.pro

    Reading C:/superbuild/qt4/src/qt4/tools/designer/src/components/lib/lib.pro

   Reading C:/superbuild/qt4/src/qt4/tools/designer/src/designer/designer.pro

   Reading C:/superbuild/qt4/src/qt4/tools/designer/src/plugins/plugins.pro

    Reading C:/superbuild/qt4/src/qt4/tools/designer/src/plugins/widgets/widgets.pro

    Reading C:/superbuild/qt4/src/qt4/tools/designer/src/plugins/activeqt/activeqt.pro

 Reading C:/superbuild/qt4/src/qt4/tools/activeqt/activeqt.pro

  Reading C:/superbuild/qt4/src/qt4/tools/activeqt/dumpdoc/dumpdoc.pro

  Reading C:/superbuild/qt4/src/qt4/tools/activeqt/dumpcpp/dumpcpp.pro

  Reading C:/superbuild/qt4/src/qt4/tools/activeqt/testcon/testcon.pro

 Reading C:/superbuild/qt4/src/qt4/tools/linguist/linguist.pro

  Reading C:/superbuild/qt4/src/qt4/tools/linguist/lrelease/lrelease.pro

  Reading C:/superbuild/qt4/src/qt4/tools/linguist/lupdate/lupdate.pro

  Reading C:/superbuild/qt4/src/qt4/tools/linguist/lconvert/lconvert.pro

  Reading C:/superbuild/qt4/src/qt4/tools/linguist/linguist/linguist.pro

 Reading C:/superbuild/qt4/src/qt4/tools/xmlpatterns/xmlpatterns.pro

 Reading C:/superbuild/qt4/src/qt4/tools/xmlpatternsvalidator/xmlpatternsvalidator.pro

 Reading C:/superbuild/qt4/src/qt4/tools/qdoc3/qdoc3.pro

Reading C:/superbuild/qt4/src/qt4/translations/translations.pro

Generating Makefiles...





Qt is now configured for building. Just run mingw32-make.

To reconfigure, run mingw32-make confclean and configure.



ninja: build stopped: subcommand failed.
-------------- next part --------------
[1/91] No build step for 'python'
[2/91] No build step for 'tbb'
[3/91] Performing configure step for 'szip'
FAILED: szip/src/szip-stamp/szip-configure 
cmd.exe /C "cd /D C:\superbuild\szip\src\szip-build && "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=C:/superbuild/install -DCMAKE_PREFIX_PATH:PATH=C:/superbuild/install "-DCMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3" "-DCMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc" -DCMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64 -DCMAKE_BUILD_TYPE:STRING=Debug "-DCMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" -GNinja C:/superbuild/szip/src/szip && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/szip/src/szip-stamp/szip-configure"
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

[4/91] Performing build step for 'qt4'
FAILED: qt4/src/qt4-stamp/qt4-build 
cmd.exe /C "cd /D C:\superbuild\qt4\src\qt4 && "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/qt4/src/qt4-stamp/qt4-build"


Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



	cd src\tools\bootstrap\ && "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" -f Makefile



Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



	"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" -f Makefile.Release



Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



NMAKE : fatal error U1073: don't know how to make 'c:/Program\'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe"' : return code '0x2'

Stop.

NMAKE : fatal error U1077: 'cd' : return code '0x2'

Stop.

[5/91] Performing install step for 'tbb'
-- Up-to-date: C:/superbuild/install/include

-- Installing: C:/superbuild/install/include/serial

-- Installing: C:/superbuild/install/include/serial/tbb

-- Installing: C:/superbuild/install/include/serial/tbb/parallel_for.h

-- Installing: C:/superbuild/install/include/serial/tbb/tbb_annotate.h

-- Installing: C:/superbuild/install/include/tbb

-- Installing: C:/superbuild/install/include/tbb/aggregator.h

-- Installing: C:/superbuild/install/include/tbb/aligned_space.h

-- Installing: C:/superbuild/install/include/tbb/atomic.h

-- Installing: C:/superbuild/install/include/tbb/blocked_range.h

-- Installing: C:/superbuild/install/include/tbb/blocked_range2d.h

-- Installing: C:/superbuild/install/include/tbb/blocked_range3d.h

-- Installing: C:/superbuild/install/include/tbb/cache_aligned_allocator.h

-- Installing: C:/superbuild/install/include/tbb/combinable.h

-- Installing: C:/superbuild/install/include/tbb/compat

-- Installing: C:/superbuild/install/include/tbb/compat/condition_variable

-- Installing: C:/superbuild/install/include/tbb/compat/ppl.h

-- Installing: C:/superbuild/install/include/tbb/compat/thread

-- Installing: C:/superbuild/install/include/tbb/compat/tuple

-- Installing: C:/superbuild/install/include/tbb/concurrent_hash_map.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_lru_cache.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_priority_queue.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_queue.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_unordered_map.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_unordered_set.h

-- Installing: C:/superbuild/install/include/tbb/concurrent_vector.h

-- Installing: C:/superbuild/install/include/tbb/critical_section.h

-- Installing: C:/superbuild/install/include/tbb/enumerable_thread_specific.h

-- Installing: C:/superbuild/install/include/tbb/flow_graph.h

-- Installing: C:/superbuild/install/include/tbb/global_control.h

-- Installing: C:/superbuild/install/include/tbb/internal

-- Installing: C:/superbuild/install/include/tbb/internal/_aggregator_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_concurrent_queue_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_concurrent_unordered_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_indexer_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_item_buffer_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_join_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_node_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_tagged_buffer_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_trace_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_flow_graph_types_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_mutex_padding.h

-- Installing: C:/superbuild/install/include/tbb/internal/_range_iterator.h

-- Installing: C:/superbuild/install/include/tbb/internal/_tbb_hash_compare_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_tbb_strings.h

-- Installing: C:/superbuild/install/include/tbb/internal/_tbb_windef.h

-- Installing: C:/superbuild/install/include/tbb/internal/_template_helpers.h

-- Installing: C:/superbuild/install/include/tbb/internal/_x86_eliding_mutex_impl.h

-- Installing: C:/superbuild/install/include/tbb/internal/_x86_rtm_rw_mutex_impl.h

-- Installing: C:/superbuild/install/include/tbb/machine

-- Installing: C:/superbuild/install/include/tbb/machine/gcc_armv7.h

-- Installing: C:/superbuild/install/include/tbb/machine/gcc_generic.h

-- Installing: C:/superbuild/install/include/tbb/machine/gcc_ia32_common.h

-- Installing: C:/superbuild/install/include/tbb/machine/gcc_itsx.h

-- Installing: C:/superbuild/install/include/tbb/machine/ibm_aix51.h

-- Installing: C:/superbuild/install/include/tbb/machine/icc_generic.h

-- Installing: C:/superbuild/install/include/tbb/machine/linux_common.h

-- Installing: C:/superbuild/install/include/tbb/machine/linux_ia32.h

-- Installing: C:/superbuild/install/include/tbb/machine/linux_ia64.h

-- Installing: C:/superbuild/install/include/tbb/machine/linux_intel64.h

-- Installing: C:/superbuild/install/include/tbb/machine/macos_common.h

-- Installing: C:/superbuild/install/include/tbb/machine/mac_ppc.h

-- Installing: C:/superbuild/install/include/tbb/machine/mic_common.h

-- Installing: C:/superbuild/install/include/tbb/machine/msvc_armv7.h

-- Installing: C:/superbuild/install/include/tbb/machine/msvc_ia32_common.h

-- Installing: C:/superbuild/install/include/tbb/machine/sunos_sparc.h

-- Installing: C:/superbuild/install/include/tbb/machine/windows_api.h

-- Installing: C:/superbuild/install/include/tbb/machine/windows_ia32.h

-- Installing: C:/superbuild/install/include/tbb/machine/windows_intel64.h

-- Installing: C:/superbuild/install/include/tbb/machine/xbox360_ppc.h

-- Installing: C:/superbuild/install/include/tbb/memory_pool.h

-- Installing: C:/superbuild/install/include/tbb/mutex.h

-- Installing: C:/superbuild/install/include/tbb/null_mutex.h

-- Installing: C:/superbuild/install/include/tbb/null_rw_mutex.h

-- Installing: C:/superbuild/install/include/tbb/parallel_do.h

-- Installing: C:/superbuild/install/include/tbb/parallel_for.h

-- Installing: C:/superbuild/install/include/tbb/parallel_for_each.h

-- Installing: C:/superbuild/install/include/tbb/parallel_invoke.h

-- Installing: C:/superbuild/install/include/tbb/parallel_reduce.h

-- Installing: C:/superbuild/install/include/tbb/parallel_scan.h

-- Installing: C:/superbuild/install/include/tbb/parallel_sort.h

-- Installing: C:/superbuild/install/include/tbb/parallel_while.h

-- Installing: C:/superbuild/install/include/tbb/partitioner.h

-- Installing: C:/superbuild/install/include/tbb/pipeline.h

-- Installing: C:/superbuild/install/include/tbb/queuing_mutex.h

-- Installing: C:/superbuild/install/include/tbb/queuing_rw_mutex.h

-- Installing: C:/superbuild/install/include/tbb/reader_writer_lock.h

-- Installing: C:/superbuild/install/include/tbb/recursive_mutex.h

-- Installing: C:/superbuild/install/include/tbb/runtime_loader.h

-- Installing: C:/superbuild/install/include/tbb/scalable_allocator.h

-- Installing: C:/superbuild/install/include/tbb/spin_mutex.h

-- Installing: C:/superbuild/install/include/tbb/spin_rw_mutex.h

-- Installing: C:/superbuild/install/include/tbb/task.h

-- Installing: C:/superbuild/install/include/tbb/task_arena.h

-- Installing: C:/superbuild/install/include/tbb/task_group.h

-- Installing: C:/superbuild/install/include/tbb/task_scheduler_init.h

-- Installing: C:/superbuild/install/include/tbb/task_scheduler_observer.h

-- Installing: C:/superbuild/install/include/tbb/tbb.h

-- Installing: C:/superbuild/install/include/tbb/tbbmalloc_proxy.h

-- Installing: C:/superbuild/install/include/tbb/tbb_allocator.h

-- Installing: C:/superbuild/install/include/tbb/tbb_config.h

-- Installing: C:/superbuild/install/include/tbb/tbb_exception.h

-- Installing: C:/superbuild/install/include/tbb/tbb_machine.h

-- Installing: C:/superbuild/install/include/tbb/tbb_profiling.h

-- Installing: C:/superbuild/install/include/tbb/tbb_stddef.h

-- Installing: C:/superbuild/install/include/tbb/tbb_thread.h

-- Installing: C:/superbuild/install/include/tbb/tick_count.h

-- Up-to-date: C:/superbuild/install/lib

-- Installing: C:/superbuild/install/lib/irml

-- Installing: C:/superbuild/install/lib/tbb.lib

-- Installing: C:/superbuild/install/lib/tbbmalloc.lib

-- Installing: C:/superbuild/install/bin/tbb.dll

-- Installing: C:/superbuild/install/bin/tbbmalloc.dll

[6/91] Performing install step for 'python'
-- Installing: C:/superbuild/install/bin/bz2.dll

-- Installing: C:/superbuild/install/bin/bzdiff

-- Installing: C:/superbuild/install/bin/bzgrep

-- Installing: C:/superbuild/install/bin/bzip2.exe

-- Installing: C:/superbuild/install/bin/bzip2recover.exe

-- Installing: C:/superbuild/install/bin/bzmore

-- Installing: C:/superbuild/install/bin/Lib

-- Installing: C:/superbuild/install/bin/Lib/abc.py

-- Installing: C:/superbuild/install/bin/Lib/abc.pyc

-- Installing: C:/superbuild/install/bin/Lib/aifc.py

-- Installing: C:/superbuild/install/bin/Lib/antigravity.py

-- Installing: C:/superbuild/install/bin/Lib/anydbm.py

-- Installing: C:/superbuild/install/bin/Lib/argparse.py

-- Installing: C:/superbuild/install/bin/Lib/ast.py

-- Installing: C:/superbuild/install/bin/Lib/asynchat.py

-- Installing: C:/superbuild/install/bin/Lib/asyncore.py

-- Installing: C:/superbuild/install/bin/Lib/atexit.py

-- Installing: C:/superbuild/install/bin/Lib/atexit.pyc

-- Installing: C:/superbuild/install/bin/Lib/audiodev.py

-- Installing: C:/superbuild/install/bin/Lib/base64.py

-- Installing: C:/superbuild/install/bin/Lib/BaseHTTPServer.py

-- Installing: C:/superbuild/install/bin/Lib/Bastion.py

-- Installing: C:/superbuild/install/bin/Lib/bdb.py

-- Installing: C:/superbuild/install/bin/Lib/binhex.py

-- Installing: C:/superbuild/install/bin/Lib/bisect.py

-- Installing: C:/superbuild/install/bin/Lib/bisect.pyc

-- Installing: C:/superbuild/install/bin/Lib/bsddb

-- Installing: C:/superbuild/install/bin/Lib/bsddb/db.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/dbobj.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/dbrecio.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/dbshelve.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/dbtables.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/dbutils.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_all.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_associate.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_basics.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_compare.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_compat.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_cursor_pget_bug.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_db.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_dbenv.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_dbobj.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_dbshelve.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_dbtables.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_distributed_transactions.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_early_close.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_fileid.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_get_none.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_join.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_lock.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_misc.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_pickle.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_queue.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_recno.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_replication.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_sequence.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/test_thread.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/bsddb/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/calendar.py

-- Installing: C:/superbuild/install/bin/Lib/cgi.py

-- Installing: C:/superbuild/install/bin/Lib/CGIHTTPServer.py

-- Installing: C:/superbuild/install/bin/Lib/cgitb.py

-- Installing: C:/superbuild/install/bin/Lib/chunk.py

-- Installing: C:/superbuild/install/bin/Lib/cmd.py

-- Installing: C:/superbuild/install/bin/Lib/code.py

-- Installing: C:/superbuild/install/bin/Lib/codecs.py

-- Installing: C:/superbuild/install/bin/Lib/codecs.pyc

-- Installing: C:/superbuild/install/bin/Lib/codeop.py

-- Installing: C:/superbuild/install/bin/Lib/collections.py

-- Installing: C:/superbuild/install/bin/Lib/collections.pyc

-- Installing: C:/superbuild/install/bin/Lib/colorsys.py

-- Installing: C:/superbuild/install/bin/Lib/commands.py

-- Installing: C:/superbuild/install/bin/Lib/commands.pyc

-- Installing: C:/superbuild/install/bin/Lib/compileall.py

-- Installing: C:/superbuild/install/bin/Lib/compiler

-- Installing: C:/superbuild/install/bin/Lib/compiler/ast.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/consts.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/future.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/misc.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/pyassem.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/pycodegen.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/symbols.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/syntax.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/transformer.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/visitor.py

-- Installing: C:/superbuild/install/bin/Lib/compiler/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/ConfigParser.py

-- Installing: C:/superbuild/install/bin/Lib/ConfigParser.pyc

-- Installing: C:/superbuild/install/bin/Lib/contextlib.py

-- Installing: C:/superbuild/install/bin/Lib/Cookie.py

-- Installing: C:/superbuild/install/bin/Lib/cookielib.py

-- Installing: C:/superbuild/install/bin/Lib/copy.py

-- Installing: C:/superbuild/install/bin/Lib/copy.pyc

-- Installing: C:/superbuild/install/bin/Lib/copy_reg.py

-- Installing: C:/superbuild/install/bin/Lib/copy_reg.pyc

-- Installing: C:/superbuild/install/bin/Lib/cProfile.py

-- Installing: C:/superbuild/install/bin/Lib/csv.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/dyld.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/dylib.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/fetch_macholib

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/fetch_macholib.bat

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/framework.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/README.ctypes

-- Installing: C:/superbuild/install/bin/Lib/ctypes/macholib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/runtests.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_anon.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_arrays.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_array_in_pointer.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_as_parameter.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_bitfields.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_buffers.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_byteswap.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_callbacks.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_cast.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_cfuncs.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_checkretval.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_delattr.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_errcheck.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_errno.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_find.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_frombuffer.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_funcptr.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_functions.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_incomplete.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_init.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_integers.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_internals.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_keeprefs.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_libc.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_loading.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_macholib.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_memfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_numbers.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_objects.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_parameters.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_pep3118.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_pickling.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_pointers.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_prototypes.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_python_api.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_random_things.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_refcounts.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_repr.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_returnfuncptrs.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_simplesubclasses.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_sizes.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_slicing.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_stringptr.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_strings.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_structures.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_struct_fields.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_unaligned_structures.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_unicode.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_values.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_varsize_struct.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/test_win32.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/util.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/wintypes.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/_endian.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/_endian.pyc

-- Installing: C:/superbuild/install/bin/Lib/ctypes/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/ctypes/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/curses

-- Installing: C:/superbuild/install/bin/Lib/curses/ascii.py

-- Installing: C:/superbuild/install/bin/Lib/curses/has_key.py

-- Installing: C:/superbuild/install/bin/Lib/curses/panel.py

-- Installing: C:/superbuild/install/bin/Lib/curses/textpad.py

-- Installing: C:/superbuild/install/bin/Lib/curses/wrapper.py

-- Installing: C:/superbuild/install/bin/Lib/curses/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/dbhash.py

-- Installing: C:/superbuild/install/bin/Lib/decimal.py

-- Installing: C:/superbuild/install/bin/Lib/difflib.py

-- Installing: C:/superbuild/install/bin/Lib/difflib.pyc

-- Installing: C:/superbuild/install/bin/Lib/dircache.py

-- Installing: C:/superbuild/install/bin/Lib/dis.py

-- Installing: C:/superbuild/install/bin/Lib/distutils

-- Installing: C:/superbuild/install/bin/Lib/distutils/archive_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/archive_util.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/bcppcompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/ccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/ccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/cmd.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/cmd.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_dumb.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_dumb.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_msi.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_rpm.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_rpm.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_wininst.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/bdist_wininst.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_clib.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_clib.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_ext.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_ext.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_py.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_py.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_scripts.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/build_scripts.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/check.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/clean.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/clean.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/command_template

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/config.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/config.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_data.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_data.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_egg_info.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_egg_info.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_headers.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_headers.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_lib.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_lib.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_scripts.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/install_scripts.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/register.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/sdist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/sdist.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/upload.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/wininst-6.0.exe

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/wininst-7.1.exe

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/wininst-8.0.exe

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/wininst-9.0-amd64.exe

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/wininst-9.0.exe

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/command/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/config.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/config.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/core.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/core.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/cygwinccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/cygwinccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/debug.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/debug.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/dep_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/dep_util.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/dir_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/dir_util.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/dist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/dist.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/emxccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/errors.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/errors.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/extension.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/extension.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/fancy_getopt.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/fancy_getopt.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/filelist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/filelist.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/file_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/file_util.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/log.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/log.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/msvc9compiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/msvc9compiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/msvccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/msvccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/README

-- Installing: C:/superbuild/install/bin/Lib/distutils/spawn.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/spawn.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/sysconfig.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/sysconfig.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/Setup.sample

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/setuptools_build_ext.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/setuptools_extension.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/support.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_archive_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_bdist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_bdist_dumb.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_bdist_msi.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_bdist_rpm.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_bdist_wininst.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_build.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_build_clib.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_build_ext.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_build_py.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_build_scripts.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_ccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_check.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_clean.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_cmd.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_config.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_config_cmd.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_core.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_dep_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_dir_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_dist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_filelist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_file_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_install.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_install_data.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_install_headers.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_install_lib.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_install_scripts.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_msvc9compiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_register.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_sdist.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_spawn.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_sysconfig.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_text_file.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_unixccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_upload.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_version.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/test_versionpredicate.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/tests/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/text_file.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/text_file.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/unixccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/unixccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/util.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/util.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/version.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/version.pyc

-- Installing: C:/superbuild/install/bin/Lib/distutils/versionpredicate.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/distutils/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/doctest.py

-- Installing: C:/superbuild/install/bin/Lib/DocXMLRPCServer.py

-- Installing: C:/superbuild/install/bin/Lib/dumbdbm.py

-- Installing: C:/superbuild/install/bin/Lib/dummy_thread.py

-- Installing: C:/superbuild/install/bin/Lib/dummy_threading.py

-- Installing: C:/superbuild/install/bin/Lib/email

-- Installing: C:/superbuild/install/bin/Lib/email/base64mime.py

-- Installing: C:/superbuild/install/bin/Lib/email/charset.py

-- Installing: C:/superbuild/install/bin/Lib/email/encoders.py

-- Installing: C:/superbuild/install/bin/Lib/email/errors.py

-- Installing: C:/superbuild/install/bin/Lib/email/feedparser.py

-- Installing: C:/superbuild/install/bin/Lib/email/generator.py

-- Installing: C:/superbuild/install/bin/Lib/email/header.py

-- Installing: C:/superbuild/install/bin/Lib/email/iterators.py

-- Installing: C:/superbuild/install/bin/Lib/email/message.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime

-- Installing: C:/superbuild/install/bin/Lib/email/mime/application.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/audio.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/base.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/image.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/message.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/multipart.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/nonmultipart.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/text.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/email/mime/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/email/parser.py

-- Installing: C:/superbuild/install/bin/Lib/email/quoprimime.py

-- Installing: C:/superbuild/install/bin/Lib/email/test

-- Installing: C:/superbuild/install/bin/Lib/email/test/data

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/audiotest.au

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_01.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_02.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_03.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_04.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_05.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_06.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_07.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_08.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_09.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_10.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_11.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_12.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_12a.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_13.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_14.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_15.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_16.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_17.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_18.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_19.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_20.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_21.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_22.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_23.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_24.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_25.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_26.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_27.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_28.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_29.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_30.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_31.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_32.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_33.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_34.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_35.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_36.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_37.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_38.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_39.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_40.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_41.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_42.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_43.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_44.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_45.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/msg_46.txt

-- Installing: C:/superbuild/install/bin/Lib/email/test/data/PyBanner048.gif

-- Installing: C:/superbuild/install/bin/Lib/email/test/test_email.py

-- Installing: C:/superbuild/install/bin/Lib/email/test/test_email_codecs.py

-- Installing: C:/superbuild/install/bin/Lib/email/test/test_email_codecs_renamed.py

-- Installing: C:/superbuild/install/bin/Lib/email/test/test_email_renamed.py

-- Installing: C:/superbuild/install/bin/Lib/email/test/test_email_torture.py

-- Installing: C:/superbuild/install/bin/Lib/email/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/email/utils.py

-- Installing: C:/superbuild/install/bin/Lib/email/_parseaddr.py

-- Installing: C:/superbuild/install/bin/Lib/email/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/email/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings

-- Installing: C:/superbuild/install/bin/Lib/encodings/aliases.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/aliases.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/ascii.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/ascii.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/base64_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/big5.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/big5hkscs.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/bz2_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/charmap.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp037.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1006.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1026.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1140.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1250.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1251.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1252.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1252.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1253.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1254.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1255.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1256.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1257.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp1258.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp424.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp437.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp500.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp720.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp737.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp775.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp850.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp852.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp855.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp856.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp857.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp858.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp860.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp861.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp862.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp863.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp864.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp865.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp866.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp869.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp874.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp875.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp932.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp949.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/cp950.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/euc_jisx0213.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/euc_jis_2004.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/euc_jp.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/euc_kr.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/gb18030.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/gb2312.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/gbk.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/hex_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/hp_roman8.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/hz.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/idna.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp_1.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp_2.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp_2004.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp_3.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_jp_ext.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso2022_kr.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_1.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_10.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_11.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_13.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_14.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_15.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_16.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_2.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_3.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_4.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_5.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_6.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_7.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_8.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/iso8859_9.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/johab.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/koi8_r.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/koi8_u.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/latin_1.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_arabic.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_centeuro.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_croatian.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_cyrillic.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_farsi.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_greek.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_iceland.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_latin2.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_roman.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_romanian.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mac_turkish.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mbcs.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/mbcs.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/palmos.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/ptcp154.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/punycode.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/quopri_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/raw_unicode_escape.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/rot_13.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/shift_jis.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/shift_jisx0213.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/shift_jis_2004.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/string_escape.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/string_escape.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/tis_620.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/undefined.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/unicode_escape.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/unicode_internal.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_16.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_16_be.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_16_le.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_32.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_32_be.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_32_be.pyc

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_32_le.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_7.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_8.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/utf_8_sig.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/uu_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/zlib_codec.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/encodings/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/filecmp.py

-- Installing: C:/superbuild/install/bin/Lib/fileinput.py

-- Installing: C:/superbuild/install/bin/Lib/fnmatch.py

-- Installing: C:/superbuild/install/bin/Lib/fnmatch.pyc

-- Installing: C:/superbuild/install/bin/Lib/formatter.py

-- Installing: C:/superbuild/install/bin/Lib/fpformat.py

-- Installing: C:/superbuild/install/bin/Lib/fractions.py

-- Installing: C:/superbuild/install/bin/Lib/ftplib.py

-- Installing: C:/superbuild/install/bin/Lib/functools.py

-- Installing: C:/superbuild/install/bin/Lib/functools.pyc

-- Installing: C:/superbuild/install/bin/Lib/genericpath.py

-- Installing: C:/superbuild/install/bin/Lib/genericpath.pyc

-- Installing: C:/superbuild/install/bin/Lib/getopt.py

-- Installing: C:/superbuild/install/bin/Lib/getopt.pyc

-- Installing: C:/superbuild/install/bin/Lib/getpass.py

-- Installing: C:/superbuild/install/bin/Lib/gettext.py

-- Installing: C:/superbuild/install/bin/Lib/glob.py

-- Installing: C:/superbuild/install/bin/Lib/glob.pyc

-- Installing: C:/superbuild/install/bin/Lib/gzip.py

-- Installing: C:/superbuild/install/bin/Lib/hashlib.py

-- Installing: C:/superbuild/install/bin/Lib/hashlib.pyc

-- Installing: C:/superbuild/install/bin/Lib/heapq.py

-- Installing: C:/superbuild/install/bin/Lib/heapq.pyc

-- Installing: C:/superbuild/install/bin/Lib/hmac.py

-- Installing: C:/superbuild/install/bin/Lib/hotshot

-- Installing: C:/superbuild/install/bin/Lib/hotshot/log.py

-- Installing: C:/superbuild/install/bin/Lib/hotshot/stats.py

-- Installing: C:/superbuild/install/bin/Lib/hotshot/stones.py

-- Installing: C:/superbuild/install/bin/Lib/hotshot/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/htmlentitydefs.py

-- Installing: C:/superbuild/install/bin/Lib/htmllib.py

-- Installing: C:/superbuild/install/bin/Lib/HTMLParser.py

-- Installing: C:/superbuild/install/bin/Lib/httplib.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib

-- Installing: C:/superbuild/install/bin/Lib/idlelib/aboutDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/AutoComplete.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/AutoCompleteWindow.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/AutoExpand.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Bindings.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/CallTips.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/CallTipWindow.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ChangeLog

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ClassBrowser.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/CodeContext.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ColorDelegator.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/config-extensions.def

-- Installing: C:/superbuild/install/bin/Lib/idlelib/config-highlight.def

-- Installing: C:/superbuild/install/bin/Lib/idlelib/config-keys.def

-- Installing: C:/superbuild/install/bin/Lib/idlelib/config-main.def

-- Installing: C:/superbuild/install/bin/Lib/idlelib/configDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/configHandler.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/configHelpSourceEdit.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/configSectionNameDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/CREDITS.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Debugger.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Delegator.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/dynOptionMenuWidget.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/EditorWindow.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/extend.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/FileList.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/FormatParagraph.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/GrepDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/help.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/HISTORY.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/HyperParser.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/folder.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/idle.icns

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/minusnode.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/openfolder.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/plusnode.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/python.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Icons/tk.gif

-- Installing: C:/superbuild/install/bin/Lib/idlelib/idle.bat

-- Installing: C:/superbuild/install/bin/Lib/idlelib/idle.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/idle.pyw

-- Installing: C:/superbuild/install/bin/Lib/idlelib/IdleHistory.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/idlever.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/IOBinding.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/keybindingDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/macosxSupport.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/MultiCall.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/MultiStatusBar.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/NEWS.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ObjectBrowser.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/OutputWindow.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ParenMatch.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/PathBrowser.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/Percolator.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/PyParse.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/PyShell.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/README.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/RemoteDebugger.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/RemoteObjectBrowser.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ReplaceDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/rpc.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/RstripExtension.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/run.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ScriptBinding.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ScrolledList.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/SearchDialog.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/SearchDialogBase.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/SearchEngine.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/StackViewer.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/tabbedpages.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/testcode.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/textView.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/TODO.txt

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ToolTip.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/TreeWidget.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/UndoDelegator.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/WidgetRedirector.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/WindowList.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/ZoomHeight.py

-- Installing: C:/superbuild/install/bin/Lib/idlelib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/ihooks.py

-- Installing: C:/superbuild/install/bin/Lib/imaplib.py

-- Installing: C:/superbuild/install/bin/Lib/imghdr.py

-- Installing: C:/superbuild/install/bin/Lib/importlib

-- Installing: C:/superbuild/install/bin/Lib/importlib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/imputil.py

-- Installing: C:/superbuild/install/bin/Lib/inspect.py

-- Installing: C:/superbuild/install/bin/Lib/io.py

-- Installing: C:/superbuild/install/bin/Lib/io.pyc

-- Installing: C:/superbuild/install/bin/Lib/json

-- Installing: C:/superbuild/install/bin/Lib/json/decoder.py

-- Installing: C:/superbuild/install/bin/Lib/json/encoder.py

-- Installing: C:/superbuild/install/bin/Lib/json/scanner.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_check_circular.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_decode.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_default.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_dump.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_encode_basestring_ascii.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_fail.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_float.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_indent.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_pass1.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_pass2.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_pass3.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_recursion.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_scanstring.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_separators.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_speedups.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/test_unicode.py

-- Installing: C:/superbuild/install/bin/Lib/json/tests/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/json/tool.py

-- Installing: C:/superbuild/install/bin/Lib/json/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/keyword.py

-- Installing: C:/superbuild/install/bin/Lib/keyword.pyc

-- Installing: C:/superbuild/install/bin/Lib/lib-tk

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Canvas.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Dialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/FileDialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/FixTk.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/ScrolledText.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/SimpleDialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/README

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/runtktests.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_tkinter

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_tkinter/test_loadtk.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_tkinter/test_text.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_tkinter/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/support.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/test_extensions.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/test_functions.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/test_style.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/test_widgets.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/test/test_ttk/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Tix.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkColorChooser.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkCommonDialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Tkconstants.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Tkdnd.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkFileDialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkFont.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/Tkinter.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkMessageBox.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/tkSimpleDialog.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/ttk.py

-- Installing: C:/superbuild/install/bin/Lib/lib-tk/turtle.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/btm_matcher.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/btm_utils.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixer_base.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixer_util.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_apply.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_basestring.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_buffer.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_callable.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_dict.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_except.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_exec.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_execfile.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_exitfunc.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_filter.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_funcattrs.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_future.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_getcwdu.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_has_key.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_idioms.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_import.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_imports.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_imports2.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_input.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_intern.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_isinstance.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_itertools.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_itertools_imports.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_long.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_map.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_metaclass.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_methodattrs.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_ne.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_next.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_nonzero.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_numliterals.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_operator.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_paren.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_print.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_raise.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_raw_input.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_reduce.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_renames.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_repr.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_set_literal.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_standarderror.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_sys_exc.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_throw.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_tuple_params.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_types.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_unicode.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_urllib.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_ws_comma.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_xrange.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_xreadlines.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/fix_zip.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/fixes/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/Grammar.txt

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/main.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/patcomp.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/PatternGrammar.txt

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/conv.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/driver.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/grammar.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/literals.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/parse.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/pgen.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/token.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/tokenize.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pgen2/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pygram.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/pytree.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/refactor.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/bom.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/crlf.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/different_encoding.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/bad_order.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/fix_explicit.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/fix_first.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/fix_last.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/fix_parrot.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/fix_preorder.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/myfixes/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/no_fixer_cls.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/fixers/parrot_example.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/infinite_recursion.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/py2_test_grammar.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/py3_test_grammar.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/data/README

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/pytree_idempotency.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/support.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_all_fixers.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_fixers.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_main.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_parser.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_pytree.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_refactor.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/test_util.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/tests/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/lib2to3/__main__.py

-- Installing: C:/superbuild/install/bin/Lib/linecache.py

-- Installing: C:/superbuild/install/bin/Lib/linecache.pyc

-- Installing: C:/superbuild/install/bin/Lib/locale.py

-- Installing: C:/superbuild/install/bin/Lib/locale.pyc

-- Installing: C:/superbuild/install/bin/Lib/logging

-- Installing: C:/superbuild/install/bin/Lib/logging/config.py

-- Installing: C:/superbuild/install/bin/Lib/logging/handlers.py

-- Installing: C:/superbuild/install/bin/Lib/logging/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/macpath.py

-- Installing: C:/superbuild/install/bin/Lib/macurl2path.py

-- Installing: C:/superbuild/install/bin/Lib/mailbox.py

-- Installing: C:/superbuild/install/bin/Lib/mailcap.py

-- Installing: C:/superbuild/install/bin/Lib/markupbase.py

-- Installing: C:/superbuild/install/bin/Lib/md5.py

-- Installing: C:/superbuild/install/bin/Lib/mhlib.py

-- Installing: C:/superbuild/install/bin/Lib/mimetools.py

-- Installing: C:/superbuild/install/bin/Lib/mimetypes.py

-- Installing: C:/superbuild/install/bin/Lib/MimeWriter.py

-- Installing: C:/superbuild/install/bin/Lib/mimify.py

-- Installing: C:/superbuild/install/bin/Lib/modulefinder.py

-- Installing: C:/superbuild/install/bin/Lib/msilib

-- Installing: C:/superbuild/install/bin/Lib/msilib/schema.py

-- Installing: C:/superbuild/install/bin/Lib/msilib/sequence.py

-- Installing: C:/superbuild/install/bin/Lib/msilib/text.py

-- Installing: C:/superbuild/install/bin/Lib/msilib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/multifile.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/connection.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/dummy

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/dummy/connection.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/dummy/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/forking.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/heap.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/managers.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/pool.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/process.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/queues.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/reduction.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/sharedctypes.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/synchronize.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/util.py

-- Installing: C:/superbuild/install/bin/Lib/multiprocessing/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/mutex.py

-- Installing: C:/superbuild/install/bin/Lib/netrc.py

-- Installing: C:/superbuild/install/bin/Lib/new.py

-- Installing: C:/superbuild/install/bin/Lib/nntplib.py

-- Installing: C:/superbuild/install/bin/Lib/ntpath.py

-- Installing: C:/superbuild/install/bin/Lib/ntpath.pyc

-- Installing: C:/superbuild/install/bin/Lib/nturl2path.py

-- Installing: C:/superbuild/install/bin/Lib/numbers.py

-- Installing: C:/superbuild/install/bin/Lib/opcode.py

-- Installing: C:/superbuild/install/bin/Lib/optparse.py

-- Installing: C:/superbuild/install/bin/Lib/os.py

-- Installing: C:/superbuild/install/bin/Lib/os.pyc

-- Installing: C:/superbuild/install/bin/Lib/os2emxpath.py

-- Installing: C:/superbuild/install/bin/Lib/pdb.doc

-- Installing: C:/superbuild/install/bin/Lib/pdb.py

-- Installing: C:/superbuild/install/bin/Lib/pickle.py

-- Installing: C:/superbuild/install/bin/Lib/pickle.pyc

-- Installing: C:/superbuild/install/bin/Lib/pickletools.py

-- Installing: C:/superbuild/install/bin/Lib/pipes.py

-- Installing: C:/superbuild/install/bin/Lib/pkgutil.py

-- Installing: C:/superbuild/install/bin/Lib/plat-aix3

-- Installing: C:/superbuild/install/bin/Lib/plat-aix3/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-aix3/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-aix4

-- Installing: C:/superbuild/install/bin/Lib/plat-aix4/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-aix4/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-atheos

-- Installing: C:/superbuild/install/bin/Lib/plat-atheos/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-atheos/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-atheos/TYPES.py

-- Installing: C:/superbuild/install/bin/Lib/plat-beos5

-- Installing: C:/superbuild/install/bin/Lib/plat-beos5/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-beos5/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-darwin

-- Installing: C:/superbuild/install/bin/Lib/plat-darwin/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-darwin/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd4

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd4/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd4/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd5

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd5/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd5/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd6

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd6/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd6/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd7

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd7/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd7/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd8

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd8/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-freebsd8/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-generic

-- Installing: C:/superbuild/install/bin/Lib/plat-generic/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/AL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/CD.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/cddb.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/cdplayer.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/CL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/CL_old.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/DEVICE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/ERRNO.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/FILE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/FL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/flp.doc

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/flp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/GET.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/GL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/GLWS.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/IOCTL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/jpeg.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/panel.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/panelparser.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/readcd.doc

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/readcd.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/SV.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/torgb.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix5/WAIT.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/AL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/CD.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/cddb.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/cdplayer.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/CL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/DEVICE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/ERRNO.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/FILE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/FL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/flp.doc

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/flp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/GET.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/GL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/GLWS.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/IOCTL.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/jpeg.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/panel.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/panelparser.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/readcd.doc

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/readcd.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/SV.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/torgb.py

-- Installing: C:/superbuild/install/bin/Lib/plat-irix6/WAIT.py

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2/CDROM.py

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2/DLFCN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-linux2/TYPES.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/aepack.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/aetools.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/aetypes.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/applesingle.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/appletrawmain.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/appletrunner.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/argvemulator.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Audio_mac.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/bgenlocations.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/buildtools.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/bundlebuilder.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/AE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/AH.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Alias.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Aliases.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/App.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Appearance.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/AppleEvents.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/AppleHelp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CarbonEvents.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CarbonEvt.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CF.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CG.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Cm.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Components.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/ControlAccessor.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Controls.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CoreFoundation.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/CoreGraphics.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Ctl.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Dialogs.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Dlg.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Drag.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Dragconst.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Events.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Evt.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/File.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Files.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Fm.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Folder.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Folders.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Fonts.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Help.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/IBCarbon.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/IBCarbonRuntime.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Icn.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Icons.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Launch.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/LaunchServices.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/List.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Lists.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/MacHelp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/MacTextEditor.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/MediaDescr.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Menu.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Menus.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Mlte.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/OSA.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/OSAconst.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Qd.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Qdoffs.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/QDOffscreen.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Qt.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/QuickDraw.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/QuickTime.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Res.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Resources.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Scrap.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Snd.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Sndihooks.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Sound.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/TE.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/TextEdit.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Win.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/Windows.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/Carbon/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/cfmfile.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/dialogs.rsrc

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/EasyDialogs.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/errors.rsrc

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/findertools.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/FrameWork.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/gensuitemodule.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/ic.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/icopen.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior/CodeWarrior_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior/Metrowerks_Shell_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior/Required.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/CodeWarrior/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/Microsoft_Internet_Explorer.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/Netscape_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/Required_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/URL_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/Web_Browser_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Explorer/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Containers_and_folders.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Enumerations.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Files.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Finder_Basics.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Finder_items.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Legacy_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Type_Definitions.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/Window_classes.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Finder/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/Mozilla_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/PowerPlant.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/Required_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/Standard_URL_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/Text.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/WorldWideWeb_suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Netscape/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/AppleScript_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Macintosh_Connectivity_Clas.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/QuickDraw_Graphics_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/QuickDraw_Graphics_Suppleme.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Required_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Table_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Text_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/Type_Names_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/StdSuites/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Disk_Folder_File_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Folder_Actions_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Hidden_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Login_Items_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Power_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Processes_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/System_Events_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/Text_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/SystemEvents/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Terminal

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Terminal/Standard_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Terminal/Terminal_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Terminal/Text_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/Terminal/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/_builtinSuites

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/_builtinSuites/builtin_Suite.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/lib-scriptpackages/_builtinSuites/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/macerrors.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/macostools.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/macresource.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/MiniAEFrame.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/pimp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/PixMapWrapper.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/terminalcommand.py

-- Installing: C:/superbuild/install/bin/Lib/plat-mac/videoreader.py

-- Installing: C:/superbuild/install/bin/Lib/plat-netbsd1

-- Installing: C:/superbuild/install/bin/Lib/plat-netbsd1/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-netbsd1/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-next3

-- Installing: C:/superbuild/install/bin/Lib/plat-next3/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/grp.py

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/pwd.py

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/SOCKET.py

-- Installing: C:/superbuild/install/bin/Lib/plat-os2emx/_emx_link.py

-- Installing: C:/superbuild/install/bin/Lib/plat-riscos

-- Installing: C:/superbuild/install/bin/Lib/plat-riscos/riscosenviron.py

-- Installing: C:/superbuild/install/bin/Lib/plat-riscos/riscospath.py

-- Installing: C:/superbuild/install/bin/Lib/plat-riscos/rourl2path.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/CDIO.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/DLFCN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/STROPTS.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/SUNAUDIODEV.py

-- Installing: C:/superbuild/install/bin/Lib/plat-sunos5/TYPES.py

-- Installing: C:/superbuild/install/bin/Lib/plat-unixware7

-- Installing: C:/superbuild/install/bin/Lib/plat-unixware7/IN.py

-- Installing: C:/superbuild/install/bin/Lib/plat-unixware7/regen

-- Installing: C:/superbuild/install/bin/Lib/plat-unixware7/STROPTS.py

-- Installing: C:/superbuild/install/bin/Lib/platform.py

-- Installing: C:/superbuild/install/bin/Lib/platform.pyc

-- Installing: C:/superbuild/install/bin/Lib/plistlib.py

-- Installing: C:/superbuild/install/bin/Lib/popen2.py

-- Installing: C:/superbuild/install/bin/Lib/poplib.py

-- Installing: C:/superbuild/install/bin/Lib/posixfile.py

-- Installing: C:/superbuild/install/bin/Lib/posixpath.py

-- Installing: C:/superbuild/install/bin/Lib/posixpath.pyc

-- Installing: C:/superbuild/install/bin/Lib/pprint.py

-- Installing: C:/superbuild/install/bin/Lib/pprint.pyc

-- Installing: C:/superbuild/install/bin/Lib/profile.py

-- Installing: C:/superbuild/install/bin/Lib/pstats.py

-- Installing: C:/superbuild/install/bin/Lib/pty.py

-- Installing: C:/superbuild/install/bin/Lib/pyclbr.py

-- Installing: C:/superbuild/install/bin/Lib/pydoc.py

-- Installing: C:/superbuild/install/bin/Lib/pydoc_data

-- Installing: C:/superbuild/install/bin/Lib/pydoc_data/topics.py

-- Installing: C:/superbuild/install/bin/Lib/pydoc_data/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/pyexpat.pyd

-- Installing: C:/superbuild/install/bin/Lib/py_compile.py

-- Installing: C:/superbuild/install/bin/Lib/py_compile.pyc

-- Installing: C:/superbuild/install/bin/Lib/Queue.py

-- Installing: C:/superbuild/install/bin/Lib/quopri.py

-- Installing: C:/superbuild/install/bin/Lib/random.py

-- Installing: C:/superbuild/install/bin/Lib/random.pyc

-- Installing: C:/superbuild/install/bin/Lib/re.py

-- Installing: C:/superbuild/install/bin/Lib/re.pyc

-- Installing: C:/superbuild/install/bin/Lib/repr.py

-- Installing: C:/superbuild/install/bin/Lib/rexec.py

-- Installing: C:/superbuild/install/bin/Lib/rfc822.py

-- Installing: C:/superbuild/install/bin/Lib/rlcompleter.py

-- Installing: C:/superbuild/install/bin/Lib/robotparser.py

-- Installing: C:/superbuild/install/bin/Lib/runpy.py

-- Installing: C:/superbuild/install/bin/Lib/sched.py

-- Installing: C:/superbuild/install/bin/Lib/select.pyd

-- Installing: C:/superbuild/install/bin/Lib/sets.py

-- Installing: C:/superbuild/install/bin/Lib/sgmllib.py

-- Installing: C:/superbuild/install/bin/Lib/sha.py

-- Installing: C:/superbuild/install/bin/Lib/shelve.py

-- Installing: C:/superbuild/install/bin/Lib/shlex.py

-- Installing: C:/superbuild/install/bin/Lib/shlex.pyc

-- Installing: C:/superbuild/install/bin/Lib/shutil.py

-- Installing: C:/superbuild/install/bin/Lib/shutil.pyc

-- Installing: C:/superbuild/install/bin/Lib/SimpleHTTPServer.py

-- Installing: C:/superbuild/install/bin/Lib/SimpleXMLRPCServer.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/easter.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/easter.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/parser.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/parser.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/relativedelta.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/relativedelta.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/rrule.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/rrule.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/tz.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/tz.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/tzwin.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/tzwin.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/zoneinfo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/zoneinfo/zoneinfo-2010g.tar.gz

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/zoneinfo/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/zoneinfo/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/dateutil/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/afm.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/afm.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/animation.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/animation.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/artist.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/artist.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/axis.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/axis.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_agg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_agg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_cairo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_cairo.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_cocoaagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_cocoaagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_emf.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_emf.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_fltkagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_fltkagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gdk.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gdk.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtk.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtk.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtkagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtkagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtkcairo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_gtkcairo.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_macosx.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_macosx.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_mixed.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_mixed.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_pdf.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_pdf.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_ps.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_ps.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt4.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt4.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt4agg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qt4agg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qtagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_qtagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_svg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_svg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_template.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_template.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_tkagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_tkagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_wx.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_wx.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_wxagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/backend_wxagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/Matplotlib.nib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/Matplotlib.nib/classes.nib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/Matplotlib.nib/info.nib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/Matplotlib.nib/keyedobjects.nib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_compat.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_compat.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/figureoptions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/figureoptions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/formlayout.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/formlayout.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/qt4_editor/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/tkagg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/tkagg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/windowing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/windowing.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/_backend_agg.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backends/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backend_bases.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/backend_bases.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/bezier.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/bezier.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/blocking_input.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/blocking_input.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/cbook.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/cbook.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/cm.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/cm.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/collections.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/collections.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/colorbar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/colorbar.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/colors.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/colors.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/container.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/container.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/contour.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/contour.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/dates.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/dates.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/interpolate.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/interpolate.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/testfuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/testfuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/triangulate.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/triangulate.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/delaunay/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/docstring.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/docstring.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/dviread.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/dviread.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/figure.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/figure.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/finance.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/finance.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/fontconfig_pattern.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/fontconfig_pattern.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/font_manager.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/font_manager.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/ft2font.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/gridspec.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/gridspec.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/hatch.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/hatch.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/image.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/image.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/legend.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/legend.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/legend_handler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/legend_handler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/lines.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/lines.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/markers.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/markers.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mathtext.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mathtext.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mlab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mlab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/cmex10.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/cmmi10.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/cmr10.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/cmsy10.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/cmtt10.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pagd8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pagdo8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pagk8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pagko8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pbkd8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pbkdi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pbkl8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pbkli8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pcrb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pcrbo8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pcrr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pcrro8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvb8an.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvbo8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvbo8an.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvl8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvlo8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvr8an.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvro8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/phvro8an.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pncb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pncbi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pncr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pncri8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pplb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pplbi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pplr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pplri8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/psyr.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/ptmb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/ptmbi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/ptmr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/ptmri8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/putb8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/putbi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/putr8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/putri8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pzcmi8a.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/afm/pzdr.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Courier-Bold.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Courier-BoldOblique.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Courier-Oblique.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Courier.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Helvetica-Bold.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Helvetica-BoldOblique.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Helvetica-Oblique.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Helvetica.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/readme.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Symbol.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Times-Bold.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Times-BoldItalic.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Times-Italic.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/Times-Roman.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts/ZapfDingbats.afm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmb10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmex10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmmi10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmr10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmss10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmsy10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/cmtt10.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/COPYRIGHT.TXT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/LICENSE_STIX

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/README.TXT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/RELEASENOTES.TXT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXGeneral.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXGeneralBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXGeneralBolIta.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXGeneralItalic.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXNonUni.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXNonUniBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXNonUniBolIta.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXNonUniIta.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizFiveSymReg.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizFourSymBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizFourSymReg.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizOneSymBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizOneSymReg.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizThreeSymBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizThreeSymReg.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizTwoSymBol.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/STIXSizTwoSymReg.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraBd.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraBI.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraIt.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraMoBd.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraMoBI.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraMoIt.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraMono.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraSe.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/fonts/ttf/VeraSeBd.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/back.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/back.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/back.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/back.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/filesave.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/filesave.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/filesave.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/filesave.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/forward.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/forward.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/forward.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/forward.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/hand.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/hand.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/hand.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/hand.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/home.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/home.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/home.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/home.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/matplotlib.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/matplotlib.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/move.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/move.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/move.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/move.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/qt4_editor_options.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/qt4_editor_options.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_close.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_close.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_down.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_down.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_left.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_left.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_refresh.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_refresh.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_right.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_right.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_save_as.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_save_as.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_up.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_up.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_zoom-in.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_zoom-in.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_zoom-out.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/stock_zoom-out.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/subplots.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/subplots.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/subplots.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/zoom_to_rect.png

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/zoom_to_rect.ppm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/zoom_to_rect.svg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/images/zoom_to_rect.xpm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/lineprops.glade

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/matplotlib.conf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl-data/matplotlibrc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/mpl.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/nxutils.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/offsetbox.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/offsetbox.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/patches.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/patches.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/path.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/path.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/patheffects.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/patheffects.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/geo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/geo.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/polar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/polar.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/projections/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pylab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pylab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pyparsing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pyparsing.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pyplot.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/pyplot.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/quiver.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/quiver.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/rcsetup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/rcsetup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sankey.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sankey.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/scale.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/scale.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/ipython_console_highlighting.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/ipython_console_highlighting.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/mathmpl.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/mathmpl.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/only_directives.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/only_directives.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/plot_directive.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/plot_directive.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/sphinxext/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/spines.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/spines.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/table.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/table.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/compare.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/compare.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/decorators.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/decorators.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/Duration.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/Duration.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/Epoch.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/Epoch.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/EpochConverter.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/EpochConverter.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/StrConverter.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/StrConverter.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDbl.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDbl.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDblConverter.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDblConverter.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDblFormatter.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/UnitDblFormatter.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/jpl_units/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/noseclasses.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/noseclasses.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/testing/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/baseline_images

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/baseline_images/dviread

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/baseline_images/dviread/test.map

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/mpltest.ttf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_agg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_agg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_backend_pdf.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_backend_pdf.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_backend_svg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_backend_svg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_basic.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_basic.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_cbook.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_cbook.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_dates.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_dates.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_delaunay.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_delaunay.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_dviread.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_dviread.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_figure.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_figure.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_image.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_image.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_legend.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_legend.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_mathtext.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_mathtext.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_mlab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_mlab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_png.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_png.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_simplification.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_simplification.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_spines.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_spines.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_text.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_text.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_tightlayout.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_tightlayout.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_transforms.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_transforms.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_triangulation.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_triangulation.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_ttconv.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/test_ttconv.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tests/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/texmanager.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/texmanager.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/text.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/text.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/textpath.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/textpath.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/ticker.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/ticker.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tight_bbox.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tight_bbox.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tight_layout.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tight_layout.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/transforms.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/transforms.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/triangulation.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/triangulation.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/tricontour.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/tricontour.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/tripcolor.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/tripcolor.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/triplot.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/triplot.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/tri/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/ttconv.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/type1font.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/type1font.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/units.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/units.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/widgets.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/widgets.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_cm.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_cm.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_cntr.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_delaunay.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_image.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_mathtext_data.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_mathtext_data.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_path.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_png.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_pylab_helpers.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_pylab_helpers.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_tri.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/_windowing.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/matplotlib-1.1.1-py2.7.egg-info

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/anchored_artists.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/anchored_artists.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/angle_helper.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/angle_helper.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_divider.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_divider.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_grid.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_grid.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_rgb.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_rgb.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_size.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axes_size.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axislines.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axislines.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axisline_style.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axisline_style.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axis_artist.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/axis_artist.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/clip_path.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/clip_path.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/colorbar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/colorbar.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/floating_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/floating_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/grid_finder.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/grid_finder.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/grid_helper_curvelinear.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/grid_helper_curvelinear.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/inset_locator.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/inset_locator.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/parasite_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/parasite_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/anchored_artists.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/anchored_artists.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_divider.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_divider.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_grid.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_grid.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_rgb.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_rgb.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_size.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/axes_size.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/colorbar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/colorbar.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/inset_locator.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/inset_locator.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/mpl_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/mpl_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/parasite_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/parasite_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axes_grid1/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/angle_helper.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/angle_helper.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axislines.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axislines.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axisline_style.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axisline_style.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axis_artist.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/axis_artist.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/clip_path.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/clip_path.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/floating_axes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/floating_axes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/grid_finder.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/grid_finder.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/grid_helper_curvelinear.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/grid_helper_curvelinear.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/axisartist/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/exceltools.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/exceltools.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/gtktools.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/gtktools.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/art3d.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/art3d.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/axes3d.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/axes3d.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/axis3d.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/axis3d.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/proj3d.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/proj3d.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/mplot3d/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/mpl_toolkits/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/add_newdocs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/add_newdocs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/py3k.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/py3k.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/_inspect.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/_inspect.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/compat/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/arrayprint.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/arrayprint.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/defchararray.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/defchararray.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/fromnumeric.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/fromnumeric.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/function_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/function_base.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/generate_numpy_api.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/generate_numpy_api.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/getlimits.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/getlimits.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/arrayobject.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/arrayscalars.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/halffloat.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/multiarray_api.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/ndarrayobject.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/ndarraytypes.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/noprefix.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_3kcompat.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_common.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_cpu.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_endian.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_interrupt.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_math.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_no_deprecated_api.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/npy_os.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/numpyconfig.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/oldnumeric.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/old_defines.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/ufuncobject.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/ufunc_api.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/utils.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/_neighborhood_iterator_imp.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/_numpyconfig.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/__multiarray_api.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/include/numpy/__ufunc_api.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/lib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/lib/npy-pkg-config

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/lib/npy-pkg-config/mlib.ini

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/lib/npy-pkg-config/npymath.ini

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/lib/npymath.lib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/machar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/machar.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/memmap.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/memmap.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/multiarray.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/multiarray_tests.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/numeric.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/numeric.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/numerictypes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/numerictypes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/operand_flag_tests.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/records.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/records.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/scalarmath.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/setup_common.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/setup_common.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/shape_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/shape_base.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/struct_ufunc_test.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/data

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/data/astype_copy.pkl

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/data/recarray_from_file.fits

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_api.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_arrayprint.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_blasdot.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_datetime.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_defchararray.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_deprecations.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_dtype.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_einsum.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_errstate.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_function_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_getlimits.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_half.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_indexerrors.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_indexing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_item_selection.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_machar.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_memmap.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_multiarray.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_multiarray_assignment.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_nditer.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_numeric.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_numerictypes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_print.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_records.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_scalarmath.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_scalarprint.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_shape_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_ufunc.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_umath.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_umath_complex.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/tests/test_unicode.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/test_rational.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/umath.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/umath_tests.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/_dummy.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/_internal.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/_internal.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/_methods.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/_methods.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/core/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ctypeslib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ctypeslib.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/ccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/ccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/autodist.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/autodist.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/bdist_rpm.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/bdist_rpm.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_clib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_clib.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_ext.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_ext.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_py.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_py.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_scripts.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_scripts.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_src.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/build_src.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/config.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/config.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/config_compiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/config_compiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/develop.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/develop.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/egg_info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/egg_info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_clib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_clib.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_data.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_data.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_headers.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/install_headers.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/sdist.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/sdist.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/command/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/compat.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/compat.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/conv_template.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/conv_template.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/core.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/core.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/cpuinfo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/cpuinfo.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/environment.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/environment.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/exec_command.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/exec_command.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/extension.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/extension.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/absoft.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/absoft.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/compaq.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/compaq.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/g95.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/g95.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/gnu.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/gnu.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/hpux.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/hpux.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/ibm.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/ibm.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/intel.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/intel.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/lahey.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/lahey.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/mips.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/mips.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/nag.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/nag.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/none.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/none.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/pathf95.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/pathf95.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/pg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/pg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/sun.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/sun.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/vast.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/vast.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/fcompiler/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/from_template.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/from_template.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/intelccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/intelccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/lib2def.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/lib2def.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/line_endings.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/line_endings.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/log.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/log.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/mingw

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/mingw/gfortran_vs2003_hack.c

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/mingw32ccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/mingw32ccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/misc_util.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/misc_util.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/npy_pkg_config.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/npy_pkg_config.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/numpy_distribution.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/numpy_distribution.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/pathccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/pathccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/system_info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/system_info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/src

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/src/fib1.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/src/fib2.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/tests/test_fib2.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_ext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/include

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/include/body.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/src

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/src/foo_free.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/tests/test_foo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/f2py_f90_ext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/gen_ext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/gen_ext/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/gen_ext/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/gen_ext/tests/test_fib3.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/gen_ext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext/primes.pyx

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext/tests/test_primes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/pyrex_ext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src/example.c

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src/example.i

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src/zoo.cc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src/zoo.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/src/zoo.i

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/tests/test_example.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/tests/test_example2.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/swig_ext/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/test_exec_command.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/test_fcompiler_gnu.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/test_fcompiler_intel.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/test_misc_util.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/tests/test_npy_pkg_config.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/unixccompiler.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/unixccompiler.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__config__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__config__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__version__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/distutils/__version__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/basics.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/basics.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/broadcasting.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/broadcasting.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/byteswapping.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/byteswapping.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/constants.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/constants.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/creation.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/creation.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/glossary.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/glossary.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/howtofind.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/howtofind.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/indexing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/indexing.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/internals.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/internals.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/io.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/io.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/jargon.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/jargon.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/methods_vs_functions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/methods_vs_functions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/misc.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/misc.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/performance.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/performance.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/structured_arrays.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/structured_arrays.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/subclassing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/subclassing.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/ufuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/ufuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/doc/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/dual.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/dual.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/auxfuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/auxfuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/capi_maps.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/capi_maps.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/cb_rules.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/cb_rules.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/cfuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/cfuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/common_rules.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/common_rules.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/crackfortran.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/crackfortran.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/diagnose.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/diagnose.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/default.css

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/docutils.conf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/FAQ.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/hello.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/HISTORY.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/OLDNEWS.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/pyforttest.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/pytest.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/README.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/simple.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/simple_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/TESTING.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/THANKS.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/allocarr.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/allocarr_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/array.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/array_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/calculate.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/calculate_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/callback.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/callback2.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/callback_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/common.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/common_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/compile_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/default.css

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/docutils.conf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/extcallback.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/extcallback_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/fib1.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/fib1.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/fib2.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/fib3.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/ftype.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/ftype_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/index.txt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/moddata.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/moddata_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/run_main_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/scalar.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/scalar_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/setup_example.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/spam.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/spam_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/string.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/string_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/var.pyf

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/docs/usersguide/var_session.dat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f2py.1

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f2py2e.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f2py2e.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f2py_testing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f2py_testing.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f90mod_rules.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/f90mod_rules.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/func2subr.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/func2subr.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/rules.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/rules.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/src

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/src/fortranobject.c

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/src/fortranobject.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/array_from_pyobj

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/array_from_pyobj/wrapmodule.c

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape/.f2py_f2cmap

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape/foo_free.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape/foo_mod.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape/foo_use.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/assumed_shape/precision.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/kind

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/kind/foo.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/mixed

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/mixed/foo.f

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/mixed/foo_fixed.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/mixed/foo_free.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/size

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/src/size/foo.f90

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_array_from_pyobj.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_assumed_shape.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_callback.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_kind.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_mixed.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_return_character.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_return_complex.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_return_integer.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_return_logical.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_return_real.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/test_size.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/tests/util.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/use_rules.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/use_rules.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/__version__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/f2py/__version__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/fftpack.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/fftpack.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/fftpack_lite.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/helper.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/helper.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/tests/test_fftpack.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/tests/test_helper.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/fft/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arraypad.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arraypad.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arraysetops.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arraysetops.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arrayterator.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/arrayterator.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/financial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/financial.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/format.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/format.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/function_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/function_base.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/index_tricks.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/index_tricks.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/nanfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/nanfunctions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/npyio.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/npyio.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/polynomial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/polynomial.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/recfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/recfunctions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/scimath.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/scimath.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/shape_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/shape_base.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/stride_tricks.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/stride_tricks.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_arraypad.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_arraysetops.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_arrayterator.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_financial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_format.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_function_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_index_tricks.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_io.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_nanfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_polynomial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_recfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_shape_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_stride_tricks.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_twodim_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_type_check.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_ufunclike.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test_utils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test__datasource.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/tests/test__iotools.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/twodim_base.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/twodim_base.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/type_check.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/type_check.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/ufunclike.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/ufunclike.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/user_array.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/user_array.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/utils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/utils.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/_compiled_base.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/_datasource.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/_datasource.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/_iotools.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/_iotools.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/lib/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/lapack_lite.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/linalg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/linalg.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/tests/test_build.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/tests/test_deprecations.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/tests/test_linalg.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/_umath_linalg.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/linalg/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/bench.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/bench.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/core.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/core.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/extras.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/extras.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/mrecords.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/mrecords.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_core.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_extras.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_mrecords.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_old_ma.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/tests/test_subclassing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/testutils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/testutils.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/timer_comparison.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/timer_comparison.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/version.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/version.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/ma/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matlib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matlib.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/defmatrix.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/defmatrix.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/tests/test_defmatrix.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/tests/test_multiarray.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/tests/test_numeric.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/matrixlib/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/alter_code1.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/alter_code1.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/alter_code2.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/alter_code2.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/compat.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/compat.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/convolve.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/convolve.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/fft.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/fft.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/functions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/functions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/image.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/image.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/arraybase.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/cfunc.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/ieeespecial.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/libnumarray.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/numcomplex.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/include/numpy/nummacro.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/linear_algebra.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/linear_algebra.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/ma.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/ma.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/matrix.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/matrix.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/mlab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/mlab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/nd_image.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/nd_image.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/numerictypes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/numerictypes.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/random_array.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/random_array.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/session.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/session.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/ufuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/ufuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/util.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/util.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/_capi.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/numarray/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/alter_code1.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/alter_code1.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/alter_code2.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/alter_code2.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/arrayfns.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/arrayfns.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/array_printer.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/array_printer.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/compat.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/compat.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/fft.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/fft.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/fix_default_axis.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/fix_default_axis.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/functions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/functions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/linear_algebra.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/linear_algebra.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/ma.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/ma.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/matrix.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/matrix.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/misc.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/misc.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/mlab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/mlab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/precision.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/precision.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/random_array.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/random_array.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/rng.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/rng.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/rng_stats.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/rng_stats.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/tests/test_oldnumeric.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/typeconv.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/typeconv.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/ufuncs.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/ufuncs.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/user_array.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/user_array.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/oldnumeric/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/chebyshev.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/chebyshev.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/hermite.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/hermite.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/hermite_e.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/hermite_e.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/laguerre.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/laguerre.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/legendre.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/legendre.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polynomial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polynomial.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polytemplate.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polytemplate.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polyutils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/polyutils.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_chebyshev.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_classes.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_hermite.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_hermite_e.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_laguerre.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_legendre.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_polynomial.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_polyutils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/tests/test_printing.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/polynomial/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/info.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/info.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/mtrand.pyd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/randomkit.h

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/tests/test_random.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/tests/test_regression.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/random/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/decorators.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/decorators.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/noseclasses.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/noseclasses.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/nosetester.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/nosetester.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/numpytest.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/numpytest.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/print_coercion_tables.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/print_coercion_tables.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/setup.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/setup.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/tests/test_decorators.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/tests/test_doctesting.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/tests/test_utils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/utils.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/utils.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/testing/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/tests

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/tests/test_ctypeslib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/tests/test_matlib.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/version.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/version.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/_import_tools.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/_import_tools.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/__config__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/__config__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/numpy-1.8.1-py2.7.egg-info

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pylab.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pylab.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/exceptions.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/exceptions.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/reference.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/reference.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/tzfile.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/tzfile.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/tzinfo.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/tzinfo.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Abidjan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Accra

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Addis_Ababa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Algiers

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Asmara

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Asmera

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Bamako

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Bangui

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Banjul

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Bissau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Blantyre

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Brazzaville

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Bujumbura

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Cairo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Casablanca

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Ceuta

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Conakry

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Dakar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Dar_es_Salaam

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Djibouti

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Douala

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/El_Aaiun

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Freetown

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Gaborone

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Harare

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Johannesburg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Kampala

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Khartoum

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Kigali

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Kinshasa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Lagos

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Libreville

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Lome

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Luanda

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Lubumbashi

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Lusaka

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Malabo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Maputo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Maseru

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Mbabane

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Mogadishu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Monrovia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Nairobi

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Ndjamena

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Niamey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Nouakchott

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Ouagadougou

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Porto-Novo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Sao_Tome

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Timbuktu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Tripoli

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Tunis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Africa/Windhoek

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Adak

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Anchorage

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Anguilla

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Antigua

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Araguaina

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Buenos_Aires

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Catamarca

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/ComodRivadavia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Cordoba

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Jujuy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/La_Rioja

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Mendoza

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Rio_Gallegos

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Salta

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/San_Juan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/San_Luis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Tucuman

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Argentina/Ushuaia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Aruba

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Asuncion

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Atikokan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Atka

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Bahia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Bahia_Banderas

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Barbados

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Belem

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Belize

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Blanc-Sablon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Boa_Vista

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Bogota

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Boise

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Buenos_Aires

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cambridge_Bay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Campo_Grande

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cancun

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Caracas

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Catamarca

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cayenne

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cayman

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Chicago

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Chihuahua

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Coral_Harbour

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cordoba

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Costa_Rica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Cuiaba

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Curacao

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Danmarkshavn

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Dawson

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Dawson_Creek

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Denver

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Detroit

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Dominica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Edmonton

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Eirunepe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/El_Salvador

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Ensenada

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Fortaleza

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Fort_Wayne

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Glace_Bay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Godthab

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Goose_Bay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Grand_Turk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Grenada

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Guadeloupe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Guatemala

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Guayaquil

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Guyana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Halifax

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Havana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Hermosillo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Indianapolis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Knox

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Marengo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Petersburg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Tell_City

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Vevay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Vincennes

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indiana/Winamac

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Indianapolis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Inuvik

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Iqaluit

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Jamaica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Jujuy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Juneau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Kentucky

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Kentucky/Louisville

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Kentucky/Monticello

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Knox_IN

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/La_Paz

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Lima

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Los_Angeles

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Louisville

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Maceio

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Managua

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Manaus

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Marigot

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Martinique

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Matamoros

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Mazatlan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Mendoza

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Menominee

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Merida

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Metlakatla

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Mexico_City

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Miquelon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Moncton

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Monterrey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Montevideo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Montreal

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Montserrat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Nassau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/New_York

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Nipigon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Nome

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Noronha

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/North_Dakota

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/North_Dakota/Beulah

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/North_Dakota/Center

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/North_Dakota/New_Salem

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Ojinaga

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Panama

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Pangnirtung

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Paramaribo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Phoenix

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Port-au-Prince

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Porto_Acre

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Porto_Velho

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Port_of_Spain

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Puerto_Rico

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Rainy_River

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Rankin_Inlet

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Recife

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Regina

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Resolute

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Rio_Branco

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Rosario

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Santarem

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Santa_Isabel

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Santiago

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Santo_Domingo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Sao_Paulo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Scoresbysund

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Shiprock

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Sitka

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Barthelemy

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Johns

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Kitts

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Lucia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Thomas

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/St_Vincent

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Swift_Current

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Tegucigalpa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Thule

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Thunder_Bay

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Tijuana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Toronto

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Tortola

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Vancouver

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Virgin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Whitehorse

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Winnipeg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Yakutat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/America/Yellowknife

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Casey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Davis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/DumontDUrville

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Macquarie

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Mawson

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/McMurdo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Palmer

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Rothera

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/South_Pole

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Syowa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Antarctica/Vostok

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Arctic

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Arctic/Longyearbyen

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Aden

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Almaty

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Amman

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Anadyr

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Aqtau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Aqtobe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ashgabat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ashkhabad

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Baghdad

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Bahrain

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Baku

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Bangkok

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Beirut

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Bishkek

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Brunei

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Calcutta

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Choibalsan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Chongqing

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Chungking

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Colombo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Dacca

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Damascus

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Dhaka

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Dili

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Dubai

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Dushanbe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Gaza

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Harbin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Hong_Kong

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Hovd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ho_Chi_Minh

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Irkutsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Istanbul

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Jakarta

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Jayapura

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Jerusalem

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kabul

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kamchatka

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Karachi

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kashgar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kathmandu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Katmandu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kolkata

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Krasnoyarsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kuala_Lumpur

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kuching

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Kuwait

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Macao

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Macau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Magadan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Makassar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Manila

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Muscat

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Nicosia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Novokuznetsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Novosibirsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Omsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Oral

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Phnom_Penh

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Pontianak

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Pyongyang

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Qatar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Qyzylorda

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Rangoon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Riyadh

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Riyadh87

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Riyadh88

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Riyadh89

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Saigon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Sakhalin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Samarkand

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Seoul

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Shanghai

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Singapore

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Taipei

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Tashkent

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Tbilisi

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Tehran

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Tel_Aviv

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Thimbu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Thimphu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Tokyo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ujung_Pandang

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ulaanbaatar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Ulan_Bator

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Urumqi

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Vientiane

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Vladivostok

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Yakutsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Yekaterinburg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Asia/Yerevan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Azores

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Bermuda

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Canary

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Cape_Verde

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Faeroe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Faroe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Jan_Mayen

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Madeira

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Reykjavik

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/South_Georgia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/Stanley

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Atlantic/St_Helena

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/ACT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Adelaide

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Brisbane

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Broken_Hill

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Canberra

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Currie

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Darwin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Eucla

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Hobart

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/LHI

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Lindeman

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Lord_Howe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Melbourne

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/North

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/NSW

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Perth

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Queensland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/South

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Sydney

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Tasmania

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Victoria

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/West

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Australia/Yancowinna

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Brazil

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Brazil/Acre

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Brazil/DeNoronha

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Brazil/East

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Brazil/West

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Atlantic

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Central

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/East-Saskatchewan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Eastern

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Mountain

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Newfoundland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Pacific

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Saskatchewan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Canada/Yukon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/CET

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Chile

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Chile/Continental

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Chile/EasterIsland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/CST6CDT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Cuba

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/EET

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Egypt

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Eire

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/EST

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/EST5EDT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+1

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+10

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+11

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+12

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+2

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+3

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+4

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+5

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+6

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+7

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+8

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT+9

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-1

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-10

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-11

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-12

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-13

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-14

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-2

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-3

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-4

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-5

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-6

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-7

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-8

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT-9

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/GMT0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/Greenwich

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/UCT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/Universal

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/UTC

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Etc/Zulu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Amsterdam

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Andorra

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Athens

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Belfast

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Belgrade

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Berlin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Bratislava

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Brussels

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Bucharest

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Budapest

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Chisinau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Copenhagen

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Dublin

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Gibraltar

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Guernsey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Helsinki

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Isle_of_Man

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Istanbul

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Jersey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Kaliningrad

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Kiev

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Lisbon

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Ljubljana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/London

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Luxembourg

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Madrid

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Malta

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Mariehamn

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Minsk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Monaco

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Moscow

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Nicosia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Oslo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Paris

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Podgorica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Prague

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Riga

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Rome

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Samara

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/San_Marino

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Sarajevo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Simferopol

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Skopje

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Sofia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Stockholm

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Tallinn

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Tirane

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Tiraspol

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Uzhgorod

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Vaduz

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Vatican

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Vienna

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Vilnius

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Volgograd

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Warsaw

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Zagreb

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Zaporozhye

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Europe/Zurich

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Factory

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GB

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GB-Eire

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GMT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GMT+0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GMT-0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/GMT0

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Greenwich

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Hongkong

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/HST

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Iceland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Antananarivo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Chagos

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Christmas

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Cocos

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Comoro

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Kerguelen

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Mahe

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Maldives

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Mauritius

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Mayotte

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Indian/Reunion

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Iran

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/iso3166.tab

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Israel

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Jamaica

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Japan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Kwajalein

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Libya

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/localtime

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/MET

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mexico

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mexico/BajaNorte

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mexico/BajaSur

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mexico/General

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mideast

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mideast/Riyadh87

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mideast/Riyadh88

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Mideast/Riyadh89

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/MST

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/MST7MDT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Navajo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/NZ

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/NZ-CHAT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Apia

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Auckland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Chatham

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Chuuk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Easter

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Efate

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Enderbury

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Fakaofo

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Fiji

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Funafuti

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Galapagos

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Gambier

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Guadalcanal

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Guam

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Honolulu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Johnston

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Kiritimati

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Kosrae

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Kwajalein

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Majuro

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Marquesas

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Midway

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Nauru

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Niue

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Norfolk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Noumea

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Pago_Pago

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Palau

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Pitcairn

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Pohnpei

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Ponape

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Port_Moresby

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Rarotonga

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Saipan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Samoa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Tahiti

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Tarawa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Tongatapu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Truk

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Wake

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Wallis

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Pacific/Yap

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Poland

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Portugal

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/posixrules

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/PRC

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/PST8PDT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/ROC

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/ROK

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Singapore

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Turkey

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/UCT

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Universal

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Alaska

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Aleutian

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Arizona

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Central

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/East-Indiana

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Eastern

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Hawaii

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Indiana-Starke

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Michigan

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Mountain

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Pacific

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Pacific-New

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/US/Samoa

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/UTC

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/W-SU

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/WET

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/zone.tab

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/zoneinfo/Zulu

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/site-packages/pytz/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/site-packages/README

-- Installing: C:/superbuild/install/bin/Lib/site.py

-- Installing: C:/superbuild/install/bin/Lib/site.pyc

-- Installing: C:/superbuild/install/bin/Lib/smtpd.py

-- Installing: C:/superbuild/install/bin/Lib/smtplib.py

-- Installing: C:/superbuild/install/bin/Lib/sndhdr.py

-- Installing: C:/superbuild/install/bin/Lib/socket.py

-- Installing: C:/superbuild/install/bin/Lib/SocketServer.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/dbapi2.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/dump.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/dbapi.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/dump.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/factory.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/hooks.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/py25tests.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/regression.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/transactions.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/types.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/userfunctions.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/sqlite3/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/sre.py

-- Installing: C:/superbuild/install/bin/Lib/sre_compile.py

-- Installing: C:/superbuild/install/bin/Lib/sre_compile.pyc

-- Installing: C:/superbuild/install/bin/Lib/sre_constants.py

-- Installing: C:/superbuild/install/bin/Lib/sre_constants.pyc

-- Installing: C:/superbuild/install/bin/Lib/sre_parse.py

-- Installing: C:/superbuild/install/bin/Lib/sre_parse.pyc

-- Installing: C:/superbuild/install/bin/Lib/ssl.py

-- Installing: C:/superbuild/install/bin/Lib/stat.py

-- Installing: C:/superbuild/install/bin/Lib/stat.pyc

-- Installing: C:/superbuild/install/bin/Lib/statvfs.py

-- Installing: C:/superbuild/install/bin/Lib/string.py

-- Installing: C:/superbuild/install/bin/Lib/string.pyc

-- Installing: C:/superbuild/install/bin/Lib/StringIO.py

-- Installing: C:/superbuild/install/bin/Lib/StringIO.pyc

-- Installing: C:/superbuild/install/bin/Lib/stringold.py

-- Installing: C:/superbuild/install/bin/Lib/stringprep.py

-- Installing: C:/superbuild/install/bin/Lib/struct.py

-- Installing: C:/superbuild/install/bin/Lib/struct.pyc

-- Installing: C:/superbuild/install/bin/Lib/subprocess.py

-- Installing: C:/superbuild/install/bin/Lib/subprocess.pyc

-- Installing: C:/superbuild/install/bin/Lib/sunau.py

-- Installing: C:/superbuild/install/bin/Lib/sunaudio.py

-- Installing: C:/superbuild/install/bin/Lib/symbol.py

-- Installing: C:/superbuild/install/bin/Lib/symtable.py

-- Installing: C:/superbuild/install/bin/Lib/sysconfig.py

-- Installing: C:/superbuild/install/bin/Lib/sysconfig.pyc

-- Installing: C:/superbuild/install/bin/Lib/tabnanny.py

-- Installing: C:/superbuild/install/bin/Lib/tarfile.py

-- Installing: C:/superbuild/install/bin/Lib/telnetlib.py

-- Installing: C:/superbuild/install/bin/Lib/tempfile.py

-- Installing: C:/superbuild/install/bin/Lib/tempfile.pyc

-- Installing: C:/superbuild/install/bin/Lib/test

-- Installing: C:/superbuild/install/bin/Lib/test/185test.db

-- Installing: C:/superbuild/install/bin/Lib/test/audiotest.au

-- Installing: C:/superbuild/install/bin/Lib/test/autotest.py

-- Installing: C:/superbuild/install/bin/Lib/test/badcert.pem

-- Installing: C:/superbuild/install/bin/Lib/test/badkey.pem

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future3.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future4.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future5.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future6.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future7.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future8.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_future9.py

-- Installing: C:/superbuild/install/bin/Lib/test/badsyntax_nocaret.py

-- Installing: C:/superbuild/install/bin/Lib/test/bad_coding.py

-- Installing: C:/superbuild/install/bin/Lib/test/bad_coding2.py

-- Installing: C:/superbuild/install/bin/Lib/test/buffer_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/cfgparser.1

-- Installing: C:/superbuild/install/bin/Lib/test/check_soundcard.vbs

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/big5-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/big5.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/big5hkscs-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/big5hkscs.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/cp949-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/cp949.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_jisx0213-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_jisx0213.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_jp-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_jp.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_kr-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/euc_kr.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gb18030-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gb18030.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gb2312-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gb2312.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gbk-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/gbk.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/hz-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/hz.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/iso2022_jp-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/iso2022_jp.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/iso2022_kr-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/iso2022_kr.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/johab-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/johab.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/shift_jis-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/shift_jis.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/shift_jisx0213-utf8.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cjkencodings/shift_jisx0213.txt

-- Installing: C:/superbuild/install/bin/Lib/test/cmath_testcases.txt

-- Installing: C:/superbuild/install/bin/Lib/test/crashers

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/bogus_code_obj.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/borrowed_ref_1.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/borrowed_ref_2.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/compiler_recursion.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/gc_has_finalizer.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/gc_inspection.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/infinite_loop_re.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/loosing_mro_ref.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/mutation_inside_cyclegc.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/nasty_eq_vs_dict.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/README

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/recursion_limit_too_high.py

-- Installing: C:/superbuild/install/bin/Lib/test/crashers/recursive_call.py

-- Installing: C:/superbuild/install/bin/Lib/test/curses_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/data

-- Installing: C:/superbuild/install/bin/Lib/test/data/README

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/abs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/add.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/and.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/base.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/clamp.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/class.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/compare.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/comparetotal.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/comparetotmag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/copy.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/copyabs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/copynegate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/copysign.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddAbs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddAdd.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddAnd.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddBase.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCanonical.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddClass.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCompare.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCompareSig.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCompareTotal.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCompareTotalMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCopy.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCopyAbs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCopyNegate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddCopySign.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddDivide.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddDivideInt.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddEncode.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddFMA.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddInvert.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddLogB.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMax.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMaxMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMin.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMinMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMinus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddMultiply.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddNextMinus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddNextPlus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddNextToward.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddOr.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddPlus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddQuantize.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddReduce.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddRemainder.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddRemainderNear.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddRotate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddSameQuantum.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddScaleB.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddShift.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddSubtract.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddToIntegral.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ddXor.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/decDouble.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/decQuad.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/decSingle.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/divide.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/divideint.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqAbs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqAdd.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqAnd.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqBase.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCanonical.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqClass.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCompare.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCompareSig.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCompareTotal.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCompareTotalMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCopy.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCopyAbs.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCopyNegate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqCopySign.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqDivide.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqDivideInt.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqEncode.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqFMA.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqInvert.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqLogB.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMax.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMaxMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMin.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMinMag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMinus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqMultiply.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqNextMinus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqNextPlus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqNextToward.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqOr.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqPlus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqQuantize.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqReduce.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqRemainder.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqRemainderNear.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqRotate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqSameQuantum.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqScaleB.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqShift.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqSubtract.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqToIntegral.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dqXor.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dsBase.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/dsEncode.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/exp.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/extra.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/fma.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/inexact.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/invert.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/ln.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/log10.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/logb.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/max.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/maxmag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/min.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/minmag.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/minus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/multiply.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/nextminus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/nextplus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/nexttoward.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/or.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/plus.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/power.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/powersqrt.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/quantize.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/randomBound32.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/randoms.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/reduce.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/remainder.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/remainderNear.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/rescale.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/rotate.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/rounding.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/samequantum.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/scaleb.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/shift.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/squareroot.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/subtract.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/testall.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/tointegral.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/tointegralx.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/decimaltestdata/xor.decTest

-- Installing: C:/superbuild/install/bin/Lib/test/doctest_aliases.py

-- Installing: C:/superbuild/install/bin/Lib/test/double_const.py

-- Installing: C:/superbuild/install/bin/Lib/test/empty.vbs

-- Installing: C:/superbuild/install/bin/Lib/test/exception_hierarchy.txt

-- Installing: C:/superbuild/install/bin/Lib/test/floating_points.txt

-- Installing: C:/superbuild/install/bin/Lib/test/fork_wait.py

-- Installing: C:/superbuild/install/bin/Lib/test/formatfloat_testcases.txt

-- Installing: C:/superbuild/install/bin/Lib/test/gdb_sample.py

-- Installing: C:/superbuild/install/bin/Lib/test/greyrgb.uue

-- Installing: C:/superbuild/install/bin/Lib/test/https_svn_python_org_root.pem

-- Installing: C:/superbuild/install/bin/Lib/test/ieee754.txt

-- Installing: C:/superbuild/install/bin/Lib/test/infinite_reload.py

-- Installing: C:/superbuild/install/bin/Lib/test/inspect_fodder.py

-- Installing: C:/superbuild/install/bin/Lib/test/inspect_fodder2.py

-- Installing: C:/superbuild/install/bin/Lib/test/keycert.pem

-- Installing: C:/superbuild/install/bin/Lib/test/leakers

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/README.txt

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/test_ctypes.py

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/test_dictself.py

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/test_gestalt.py

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/test_selftype.py

-- Installing: C:/superbuild/install/bin/Lib/test/leakers/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/test/list_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/lock_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/mapping_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/math_testcases.txt

-- Installing: C:/superbuild/install/bin/Lib/test/nokia.pem

-- Installing: C:/superbuild/install/bin/Lib/test/nullcert.pem

-- Installing: C:/superbuild/install/bin/Lib/test/outstanding_bugs.py

-- Installing: C:/superbuild/install/bin/Lib/test/pickletester.py

-- Installing: C:/superbuild/install/bin/Lib/test/profilee.py

-- Installing: C:/superbuild/install/bin/Lib/test/pyclbr_input.py

-- Installing: C:/superbuild/install/bin/Lib/test/pydocfodder.py

-- Installing: C:/superbuild/install/bin/Lib/test/pydoc_mod.py

-- Installing: C:/superbuild/install/bin/Lib/test/pystone.py

-- Installing: C:/superbuild/install/bin/Lib/test/randv2_32.pck

-- Installing: C:/superbuild/install/bin/Lib/test/randv2_64.pck

-- Installing: C:/superbuild/install/bin/Lib/test/randv3.pck

-- Installing: C:/superbuild/install/bin/Lib/test/regrtest.py

-- Installing: C:/superbuild/install/bin/Lib/test/relimport.py

-- Installing: C:/superbuild/install/bin/Lib/test/reperf.py

-- Installing: C:/superbuild/install/bin/Lib/test/re_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/sample_doctest.py

-- Installing: C:/superbuild/install/bin/Lib/test/script_helper.py

-- Installing: C:/superbuild/install/bin/Lib/test/seq_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/sgml_input.html

-- Installing: C:/superbuild/install/bin/Lib/test/sha256.pem

-- Installing: C:/superbuild/install/bin/Lib/test/Sine-1000Hz-300ms.aif

-- Installing: C:/superbuild/install/bin/Lib/test/sortperf.py

-- Installing: C:/superbuild/install/bin/Lib/test/ssl_cert.pem

-- Installing: C:/superbuild/install/bin/Lib/test/ssl_key.pem

-- Installing: C:/superbuild/install/bin/Lib/test/string_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/subprocessdata

-- Installing: C:/superbuild/install/bin/Lib/test/subprocessdata/sigchild_ignore.py

-- Installing: C:/superbuild/install/bin/Lib/test/testall.py

-- Installing: C:/superbuild/install/bin/Lib/test/testcodec.py

-- Installing: C:/superbuild/install/bin/Lib/test/testimg.uue

-- Installing: C:/superbuild/install/bin/Lib/test/testimgr.uue

-- Installing: C:/superbuild/install/bin/Lib/test/testrgb.uue

-- Installing: C:/superbuild/install/bin/Lib/test/testtar.tar

-- Installing: C:/superbuild/install/bin/Lib/test/test_abc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_abstract_numbers.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_aepack.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_aifc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_al.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_anydbm.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_applesingle.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_argparse.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_array.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ascii_formatd.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ast.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_asynchat.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_asyncore.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_atexit.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_audioop.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_augassign.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_base64.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bastion.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bigaddrspace.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bigmem.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_binascii.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_binhex.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_binop.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bisect.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bool.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bsddb.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bsddb185.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bsddb3.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_buffer.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bufio.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_builtin.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bytes.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_bz2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_calendar.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_call.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_capi.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cd.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cfgparser.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cgi.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_charmapcodec.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_class.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cmath.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cmd.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cmd_line.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cmd_line_script.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_code.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codeccallbacks.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_cn.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_hk.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_iso2022.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_jp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_kr.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecencodings_tw.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecmaps_cn.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecmaps_hk.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecmaps_jp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecmaps_kr.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecmaps_tw.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codecs.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_codeop.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_coding.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_coercion.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_collections.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_colorsys.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_commands.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_compare.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_compile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_compileall.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_compiler.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_complex.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_complex_args.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_contains.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_contextlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cookie.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cookielib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_copy.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_copy_reg.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cpickle.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_cprofile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_crypt.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_csv.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ctypes.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_curses.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_datetime.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dbm.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_decimal.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_decorators.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_defaultdict.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_deque.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_descr.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_descrtut.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dict.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dictcomps.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dictviews.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_difflib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_difflib_expect.html

-- Installing: C:/superbuild/install/bin/Lib/test/test_dircache.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dis.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_distutils.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest.txt

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest2.txt

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest3.txt

-- Installing: C:/superbuild/install/bin/Lib/test/test_doctest4.txt

-- Installing: C:/superbuild/install/bin/Lib/test/test_docxmlrpc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dumbdbm.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dummy_thread.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_dummy_threading.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_email.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_email_codecs.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_email_renamed.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_enumerate.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_eof.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_epoll.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_errno.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_exceptions.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_exception_variations.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_extcall.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fcntl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_file.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_file2k.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_filecmp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fileinput.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fileio.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_float.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fnmatch.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fork1.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_format.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fpformat.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_fractions.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_frozen.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ftplib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_funcattrs.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_functools.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future1.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future3.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future4.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future5.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_future_builtins.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gdb.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gdbm.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_generators.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_genericpath.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_genexps.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_getargs.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_getargs2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_getopt.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gettext.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_glob.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_global.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_grammar.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_grp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_gzip.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_hash.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_hashlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_heapq.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_hmac.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_hotshot.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_htmllib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_htmlparser.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_httplib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_httpservers.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_imageop.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_imaplib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_imgfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_imp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_import.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_importhooks.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_importlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_index.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_inspect.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_int.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_int_literal.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_io.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ioctl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_isinstance.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_iter.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_iterlen.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_itertools.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_json.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_kqueue.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_largefile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_lib2to3.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_linecache.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_linuxaudiodev.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_list.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_locale.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_logging.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_long.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_longexp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_long_future.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_macos.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_macostools.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_macpath.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mailbox.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_marshal.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_math.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_md5.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_memoryio.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_memoryview.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mhlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mimetools.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mimetypes.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_MimeWriter.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_minidom.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mmap.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_module.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_modulefinder.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_msilib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_multibytecodec.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_multibytecodec_support.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_multifile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_multiprocessing.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mutants.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_mutex.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_netrc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_new.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_nis.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_normalization.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ntpath.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_old_mailbox.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_opcodes.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_openpty.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_operator.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_optparse.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_os.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ossaudiodev.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_parser.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pdb.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_peepholer.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pep247.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pep263.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pep277.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pep292.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pep352.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pickle.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pickletools.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pipes.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pkg.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pkgimport.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pkgutil.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_platform.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_plistlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_poll.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_popen.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_popen2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_poplib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_posix.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_posixpath.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pow.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pprint.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_print.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_profile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_property.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pstats.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pty.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pwd.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_py3kwarn.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pyclbr.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pydoc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_pyexpat.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_py_compile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_queue.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_quopri.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_random.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_re.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_readline.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_repr.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_resource.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_rfc822.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_richcmp.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_rlcompleter.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_robotparser.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_runpy.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sax.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_scope.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_scriptpackages.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_select.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_set.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_setcomps.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sets.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sgmllib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sha.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_shelve.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_shlex.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_shutil.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_signal.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_SimpleHTTPServer.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_site.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_slice.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_smtplib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_smtpnet.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_socket.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_socketserver.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_softspace.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sort.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sqlite.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ssl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_startfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_str.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_strftime.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_string.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_StringIO.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_stringprep.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_strop.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_strptime.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_strtod.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_struct.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_structmembers.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_structseq.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_subprocess.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sunaudiodev.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sundry.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_support.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_symtable.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_syntax.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sys.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sysconfig.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sys_setprofile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_sys_settrace.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tarfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tcl.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_telnetlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tempfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_textwrap.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_thread.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_threadedtempfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_threaded_import.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_threading.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_threading_local.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_threadsignals.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_time.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_timeout.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tk.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tokenize.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_trace.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_traceback.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_transformer.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ttk_guionly.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ttk_textonly.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_tuple.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_typechecks.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_types.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_ucn.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unary.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_undocumented_details.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unicode.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unicodedata.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unicode_file.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unittest.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_univnewlines.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_univnewlines2k.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_unpack.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urllib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urllib2.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urllib2net.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urllib2_localnet.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urllibnet.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_urlparse.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_userdict.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_userlist.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_userstring.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_uu.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_uuid.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_wait3.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_wait4.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_warnings.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_wave.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_weakref.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_weakset.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_whichdb.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_winreg.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_winsound.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_with.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_wsgiref.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xdrlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xmllib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xmlrpc.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xml_etree.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xml_etree_c.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xpickle.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_xrange.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_zipfile.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_zipfile64.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_zipimport.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_zipimport_support.py

-- Installing: C:/superbuild/install/bin/Lib/test/test_zlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/test__locale.py

-- Installing: C:/superbuild/install/bin/Lib/test/test___all__.py

-- Installing: C:/superbuild/install/bin/Lib/test/test___future__.py

-- Installing: C:/superbuild/install/bin/Lib/test/tf_inherit_check.py

-- Installing: C:/superbuild/install/bin/Lib/test/threaded_import_hangers.py

-- Installing: C:/superbuild/install/bin/Lib/test/time_hashlib.py

-- Installing: C:/superbuild/install/bin/Lib/test/tokenize_tests.txt

-- Installing: C:/superbuild/install/bin/Lib/test/tracedmodules

-- Installing: C:/superbuild/install/bin/Lib/test/tracedmodules/testmod.py

-- Installing: C:/superbuild/install/bin/Lib/test/tracedmodules/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/test/warning_tests.py

-- Installing: C:/superbuild/install/bin/Lib/test/win_console_handler.py

-- Installing: C:/superbuild/install/bin/Lib/test/wrongcert.pem

-- Installing: C:/superbuild/install/bin/Lib/test/xmltestdata

-- Installing: C:/superbuild/install/bin/Lib/test/xmltestdata/simple-ns.xml

-- Installing: C:/superbuild/install/bin/Lib/test/xmltestdata/simple.xml

-- Installing: C:/superbuild/install/bin/Lib/test/xmltestdata/test.xml

-- Installing: C:/superbuild/install/bin/Lib/test/xmltestdata/test.xml.out

-- Installing: C:/superbuild/install/bin/Lib/test/xmltests.py

-- Installing: C:/superbuild/install/bin/Lib/test/zipdir.zip

-- Installing: C:/superbuild/install/bin/Lib/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/textwrap.py

-- Installing: C:/superbuild/install/bin/Lib/textwrap.pyc

-- Installing: C:/superbuild/install/bin/Lib/this.py

-- Installing: C:/superbuild/install/bin/Lib/threading.py

-- Installing: C:/superbuild/install/bin/Lib/threading.pyc

-- Installing: C:/superbuild/install/bin/Lib/timeit.py

-- Installing: C:/superbuild/install/bin/Lib/toaiff.py

-- Installing: C:/superbuild/install/bin/Lib/token.py

-- Installing: C:/superbuild/install/bin/Lib/tokenize.py

-- Installing: C:/superbuild/install/bin/Lib/trace.py

-- Installing: C:/superbuild/install/bin/Lib/traceback.py

-- Installing: C:/superbuild/install/bin/Lib/traceback.pyc

-- Installing: C:/superbuild/install/bin/Lib/tty.py

-- Installing: C:/superbuild/install/bin/Lib/types.py

-- Installing: C:/superbuild/install/bin/Lib/types.pyc

-- Installing: C:/superbuild/install/bin/Lib/unicodedata.pyd

-- Installing: C:/superbuild/install/bin/Lib/unittest

-- Installing: C:/superbuild/install/bin/Lib/unittest/case.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/case.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/loader.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/loader.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/main.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/main.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/result.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/result.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/runner.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/runner.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/signals.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/signals.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/suite.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/suite.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/test

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/dummy.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/support.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_assertions.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_break.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_case.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_discovery.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_functiontestcase.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_loader.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_program.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_result.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_runner.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_setups.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_skipping.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/test_suite.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/test/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/util.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/util.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/unittest/__init__.pyc

-- Installing: C:/superbuild/install/bin/Lib/unittest/__main__.py

-- Installing: C:/superbuild/install/bin/Lib/urllib.py

-- Installing: C:/superbuild/install/bin/Lib/urllib2.py

-- Installing: C:/superbuild/install/bin/Lib/urlparse.py

-- Installing: C:/superbuild/install/bin/Lib/user.py

-- Installing: C:/superbuild/install/bin/Lib/UserDict.py

-- Installing: C:/superbuild/install/bin/Lib/UserDict.pyc

-- Installing: C:/superbuild/install/bin/Lib/UserList.py

-- Installing: C:/superbuild/install/bin/Lib/UserString.py

-- Installing: C:/superbuild/install/bin/Lib/uu.py

-- Installing: C:/superbuild/install/bin/Lib/uuid.py

-- Installing: C:/superbuild/install/bin/Lib/warnings.py

-- Installing: C:/superbuild/install/bin/Lib/warnings.pyc

-- Installing: C:/superbuild/install/bin/Lib/wave.py

-- Installing: C:/superbuild/install/bin/Lib/weakref.py

-- Installing: C:/superbuild/install/bin/Lib/weakref.pyc

-- Installing: C:/superbuild/install/bin/Lib/webbrowser.py

-- Installing: C:/superbuild/install/bin/Lib/whichdb.py

-- Installing: C:/superbuild/install/bin/Lib/winsound.pyd

-- Installing: C:/superbuild/install/bin/Lib/wsgiref

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/handlers.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/headers.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/simple_server.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/util.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/validate.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/wsgiref.egg-info

-- Installing: C:/superbuild/install/bin/Lib/xdrlib.py

-- Installing: C:/superbuild/install/bin/Lib/xml

-- Installing: C:/superbuild/install/bin/Lib/xml/dom

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/domreg.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/expatbuilder.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/minicompat.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/minidom.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/NodeFilter.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/pulldom.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/xmlbuilder.py

-- Installing: C:/superbuild/install/bin/Lib/xml/dom/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/xml/etree

-- Installing: C:/superbuild/install/bin/Lib/xml/etree/cElementTree.py

-- Installing: C:/superbuild/install/bin/Lib/xml/etree/ElementInclude.py

-- Installing: C:/superbuild/install/bin/Lib/xml/etree/ElementPath.py

-- Installing: C:/superbuild/install/bin/Lib/xml/etree/ElementTree.py

-- Installing: C:/superbuild/install/bin/Lib/xml/etree/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/xml/parsers

-- Installing: C:/superbuild/install/bin/Lib/xml/parsers/expat.py

-- Installing: C:/superbuild/install/bin/Lib/xml/parsers/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/expatreader.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/handler.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/saxutils.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/xmlreader.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/_exceptions.py

-- Installing: C:/superbuild/install/bin/Lib/xml/sax/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/xml/__init__.py

-- Installing: C:/superbuild/install/bin/Lib/xmllib.py

-- Installing: C:/superbuild/install/bin/Lib/xmlrpclib.py

-- Installing: C:/superbuild/install/bin/Lib/zipfile.py

-- Installing: C:/superbuild/install/bin/Lib/_abcoll.py

-- Installing: C:/superbuild/install/bin/Lib/_abcoll.pyc

-- Installing: C:/superbuild/install/bin/Lib/_ctypes.pyd

-- Installing: C:/superbuild/install/bin/Lib/_ctypes_test.pyd

-- Installing: C:/superbuild/install/bin/Lib/_elementtree.pyd

-- Installing: C:/superbuild/install/bin/Lib/_LWPCookieJar.py

-- Installing: C:/superbuild/install/bin/Lib/_MozillaCookieJar.py

-- Installing: C:/superbuild/install/bin/Lib/_msi.pyd

-- Installing: C:/superbuild/install/bin/Lib/_multiprocessing.pyd

-- Installing: C:/superbuild/install/bin/Lib/_pyio.py

-- Installing: C:/superbuild/install/bin/Lib/_socket.pyd

-- Installing: C:/superbuild/install/bin/Lib/_strptime.py

-- Installing: C:/superbuild/install/bin/Lib/_testcapi.pyd

-- Installing: C:/superbuild/install/bin/Lib/_threading_local.py

-- Installing: C:/superbuild/install/bin/Lib/_weakrefset.py

-- Installing: C:/superbuild/install/bin/Lib/_weakrefset.pyc

-- Installing: C:/superbuild/install/bin/Lib/__future__.py

-- Installing: C:/superbuild/install/bin/Lib/__future__.pyc

-- Installing: C:/superbuild/install/bin/Lib/__phello__.foo.py

-- Installing: C:/superbuild/install/bin/libpng-config

-- Installing: C:/superbuild/install/bin/libpng14-config

-- Installing: C:/superbuild/install/bin/libpng14.dll

-- Installing: C:/superbuild/install/bin/python.exe

-- Installing: C:/superbuild/install/bin/python27.dll

-- Installing: C:/superbuild/install/bin/pythonw.exe

-- Installing: C:/superbuild/install/bin/w9xpopen.exe

-- Installing: C:/superbuild/install/bin/zlib1.dll

-- Installing: C:/superbuild/install/include/bzlib.h

-- Installing: C:/superbuild/install/include/freetype2

-- Installing: C:/superbuild/install/include/freetype2/freetype

-- Installing: C:/superbuild/install/include/freetype2/freetype/config

-- Installing: C:/superbuild/install/include/freetype2/freetype/config/ftconfig.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/config/ftheader.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/config/ftmodule.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/config/ftoption.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/config/ftstdlib.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/freetype.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftadvanc.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftbbox.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftbdf.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftbitmap.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftbzip2.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftcache.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftchapters.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftcid.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/fterrdef.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/fterrors.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftgasp.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftglyph.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftgxval.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftgzip.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftimage.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftincrem.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftlcdfil.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftlist.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftlzw.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftmac.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftmm.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftmodapi.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftmoderr.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftotval.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftoutln.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftpfr.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftrender.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftsizes.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftsnames.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftstroke.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftsynth.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftsystem.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/fttrigon.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/fttypes.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftwinfnt.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ftxf86.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/autohint.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftcalc.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftdebug.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftdriver.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftgloadr.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftmemory.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftobjs.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftpic.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftrfork.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftserv.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftstream.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/fttrace.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/ftvalid.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/internal.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/psaux.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/pshints.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svbdf.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svcid.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svgldict.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svgxval.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svkern.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svmm.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svotval.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svpfr.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svpostnm.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svpscmap.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svpsinfo.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svsfnt.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svttcmap.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svtteng.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svttglyf.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svwinfnt.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/services/svxf86nm.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/sfnt.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/t1types.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/internal/tttypes.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/t1tables.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ttnameid.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/tttables.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/tttags.h

-- Installing: C:/superbuild/install/include/freetype2/freetype/ttunpat.h

-- Installing: C:/superbuild/install/include/freetype2/ft2build.h

-- Installing: C:/superbuild/install/include/libpng14

-- Installing: C:/superbuild/install/include/libpng14/png.h

-- Installing: C:/superbuild/install/include/libpng14/pngconf.h

-- Installing: C:/superbuild/install/include/png.h

-- Installing: C:/superbuild/install/include/pngconf.h

-- Installing: C:/superbuild/install/include/python2.7

-- Installing: C:/superbuild/install/include/python2.7/abstract.h

-- Installing: C:/superbuild/install/include/python2.7/asdl.h

-- Installing: C:/superbuild/install/include/python2.7/ast.h

-- Installing: C:/superbuild/install/include/python2.7/bitset.h

-- Installing: C:/superbuild/install/include/python2.7/boolobject.h

-- Installing: C:/superbuild/install/include/python2.7/bufferobject.h

-- Installing: C:/superbuild/install/include/python2.7/bytearrayobject.h

-- Installing: C:/superbuild/install/include/python2.7/bytesobject.h

-- Installing: C:/superbuild/install/include/python2.7/bytes_methods.h

-- Installing: C:/superbuild/install/include/python2.7/cellobject.h

-- Installing: C:/superbuild/install/include/python2.7/ceval.h

-- Installing: C:/superbuild/install/include/python2.7/classobject.h

-- Installing: C:/superbuild/install/include/python2.7/cobject.h

-- Installing: C:/superbuild/install/include/python2.7/code.h

-- Installing: C:/superbuild/install/include/python2.7/codecs.h

-- Installing: C:/superbuild/install/include/python2.7/compile.h

-- Installing: C:/superbuild/install/include/python2.7/complexobject.h

-- Installing: C:/superbuild/install/include/python2.7/cStringIO.h

-- Installing: C:/superbuild/install/include/python2.7/datetime.h

-- Installing: C:/superbuild/install/include/python2.7/descrobject.h

-- Installing: C:/superbuild/install/include/python2.7/dictobject.h

-- Installing: C:/superbuild/install/include/python2.7/dtoa.h

-- Installing: C:/superbuild/install/include/python2.7/enumobject.h

-- Installing: C:/superbuild/install/include/python2.7/errcode.h

-- Installing: C:/superbuild/install/include/python2.7/eval.h

-- Installing: C:/superbuild/install/include/python2.7/fileobject.h

-- Installing: C:/superbuild/install/include/python2.7/floatobject.h

-- Installing: C:/superbuild/install/include/python2.7/frameobject.h

-- Installing: C:/superbuild/install/include/python2.7/funcobject.h

-- Installing: C:/superbuild/install/include/python2.7/genobject.h

-- Installing: C:/superbuild/install/include/python2.7/graminit.h

-- Installing: C:/superbuild/install/include/python2.7/grammar.h

-- Installing: C:/superbuild/install/include/python2.7/import.h

-- Installing: C:/superbuild/install/include/python2.7/intobject.h

-- Installing: C:/superbuild/install/include/python2.7/intrcheck.h

-- Installing: C:/superbuild/install/include/python2.7/iterobject.h

-- Installing: C:/superbuild/install/include/python2.7/listobject.h

-- Installing: C:/superbuild/install/include/python2.7/longintrepr.h

-- Installing: C:/superbuild/install/include/python2.7/longobject.h

-- Installing: C:/superbuild/install/include/python2.7/marshal.h

-- Installing: C:/superbuild/install/include/python2.7/memoryobject.h

-- Installing: C:/superbuild/install/include/python2.7/metagrammar.h

-- Installing: C:/superbuild/install/include/python2.7/methodobject.h

-- Installing: C:/superbuild/install/include/python2.7/modsupport.h

-- Installing: C:/superbuild/install/include/python2.7/moduleobject.h

-- Installing: C:/superbuild/install/include/python2.7/node.h

-- Installing: C:/superbuild/install/include/python2.7/object.h

-- Installing: C:/superbuild/install/include/python2.7/objimpl.h

-- Installing: C:/superbuild/install/include/python2.7/opcode.h

-- Installing: C:/superbuild/install/include/python2.7/osdefs.h

-- Installing: C:/superbuild/install/include/python2.7/parsetok.h

-- Installing: C:/superbuild/install/include/python2.7/patchlevel.h

-- Installing: C:/superbuild/install/include/python2.7/pgen.h

-- Installing: C:/superbuild/install/include/python2.7/pgenheaders.h

-- Installing: C:/superbuild/install/include/python2.7/pyarena.h

-- Installing: C:/superbuild/install/include/python2.7/pycapsule.h

-- Installing: C:/superbuild/install/include/python2.7/pyconfig.h

-- Installing: C:/superbuild/install/include/python2.7/pyctype.h

-- Installing: C:/superbuild/install/include/python2.7/pydebug.h

-- Installing: C:/superbuild/install/include/python2.7/pyerrors.h

-- Installing: C:/superbuild/install/include/python2.7/pyexpat.h

-- Installing: C:/superbuild/install/include/python2.7/pyfpe.h

-- Installing: C:/superbuild/install/include/python2.7/pygetopt.h

-- Installing: C:/superbuild/install/include/python2.7/pymacconfig.h

-- Installing: C:/superbuild/install/include/python2.7/pymactoolbox.h

-- Installing: C:/superbuild/install/include/python2.7/pymath.h

-- Installing: C:/superbuild/install/include/python2.7/pymem.h

-- Installing: C:/superbuild/install/include/python2.7/pyport.h

-- Installing: C:/superbuild/install/include/python2.7/pystate.h

-- Installing: C:/superbuild/install/include/python2.7/pystrcmp.h

-- Installing: C:/superbuild/install/include/python2.7/pystrtod.h

-- Installing: C:/superbuild/install/include/python2.7/Python-ast.h

-- Installing: C:/superbuild/install/include/python2.7/Python.h

-- Installing: C:/superbuild/install/include/python2.7/pythonrun.h

-- Installing: C:/superbuild/install/include/python2.7/pythread.h

-- Installing: C:/superbuild/install/include/python2.7/py_curses.h

-- Installing: C:/superbuild/install/include/python2.7/rangeobject.h

-- Installing: C:/superbuild/install/include/python2.7/setobject.h

-- Installing: C:/superbuild/install/include/python2.7/sliceobject.h

-- Installing: C:/superbuild/install/include/python2.7/stringobject.h

-- Installing: C:/superbuild/install/include/python2.7/structmember.h

-- Installing: C:/superbuild/install/include/python2.7/structseq.h

-- Installing: C:/superbuild/install/include/python2.7/symtable.h

-- Installing: C:/superbuild/install/include/python2.7/sysmodule.h

-- Installing: C:/superbuild/install/include/python2.7/timefuncs.h

-- Installing: C:/superbuild/install/include/python2.7/token.h

-- Installing: C:/superbuild/install/include/python2.7/traceback.h

-- Installing: C:/superbuild/install/include/python2.7/tupleobject.h

-- Installing: C:/superbuild/install/include/python2.7/ucnhash.h

-- Installing: C:/superbuild/install/include/python2.7/unicodeobject.h

-- Installing: C:/superbuild/install/include/python2.7/warnings.h

-- Installing: C:/superbuild/install/include/python2.7/weakrefobject.h

-- Installing: C:/superbuild/install/include/zconf.h

-- Installing: C:/superbuild/install/include/zlib.h

-- Installing: C:/superbuild/install/lib/bz2.lib

-- Installing: C:/superbuild/install/lib/freetype.lib

-- Installing: C:/superbuild/install/lib/libpng

-- Installing: C:/superbuild/install/lib/libpng/libpng14-release.cmake

-- Installing: C:/superbuild/install/lib/libpng/libpng14.cmake

-- Installing: C:/superbuild/install/lib/libpng14.lib

-- Installing: C:/superbuild/install/lib/libpng14_static.lib

-- Installing: C:/superbuild/install/lib/pkgconfig

-- Installing: C:/superbuild/install/lib/pkgconfig/libpng.pc

-- Installing: C:/superbuild/install/lib/pkgconfig/libpng14.pc

-- Installing: C:/superbuild/install/lib/png.lib

-- Installing: C:/superbuild/install/lib/pyexpat.lib

-- Installing: C:/superbuild/install/lib/python27.lib

-- Installing: C:/superbuild/install/lib/select.lib

-- Installing: C:/superbuild/install/lib/unicodedata.lib

-- Installing: C:/superbuild/install/lib/winsound.lib

-- Installing: C:/superbuild/install/lib/z.lib

-- Installing: C:/superbuild/install/lib/zlib.lib

-- Installing: C:/superbuild/install/lib/zlibstatic.lib

-- Installing: C:/superbuild/install/lib/_ctypes.lib

-- Installing: C:/superbuild/install/lib/_ctypes_test.lib

-- Installing: C:/superbuild/install/lib/_elementtree.lib

-- Installing: C:/superbuild/install/lib/_msi.lib

-- Installing: C:/superbuild/install/lib/_multiprocessing.lib

-- Installing: C:/superbuild/install/lib/_socket.lib

-- Installing: C:/superbuild/install/lib/_testcapi.lib

-- Installing: C:/superbuild/install/share/man

-- Installing: C:/superbuild/install/share/man/man3

-- Installing: C:/superbuild/install/share/man/man3/libpng.3

-- Installing: C:/superbuild/install/share/man/man3/libpngpf.3

-- Installing: C:/superbuild/install/share/man/man3/zlib.3

-- Installing: C:/superbuild/install/share/man/man5

-- Installing: C:/superbuild/install/share/man/man5/png.5

-- Installing: C:/superbuild/install/share/pkgconfig

-- Installing: C:/superbuild/install/share/pkgconfig/zlib.pc

ninja: build stopped: subcommand failed.
-------------- next part --------------
[1/87] Completed 'tbb'
[2/87] Completed 'python'
[3/87] Performing configure step for 'szip'
FAILED: szip/src/szip-stamp/szip-configure 
cmd.exe /C "cd /D C:\superbuild\szip\src\szip-build && "C:\Program Files (x86)\CMake\bin\cmake.exe" -DBUILD_SHARED_LIBS:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=C:/superbuild/install -DCMAKE_PREFIX_PATH:PATH=C:/superbuild/install "-DCMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3" "-DCMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc" -DCMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64 -DCMAKE_BUILD_TYPE:STRING=Debug "-DCMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1" "-DCMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG" "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG" -GNinja C:/superbuild/szip/src/szip && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/szip/src/szip-stamp/szip-configure"
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

[4/87] No configure step for 'zlib'
[5/87] Creating directories for 'matplotlib'
[6/87] Creating directories for 'freetype'
[7/87] Creating directories for 'numpy'
[8/87] Performing build step for 'qt4'
FAILED: qt4/src/qt4-stamp/qt4-build 
cmd.exe /C "cd /D C:\superbuild\qt4\src\qt4 && "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E touch C:/superbuild/qt4/src/qt4-stamp/qt4-build"


Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



	cd src\tools\bootstrap\ && "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" -f Makefile



Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



	"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe" -f Makefile.Release



Microsoft (R) Program Maintenance Utility Version 12.00.21005.1

Copyright (C) Microsoft Corporation.  All rights reserved.



NMAKE : fatal error U1073: don't know how to make 'c:/Program\'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\nmake.exe"' : return code '0x2'

Stop.

NMAKE : fatal error U1077: 'cd' : return code '0x2'

Stop.

ninja: build stopped: subcommand failed.