From sankhesh.jhaveri at kitware.com  Wed Oct  1 12:31:06 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Wed, 01 Oct 2014 09:31:06 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Tuesday, September 30 2014
Message-ID: <20141001163104.D53547FF51@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Mac10.7.5-clang-nightlymaster-release 2
   -------------------- REPORT --------------------
   2 FAILURES
   [2]pvcrs.TraceSupplementalProxiesFully , 1 ,
   ['Mac10.7.5-clang-nightlymaster-release']
   [3]pvcrs.TraceExportAndSaveData , 1 ,
   ['Mac10.7.5-clang-nightlymaster-release']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [4]Win32-vs9-shared-release 1
   [5]Win7x64-ninja-nightlynext-shared-release 1
   [6]Win7x64-vs10-static-release 1
   [7]Win64-vs9-shared-debug-nocollab 1
   [8]Win7x64-vs10-shared-release 1
   -------------------- REPORT --------------------
   2 FAILURES
   [9]pv.CatalystLiveSetBreakpoint , 1 ,
   ['Win64-vs9-shared-debug-nocollab']
   [10]pv.ResetToVisibleRange , 4 , ['Win32-vs9-shared-release',
   'Win7x64-ninja-nightlynext-shared-release',
   'Win7x64-vs10-static-release', 'Win7x64-vs10-shared-release']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   2. http://open.cdash.org/testSummary.php?project=9&date=2014-10-01&name=pvcrs.TraceSupplementalProxiesFully
   3. http://open.cdash.org/testSummary.php?project=9&date=2014-10-01&name=pvcrs.TraceExportAndSaveData
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-01&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release
   9. http://open.cdash.org/testSummary.php?project=9&date=2014-10-01&name=pv.CatalystLiveSetBreakpoint
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-01&name=pv.ResetToVisibleRange

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141001/e16489e0/attachment-0001.html>

From panos.asproulis at gmail.com  Thu Oct  2 07:40:42 2014
From: panos.asproulis at gmail.com (Panos Asproulis)
Date: Thu, 02 Oct 2014 13:40:42 +0200
Subject: [Paraview-developers] XY Chart Plots - changes in ParaView 4.2.0
Message-ID: <542D39BA.7030001@gmail.com>

Hi all,

In ParaView 4.1.0 I use the following code in order to specify some 
information regarding the axes in a typical XY line plot (chart):

   // Specify the name of the axes
   QList<QVariant> axisTitles;
   axisTitles << "Error" << "Number of Time Steps" << "";
   pqSMAdaptor::setMultipleElementProperty(
       viewProxy->GetProperty("AxisTitle"), axisTitles);

   // Enable the logarithmic scale for the y-axis
   QList<QVariant> logScale;
   logScale << 1 << 0 << 0;
   pqSMAdaptor::setMultipleElementProperty(
       viewProxy->GetProperty("AxisLogScale"), logScale);

Although this works fine in 4.1.0 it no longer works in ParaView 4.2.0 
because the properties "AxisTitle" and "AxisLogScale" no longer exist. 
They have been replaced by "LeftAxisTitle", "BottomAxisTitle" etc and 
"LeftAxisLogScale", "BottomAxisLogScale" etc. So, I changed the above 
code to the following:

   // Set the name of the left axis
   QList<QVariant> leftAxisTitle;
   leftAxisTitle << "Error";
   pqSMAdaptor::setElementProperty(
       viewProxy->GetProperty("LeftAxisTitle"), leftAxisTitle);

   // Set the name of the bottom axis
   QList<QVariant> bottomAxisTitle;
   bottomAxisTitle << "Number of Time Steps";
   pqSMAdaptor::setElementProperty(
       viewProxy->GetProperty("BottomAxisTitle"), bottomAxisTitle);

   // Enable the logarithmic scalefor the left axis
   QList<QVariant> onLogScale, offLogScale;
   onLogScale  << 1;
   offLogScale << 0;
   pqSMAdaptor::setElementProperty(
       viewProxy->GetProperty("LeftAxisLogScale"), onLogScale);
   pqSMAdaptor::setElementProperty(
       viewProxy->GetProperty("BottomAxisLogScale"), offLogScale);

However, this has no effect. It does not change the title of the axes 
and it does not switch on the logarithmic scale for the left axis. Could 
someone let me know how to do that in 4.2.0?

Regards,
Panos


From frank.tt at einseinself.org  Thu Oct  2 08:22:26 2014
From: frank.tt at einseinself.org (Frank TT)
Date: Thu, 02 Oct 2014 14:22:26 +0200
Subject: [Paraview-developers] Filter Plugin
In-Reply-To: <CADHSJjApAYveFUA9Jx5yC1+W-=_YJ3PUrbVzbJbWfJcmfiswnw@mail.gmail.com>
References: <1411957714.20122.15.camel@Judika>
 <CADHSJjApAYveFUA9Jx5yC1+W-=_YJ3PUrbVzbJbWfJcmfiswnw@mail.gmail.com>
Message-ID: <cd6f417b743b3232a5a9b7cc0b05e22f@einseinself.org>

On 2014-09-29 14:37, Utkarsh Ayachit wrote:
> Frank,
> 
> ParaView is based on VTK, and relies on VTK to provide the execution
> model and data model. Thus, when writing you a new data processing
> filter, you're basically going to wrote a VTK filter. The ParaView
> plugin infrastructure comes into play to make such a VTK filter
> available/accessible in ParaView.
> 
> I'd suggesting starting with a existing VTK filter that closely
> matches what you're doing e.g. vtkMarchingCubes [1].
> 
> [1] http://www.vtk.org/doc/nightly/html/classvtkImageMarchingCubes.html

Thx, the plugin is working, in basic. I have a problem to update the iso 
surface, when the iso value was changed by user. vtkPolyData has no 
Update() function.
How can I do an update on outputData?

Greetings,

Frank




### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### 
###
//marchingCubes.cxx

#include <iostream>

#include "vtkObjectFactory.h"
#include "vtkInformation.h"
#include "vtkInformationVector.h"
#include "vtkSmartPointer.h"
#include "vtkDemandDrivenPipeline.h"
#include "vtkImageData.h"
#include "vtkPolyData.h"

#include "marchingCubes.h"

vtkStandardNewMacro(marchingCubes);

//----------------------------------------------------------------------------
marchingCubes::marchingCubes()
{
     inputInfo = vtkSmartPointer< vtkInformation >::New();
     outputInfo = vtkSmartPointer< vtkInformation >::New();

     inputData = vtkSmartPointer< vtkImageData >::New();
     outputData = vtkSmartPointer< vtkPolyData >::New();

     marchingData = vtkSmartPointer< vtkImageMarchingCubes >::New();

     firstRun = true;// Will be true, while ::RequestData(?) was not 
running. (When 'Apply' was already not pressed.)
}

//----------------------------------------------------------------------------
marchingCubes::~marchingCubes()
{

}

//----------------------------------------------------------------------------
void marchingCubes::PrintSelf(ostream& os, vtkIndent indent)
{
   this->Superclass::PrintSelf(os,indent);
}

//----------------------------------------------------------------------------
int marchingCubes::RequestData( vtkInformation *vtkNotUsed(request),
                                         vtkInformationVector 
**inputVector,
                                         vtkInformationVector 
*outputVector)
{
     inputInfo = inputVector[0]->GetInformationObject(0);
     outputInfo = outputVector->GetInformationObject(0);

     inputData = vtkImageData::SafeDownCast( inputInfo->Get( 
vtkDataObject::DATA_OBJECT() ) );
     outputData = vtkPolyData::SafeDownCast( 
outputInfo->Get(vtkDataObject::DATA_OBJECT() ) );

     this->updateMarchingData();

     firstRun = false;

     return 1;
}

//----------------------------------------------------------------------------
// From application.
void marchingCubes::setIsoValue(double value)
{
     isoValue = value;
     this->updateMarchingData();
}

double marchingCubes::getIsoValue()
{
     return isoValue;
}

//----------------------------------------------------------------------------
void marchingCubes::updateMarchingData()
{
//TODO: Implement all iso surface(s) creation modes by 
vtkImageMarchingCubes.

     if(!firstRun)
     {
         marchingData->SetValue(0, this->getIsoValue());
         marchingData->Update();

         //outputData = NULL;
         //outputData->Delete();
         outputData->CopyStructure(marchingData->GetOutput(0));
     }else
     {
             marchingData->SetInputData(inputData);
             marchingData->SetValue(0, this->getIsoValue());
             marchingData->Update();

             
//outputData->SetPolys(marchingData->GetOutput()->GetPolys());// Does 
not work.
             outputData->CopyStructure(marchingData->GetOutput(0));
     }
}


From utkarsh.ayachit at kitware.com  Thu Oct  2 08:24:32 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Oct 2014 08:24:32 -0400
Subject: [Paraview-developers] Filter Plugin
In-Reply-To: <cd6f417b743b3232a5a9b7cc0b05e22f@einseinself.org>
References: <1411957714.20122.15.camel@Judika>
 <CADHSJjApAYveFUA9Jx5yC1+W-=_YJ3PUrbVzbJbWfJcmfiswnw@mail.gmail.com>
 <cd6f417b743b3232a5a9b7cc0b05e22f@einseinself.org>
Message-ID: <CADHSJjC36gVPDRDzbdA08dSndNvSKAdTtqDBHL=dmgD5CY=3Vw@mail.gmail.com>

You need to call Modified() any time properties on the
vtkAlogirthm-subclass change to trigger execution.

void marchingCubes::setIsoValue(double value)
{
   if (isoValue !=  value)
    {
    isoValue = value;
    this->updateMarchingData();
    this->Modified();
    }
}

On Thu, Oct 2, 2014 at 8:22 AM, Frank TT <frank.tt at einseinself.org> wrote:
> On 2014-09-29 14:37, Utkarsh Ayachit wrote:
>>
>> Frank,
>>
>> ParaView is based on VTK, and relies on VTK to provide the execution
>> model and data model. Thus, when writing you a new data processing
>> filter, you're basically going to wrote a VTK filter. The ParaView
>> plugin infrastructure comes into play to make such a VTK filter
>> available/accessible in ParaView.
>>
>> I'd suggesting starting with a existing VTK filter that closely
>> matches what you're doing e.g. vtkMarchingCubes [1].
>>
>> [1] http://www.vtk.org/doc/nightly/html/classvtkImageMarchingCubes.html
>
>
> Thx, the plugin is working, in basic. I have a problem to update the iso
> surface, when the iso value was changed by user. vtkPolyData has no Update()
> function.
> How can I do an update on outputData?
>
> Greetings,
>
> Frank
>
>
>
>
> ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
> //marchingCubes.cxx
>
> #include <iostream>
>
> #include "vtkObjectFactory.h"
> #include "vtkInformation.h"
> #include "vtkInformationVector.h"
> #include "vtkSmartPointer.h"
> #include "vtkDemandDrivenPipeline.h"
> #include "vtkImageData.h"
> #include "vtkPolyData.h"
>
> #include "marchingCubes.h"
>
> vtkStandardNewMacro(marchingCubes);
>
> //----------------------------------------------------------------------------
> marchingCubes::marchingCubes()
> {
>     inputInfo = vtkSmartPointer< vtkInformation >::New();
>     outputInfo = vtkSmartPointer< vtkInformation >::New();
>
>     inputData = vtkSmartPointer< vtkImageData >::New();
>     outputData = vtkSmartPointer< vtkPolyData >::New();
>
>     marchingData = vtkSmartPointer< vtkImageMarchingCubes >::New();
>
>     firstRun = true;// Will be true, while ::RequestData(?) was not running.
> (When 'Apply' was already not pressed.)
> }
>
> //----------------------------------------------------------------------------
> marchingCubes::~marchingCubes()
> {
>
> }
>
> //----------------------------------------------------------------------------
> void marchingCubes::PrintSelf(ostream& os, vtkIndent indent)
> {
>   this->Superclass::PrintSelf(os,indent);
> }
>
> //----------------------------------------------------------------------------
> int marchingCubes::RequestData( vtkInformation *vtkNotUsed(request),
>                                         vtkInformationVector **inputVector,
>                                         vtkInformationVector *outputVector)
> {
>     inputInfo = inputVector[0]->GetInformationObject(0);
>     outputInfo = outputVector->GetInformationObject(0);
>
>     inputData = vtkImageData::SafeDownCast( inputInfo->Get(
> vtkDataObject::DATA_OBJECT() ) );
>     outputData = vtkPolyData::SafeDownCast(
> outputInfo->Get(vtkDataObject::DATA_OBJECT() ) );
>
>     this->updateMarchingData();
>
>     firstRun = false;
>
>     return 1;
> }
>
> //----------------------------------------------------------------------------
> // From application.
> void marchingCubes::setIsoValue(double value)
> {
>     isoValue = value;
>     this->updateMarchingData();
> }
>
> double marchingCubes::getIsoValue()
> {
>     return isoValue;
> }
>
> //----------------------------------------------------------------------------
> void marchingCubes::updateMarchingData()
> {
> //TODO: Implement all iso surface(s) creation modes by
> vtkImageMarchingCubes.
>
>     if(!firstRun)
>     {
>         marchingData->SetValue(0, this->getIsoValue());
>         marchingData->Update();
>
>         //outputData = NULL;
>         //outputData->Delete();
>         outputData->CopyStructure(marchingData->GetOutput(0));
>     }else
>     {
>             marchingData->SetInputData(inputData);
>             marchingData->SetValue(0, this->getIsoValue());
>             marchingData->Update();
>
>             //outputData->SetPolys(marchingData->GetOutput()->GetPolys());//
> Does not work.
>             outputData->CopyStructure(marchingData->GetOutput(0));
>     }
> }
>

From frank.tt at einseinself.org  Thu Oct  2 09:45:29 2014
From: frank.tt at einseinself.org (Frank TT)
Date: Thu, 02 Oct 2014 15:45:29 +0200
Subject: [Paraview-developers] Filter Plugin (update plugin data)
In-Reply-To: <CADHSJjC36gVPDRDzbdA08dSndNvSKAdTtqDBHL=dmgD5CY=3Vw@mail.gmail.com>
References: <1411957714.20122.15.camel@Judika>
 <CADHSJjApAYveFUA9Jx5yC1+W-=_YJ3PUrbVzbJbWfJcmfiswnw@mail.gmail.com>
 <cd6f417b743b3232a5a9b7cc0b05e22f@einseinself.org>
 <CADHSJjC36gVPDRDzbdA08dSndNvSKAdTtqDBHL=dmgD5CY=3Vw@mail.gmail.com>
Message-ID: <9651a9d97bf73ff82d8a599f76b2d71f@einseinself.org>

On 2014-10-02 14:24, Utkarsh Ayachit wrote:
> You need to call Modified() any time properties on the
> vtkAlogirthm-subclass change to trigger execution.
> 
> void marchingCubes::setIsoValue(double value)
> {
>    if (isoValue !=  value)
>     {
>     isoValue = value;
>     this->updateMarchingData();
>     this->Modified();
>     }
> }

Thx. It's working.






> On Thu, Oct 2, 2014 at 8:22 AM, Frank TT <frank.tt at einseinself.org> 
> wrote:
>> On 2014-09-29 14:37, Utkarsh Ayachit wrote:
>>> 
>>> Frank,
>>> 
>>> ParaView is based on VTK, and relies on VTK to provide the execution
>>> model and data model. Thus, when writing you a new data processing
>>> filter, you're basically going to wrote a VTK filter. The ParaView
>>> plugin infrastructure comes into play to make such a VTK filter
>>> available/accessible in ParaView.
>>> 
>>> I'd suggesting starting with a existing VTK filter that closely
>>> matches what you're doing e.g. vtkMarchingCubes [1].
>>> 
>>> [1] 
>>> http://www.vtk.org/doc/nightly/html/classvtkImageMarchingCubes.html
>> 
>> 
>> Thx, the plugin is working, in basic. I have a problem to update the 
>> iso
>> surface, when the iso value was changed by user. vtkPolyData has no 
>> Update()
>> function.
>> How can I do an update on outputData?
>> 
>> Greetings,
>> 
>> Frank
>> 
>> 
>> 
>> 
>> ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### 
>> ### ###
>> //marchingCubes.cxx
>> 
>> #include <iostream>
>> 
>> #include "vtkObjectFactory.h"
>> #include "vtkInformation.h"
>> #include "vtkInformationVector.h"
>> #include "vtkSmartPointer.h"
>> #include "vtkDemandDrivenPipeline.h"
>> #include "vtkImageData.h"
>> #include "vtkPolyData.h"
>> 
>> #include "marchingCubes.h"
>> 
>> vtkStandardNewMacro(marchingCubes);
>> 
>> //----------------------------------------------------------------------------
>> marchingCubes::marchingCubes()
>> {
>>     inputInfo = vtkSmartPointer< vtkInformation >::New();
>>     outputInfo = vtkSmartPointer< vtkInformation >::New();
>> 
>>     inputData = vtkSmartPointer< vtkImageData >::New();
>>     outputData = vtkSmartPointer< vtkPolyData >::New();
>> 
>>     marchingData = vtkSmartPointer< vtkImageMarchingCubes >::New();
>> 
>>     firstRun = true;// Will be true, while ::RequestData(?) was not 
>> running.
>> (When 'Apply' was already not pressed.)
>> }
>> 
>> //----------------------------------------------------------------------------
>> marchingCubes::~marchingCubes()
>> {
>> 
>> }
>> 
>> //----------------------------------------------------------------------------
>> void marchingCubes::PrintSelf(ostream& os, vtkIndent indent)
>> {
>>   this->Superclass::PrintSelf(os,indent);
>> }
>> 
>> //----------------------------------------------------------------------------
>> int marchingCubes::RequestData( vtkInformation *vtkNotUsed(request),
>>                                         vtkInformationVector 
>> **inputVector,
>>                                         vtkInformationVector 
>> *outputVector)
>> {
>>     inputInfo = inputVector[0]->GetInformationObject(0);
>>     outputInfo = outputVector->GetInformationObject(0);
>> 
>>     inputData = vtkImageData::SafeDownCast( inputInfo->Get(
>> vtkDataObject::DATA_OBJECT() ) );
>>     outputData = vtkPolyData::SafeDownCast(
>> outputInfo->Get(vtkDataObject::DATA_OBJECT() ) );
>> 
>>     this->updateMarchingData();
>> 
>>     firstRun = false;
>> 
>>     return 1;
>> }
>> 
>> //----------------------------------------------------------------------------
>> // From application.
>> void marchingCubes::setIsoValue(double value)
>> {
>>     isoValue = value;
>>     this->updateMarchingData();
>> }
>> 
>> double marchingCubes::getIsoValue()
>> {
>>     return isoValue;
>> }
>> 
>> //----------------------------------------------------------------------------
>> void marchingCubes::updateMarchingData()
>> {
>> //TODO: Implement all iso surface(s) creation modes by
>> vtkImageMarchingCubes.
>> 
>>     if(!firstRun)
>>     {
>>         marchingData->SetValue(0, this->getIsoValue());
>>         marchingData->Update();
>> 
>>         //outputData = NULL;
>>         //outputData->Delete();
>>         outputData->CopyStructure(marchingData->GetOutput(0));
>>     }else
>>     {
>>             marchingData->SetInputData(inputData);
>>             marchingData->SetValue(0, this->getIsoValue());
>>             marchingData->Update();
>> 
>>             
>> //outputData->SetPolys(marchingData->GetOutput()->GetPolys());//
>> Does not work.
>>             outputData->CopyStructure(marchingData->GetOutput(0));
>>     }
>> }
>> 

From dan.lipsa at kitware.com  Thu Oct  2 11:06:38 2014
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Thu, 2 Oct 2014 11:06:38 -0400
Subject: [Paraview-developers] XY Chart Plots - changes in ParaView 4.2.0
In-Reply-To: <CADHSJjAjHFzAdRxkoNhmLNzOWO0RcSnCb-1zFeG2wnS3e3y7Ng@mail.gmail.com>
References: <542D39BA.7030001@gmail.com>
 <CADHSJjAjHFzAdRxkoNhmLNzOWO0RcSnCb-1zFeG2wnS3e3y7Ng@mail.gmail.com>
Message-ID: <CADwGrVrvZZypYm=v8RQcrFVU3kbddR1DVUt82hiZgdVFbHsLWA@mail.gmail.com>

Hi Panos,

I believe leftAxisTitle, bottomAxisTitle are not QList<QVariant> but just
QVariant.
The same is true for onLogScale, offLogScale.

Does this work?
Dan





> ---------- Forwarded message ----------
> From: Panos Asproulis <panos.asproulis at gmail.com>
> Date: Thu, Oct 2, 2014 at 7:40 AM
> Subject: [Paraview-developers] XY Chart Plots - changes in ParaView 4.2.0
> To: paraview-developers at paraview.org
>
>
> Hi all,
>
> In ParaView 4.1.0 I use the following code in order to specify some
> information regarding the axes in a typical XY line plot (chart):
>
>   // Specify the name of the axes
>   QList<QVariant> axisTitles;
>   axisTitles << "Error" << "Number of Time Steps" << "";
>   pqSMAdaptor::setMultipleElementProperty(
>       viewProxy->GetProperty("AxisTitle"), axisTitles);
>
>   // Enable the logarithmic scale for the y-axis
>   QList<QVariant> logScale;
>   logScale << 1 << 0 << 0;
>   pqSMAdaptor::setMultipleElementProperty(
>       viewProxy->GetProperty("AxisLogScale"), logScale);
>
> Although this works fine in 4.1.0 it no longer works in ParaView 4.2.0
> because the properties "AxisTitle" and "AxisLogScale" no longer exist.
> They have been replaced by "LeftAxisTitle", "BottomAxisTitle" etc and
> "LeftAxisLogScale", "BottomAxisLogScale" etc. So, I changed the above
> code to the following:
>
>   // Set the name of the left axis
>   QList<QVariant> leftAxisTitle;
>   leftAxisTitle << "Error";
>   pqSMAdaptor::setElementProperty(
>       viewProxy->GetProperty("LeftAxisTitle"), leftAxisTitle);
>
>   // Set the name of the bottom axis
>   QList<QVariant> bottomAxisTitle;
>   bottomAxisTitle << "Number of Time Steps";
>   pqSMAdaptor::setElementProperty(
>       viewProxy->GetProperty("BottomAxisTitle"), bottomAxisTitle);
>
>   // Enable the logarithmic scalefor the left axis
>   QList<QVariant> onLogScale, offLogScale;
>   onLogScale  << 1;
>   offLogScale << 0;
>   pqSMAdaptor::setElementProperty(
>       viewProxy->GetProperty("LeftAxisLogScale"), onLogScale);
>   pqSMAdaptor::setElementProperty(
>       viewProxy->GetProperty("BottomAxisLogScale"), offLogScale);
>
> However, this has no effect. It does not change the title of the axes
> and it does not switch on the logarithmic scale for the left axis.
> Could someone let me know how to do that in 4.2.0?
>
> Regards,
> Panos
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141002/df236289/attachment-0001.html>

From dan.lipsa at kitware.com  Thu Oct  2 11:30:00 2014
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Thu, 2 Oct 2014 11:30:00 -0400
Subject: [Paraview-developers] XY Chart Plots - changes in ParaView 4.2.0
In-Reply-To: <CADwGrVrvZZypYm=v8RQcrFVU3kbddR1DVUt82hiZgdVFbHsLWA@mail.gmail.com>
References: <542D39BA.7030001@gmail.com>
 <CADHSJjAjHFzAdRxkoNhmLNzOWO0RcSnCb-1zFeG2wnS3e3y7Ng@mail.gmail.com>
 <CADwGrVrvZZypYm=v8RQcrFVU3kbddR1DVUt82hiZgdVFbHsLWA@mail.gmail.com>
Message-ID: <CADwGrVpjtvBPKYApxxDhaAtVpb7RNjWiJvSr6MD4MHmH0Y1bbw@mail.gmail.com>

See also

http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/api-changes.html

for a list of all Python API changes for ParaView 4.2

Dan


On Thu, Oct 2, 2014 at 11:06 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:

>
> Hi Panos,
>
> I believe leftAxisTitle, bottomAxisTitle are not QList<QVariant> but just
> QVariant.
> The same is true for onLogScale, offLogScale.
>
> Does this work?
> Dan
>
>
>
>
>
>> ---------- Forwarded message ----------
>> From: Panos Asproulis <panos.asproulis at gmail.com>
>> Date: Thu, Oct 2, 2014 at 7:40 AM
>> Subject: [Paraview-developers] XY Chart Plots - changes in ParaView 4.2.0
>> To: paraview-developers at paraview.org
>>
>>
>> Hi all,
>>
>> In ParaView 4.1.0 I use the following code in order to specify some
>> information regarding the axes in a typical XY line plot (chart):
>>
>>   // Specify the name of the axes
>>   QList<QVariant> axisTitles;
>>   axisTitles << "Error" << "Number of Time Steps" << "";
>>   pqSMAdaptor::setMultipleElementProperty(
>>       viewProxy->GetProperty("AxisTitle"), axisTitles);
>>
>>   // Enable the logarithmic scale for the y-axis
>>   QList<QVariant> logScale;
>>   logScale << 1 << 0 << 0;
>>   pqSMAdaptor::setMultipleElementProperty(
>>       viewProxy->GetProperty("AxisLogScale"), logScale);
>>
>> Although this works fine in 4.1.0 it no longer works in ParaView 4.2.0
>> because the properties "AxisTitle" and "AxisLogScale" no longer exist.
>> They have been replaced by "LeftAxisTitle", "BottomAxisTitle" etc and
>> "LeftAxisLogScale", "BottomAxisLogScale" etc. So, I changed the above
>> code to the following:
>>
>>   // Set the name of the left axis
>>   QList<QVariant> leftAxisTitle;
>>   leftAxisTitle << "Error";
>>   pqSMAdaptor::setElementProperty(
>>       viewProxy->GetProperty("LeftAxisTitle"), leftAxisTitle);
>>
>>   // Set the name of the bottom axis
>>   QList<QVariant> bottomAxisTitle;
>>   bottomAxisTitle << "Number of Time Steps";
>>   pqSMAdaptor::setElementProperty(
>>       viewProxy->GetProperty("BottomAxisTitle"), bottomAxisTitle);
>>
>>   // Enable the logarithmic scalefor the left axis
>>   QList<QVariant> onLogScale, offLogScale;
>>   onLogScale  << 1;
>>   offLogScale << 0;
>>   pqSMAdaptor::setElementProperty(
>>       viewProxy->GetProperty("LeftAxisLogScale"), onLogScale);
>>   pqSMAdaptor::setElementProperty(
>>       viewProxy->GetProperty("BottomAxisLogScale"), offLogScale);
>>
>> However, this has no effect. It does not change the title of the axes
>> and it does not switch on the logarithmic scale for the left axis.
>> Could someone let me know how to do that in 4.2.0?
>>
>> Regards,
>> Panos
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141002/f76b8e7f/attachment.html>

From sankhesh.jhaveri at kitware.com  Thu Oct  2 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Thu, 02 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Wednesday, October 01 2014
Message-ID: <20141002163103.C00127FF4A@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster 1
   [2]ubuntu-x64-nightlymaster-static 1
   -------------------- REPORT --------------------
   2 FAILURES
   [3]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster']
   [4]pvcs.Contour , 1 , ['ubuntu-x64-nightlymaster-static']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [5]fedora-x64-icc-nightlynext-release 1
   [6]ubuntu-x64-nightlynext 9
   [7]Win64-vs9-static-release 3
   [8]Win64-vs9-shared-debug-nocollab 2
   [9]ubuntu-x64-nightlynext-static 4
   [10]ubuntu-x64-nightlynext-nogui 2
   [11]ubuntu-x64-coverage 10
   [12]ubuntu-x64-nightlynext 1
   [13]Win7x64-vs10-static-release 1
   [14]Win7x64-vs10-shared-release 1
   [15]Win32-vs9-shared-release 2
   [16]Win7x64-ninja-nightlynext-shared-release 3
   -------------------- REPORT --------------------
   18 FAILURES
   [17]pv.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlynext']
   [18]pv.TestDevelopmentInstall , 1 , ['ubuntu-x64-nightlynext']
   [19]pv.ChartAxisRangeAndLabels , 1 , ['ubuntu-x64-coverage']
   [20]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-coverage']
   [21]pvcs.LogColorMap , 1 , ['Win64-vs9-static-release']
   [22]pv.FindWidget , 1 , ['ubuntu-x64-coverage']
   [23]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['ubuntu-x64-nightlynext']
   [24]pqCoreBasicApp , 1 , ['ubuntu-x64-coverage']
   [25]pvcrs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlynext']
   [26]pvcs.Contour , 1 , ['Win64-vs9-static-release']
   [27]pqFileDialogTest , 1 , ['ubuntu-x64-coverage']
   [28]vtkPVServerManagerDefaultPython-MPI-MultiView , 1 ,
   ['ubuntu-x64-nightlynext']
   [29]pvcs.ProbePicking , 2 , ['Win64-vs9-static-release',
   'ubuntu-x64-nightlynext-static']
   [30]pvpythonPython-MPI-StructuredGridVolumeRendering , 2 ,
   ['ubuntu-x64-nightlynext', 'ubuntu-x64-coverage']
   [31]pv.ResetToVisibleRange , 3 , ['Win7x64-vs10-static-release',
   'Win7x64-vs10-shared-release',
   'Win7x64-ninja-nightlynext-shared-release']
   [32]pvpythonPython-TestColorHistogram , 3 ,
   ['Win64-vs9-shared-debug-nocollab', 'Win32-vs9-shared-release',
   'Win7x64-ninja-nightlynext-shared-release']
   [33]pv.ProbePicking , 4 , ['ubuntu-x64-nightlynext',
   'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage',
   'ubuntu-x64-coverage']
   [34]vtkPVServerManagerCorePython-Settings , 13 ,
   ['fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext',
   'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab',
   'ubuntu-x64-nightlynext-static', 'ubuntu-x64-nightlynext-static',
   'ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-nightlynext-nogui',
   'ubuntu-x64-coverage', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext',
   'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release
   KargadMac.kitware , Lion-gcc-pvVTK
   kamino.kitware , Mac10.7.5-gcc-nightlymaster-release
   kamino.kitware , Mac10.7.5-clang-nightlymaster-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   3. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.ColorOpacityTableEditing
   4. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.Contour
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-02&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  17. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.ColorOpacityTableEditing
  18. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.TestDevelopmentInstall
  19. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.ChartAxisRangeAndLabels
  20. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.ColorOpacityTableEditing
  21. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.LogColorMap
  22. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.FindWidget
  23. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  24. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pqCoreBasicApp
  25. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcrs.ColorOpacityTableEditing
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.Contour
  27. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pqFileDialogTest
  28. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=vtkPVServerManagerDefaultPython-MPI-MultiView
  29. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvcs.ProbePicking
  30. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvpythonPython-MPI-StructuredGridVolumeRendering
  31. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.ResetToVisibleRange
  32. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pvpythonPython-TestColorHistogram
  33. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=pv.ProbePicking
  34. http://open.cdash.org/testSummary.php?project=9&date=2014-10-02&name=vtkPVServerManagerCorePython-Settings

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

From panos.asproulis at gmail.com  Thu Oct  2 12:32:48 2014
From: panos.asproulis at gmail.com (Panos Asproulis)
Date: Thu, 02 Oct 2014 18:32:48 +0200
Subject: [Paraview-developers] Specifying HiResLineSource to StreamTracer
Message-ID: <542D7E30.4020004@gmail.com>

Hi all,

I am trying to write code to create a streamline plot using the 
StreamTracer filter. The problem I have is the following: the 
StreamTracer filter receives as seed points a set of points created 
either by "PointSource" (extended_source) object or the 
"HiResLineSource" alternative. The default is "PointSource" so in the 
following code:

   pqPipelineSource* streamFilter = builder->createFilter("filters", 
"StreamTracer", namedInputs,
       paraview->getActiveServer());

   pqSMProxy sourceProxy =
pqSMAdaptor::getProxyProperty(streamProxy->GetProperty("Source"));

std::cout << sourceProxy->GetXMLName() << std::endl;

the object sourceProxy is indeed a "PointSource" object. How can I 
specify to the StreamTracer filter that I want it to use the 
"HiResLineSource" object instead? Do I need to create it? Is it 
available somewhere?

Thanks in advance,
Panos


From utkarsh.ayachit at kitware.com  Thu Oct  2 16:10:54 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Oct 2014 16:10:54 -0400
Subject: [Paraview-developers] How to read time data in custom reader
	plugin
In-Reply-To: <08F52AD6-6DE6-4BC2-80AC-470AA37CB32E@aia.rwth-aachen.de>
References: <E8388201-1F64-4C2D-9A94-11EF0255A171@aia.rwth-aachen.de>
 <CADHSJjC3VjOLwY8NJDxjgvoqVGLJiTsPtp=KJPSaTnd483X03g@mail.gmail.com>
 <08F52AD6-6DE6-4BC2-80AC-470AA37CB32E@aia.rwth-aachen.de>
Message-ID: <CADHSJjCYt82puBcy=pzrduJi0Lp-ScLkeRey_mdSUUySv74O-g@mail.gmail.com>

Michael,

I think you may just need a "TimestepValues" property like follows:

  <DoubleVectorProperty information_only="1"
                            name="TimestepValues"
                            repeatable="1">
        <TimeStepsInformationHelper />
        <Documentation>Available timestep values.</Documentation>
      </DoubleVectorProperty>

Refer to readers.xml[1] for examples of other readers that do the same.

Utkarsh

[1] https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml

On Thu, Oct 2, 2014 at 11:30 AM, Schlottke, Michael
<M.Schlottke at aia.rwth-aachen.de> wrote:
> Dear Utkarsh,
>
> OK, this seems to work! Is there any way I can make this work (display of time) when I read a single file, i.e. bypassing the vtkFileSeriesReader?
>
> Michael
>
> On 28 Aug 2014, at 17:05 , Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>
>> What you can do is make your internal reader which is used to read a
>> timestep put out a correct value for
>> vtkStreamingDemandDrivenPipeline::TIME_STEPS()/TIME_RANGE() keys in
>> the outInfo in its RequestInformation(). The vtkFileSeriesReader
>> iterates over all files in the series to gather that information is
>> possible ( see  vtkFileSeriesReader::RequestInformation).
>>
>> Utkarsh
>>
>> On Thu, Jul 31, 2014 at 5:45 AM, Schlottke, Michael
>> <M.Schlottke at aia.rwth-aachen.de> wrote:
>>> Hi folks,
>>>
>>> How can I make my custom plugin reader be aware of the simulation time,
>>> which is stored in the solution files I want to read? Thanks to the
>>> vtkFileSeriesReader (?) plugin I can already read in a series of files (i.e.
>>> solution_000*) and traverse through them in the correct order. However, in
>>> the ?time? field only the time step number is displayed, but not the actual
>>> simulation time. How can I make ParaView use the correct time? I guess it's
>>> something I have to add to the ?RequestInformation(..)? method in my reader.
>>> Is anyone there who has already solved this problem for her/himself?
>>>
>>> Thank you very much in advance
>>>
>>> Michael
>>>
>>> P.S.: I?m sure that this must have been asked here before, but I wasn?t able
>>> to find anything in the archives. If I missed something I?d greatly
>>> appreciate a link to the correct thread.
>>>
>>>
>>> --
>>> Michael Schlottke
>>>
>>> SimLab Highly Scalable Fluids & Solids Engineering
>>> J?lich Aachen Research Alliance (JARA-HPC)
>>> RWTH Aachen University
>>> W?llnerstra?e 5a
>>> 52062 Aachen
>>> Germany
>>>
>>> Phone: +49 (241) 80 95188
>>> Fax: +49 (241) 80 92257
>>> Mail: m.schlottke at aia.rwth-aachen.de
>>> Web: http://www.jara.org/jara-hpc
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>

From utkarsh.ayachit at kitware.com  Sat Oct  4 10:17:44 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 4 Oct 2014 10:17:44 -0400
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjC3Ji_JvsW60QRquitRovi+-fzC=nHdVM87mj4QFG-91A@mail.gmail.com>

SUMMARY
---------------------------------------------
Topics merged into master:
(VTK)   15014-dax-plugin
        live-breakpoint
(VTK)   pv-plot-bar-lut


---------------------------------------------
Topics reverted from next:
  visible_range

From sankhesh.jhaveri at kitware.com  Wed Oct  8 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Wed, 08 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Tuesday, October 07 2014
Message-ID: <20141008163103.A06397FFD4@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-static-nogui 1
   [2]ubuntu-x64-nightlymaster-kits 1
   [3]fedora-x64-icc-nightlymaster-debug 1
   [4]ubuntu-x64-nightlymaster-static 2
   [5]ubuntu-x64-nightlymaster-unified 1
   [6]Mac10.7.5-gcc-nightlymaster-release 4
   [7]Mac10.7.5-clang-nightlymaster-release 7
   [8]Win7x64-ninja-nightlymaster-static-release 2
   [9]ubuntu-x64-nightlymaster 1
   [10]Win7x64-vs9-nightlymaster-shared-release 2
   [11]ubuntu-x64-nightlymaster 1
   -------------------- REPORT --------------------
   7 FAILURES
   [12]pvcrs.ExtractLevel , 1 , ['ubuntu-x64-nightlymaster-static']
   [13]pvcs-collab.VariableSelector , 1 ,
   ['Mac10.7.5-clang-nightlymaster-release']
   [14]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [15]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [16]pvcs.CatalystLiveSetBreakpoint , 3 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [17]pv.CatalystLiveSetBreakpoint , 3 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [18]vtkPVServerManagerCorePython-Settings , 12 ,
   ['ubuntu-x64-nightlymaster-static-nogui',
   'ubuntu-x64-nightlymaster-kits', 'fedora-x64-icc-nightlymaster-debug',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster-unified',
   'Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [19]Lion-gcc-pvVTK 1
   [20]ubuntu-x64-nightlynext-static 1
   [21]ubuntu-x64-coverage 1
   [22]Win7x64-ninja-nightlynext-shared-release 1
   [23]fedora-x64-icc-nightlynext-release 1
   [24]ubuntu-x64-nightlynext 1
   [25]Win64-vs9-static-release 1
   [26]Win32-vs9-shared-release 1
   [27]ubuntu-x64-nightlynext-nogui 1
   [28]ubuntu-x64-nightlynext 1
   [29]Win64-vs9-shared-debug-nocollab 1
   -------------------- REPORT --------------------
   2 FAILURES
   [30]pvcs-collab.SpreadSheet1 , 1 , ['Win64-vs9-static-release']
   [31]vtkPVServerManagerCorePython-Settings , 10 , ['Lion-gcc-pvVTK',
   'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage',
   'Win7x64-ninja-nightlynext-shared-release',
   'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext',
   'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext-nogui',
   'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab']

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pvcrs.ExtractLevel
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pvcs-collab.VariableSelector
  14. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  15. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pvpythonPython-TestColorHistogram
  16. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pvcs.CatalystLiveSetBreakpoint
  17. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pv.CatalystLiveSetBreakpoint
  18. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=vtkPVServerManagerCorePython-Settings
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release
  26. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  27. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  28. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  29. http://open.cdash.org/index.php?project=ParaView&date=2014-10-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  30. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=pvcs-collab.SpreadSheet1
  31. http://open.cdash.org/testSummary.php?project=9&date=2014-10-08&name=vtkPVServerManagerCorePython-Settings

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

From sankhesh.jhaveri at kitware.com  Thu Oct  9 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Thu, 09 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Wednesday, October 08 2014
Message-ID: <20141009163104.516F9835FD@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-static 1
   [2]ubuntu-x64-nightlymaster 1
   [3]fedora-x64-icc-nightlymaster-debug 2
   [4]Win7x64-ninja-nightlymaster-static-release 2
   [5]ubuntu-x64-nightlymaster 1
   [6]ubuntu-x64-nightlymaster-unified 1
   [7]ubuntu-x64-nightlymaster-kits 1
   [8]Win7x64-vs9-nightlymaster-shared-release 2
   [9]ubuntu-x64-nightlymaster-static-nogui 1
   -------------------- REPORT --------------------
   3 FAILURES
   [10]pv.TestPopOutWidget , 1 , ['fedora-x64-icc-nightlymaster-debug']
   [11]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [12]vtkPVServerManagerCorePython-Settings , 9 ,
   ['ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster',
   'fedora-x64-icc-nightlymaster-debug',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'ubuntu-x64-nightlymaster-unified',
   'ubuntu-x64-nightlymaster-kits',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-static-nogui']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [13]Win32-vs9-shared-release 1
   [14]ubuntu-x64-nightlynext-static-nogui 1
   [15]ubuntu-x64-coverage 1
   [16]Win7x64-ninja-nightlynext-shared-release 1
   [17]ubuntu-x64-nightlynext 1
   [18]ubuntu-x64-nightlynext-static 1
   [19]Lion-gcc-pvVTK 1
   [20]fedora-x64-icc-nightlynext-release 1
   [21]Win64-vs9-shared-debug-nocollab 1
   [22]ubuntu-x64-nightlynext 1
   [23]ubuntu-x64-nightlynext-nogui 1
   -------------------- REPORT --------------------
   1 FAILURES
   [24]vtkPVServerManagerCorePython-Settings , 11 ,
   ['Win32-vs9-shared-release', 'ubuntu-x64-nightlynext-static-nogui',
   'ubuntu-x64-coverage', 'Win7x64-ninja-nightlynext-shared-release',
   'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static',
   'Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext',
   'ubuntu-x64-nightlynext-nogui']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release
   kamino.kitware , Mac10.7.5-gcc-nightlymaster-release
   kamino.kitware , Mac10.7.5-clang-nightlymaster-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-09&name=pv.TestPopOutWidget
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-09&name=pvpythonPython-TestColorHistogram
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-09&name=vtkPVServerManagerCorePython-Settings
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-09&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  24. http://open.cdash.org/testSummary.php?project=9&date=2014-10-09&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141009/60027173/attachment-0001.html>

From sankhesh.jhaveri at kitware.com  Fri Oct 10 12:31:06 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Fri, 10 Oct 2014 09:31:06 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Thursday, October 09 2014
Message-ID: <20141010163104.490127FF52@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Win7x64-ninja-nightlymaster-static-release 2
   [2]ubuntu-x64-nightlymaster-unified 1
   [3]fedora-x64-icc-nightlymaster-debug 1
   [4]Mac10.7.5-clang-nightlymaster-release 3
   [5]Mac10.7.5-gcc-nightlymaster-release 3
   [6]ubuntu-x64-nightlymaster-kits 1
   [7]Win7x64-vs9-nightlymaster-shared-release 2
   [8]ubuntu-x64-nightlymaster 1
   -------------------- REPORT --------------------
   4 FAILURES
   [9]pv.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release']
   [10]pvcs.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release']
   [11]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [12]vtkPVServerManagerCorePython-Settings , 8 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster-unified',
   'fedora-x64-icc-nightlymaster-debug',
   'Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release', 'ubuntu-x64-nightlymaster-kits',
   'Win7x64-vs9-nightlymaster-shared-release', 'ubuntu-x64-nightlymaster']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [13]Win64-vs9-static-release 1
   [14]Lion-gcc-pvVTK 1
   [15]Win32-vs9-shared-release 1
   [16]Win7x64-ninja-nightlynext-shared-release 1
   [17]fedora-x64-icc-nightlynext-release 1
   [18]Win64-vs9-shared-debug-nocollab 1
   [19]ubuntu-x64-nightlynext 2
   -------------------- REPORT --------------------
   3 FAILURES
   [20]pvcs-collab.SpreadSheet1 , 1 , ['Win64-vs9-static-release']
   [21]pvcs-collab.VariableSelector , 1 , ['ubuntu-x64-nightlynext']
   [22]vtkPVServerManagerCorePython-Settings , 6 , ['Lion-gcc-pvVTK',
   'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release',
   'fedora-x64-icc-nightlynext-release',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   9. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=pv.CatalystLiveSetBreakpoint
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=pvcs.CatalystLiveSetBreakpoint
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=pvpythonPython-TestColorHistogram
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=vtkPVServerManagerCorePython-Settings
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-10&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  20. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=pvcs-collab.SpreadSheet1
  21. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=pvcs-collab.VariableSelector
  22. http://open.cdash.org/testSummary.php?project=9&date=2014-10-10&name=vtkPVServerManagerCorePython-Settings

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

From sankhesh.jhaveri at kitware.com  Sat Oct 11 12:31:08 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Sat, 11 Oct 2014 09:31:08 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Friday, October 10 2014
Message-ID: <20141011163103.EB69280771@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Mac10.7.5-clang-nightlymaster-release 3
   [2]ubuntu-x64-nightlymaster-kits 1
   [3]ubuntu-x64-nightlymaster 1
   [4]Mac10.7.5-gcc-nightlymaster-release 3
   [5]Win7x64-ninja-nightlymaster-static-release 2
   [6]Win7x64-vs9-nightlymaster-shared-release 2
   [7]ubuntu-x64-nightlymaster-unified 1
   [8]fedora-x64-icc-nightlymaster-debug 1
   -------------------- REPORT --------------------
   4 FAILURES
   [9]pv.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release']
   [10]pvcs.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release']
   [11]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [12]vtkPVServerManagerCorePython-Settings , 8 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'ubuntu-x64-nightlymaster-kits', 'ubuntu-x64-nightlymaster',
   'Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-unified',
   'fedora-x64-icc-nightlymaster-debug']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [13]Win7x64-ninja-nightlynext-shared-release 1
   [14]Lion-gcc-pvVTK 1
   [15]Win64-vs9-shared-debug-nocollab 1
   [16]ubuntu-x64-nightlynext 1
   [17]Win32-vs9-shared-release 1
   [18]fedora-x64-icc-nightlynext-release 1
   -------------------- REPORT --------------------
   1 FAILURES
   [19]vtkPVServerManagerCorePython-Settings , 6 ,
   ['Win7x64-ninja-nightlynext-shared-release', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext',
   'Win32-vs9-shared-release', 'fedora-x64-icc-nightlynext-release']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   9. http://open.cdash.org/testSummary.php?project=9&date=2014-10-11&name=pv.CatalystLiveSetBreakpoint
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-11&name=pvcs.CatalystLiveSetBreakpoint
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-11&name=pvpythonPython-TestColorHistogram
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-11&name=vtkPVServerManagerCorePython-Settings
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-11&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  19. http://open.cdash.org/testSummary.php?project=9&date=2014-10-11&name=vtkPVServerManagerCorePython-Settings

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

From sankhesh.jhaveri at kitware.com  Sun Oct 12 12:31:11 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Sun, 12 Oct 2014 09:31:11 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Saturday, October 11 2014
Message-ID: <20141012163103.E521680002@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-unified 1
   [2]Win7x64-ninja-nightlymaster-static-release 2
   [3]ubuntu-x64-nightlymaster 1
   [4]Mac10.7.5-gcc-nightlymaster-release 4
   [5]Win7x64-vs9-nightlymaster-shared-release 2
   [6]Mac10.7.5-clang-nightlymaster-release 3
   [7]ubuntu-x64-nightlymaster-kits 1
   [8]fedora-x64-icc-nightlymaster-debug 1
   -------------------- REPORT --------------------
   5 FAILURES
   [9]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1
   , ['Mac10.7.5-gcc-nightlymaster-release']
   [10]pv.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [11]pvcs.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [12]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [13]vtkPVServerManagerCorePython-Settings , 8 ,
   ['ubuntu-x64-nightlymaster-unified',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'ubuntu-x64-nightlymaster-kits', 'fedora-x64-icc-nightlymaster-debug']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]ubuntu-x64-nightlynext 1
   [15]Win7x64-ninja-nightlynext-shared-release 1
   [16]fedora-x64-icc-nightlynext-release 1
   [17]Lion-gcc-pvVTK 1
   [18]Win64-vs9-shared-debug-nocollab 1
   [19]Win32-vs9-shared-release 1
   -------------------- REPORT --------------------
   1 FAILURES
   [20]vtkPVServerManagerCorePython-Settings , 6 ,
   ['ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release',
   'fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'Win32-vs9-shared-release']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   9. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=pv.CatalystLiveSetBreakpoint
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=pvcs.CatalystLiveSetBreakpoint
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=pvpythonPython-TestColorHistogram
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  20. http://open.cdash.org/testSummary.php?project=9&date=2014-10-12&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141012/a17f0f08/attachment-0001.html>

From sankhesh.jhaveri at kitware.com  Mon Oct 13 12:31:13 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Mon, 13 Oct 2014 09:31:13 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Sunday, October 12 2014
Message-ID: <20141013163103.C89D47FFAE@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Mac10.7.5-gcc-nightlymaster-release 4
   [2]Win7x64-vs9-nightlymaster-shared-release 2
   [3]Win7x64-ninja-nightlymaster-static-release 2
   [4]fedora-x64-icc-nightlymaster-debug 1
   [5]ubuntu-x64-nightlymaster-unified 1
   [6]ubuntu-x64-nightlymaster-kits 1
   [7]Mac10.7.5-clang-nightlymaster-release 3
   [8]ubuntu-x64-nightlymaster 1
   -------------------- REPORT --------------------
   5 FAILURES
   [9]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1
   , ['Mac10.7.5-gcc-nightlymaster-release']
   [10]pv.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [11]pvcs.CatalystLiveSetBreakpoint , 2 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release']
   [12]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-vs9-nightlymaster-shared-release',
   'Win7x64-ninja-nightlymaster-static-release']
   [13]vtkPVServerManagerCorePython-Settings , 8 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'Win7x64-ninja-nightlymaster-static-release',
   'fedora-x64-icc-nightlymaster-debug',
   'ubuntu-x64-nightlymaster-unified', 'ubuntu-x64-nightlymaster-kits',
   'Mac10.7.5-clang-nightlymaster-release', 'ubuntu-x64-nightlymaster']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]fedora-x64-icc-nightlynext-release 1
   [15]Lion-gcc-pvVTK 1
   [16]Win64-vs9-shared-debug-nocollab 1
   [17]Win32-vs9-shared-release 1
   [18]Win7x64-ninja-nightlynext-shared-release 1
   [19]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   1 FAILURES
   [20]vtkPVServerManagerCorePython-Settings , 6 ,
   ['fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'Win32-vs9-shared-release',
   'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   9. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  10. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=pv.CatalystLiveSetBreakpoint
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=pvcs.CatalystLiveSetBreakpoint
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=pvpythonPython-TestColorHistogram
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-13&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  20. http://open.cdash.org/testSummary.php?project=9&date=2014-10-13&name=vtkPVServerManagerCorePython-Settings

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

From reuterma at ornl.gov  Tue Oct 14 10:34:39 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Tue, 14 Oct 2014 14:34:39 +0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
Message-ID: <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>

I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:

ImportError: No module named site
[8854 refs]

However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?

Thanks,
M


On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:

> I am out of ideas at this point. Any Windows gurus out there?
> 
> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>> 
>> 
>> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
>> 
>> The IESHIM thing can be ignored. It often shows up missing. Are the
>> right Python dlls being loaded? Is it accidentally picking them up
>> from some other path?
>> 
>> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>> 
>> M
>> 
>> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>> 
>> Since you said you build with your own installation of Python, is
>> Python in PATH? Try using the dependency walker[1] to see if it can
>> find all the dependencies correctly.
>> 
>> Utkarsh
>> 
>> [1] http://www.dependencywalker.com/
>> 
>> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
>> Hi,
>> 
>> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>> 
>> Thanks,
>> M
>> 
>> Dr. Michael Reuter
>> Scientific Data Analysis Group
>> Neutron Data Analysis and Visualization Division
>> Oak Ridge National Laboratory
>> 
>> Office: 1-865-241-7216
>> Fax: 1-865-574-6080
>> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> 
>> 


From utkarsh.ayachit at kitware.com  Tue Oct 14 11:26:03 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 14 Oct 2014 11:26:03 -0400
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
Message-ID: <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>

I am still confused, but mind attaching your CMakeCache.txt? Let's see
if that shows anything. These issues are when simply building ParaView
4.2. (not Superbuild) with Python, Qt libraries already on the
machine, is that correct?

Utkarsh

On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
> I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:
>
> ImportError: No module named site
> [8854 refs]
>
> However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?
>
> Thanks,
> M
>
>
> On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>
>> I am out of ideas at this point. Any Windows gurus out there?
>>
>> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>>> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>>>
>>>
>>> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>
>>> The IESHIM thing can be ignored. It often shows up missing. Are the
>>> right Python dlls being loaded? Is it accidentally picking them up
>>> from some other path?
>>>
>>> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>>> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>>>
>>> M
>>>
>>> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>
>>> Since you said you build with your own installation of Python, is
>>> Python in PATH? Try using the dependency walker[1] to see if it can
>>> find all the dependencies correctly.
>>>
>>> Utkarsh
>>>
>>> [1] http://www.dependencywalker.com/
>>>
>>> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
>>> Hi,
>>>
>>> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>>>
>>> Thanks,
>>> M
>>>
>>> Dr. Michael Reuter
>>> Scientific Data Analysis Group
>>> Neutron Data Analysis and Visualization Division
>>> Oak Ridge National Laboratory
>>>
>>> Office: 1-865-241-7216
>>> Fax: 1-865-574-6080
>>> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>>
>

From sankhesh.jhaveri at kitware.com  Tue Oct 14 12:31:07 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Tue, 14 Oct 2014 09:31:07 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Monday, October 13 2014
Message-ID: <20141014163104.432D27FF5E@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-kits 1
   [2]fedora-x64-icc-nightlymaster-debug 1
   [3]Win7x64-ninja-nightlymaster-static-release 2
   [4]ubuntu-x64-nightlymaster 1
   [5]Win7x64-vs9-nightlymaster-shared-release 2
   [6]ubuntu-x64-nightlymaster-unified 1
   -------------------- REPORT --------------------
   2 FAILURES
   [7]pvpythonPython-TestColorHistogram , 2 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [8]vtkPVServerManagerCorePython-Settings , 6 ,
   ['ubuntu-x64-nightlymaster-kits', 'fedora-x64-icc-nightlymaster-debug',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-unified']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [9]Win64-vs9-shared-debug-nocollab 1
   [10]Win7x64-ninja-nightlynext-shared-release 1
   [11]Lion-gcc-pvVTK 1
   [12]ubuntu-x64-nightlynext 2
   [13]Win32-vs9-shared-release 1
   [14]fedora-x64-icc-nightlynext-release 1
   -------------------- REPORT --------------------
   2 FAILURES
   [15]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext']
   [16]vtkPVServerManagerCorePython-Settings , 6 ,
   ['Win64-vs9-shared-debug-nocollab',
   'Win7x64-ninja-nightlynext-shared-release', 'Lion-gcc-pvVTK',
   'ubuntu-x64-nightlynext', 'Win32-vs9-shared-release',
   'fedora-x64-icc-nightlynext-release']

   Issues with submitters
   The following expected submitters did not submit:
   Blight.kitware , ubuntu-x64-nightlymaster
   Blight.kitware , ubuntu-x64-nightlymaster-static
   Blight.kitware , ubuntu-x64-coverage
   Blight.kitware , ubuntu-x64-nightlynext
   Blight.kitware , ubuntu-x64-nightlynext-static
   Blight.kitware , ubuntu-x64-nightlynext-nogui
   amber12.kitware , Master-Win64-vs9-static-release
   kamino.kitware , Mac10.7.5-gcc-nightlymaster-release
   kamino.kitware , Mac10.7.5-clang-nightlymaster-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   7. http://open.cdash.org/testSummary.php?project=9&date=2014-10-14&name=pvpythonPython-TestColorHistogram
   8. http://open.cdash.org/testSummary.php?project=9&date=2014-10-14&name=vtkPVServerManagerCorePython-Settings
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-14&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  15. http://open.cdash.org/testSummary.php?project=9&date=2014-10-14&name=pvcs-collab.CreateDelete
  16. http://open.cdash.org/testSummary.php?project=9&date=2014-10-14&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141014/24b61b85/attachment-0001.html>

From reuterma at ornl.gov  Wed Oct 15 08:57:55 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Wed, 15 Oct 2014 12:57:55 +0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
Message-ID: <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>

I sent a response to this but it got swallowed by the size monitor. :-)

M

On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:

> I am still confused, but mind attaching your CMakeCache.txt? Let's see
> if that shows anything. These issues are when simply building ParaView
> 4.2. (not Superbuild) with Python, Qt libraries already on the
> machine, is that correct?
> 
> Utkarsh
> 
> On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>> I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:
>> 
>> ImportError: No module named site
>> [8854 refs]
>> 
>> However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?
>> 
>> Thanks,
>> M
>> 
>> 
>> On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>> 
>>> I am out of ideas at this point. Any Windows gurus out there?
>>> 
>>> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>>>> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>>>> 
>>>> 
>>>> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>> 
>>>> The IESHIM thing can be ignored. It often shows up missing. Are the
>>>> right Python dlls being loaded? Is it accidentally picking them up
>>>> from some other path?
>>>> 
>>>> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>>>> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>>>> 
>>>> M
>>>> 
>>>> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>> 
>>>> Since you said you build with your own installation of Python, is
>>>> Python in PATH? Try using the dependency walker[1] to see if it can
>>>> find all the dependencies correctly.
>>>> 
>>>> Utkarsh
>>>> 
>>>> [1] http://www.dependencywalker.com/
>>>> 
>>>> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
>>>> Hi,
>>>> 
>>>> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>>>> 
>>>> Thanks,
>>>> M
>>>> 
>>>> Dr. Michael Reuter
>>>> Scientific Data Analysis Group
>>>> Neutron Data Analysis and Visualization Division
>>>> Oak Ridge National Laboratory
>>>> 
>>>> Office: 1-865-241-7216
>>>> Fax: 1-865-574-6080
>>>> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Paraview-developers mailing list
>>>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>> 
>>>> 
>> 


From utkarsh.ayachit at kitware.com  Wed Oct 15 10:16:28 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Oct 2014 10:16:28 -0400
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
Message-ID: <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>

I got the CMakeCache.txt. Still not sure what could be the issue. Mind
just building it once with Python27 from python.org direrctly, rather
than the one from within Mantid?

Utkarsh

On Wed, Oct 15, 2014 at 8:57 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
> I sent a response to this but it got swallowed by the size monitor. :-)
>
> M
>
> On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>
>> I am still confused, but mind attaching your CMakeCache.txt? Let's see
>> if that shows anything. These issues are when simply building ParaView
>> 4.2. (not Superbuild) with Python, Qt libraries already on the
>> machine, is that correct?
>>
>> Utkarsh
>>
>> On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>>> I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:
>>>
>>> ImportError: No module named site
>>> [8854 refs]
>>>
>>> However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?
>>>
>>> Thanks,
>>> M
>>>
>>>
>>> On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>>>
>>>> I am out of ideas at this point. Any Windows gurus out there?
>>>>
>>>> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>>>>> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>>>>>
>>>>>
>>>>> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>>>
>>>>> The IESHIM thing can be ignored. It often shows up missing. Are the
>>>>> right Python dlls being loaded? Is it accidentally picking them up
>>>>> from some other path?
>>>>>
>>>>> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>>>>> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>>>>>
>>>>> M
>>>>>
>>>>> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>>>
>>>>> Since you said you build with your own installation of Python, is
>>>>> Python in PATH? Try using the dependency walker[1] to see if it can
>>>>> find all the dependencies correctly.
>>>>>
>>>>> Utkarsh
>>>>>
>>>>> [1] http://www.dependencywalker.com/
>>>>>
>>>>> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
>>>>> Hi,
>>>>>
>>>>> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>>>>>
>>>>> Thanks,
>>>>> M
>>>>>
>>>>> Dr. Michael Reuter
>>>>> Scientific Data Analysis Group
>>>>> Neutron Data Analysis and Visualization Division
>>>>> Oak Ridge National Laboratory
>>>>>
>>>>> Office: 1-865-241-7216
>>>>> Fax: 1-865-574-6080
>>>>> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Paraview-developers mailing list
>>>>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>>>
>>>>>
>>>
>

From utkarsh.ayachit at kitware.com  Wed Oct 15 10:34:27 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Oct 2014 10:34:27 -0400
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjCOqh67MBQB0S0dVEmtwoKV16WSYhJx9TWzT=ghdmz4LQ@mail.gmail.com>

Topics merged into master:
        15025_fix_annotations
        15035_reverse_connections_dsrs
        15043_add_qmake_variable_back
        15044_update_example_plugins
        cmake-cmp0053-warnings
        live-breakpoint
        pv-plot-bar-lut
        visible_range

From reuterma at ornl.gov  Wed Oct 15 10:57:40 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Wed, 15 Oct 2014 14:57:40 +0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
 <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
Message-ID: <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>

Sure. I?ll let you know how it goes.

M


On Oct 15, 2014, at 10:16 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

I got the CMakeCache.txt. Still not sure what could be the issue. Mind
just building it once with Python27 from python.org<http://python.org> direrctly, rather
than the one from within Mantid?

Utkarsh

On Wed, Oct 15, 2014 at 8:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
I sent a response to this but it got swallowed by the size monitor. :-)

M

On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

I am still confused, but mind attaching your CMakeCache.txt? Let's see
if that shows anything. These issues are when simply building ParaView
4.2. (not Superbuild) with Python, Qt libraries already on the
machine, is that correct?

Utkarsh

On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:

ImportError: No module named site
[8854 refs]

However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?

Thanks,
M


On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

I am out of ideas at this point. Any Windows gurus out there?

On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.


On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

The IESHIM thing can be ignored. It often shows up missing. Are the
right Python dlls being loaded? Is it accidentally picking them up
from some other path?

On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.

M

On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

Since you said you build with your own installation of Python, is
Python in PATH? Try using the dependency walker[1] to see if it can
find all the dependencies correctly.

Utkarsh

[1] http://www.dependencywalker.com/

On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Hi,

I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.

Thanks,
M

Dr. Michael Reuter
Scientific Data Analysis Group
Neutron Data Analysis and Visualization Division
Oak Ridge National Laboratory

Office: 1-865-241-7216
Fax: 1-865-574-6080
Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>






_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers






From sankhesh.jhaveri at kitware.com  Wed Oct 15 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Wed, 15 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Tuesday, October 14 2014
Message-ID: <20141015163103.EE77A7FF5F@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]fedora-x64-icc-nightlymaster-debug 4
   [2]Win7x64-ninja-nightlymaster-static-release 2
   [3]ubuntu-x64-nightlymaster 1
   [4]ubuntu-x64-nightlymaster-kits 1
   [5]Mac10.7.5-gcc-nightlymaster-release 27
   [6]Win7x64-vs9-nightlymaster-shared-release 2
   [7]ubuntu-x64-nightlymaster-static-nogui 1
   [8]ubuntu-x64-nightlymaster-static 1
   [9]ubuntu-x64-nightlymaster 1
   [10]ubuntu-x64-nightlymaster-unified 1
   -------------------- REPORT --------------------
   29 FAILURES
   [11]vtkPVServerManagerDefaultPython-ProgrammableFilterProperties , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [12]pvcrs.FindDataDialog , 1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [13]pvpythonPython-TestPythonAnnotationFilterNoMerge , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [14]SurfaceLIC-ShuttleAll-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [15]vtkPVServerManagerDefaultPython-MPI-MultiView , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [16]vtkPVServerManagerDefaultPython-MPI-SymmetricMultiView , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [17]SurfaceLIC-ShuttleZoom2-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [18]pv.TestPopOutWidget , 1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [19]SurfaceLIC-OfficeContour-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [20]vtkPVServerManagerDefaultPython-ProgrammableFilter , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [21]multi-serversPython-TestRemoteProgrammableFilter , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [22]SurfaceLIC-OfficeSlices-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [23]pvcs.FindDataDialog , 1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [24]pvpythonPython-TestPythonViewNumpyScript , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [25]SurfaceLIC-OfficeHSlice-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [26]pvpythonPython-TestPythonAnnotationFilter , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [27]pvpythonPython-MPI-StructuredGridVolumeRendering , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [28]pv.CatalystLiveSetBreakpoint , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [29]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [30]vtkPVServerManagerDefaultPython-PythonSelection , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [31]pv.LogColorMap , 1 , ['fedora-x64-icc-nightlymaster-debug']
   [32]pv.FindDataDialog , 1 , ['Mac10.7.5-gcc-nightlymaster-release']
   [33]SurfaceLIC-OfficeVSlice-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [34]SurfaceLIC-ShuttleZoom1-Batch , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [35]pvpythonPython-TestPythonViewScript , 1 ,
   ['Mac10.7.5-gcc-nightlymaster-release']
   [36]pvpythonPython-CinemaTest , 1 ,
   ['fedora-x64-icc-nightlymaster-debug']
   [37]pvcs.CatalystLiveSetBreakpoint , 2 ,
   ['fedora-x64-icc-nightlymaster-debug',
   'Mac10.7.5-gcc-nightlymaster-release']
   [38]pvpythonPython-TestColorHistogram , 3 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-vs9-nightlymaster-shared-release']
   [39]vtkPVServerManagerCorePython-Settings , 10 ,
   ['fedora-x64-icc-nightlymaster-debug',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'ubuntu-x64-nightlymaster-kits',
   'Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-static-nogui',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster',
   'ubuntu-x64-nightlymaster-unified']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [40]ubuntu-x64-nightlynext-static 1
   [41]Win32-vs9-shared-release 1
   [42]Win64-vs9-shared-debug-nocollab 1
   [43]ubuntu-x64-nightlynext 1
   [44]Lion-gcc-pvVTK 1
   [45]ubuntu-x64-nightlynext 1
   [46]ubuntu-x64-coverage 1
   [47]ubuntu-x64-nightlynext-nogui 1
   [48]ubuntu-x64-nightlynext-static-nogui 1
   -------------------- REPORT --------------------
   1 FAILURES
   [49]vtkPVServerManagerCorePython-Settings , 9 ,
   ['ubuntu-x64-nightlynext-static', 'Win32-vs9-shared-release',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext',
   'Lion-gcc-pvVTK', 'ubuntu-x64-nightlynext', 'ubuntu-x64-coverage',
   'ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-nightlynext-static-nogui']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release
   kamino.kitware , Mac10.7.5-gcc-nightlymaster-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-ProgrammableFilterProperties
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvcrs.FindDataDialog
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-TestPythonAnnotationFilterNoMerge
  14. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-ShuttleAll-Batch
  15. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-MPI-MultiView
  16. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-MPI-SymmetricMultiView
  17. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-ShuttleZoom2-Batch
  18. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pv.TestPopOutWidget
  19. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-OfficeContour-Batch
  20. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-ProgrammableFilter
  21. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=multi-serversPython-TestRemoteProgrammableFilter
  22. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-OfficeSlices-Batch
  23. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvcs.FindDataDialog
  24. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-TestPythonViewNumpyScript
  25. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-OfficeHSlice-Batch
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-TestPythonAnnotationFilter
  27. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-MPI-StructuredGridVolumeRendering
  28. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pv.CatalystLiveSetBreakpoint
  29. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  30. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerDefaultPython-PythonSelection
  31. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pv.LogColorMap
  32. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pv.FindDataDialog
  33. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-OfficeVSlice-Batch
  34. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=SurfaceLIC-ShuttleZoom1-Batch
  35. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-TestPythonViewScript
  36. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-CinemaTest
  37. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvcs.CatalystLiveSetBreakpoint
  38. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=pvpythonPython-TestColorHistogram
  39. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerCorePython-Settings
  40. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  41. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  42. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  43. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  44. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  45. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  46. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  47. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  48. http://open.cdash.org/index.php?project=ParaView&date=2014-10-15&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  49. http://open.cdash.org/testSummary.php?project=9&date=2014-10-15&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141015/b5bf6116/attachment-0001.html>

From reuterma at ornl.gov  Thu Oct 16 10:00:39 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Thu, 16 Oct 2014 14:00:39 +0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
 <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
 <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>
Message-ID: <94B7E220-B406-4444-ABCE-92AAC468D654@ornl.gov>

Building against the python.org<http://python.org> version makes ParaView startup fine. The weird thing is that now my originally broken build now works while still pointing at the Mantid python. I did not put the python.org<http://python.org> version into the system path so the libraries shouldn?t be getting confused. I?m now suspecting that this has something to do with the registry, but I have no idea what.

M


On Oct 15, 2014, at 10:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:

Sure. I?ll let you know how it goes.

M


On Oct 15, 2014, at 10:16 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I got the CMakeCache.txt. Still not sure what could be the issue. Mind
just building it once with Python27 from python.org<http://python.org><http://python.org> direrctly, rather
than the one from within Mantid?

Utkarsh

On Wed, Oct 15, 2014 at 8:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
I sent a response to this but it got swallowed by the size monitor. :-)

M

On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I am still confused, but mind attaching your CMakeCache.txt? Let's see
if that shows anything. These issues are when simply building ParaView
4.2. (not Superbuild) with Python, Qt libraries already on the
machine, is that correct?

Utkarsh

On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:

ImportError: No module named site
[8854 refs]

However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?

Thanks,
M


On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I am out of ideas at this point. Any Windows gurus out there?

On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.


On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

The IESHIM thing can be ignored. It often shows up missing. Are the
right Python dlls being loaded? Is it accidentally picking them up
from some other path?

On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.

M

On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

Since you said you build with your own installation of Python, is
Python in PATH? Try using the dependency walker[1] to see if it can
find all the dependencies correctly.

Utkarsh

[1] http://www.dependencywalker.com/

On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Hi,

I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.

Thanks,
M

Dr. Michael Reuter
Scientific Data Analysis Group
Neutron Data Analysis and Visualization Division
Oak Ridge National Laboratory

Office: 1-865-241-7216
Fax: 1-865-574-6080
Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>






_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers





_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org
http://public.kitware.com/mailman/listinfo/paraview-developers


From utkarsh.ayachit at kitware.com  Thu Oct 16 10:34:15 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Oct 2014 10:34:15 -0400
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <94B7E220-B406-4444-ABCE-92AAC468D654@ornl.gov>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
 <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
 <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>
 <94B7E220-B406-4444-ABCE-92AAC468D654@ornl.gov>
Message-ID: <CADHSJjD8ktqwAKO0Fx2JZ2Q+dBeOp5o6cE9Ppz_JLXZQ1iLPYg@mail.gmail.com>

I am at a loss too.

Utkarsh

On Thu, Oct 16, 2014 at 10:00 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
> Building against the python.org<http://python.org> version makes ParaView startup fine. The weird thing is that now my originally broken build now works while still pointing at the Mantid python. I did not put the python.org<http://python.org> version into the system path so the libraries shouldn?t be getting confused. I?m now suspecting that this has something to do with the registry, but I have no idea what.
>
> M
>
>
> On Oct 15, 2014, at 10:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>
> Sure. I?ll let you know how it goes.
>
> M
>
>
> On Oct 15, 2014, at 10:16 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>
> I got the CMakeCache.txt. Still not sure what could be the issue. Mind
> just building it once with Python27 from python.org<http://python.org><http://python.org> direrctly, rather
> than the one from within Mantid?
>
> Utkarsh
>
> On Wed, Oct 15, 2014 at 8:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
> I sent a response to this but it got swallowed by the size monitor. :-)
>
> M
>
> On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>
> I am still confused, but mind attaching your CMakeCache.txt? Let's see
> if that shows anything. These issues are when simply building ParaView
> 4.2. (not Superbuild) with Python, Qt libraries already on the
> machine, is that correct?
>
> Utkarsh
>
> On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
> I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:
>
> ImportError: No module named site
> [8854 refs]
>
> However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?
>
> Thanks,
> M
>
>
> On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>
> I am out of ideas at this point. Any Windows gurus out there?
>
> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>
>
> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>
> The IESHIM thing can be ignored. It often shows up missing. Are the
> right Python dlls being loaded? Is it accidentally picking them up
> from some other path?
>
> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>
> M
>
> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>
> Since you said you build with your own installation of Python, is
> Python in PATH? Try using the dependency walker[1] to see if it can
> find all the dependencies correctly.
>
> Utkarsh
>
> [1] http://www.dependencywalker.com/
>
> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
> Hi,
>
> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>
> Thanks,
> M
>
> Dr. Michael Reuter
> Scientific Data Analysis Group
> Neutron Data Analysis and Visualization Division
> Oak Ridge National Laboratory
>
> Office: 1-865-241-7216
> Fax: 1-865-574-6080
> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>
>
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From reuterma at ornl.gov  Thu Oct 16 10:58:47 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Thu, 16 Oct 2014 14:58:47 +0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <CADHSJjD8ktqwAKO0Fx2JZ2Q+dBeOp5o6cE9Ppz_JLXZQ1iLPYg@mail.gmail.com>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
 <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
 <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>
 <94B7E220-B406-4444-ABCE-92AAC468D654@ornl.gov>
 <CADHSJjD8ktqwAKO0Fx2JZ2Q+dBeOp5o6cE9Ppz_JLXZQ1iLPYg@mail.gmail.com>
Message-ID: <AD41D285-A36D-40A9-8C89-417250A3B4BA@ornl.gov>

Turns out that the Superbuild kit I made for Windows also does not start up if python.org<http://python.org> Python is not available. :-( I did not realize it was on the system I did the original test on until now.


On Oct 16, 2014, at 10:34 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

I am at a loss too.

Utkarsh

On Thu, Oct 16, 2014 at 10:00 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
Building against the python.org<http://python.org><http://python.org> version makes ParaView startup fine. The weird thing is that now my originally broken build now works while still pointing at the Mantid python. I did not put the python.org<http://python.org><http://python.org> version into the system path so the libraries shouldn?t be getting confused. I?m now suspecting that this has something to do with the registry, but I have no idea what.

M


On Oct 15, 2014, at 10:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:

Sure. I?ll let you know how it goes.

M


On Oct 15, 2014, at 10:16 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I got the CMakeCache.txt. Still not sure what could be the issue. Mind
just building it once with Python27 from python.org<http://python.org><http://python.org><http://python.org> direrctly, rather
than the one from within Mantid?

Utkarsh

On Wed, Oct 15, 2014 at 8:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
I sent a response to this but it got swallowed by the size monitor. :-)

M

On Oct 14, 2014, at 11:26 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I am still confused, but mind attaching your CMakeCache.txt? Let's see
if that shows anything. These issues are when simply building ParaView
4.2. (not Superbuild) with Python, Qt libraries already on the
machine, is that correct?

Utkarsh

On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:

ImportError: No module named site
[8854 refs]

However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?

Thanks,
M


On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

I am out of ideas at this point. Any Windows gurus out there?

On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.


On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

The IESHIM thing can be ignored. It often shows up missing. Are the
right Python dlls being loaded? Is it accidentally picking them up
from some other path?

On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.

M

On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:

Since you said you build with your own installation of Python, is
Python in PATH? Try using the dependency walker[1] to see if it can
find all the dependencies correctly.

Utkarsh

[1] http://www.dependencywalker.com/

On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
Hi,

I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.

Thanks,
M

Dr. Michael Reuter
Scientific Data Analysis Group
Neutron Data Analysis and Visualization Division
Oak Ridge National Laboratory

Office: 1-865-241-7216
Fax: 1-865-574-6080
Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>






_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers





_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org
http://public.kitware.com/mailman/listinfo/paraview-developers



From utkarsh.ayachit at kitware.com  Thu Oct 16 11:02:01 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Oct 2014 11:02:01 -0400
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <AD41D285-A36D-40A9-8C89-417250A3B4BA@ornl.gov>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
 <E8CEB030-6B6D-4539-B12A-2802C561BC27@ornl.gov>
 <CADHSJjBo+W7PGOcSjLeVmgM5oYLN5BwPpzrWKfumUZpkv61V2g@mail.gmail.com>
 <FAB567B2-C215-419C-A577-1954A23BCB5E@ornl.gov>
 <94B7E220-B406-4444-ABCE-92AAC468D654@ornl.gov>
 <CADHSJjD8ktqwAKO0Fx2JZ2Q+dBeOp5o6cE9Ppz_JLXZQ1iLPYg@mail.gmail.com>
 <AD41D285-A36D-40A9-8C89-417250A3B4BA@ornl.gov>
Message-ID: <CADHSJjCFet6C8OnMtaPs37opMQEiE2hnmnPHSu3161pZhtCptQ@mail.gmail.com>

On Thu, Oct 16, 2014 at 10:58 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
> Turns out that the Superbuild kit I made for Windows also does not start up if python.org<http://python.org> Python is not available. :-( I did not realize it was on the system I did the original test on until now.

I do not follow. Are you saying an installer you build using the
Superbuild fails to deploy on other target machines where Python is
not available? Note that Superbuild with Python enabled currently
needs VS2008.

From sankhesh.jhaveri at kitware.com  Thu Oct 16 12:31:07 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Thu, 16 Oct 2014 09:31:07 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Wednesday, October 15 2014
Message-ID: <20141016163103.C4108807AC@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster 1
   [2]Win7x64-ninja-nightlymaster-static-release 1
   [3]ubuntu-x64-nightlymaster-static 1
   [4]ubuntu-x64-nightlymaster 1
   [5]Mac10.7.5-gcc-nightlymaster-release 2
   [6]ubuntu-x64-nightlymaster-unified 1
   [7]fedora-x64-icc-nightlymaster-debug 1
   [8]ubuntu-x64-nightlymaster-static-nogui 2
   [9]Win7x64-vs9-nightlymaster-shared-release 1
   [10]ubuntu-x64-nightlymaster-kits 1
   -------------------- REPORT --------------------
   2 FAILURES
   [11]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   2 , ['Mac10.7.5-gcc-nightlymaster-release',
   'ubuntu-x64-nightlymaster-static-nogui']
   [12]vtkPVServerManagerCorePython-Settings , 10 ,
   ['ubuntu-x64-nightlymaster',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster',
   'Mac10.7.5-gcc-nightlymaster-release',
   'ubuntu-x64-nightlymaster-unified',
   'fedora-x64-icc-nightlymaster-debug',
   'ubuntu-x64-nightlymaster-static-nogui',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-kits']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [13]ubuntu-x64-coverage 1
   [14]ubuntu-x64-nightlynext-static-nogui 1
   [15]ubuntu-x64-nightlynext 2
   [16]Win64-vs9-static-release 3
   [17]ubuntu-x64-nightlynext-static 1
   [18]Win32-vs9-shared-release 1
   [19]ubuntu-x64-nightlynext-nogui 1
   [20]fedora-x64-icc-nightlynext-release 1
   [21]Win7x64-ninja-nightlynext-shared-release 1
   [22]Lion-gcc-pvVTK 1
   [23]Win64-vs9-shared-debug-nocollab 1
   [24]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   5 FAILURES
   [25]pvcs.ProbePicking , 1 , ['Win64-vs9-static-release']
   [26]pvcs-collab.VariableSelector , 1 , ['ubuntu-x64-nightlynext']
   [27]pvcs.Contour , 1 , ['Win64-vs9-static-release']
   [28]pvcs.SimpleInteraction , 1 , ['Win64-vs9-static-release']
   [29]vtkPVServerManagerCorePython-Settings , 11 ,
   ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext-static-nogui',
   'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static',
   'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext-nogui',
   'fedora-x64-icc-nightlynext-release',
   'Win7x64-ninja-nightlynext-shared-release', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=vtkPVServerManagerCorePython-Settings
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-16&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  25. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=pvcs.ProbePicking
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=pvcs-collab.VariableSelector
  27. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=pvcs.Contour
  28. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=pvcs.SimpleInteraction
  29. http://open.cdash.org/testSummary.php?project=9&date=2014-10-16&name=vtkPVServerManagerCorePython-Settings

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

From biddisco at cscs.ch  Fri Oct 17 08:48:04 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Fri, 17 Oct 2014 12:48:04 +0000
Subject: [Paraview-developers] pqObjectInspector
Message-ID: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>

I used to use pqObjectInspector quite heavily, in fact my plugin has a subclass of it which displays all the properties of my live-viz manager class inside a window.
Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel, but it does not have a setProxy method, and only seems to want pqPipeLinesource objects.

is there something I can use to display all my stuff and have an accept/reset button like the old object inspector ?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

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

From sankhesh.jhaveri at kitware.com  Fri Oct 17 12:31:10 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Fri, 17 Oct 2014 09:31:10 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Thursday, October 16 2014
Message-ID: <20141017163103.921707FF84@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Win7x64-ninja-nightlymaster-static-release 1
   [2]ubuntu-x64-nightlymaster 1
   [3]Mac10.7.5-clang-nightlymaster-release 2
   [4]ubuntu-x64-nightlymaster-static-nogui 1
   [5]Mac10.7.5-gcc-nightlymaster-release 1
   [6]ubuntu-x64-nightlymaster 1
   [7]ubuntu-x64-nightlymaster-unified 3
   [8]ubuntu-x64-nightlymaster-static 2
   [9]Win7x64-vs9-nightlymaster-shared-release 1
   [10]ubuntu-x64-nightlymaster-kits 1
   [11]Win7x64-vs10-static-release 1
   -------------------- REPORT --------------------
   4 FAILURES
   [12]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-clang-nightlymaster-release']
   [13]pvcrs.Contour , 1 , ['ubuntu-x64-nightlymaster-unified']
   [14]pv.ServerConnectDialog , 3 , ['ubuntu-x64-nightlymaster-unified',
   'ubuntu-x64-nightlymaster-static', 'Win7x64-vs10-static-release']
   [15]vtkPVServerManagerCorePython-Settings , 10 ,
   ['Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'Mac10.7.5-clang-nightlymaster-release',
   'ubuntu-x64-nightlymaster-static-nogui',
   'Mac10.7.5-gcc-nightlymaster-release', 'ubuntu-x64-nightlymaster',
   'ubuntu-x64-nightlymaster-unified', 'ubuntu-x64-nightlymaster-static',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-kits']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [16]Win32-vs9-shared-release 1
   [17]ubuntu-x64-nightlynext 1
   [18]Win64-vs9-shared-debug-nocollab 1
   [19]Win7x64-ninja-nightlynext-shared-release 1
   [20]ubuntu-x64-nightlynext 1
   [21]ubuntu-x64-nightlynext-nogui 1
   [22]Win7x64-vs9-nightlynext-static-release 1
   [23]ubuntu-x64-coverage 1
   [24]Lion-gcc-pvVTK 1
   [25]ubuntu-x64-nightlynext-static 1
   -------------------- REPORT --------------------
   1 FAILURES
   [26]vtkPVServerManagerCorePython-Settings , 10 ,
   ['Win32-vs9-shared-release', 'ubuntu-x64-nightlynext',
   'Win64-vs9-shared-debug-nocollab',
   'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext',
   'ubuntu-x64-nightlynext-nogui',
   'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage',
   'Lion-gcc-pvVTK', 'ubuntu-x64-nightlynext-static']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-17&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-17&name=pvcrs.Contour
  14. http://open.cdash.org/testSummary.php?project=9&date=2014-10-17&name=pv.ServerConnectDialog
  15. http://open.cdash.org/testSummary.php?project=9&date=2014-10-17&name=vtkPVServerManagerCorePython-Settings
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-17&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141017/2084a437/attachment-0001.html>

From biddisco at cscs.ch  Mon Oct 20 09:52:40 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 20 Oct 2014 13:52:40 +0000
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
Message-ID: <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>

I managed to get something working with a pqPropertiesPanel and creating my own pqPipelineSource, so properties become visible.

Question:
My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out, save and default buttons for (presumable) the view properties and display properties which I don't need. Can I make them hidden?

There appears to be a bug in the advanced properties gear button thingy, because one you type something in there, everything disappears and never comes back! (I noticed in the main preferences, lots of options are hidden until you enter a space in the search box, then tons appear - as if by magic - could there be something wrong with the property search feature?)

ta

JB

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe, John A.
Sent: 17 October 2014 14:48
To: paraview-developers at paraview.org
Subject: [Paraview-developers] pqObjectInspector

I used to use pqObjectInspector quite heavily, in fact my plugin has a subclass of it which displays all the properties of my live-viz manager class inside a window.
Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel, but it does not have a setProxy method, and only seems to want pqPipeLinesource objects.

is there something I can use to display all my stuff and have an accept/reset button like the old object inspector ?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

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

From dan.lipsa at kitware.com  Mon Oct 20 10:25:02 2014
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Mon, 20 Oct 2014 10:25:02 -0400
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
Message-ID: <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>

Hi John,
Not a direct answer to your question but I found the following wiki entry
useful in adding/debugging entries in the properties panel.
See especially the environment variable PV_DEBUG_PANELS

http://www.paraview.org/Wiki/ParaView/Properties_Panel

Dan


On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  I managed to get something working with a pqPropertiesPanel and creating
> my own pqPipelineSource, so properties become visible.
>
>
>
> Question:
>
> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
> save and default buttons for (presumable) the view properties and display
> properties which I don?t need. Can I make them hidden?
>
>
>
> There appears to be a bug in the advanced properties gear button thingy,
> because one you type something in there, everything disappears and never
> comes back! (I noticed in the main preferences, lots of options are hidden
> until you enter a space in the search box, then tons appear - as if by
> magic - could there be something wrong with the property search feature?)
>
>
>
> ta
>
>
>
> JB
>
>
>
> *From:* Paraview-developers [mailto:
> paraview-developers-bounces at paraview.org] *On Behalf Of *Biddiscombe,
> John A.
> *Sent:* 17 October 2014 14:48
> *To:* paraview-developers at paraview.org
> *Subject:* [Paraview-developers] pqObjectInspector
>
>
>
> I used to use pqObjectInspector quite heavily, in fact my plugin has a
> subclass of it which displays all the properties of my live-viz manager
> class inside a window.
>
> Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel,
> but it does not have a setProxy method, and only seems to want
> pqPipeLinesource objects.
>
>
>
> is there something I can use to display all my stuff and have an
> accept/reset button like the old object inspector ?
>
>
>
> thanks
>
>
>
> JB
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141020/8fccea17/attachment.html>

From dan.lipsa at kitware.com  Mon Oct 20 10:27:31 2014
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Mon, 20 Oct 2014 10:27:31 -0400
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
 <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>
Message-ID: <CADwGrVoGEuE3jv=zwxNHeUtwemz7Ycd6g50kHXjoGJowG+caPQ@mail.gmail.com>

See also
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel

Dan


On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:

> Hi John,
> Not a direct answer to your question but I found the following wiki entry
> useful in adding/debugging entries in the properties panel.
> See especially the environment variable PV_DEBUG_PANELS
>
> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>
> Dan
>
>
> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>
>>  I managed to get something working with a pqPropertiesPanel and
>> creating my own pqPipelineSource, so properties become visible.
>>
>>
>>
>> Question:
>>
>> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
>> save and default buttons for (presumable) the view properties and display
>> properties which I don?t need. Can I make them hidden?
>>
>>
>>
>> There appears to be a bug in the advanced properties gear button thingy,
>> because one you type something in there, everything disappears and never
>> comes back! (I noticed in the main preferences, lots of options are hidden
>> until you enter a space in the search box, then tons appear - as if by
>> magic - could there be something wrong with the property search feature?)
>>
>>
>>
>> ta
>>
>>
>>
>> JB
>>
>>
>>
>> *From:* Paraview-developers [mailto:
>> paraview-developers-bounces at paraview.org] *On Behalf Of *Biddiscombe,
>> John A.
>> *Sent:* 17 October 2014 14:48
>> *To:* paraview-developers at paraview.org
>> *Subject:* [Paraview-developers] pqObjectInspector
>>
>>
>>
>> I used to use pqObjectInspector quite heavily, in fact my plugin has a
>> subclass of it which displays all the properties of my live-viz manager
>> class inside a window.
>>
>> Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel,
>> but it does not have a setProxy method, and only seems to want
>> pqPipeLinesource objects.
>>
>>
>>
>> is there something I can use to display all my stuff and have an
>> accept/reset button like the old object inspector ?
>>
>>
>>
>> thanks
>>
>>
>>
>> JB
>>
>>
>>
>> --
>>
>> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>>
>> http://www.cscs.ch/
>>
>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>>
>> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141020/6d219cec/attachment-0001.html>

From sankhesh.jhaveri at kitware.com  Mon Oct 20 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Mon, 20 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Sunday, October 19 2014
Message-ID: <20141020163103.CF08D7FFD0@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster 1
   [2]Master-Win64-vs9-shared-release 1
   [3]ubuntu-x64-nightlymaster-unified 1
   [4]fedora-x64-icc-nightlymaster-debug 2
   [5]ubuntu-x64-nightlymaster 1
   [6]Win7x64-ninja-nightlymaster-static-release 1
   [7]Win7x64-vs9-nightlymaster-shared-release 1
   [8]ubuntu-x64-nightlymaster-kits 1
   [9]ubuntu-x64-nightlymaster-static-nogui 1
   [10]ubuntu-x64-nightlymaster-static 1
   [11]Master-Win64-vs9-static-release 1
   [12]Mac10.7.5-clang-nightlymaster-release 1
   [13]Mac10.7.5-gcc-nightlymaster-release 1
   -------------------- REPORT --------------------
   3 FAILURES
   [14]pvcrs.SimpleInteraction , 1 , ['Master-Win64-vs9-static-release']
   [15]pvcs-collab.CreateDelete , 1 ,
   ['fedora-x64-icc-nightlymaster-debug']
   [16]vtkPVServerManagerCorePython-Settings , 12 ,
   ['ubuntu-x64-nightlymaster', 'Master-Win64-vs9-shared-release',
   'ubuntu-x64-nightlymaster-unified',
   'fedora-x64-icc-nightlymaster-debug', 'ubuntu-x64-nightlymaster',
   'Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-kits',
   'ubuntu-x64-nightlymaster-static-nogui',
   'ubuntu-x64-nightlymaster-static',
   'Mac10.7.5-clang-nightlymaster-release',
   'Mac10.7.5-gcc-nightlymaster-release']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [17]ubuntu-x64-nightlynext 2
   [18]Win7x64-vs9-nightlynext-static-release 1
   [19]ubuntu-x64-nightlynext-nogui 1
   [20]fedora-x64-icc-nightlynext-release 2
   [21]ubuntu-x64-nightlynext-static 1
   [22]Win7x64-ninja-nightlynext-shared-release 1
   [23]Lion-gcc-pvVTK 1
   [24]ubuntu-x64-coverage 1
   [25]ubuntu-x64-nightlynext-static-nogui 1
   [26]Win32-vs9-shared-release 1
   [27]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   3 FAILURES
   [28]pv.TestPopOutWidget , 1 , ['fedora-x64-icc-nightlynext-release']
   [29]pvcs-collab.SpreadSheet1 , 1 , ['ubuntu-x64-nightlynext']
   [30]vtkPVServerManagerCorePython-Settings , 11 ,
   ['ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release',
   'ubuntu-x64-nightlynext-nogui', 'fedora-x64-icc-nightlynext-release',
   'ubuntu-x64-nightlynext-static',
   'Win7x64-ninja-nightlynext-shared-release', 'Lion-gcc-pvVTK',
   'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext-static-nogui',
   'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext']

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-static-release
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
  14. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=pvcrs.SimpleInteraction
  15. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=pvcs-collab.CreateDelete
  16. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=vtkPVServerManagerCorePython-Settings
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  26. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  27. http://open.cdash.org/index.php?project=ParaView&date=2014-10-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  28. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=pv.TestPopOutWidget
  29. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=pvcs-collab.SpreadSheet1
  30. http://open.cdash.org/testSummary.php?project=9&date=2014-10-20&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141020/57a029f0/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Oct 20 23:07:23 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 20 Oct 2014 20:07:23 -0700
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
Message-ID: <CADHSJjDk2WWLHYQQwA3i524vQ_ABmtRqiu3CdGWd7F82M3-UYg@mail.gmail.com>

> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out, save
> and default buttons for (presumable) the view properties and display
> properties which I don?t need. Can I make them hidden?

Try using pqProxyWidget directly instead. It'll offer you more finer
control. If you want to use pqProperties panel,
pqPropertiesPanel::setPanelMode() may prove useful to make the panel
no show view/display properties sections.

> There appears to be a bug in the advanced properties gear button thingy,
> because one you type something in there, everything disappears and never
> comes back! (I noticed in the main preferences, lots of options are hidden
> until you enter a space in the search box, then tons appear - as if by magic
> - could there be something wrong with the property search feature?)

Did you try hitting the "Esc" key to clear the text field, or just
deleting all text using backspace or del keys? Check this post out
[1]. It explains how searching/advanced/default widgets work. Hitting
" " results in a search for " " which matches several property labels
and those will get shown.

[1] http://www.kitware.com/blog/home/post/491

From sankhesh.jhaveri at kitware.com  Tue Oct 21 12:31:07 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Tue, 21 Oct 2014 09:31:07 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Monday, October 20 2014
Message-ID: <20141021163104.84C027FF60@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-static-nogui 1
   [2]fedora-x64-icc-nightlymaster-debug 1
   [3]ubuntu-x64-nightlymaster 1
   [4]ubuntu-x64-nightlymaster-unified 1
   [5]ubuntu-x64-nightlymaster-kits 1
   [6]Win7x64-ninja-nightlymaster-static-release 1
   [7]Win7x64-vs9-nightlymaster-shared-release 1
   [8]ubuntu-x64-nightlymaster-static 1
   [9]Master-Win64-vs9-shared-release 1
   [10]ubuntu-x64-nightlymaster 1
   -------------------- REPORT --------------------
   1 FAILURES
   [11]vtkPVServerManagerCorePython-Settings , 10 ,
   ['ubuntu-x64-nightlymaster-static-nogui',
   'fedora-x64-icc-nightlymaster-debug', 'ubuntu-x64-nightlymaster',
   'ubuntu-x64-nightlymaster-unified', 'ubuntu-x64-nightlymaster-kits',
   'Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-static', 'Master-Win64-vs9-shared-release',
   'ubuntu-x64-nightlymaster']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [12]Win7x64-ninja-nightlynext-shared-release 1
   [13]ubuntu-x64-coverage 1
   [14]Win7x64-vs9-nightlynext-static-release 1
   [15]Win64-vs9-shared-debug-nocollab 1
   [16]ubuntu-x64-nightlynext-static 1
   [17]ubuntu-x64-nightlynext-nogui 1
   [18]fedora-x64-icc-nightlynext-release 1
   [19]ubuntu-x64-nightlynext 1
   [20]Lion-gcc-pvVTK 1
   [21]ubuntu-x64-nightlynext-static-nogui 1
   [22]Win32-vs9-shared-release 1
   [23]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   1 FAILURES
   [24]vtkPVServerManagerCorePython-Settings , 12 ,
   ['Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-coverage',
   'Win7x64-vs9-nightlynext-static-release',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext-static',
   'ubuntu-x64-nightlynext-nogui', 'fedora-x64-icc-nightlynext-release',
   'ubuntu-x64-nightlynext', 'Lion-gcc-pvVTK',
   'ubuntu-x64-nightlynext-static-nogui', 'Win32-vs9-shared-release',
   'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release
   kamino.kitware , Mac10.7.5-gcc-nightlymaster-release
   kamino.kitware , Mac10.7.5-clang-nightlymaster-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
  11. http://open.cdash.org/testSummary.php?project=9&date=2014-10-21&name=vtkPVServerManagerCorePython-Settings
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  13. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  24. http://open.cdash.org/testSummary.php?project=9&date=2014-10-21&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141021/6d64a91e/attachment-0001.html>

From biddisco at cscs.ch  Wed Oct 22 06:28:32 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Wed, 22 Oct 2014 10:28:32 +0000
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <CADwGrVoGEuE3jv=zwxNHeUtwemz7Ycd6g50kHXjoGJowG+caPQ@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
 <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>
 <CADwGrVoGEuE3jv=zwxNHeUtwemz7Ycd6g50kHXjoGJowG+caPQ@mail.gmail.com>
Message-ID: <50320452A334BD42A5EC72BAD214509918FD5CAF@MBX210.d.ethz.ch>

Dan, Utkarsh

Thanks for the links. (I didn?t want to use a property widget as I need the apply button feature in my own dock window etc).

I?m of the opinion that the greyed out buttons (for view/display/etc) should be invisible if the panel mode does not include them.
Attached is a patch to hide them. #001

I needed to subclass panel properties to override some methods so that I can intercept apply and other methods.
Attached is a patch which makes a couple of functions virtual and also adds a preapplied signal emitted before new properties are ?applied?. #002,

The gear search thingy seems very broken - I?ll submit a patch if and when I find what?s wrong.

it?d be lovely if these patches could be applied to master.

(PS. any news of when I can do this via a github #PR and have it part of the accepted means of contributing?)

thanks very much, all seems to be working as before now, (subject to a few ongoing tweaks)

JB

From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
Sent: 20 October 2014 16:28
To: Biddiscombe, John A.
Cc: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
Subject: Re: [Paraview-developers] pqObjectInspector

See also
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel

Dan


On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com<mailto:dan.lipsa at kitware.com>> wrote:
Hi John,
Not a direct answer to your question but I found the following wiki entry useful in adding/debugging entries in the properties panel.
See especially the environment variable PV_DEBUG_PANELS

http://www.paraview.org/Wiki/ParaView/Properties_Panel

Dan


On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:
I managed to get something working with a pqPropertiesPanel and creating my own pqPipelineSource, so properties become visible.

Question:
My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out, save and default buttons for (presumable) the view properties and display properties which I don?t need. Can I make them hidden?

There appears to be a bug in the advanced properties gear button thingy, because one you type something in there, everything disappears and never comes back! (I noticed in the main preferences, lots of options are hidden until you enter a space in the search box, then tons appear - as if by magic - could there be something wrong with the property search feature?)

ta

JB

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org<mailto:paraview-developers-bounces at paraview.org>] On Behalf Of Biddiscombe, John A.
Sent: 17 October 2014 14:48
To: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
Subject: [Paraview-developers] pqObjectInspector

I used to use pqObjectInspector quite heavily, in fact my plugin has a subclass of it which displays all the properties of my live-viz manager class inside a window.
Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel, but it does not have a setProxy method, and only seems to want pqPipeLinesource objects.

is there something I can use to display all my stuff and have an accept/reset button like the old object inspector ?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch<http://cscs.ch>
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07<tel:%2B41%20%2891%29%20610.82.07>
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82<tel:%2B41%20%2891%29%20610.82.82>


_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141022/27e7f35e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Hide-buttons-which-are-not-used-for-a-panel-mode.patch
Type: application/octet-stream
Size: 1363 bytes
Desc: 0001-Hide-buttons-which-are-not-used-for-a-panel-mode.patch
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141022/27e7f35e/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Add-preapplied-signal-to-pqPropertiesPanel-make-some.patch
Type: application/octet-stream
Size: 2360 bytes
Desc: 0002-Add-preapplied-signal-to-pqPropertiesPanel-make-some.patch
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141022/27e7f35e/attachment-0003.obj>

From frank.tt at einseinself.org  Wed Oct 22 09:40:11 2014
From: frank.tt at einseinself.org (Frank tt)
Date: Wed, 22 Oct 2014 15:40:11 +0200
Subject: [Paraview-developers] Using vtkImageMarchingCubes as multithread
 process gives wrong output
Message-ID: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de>

Hi,

I wrote a PV plugin based on vtkImageMarchingCubes.h. At my local
machine it's working fine. But at the server, when running with mpiexec
I get some wrong output of the createt surface. (See attachments)

Now I'm not sure if this depends on the vtkImageMarchingCubes.h or at
mpiexec.

I'm using at server:
* cuda-5.5
* gcc-4.7.1
* mesa-7.11.2 (selfbuild, like the superbuild)
* openmpi-1.8.1 (selfbuild)
* paraview-4.1.0 (selfbuild)

Has anybody any idea what I did wrong or what I can do?

I have the option to use the servers mpi installation
(parastation/gcc-mt-5.0.29). This is what I'm actually doing (I'm
waiting for the next proc slot a the server).

Greetings

Frank


From dan.lipsa at kitware.com  Wed Oct 22 09:41:06 2014
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Wed, 22 Oct 2014 09:41:06 -0400
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <50320452A334BD42A5EC72BAD214509918FD5CAF@MBX210.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
 <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>
 <CADwGrVoGEuE3jv=zwxNHeUtwemz7Ycd6g50kHXjoGJowG+caPQ@mail.gmail.com>
 <50320452A334BD42A5EC72BAD214509918FD5CAF@MBX210.d.ethz.ch>
Message-ID: <CADwGrVoSviBRjpeDxz-PreyjRKJ9ixgLTi-Y50ywD6EpFdytKg@mail.gmail.com>

John,
You can submitted your patches to gerrit for review.

http://www.paraview.org/Wiki/ParaView/Git/Develop

Dan


On Wed, Oct 22, 2014 at 6:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  Dan, Utkarsh
>
>
>
> Thanks for the links. (I didn?t want to use a property widget as I need
> the apply button feature in my own dock window etc).
>
>
>
> I?m of the opinion that the greyed out buttons (for view/display/etc)
> should be invisible if the panel mode does not include them.
>
> Attached is a patch to hide them. #001
>
>
>
> I needed to subclass panel properties to override some methods so that I
> can intercept apply and other methods.
>
> Attached is a patch which makes a couple of functions virtual and also
> adds a preapplied signal emitted before new properties are ?applied?. #002,
>
>
>
> The gear search thingy seems very broken - I?ll submit a patch if and when
> I find what?s wrong.
>
>
>
> it?d be lovely if these patches could be applied to master.
>
>
>
> (PS. any news of when I can do this via a github #PR and have it part of
> the accepted means of contributing?)
>
>
>
> thanks very much, all seems to be working as before now, (subject to a few
> ongoing tweaks)
>
>
>
> JB
>
>
>
> *From:* Dan Lipsa [mailto:dan.lipsa at kitware.com <dan.lipsa at kitware.com>]
> *Sent:* 20 October 2014 16:28
> *To:* Biddiscombe, John A.
> *Cc:* paraview-developers at paraview.org
> *Subject:* Re: [Paraview-developers] pqObjectInspector
>
>
>
> See also
>
>
> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel
>
>
>
> Dan
>
>
>
>
>
> On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>
> Hi John,
>
> Not a direct answer to your question but I found the following wiki entry
> useful in adding/debugging entries in the properties panel.
>
> See especially the environment variable PV_DEBUG_PANELS
>
>
>
> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>
>
>
> Dan
>
>
>
>
>
> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>
>   I managed to get something working with a pqPropertiesPanel and
> creating my own pqPipelineSource, so properties become visible.
>
>
>
> Question:
>
> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
> save and default buttons for (presumable) the view properties and display
> properties which I don?t need. Can I make them hidden?
>
>
>
> There appears to be a bug in the advanced properties gear button thingy,
> because one you type something in there, everything disappears and never
> comes back! (I noticed in the main preferences, lots of options are hidden
> until you enter a space in the search box, then tons appear - as if by
> magic - could there be something wrong with the property search feature?)
>
>
>
> ta
>
>
>
> JB
>
>
>
> *From:* Paraview-developers [mailto:
> paraview-developers-bounces at paraview.org] *On Behalf Of *Biddiscombe,
> John A.
> *Sent:* 17 October 2014 14:48
> *To:* paraview-developers at paraview.org
> *Subject:* [Paraview-developers] pqObjectInspector
>
>
>
> I used to use pqObjectInspector quite heavily, in fact my plugin has a
> subclass of it which displays all the properties of my live-viz manager
> class inside a window.
>
> Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel,
> but it does not have a setProxy method, and only seems to want
> pqPipeLinesource objects.
>
>
>
> is there something I can use to display all my stuff and have an
> accept/reset button like the old object inspector ?
>
>
>
> thanks
>
>
>
> JB
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141022/efe43927/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Oct 22 14:11:04 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 11:11:04 -0700
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <CADwGrVoSviBRjpeDxz-PreyjRKJ9ixgLTi-Y50ywD6EpFdytKg@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD214509918F7F768@MBX110.d.ethz.ch>
 <50320452A334BD42A5EC72BAD214509918FBFD79@MBX110.d.ethz.ch>
 <CADwGrVr1zOYLPk20DgAVNAADfQ01CEMRsh=EHUkPBWth+PZsgA@mail.gmail.com>
 <CADwGrVoGEuE3jv=zwxNHeUtwemz7Ycd6g50kHXjoGJowG+caPQ@mail.gmail.com>
 <50320452A334BD42A5EC72BAD214509918FD5CAF@MBX210.d.ethz.ch>
 <CADwGrVoSviBRjpeDxz-PreyjRKJ9ixgLTi-Y50ywD6EpFdytKg@mail.gmail.com>
Message-ID: <CADHSJjAQfZCK1LyuBsrJkmpuA+Owsxry-641LF0huaCqkPV+vQ@mail.gmail.com>

John,

Speaking of the "gear" thingy -- while it's believable there are bugs,
it's less likely since it's widely used and no one reported any issues
with it so far. Just to make sure we're clear in our expectations from
it, let me explain some of the usage details:

1. There are basically 2 types of properties -- advanced and default.
2. When the "gear" is pressed, all properties including the properties
labeled default or advanced are shown. When the "gear" is unpressed,
only the default properties are shown.
3. The search box is used to search for properties -- all properties,
including advanced and default, irrespective of the gear state. As
soon as you start typing, the gear gets disabled to indicate that it
doesn't matter what "mode" the panel was in, all properties are now
being searched.
4. The search matches the text typed with the label used for the
properties. Only those properties that have label text matching the
typed text will be shown, if there's non-empty text in the search box.

Utkarsh



On Wed, Oct 22, 2014 at 6:41 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
> John,
> You can submitted your patches to gerrit for review.
>
> http://www.paraview.org/Wiki/ParaView/Git/Develop
>
> Dan
>
>
> On Wed, Oct 22, 2014 at 6:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>>
>> Dan, Utkarsh
>>
>>
>>
>> Thanks for the links. (I didn?t want to use a property widget as I need
>> the apply button feature in my own dock window etc).
>>
>>
>>
>> I?m of the opinion that the greyed out buttons (for view/display/etc)
>> should be invisible if the panel mode does not include them.
>>
>> Attached is a patch to hide them. #001
>>
>>
>>
>> I needed to subclass panel properties to override some methods so that I
>> can intercept apply and other methods.
>>
>> Attached is a patch which makes a couple of functions virtual and also
>> adds a preapplied signal emitted before new properties are ?applied?. #002,
>>
>>
>>
>> The gear search thingy seems very broken - I?ll submit a patch if and when
>> I find what?s wrong.
>>
>>
>>
>> it?d be lovely if these patches could be applied to master.
>>
>>
>>
>> (PS. any news of when I can do this via a github #PR and have it part of
>> the accepted means of contributing?)
>>
>>
>>
>> thanks very much, all seems to be working as before now, (subject to a few
>> ongoing tweaks)
>>
>>
>>
>> JB
>>
>>
>>
>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>> Sent: 20 October 2014 16:28
>> To: Biddiscombe, John A.
>> Cc: paraview-developers at paraview.org
>> Subject: Re: [Paraview-developers] pqObjectInspector
>>
>>
>>
>> See also
>>
>>
>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>
>> Hi John,
>>
>> Not a direct answer to your question but I found the following wiki entry
>> useful in adding/debugging entries in the properties panel.
>>
>> See especially the environment variable PV_DEBUG_PANELS
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A. <biddisco at cscs.ch>
>> wrote:
>>
>> I managed to get something working with a pqPropertiesPanel and creating
>> my own pqPipelineSource, so properties become visible.
>>
>>
>>
>> Question:
>>
>> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
>> save and default buttons for (presumable) the view properties and display
>> properties which I don?t need. Can I make them hidden?
>>
>>
>>
>> There appears to be a bug in the advanced properties gear button thingy,
>> because one you type something in there, everything disappears and never
>> comes back! (I noticed in the main preferences, lots of options are hidden
>> until you enter a space in the search box, then tons appear - as if by magic
>> - could there be something wrong with the property search feature?)
>>
>>
>>
>> ta
>>
>>
>>
>> JB
>>
>>
>>
>> From: Paraview-developers
>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe,
>> John A.
>> Sent: 17 October 2014 14:48
>> To: paraview-developers at paraview.org
>> Subject: [Paraview-developers] pqObjectInspector
>>
>>
>>
>> I used to use pqObjectInspector quite heavily, in fact my plugin has a
>> subclass of it which displays all the properties of my live-viz manager
>> class inside a window.
>>
>> Now that pqObjectInspector has gone, I tried to use a pqPropertiesPanel,
>> but it does not have a setProxy method, and only seems to want
>> pqPipeLinesource objects.
>>
>>
>>
>> is there something I can use to display all my stuff and have an
>> accept/reset button like the old object inspector ?
>>
>>
>>
>> thanks
>>
>>
>>
>> JB
>>
>>
>>
>> --
>>
>> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>>
>> http://www.cscs.ch/
>>
>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>>
>> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>>
>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>>
>>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From utkarsh.ayachit at kitware.com  Wed Oct 22 14:58:05 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 11:58:05 -0700
Subject: [Paraview-developers] Using vtkImageMarchingCubes as
 multithread process gives wrong output
In-Reply-To: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de>
References: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de>
Message-ID: <CADHSJjB+qeF61hDo6ndGysw0RXEHt-u6JUY085qhO8nsazzfJQ@mail.gmail.com>

Frank,

Did you forget to attach the attachments.

Utkarsh

On Wed, Oct 22, 2014 at 6:40 AM, Frank tt <frank.tt at einseinself.org> wrote:
> Hi,
>
> I wrote a PV plugin based on vtkImageMarchingCubes.h. At my local
> machine it's working fine. But at the server, when running with mpiexec
> I get some wrong output of the createt surface. (See attachments)
>
> Now I'm not sure if this depends on the vtkImageMarchingCubes.h or at
> mpiexec.
>
> I'm using at server:
> * cuda-5.5
> * gcc-4.7.1
> * mesa-7.11.2 (selfbuild, like the superbuild)
> * openmpi-1.8.1 (selfbuild)
> * paraview-4.1.0 (selfbuild)
>
> Has anybody any idea what I did wrong or what I can do?
>
> I have the option to use the servers mpi installation
> (parastation/gcc-mt-5.0.29). This is what I'm actually doing (I'm
> waiting for the next proc slot a the server).
>
> Greetings
>
> Frank
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From utkarsh.ayachit at kitware.com  Wed Oct 22 15:40:38 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 12:40:38 -0700
Subject: [Paraview-developers] How to find the selected object?
In-Reply-To: <CAPK9r69gQE9OBetTT_fFAL2FG4BCwWTz96sig5hbRrsvW1Vy3A@mail.gmail.com>
References: <54259CBF.4050806@xs4all.nl>
 <CADHSJjAVS2MhvhShpU-PAO--aE8DaqET=AB3Aw1O=yVz2=ChVg@mail.gmail.com>
 <CAPK9r69gQE9OBetTT_fFAL2FG4BCwWTz96sig5hbRrsvW1Vy3A@mail.gmail.com>
Message-ID: <CADHSJjBesTcZvc9eKRrGveR9udO0bBes28SLXXbe_i_a00mFaQ@mail.gmail.com>

The easiest way would be as follows:

vtkSMProxySelectionModel* selModel = pqActiveObjects::instance().
activeSourcesSelectionModel();
for (unsigned int cc=0, max = selModel->GetNumberOfSelectedProxies();
      cc<max; cc++)
  {
  vtkSMProxy* item = selModel->GetSelectedProxy(cc);
  // item can be a vtkSMSourceProxy or a vtkSMOutputPort.
  }

Utkarsh

On Mon, Sep 29, 2014 at 10:46 AM, Ronald R?mer <rroemer at gmail.com> wrote:
> This sounds interesting! Could you write a snippet of how to get the
> selected sources from the pipeline browser? Let us assume that a user
> selects two sources. What's the simplest way to get both output-ports? I
> could use this information for my plugin, that consumes two polydata inputs.
> Currently a dialog is opened, where the user must select the second input.
> This takes too much time ...
>
> Thanks.
>
> Am 29.09.2014 15:00 schrieb "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com>:
>
>> Depends on what you mean by "selection". If you're referring to the
>> selection in the Pipeline browser i.e. the "active" source, then use
>> pqActiveObjects [1]. If you're looking for selection by
>> clicking/selecting in the render view, pqSelectionManager [2]. [1]
>> Would often suffice for [2] too depending on what you're looking for
>> to do once you've determined what was selected since selecting in
>> render view, also makes the source active.
>>
>> Utkarsh
>>
>> [1]
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqActiveObjects.html
>> [2]
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqSelectionManager.html
>>
>> On Fri, Sep 26, 2014 at 1:05 PM, B.W.H. van Beest <bwvb at xs4all.nl> wrote:
>> > Hello,
>> >
>> > I'm trying to build my own plugin (C++) in Paraview.
>> > I wonder how one can programattically find which object (point, box,
>> > sphere, ... etc) is selected/clicked by a user.
>> >
>> > Any hint is much appreciated.
>> >
>> > Regards,
>> > Bertwim
>> >
>> >
>> > _______________________________________________
>> > Paraview-developers mailing list
>> > Paraview-developers at paraview.org
>> > http://public.kitware.com/mailman/listinfo/paraview-developers
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers

From biddisco at cscs.ch  Wed Oct 22 16:33:49 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Wed, 22 Oct 2014 20:33:49 +0000
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <CADHSJjAQfZCK1LyuBsrJkmpuA+Owsxry-641LF0huaCqkPV+vQ@mail.gmail.com>
Message-ID: <D06DCBF8.6C8D8%biddisco@cscs.ch>

Utkarsh,

When I say the gears are broken ...

If you go to the paraview/settings panel, the tabs with different options
are half empty, until you enter a ?space? in the search box, and then
suddenly all the properties appear.

It?s like that on my mac and windows boxes. I only build pvserver on
linux, so didn?t test there. I?m sure other people must have noticed it?

JB

On 22/10/14 20:11, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:

>John,
>
>Speaking of the "gear" thingy -- while it's believable there are bugs,
>it's less likely since it's widely used and no one reported any issues
>with it so far. Just to make sure we're clear in our expectations from
>it, let me explain some of the usage details:
>
>1. There are basically 2 types of properties -- advanced and default.
>2. When the "gear" is pressed, all properties including the properties
>labeled default or advanced are shown. When the "gear" is unpressed,
>only the default properties are shown.
>3. The search box is used to search for properties -- all properties,
>including advanced and default, irrespective of the gear state. As
>soon as you start typing, the gear gets disabled to indicate that it
>doesn't matter what "mode" the panel was in, all properties are now
>being searched.
>4. The search matches the text typed with the label used for the
>properties. Only those properties that have label text matching the
>typed text will be shown, if there's non-empty text in the search box.
>
>Utkarsh
>
>
>
>On Wed, Oct 22, 2014 at 6:41 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>> John,
>> You can submitted your patches to gerrit for review.
>>
>> http://www.paraview.org/Wiki/ParaView/Git/Develop
>>
>> Dan
>>
>>
>> On Wed, Oct 22, 2014 at 6:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
>> wrote:
>>>
>>> Dan, Utkarsh
>>>
>>>
>>>
>>> Thanks for the links. (I didn?t want to use a property widget as I need
>>> the apply button feature in my own dock window etc).
>>>
>>>
>>>
>>> I?m of the opinion that the greyed out buttons (for view/display/etc)
>>> should be invisible if the panel mode does not include them.
>>>
>>> Attached is a patch to hide them. #001
>>>
>>>
>>>
>>> I needed to subclass panel properties to override some methods so that
>>>I
>>> can intercept apply and other methods.
>>>
>>> Attached is a patch which makes a couple of functions virtual and also
>>> adds a preapplied signal emitted before new properties are ?applied?.
>>>#002,
>>>
>>>
>>>
>>> The gear search thingy seems very broken - I?ll submit a patch if and
>>>when
>>> I find what?s wrong.
>>>
>>>
>>>
>>> it?d be lovely if these patches could be applied to master.
>>>
>>>
>>>
>>> (PS. any news of when I can do this via a github #PR and have it part
>>>of
>>> the accepted means of contributing?)
>>>
>>>
>>>
>>> thanks very much, all seems to be working as before now, (subject to a
>>>few
>>> ongoing tweaks)
>>>
>>>
>>>
>>> JB
>>>
>>>
>>>
>>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>>> Sent: 20 October 2014 16:28
>>> To: Biddiscombe, John A.
>>> Cc: paraview-developers at paraview.org
>>> Subject: Re: [Paraview-developers] pqObjectInspector
>>>
>>>
>>>
>>> See also
>>>
>>>
>>> 
>>>http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Prop
>>>erties_Panel
>>>
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com>
>>>wrote:
>>>
>>> Hi John,
>>>
>>> Not a direct answer to your question but I found the following wiki
>>>entry
>>> useful in adding/debugging entries in the properties panel.
>>>
>>> See especially the environment variable PV_DEBUG_PANELS
>>>
>>>
>>>
>>> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>>>
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A.
>>><biddisco at cscs.ch>
>>> wrote:
>>>
>>> I managed to get something working with a pqPropertiesPanel and
>>>creating
>>> my own pqPipelineSource, so properties become visible.
>>>
>>>
>>>
>>> Question:
>>>
>>> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
>>> save and default buttons for (presumable) the view properties and
>>>display
>>> properties which I don?t need. Can I make them hidden?
>>>
>>>
>>>
>>> There appears to be a bug in the advanced properties gear button
>>>thingy,
>>> because one you type something in there, everything disappears and
>>>never
>>> comes back! (I noticed in the main preferences, lots of options are
>>>hidden
>>> until you enter a space in the search box, then tons appear - as if by
>>>magic
>>> - could there be something wrong with the property search feature?)
>>>
>>>
>>>
>>> ta
>>>
>>>
>>>
>>> JB
>>>
>>>
>>>
>>> From: Paraview-developers
>>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of
>>>Biddiscombe,
>>> John A.
>>> Sent: 17 October 2014 14:48
>>> To: paraview-developers at paraview.org
>>> Subject: [Paraview-developers] pqObjectInspector
>>>
>>>
>>>
>>> I used to use pqObjectInspector quite heavily, in fact my plugin has a
>>> subclass of it which displays all the properties of my live-viz manager
>>> class inside a window.
>>>
>>> Now that pqObjectInspector has gone, I tried to use a
>>>pqPropertiesPanel,
>>> but it does not have a setProxy method, and only seems to want
>>> pqPipeLinesource objects.
>>>
>>>
>>>
>>> is there something I can use to display all my stuff and have an
>>> accept/reset button like the old object inspector ?
>>>
>>>
>>>
>>> thanks
>>>
>>>
>>>
>>> JB
>>>
>>>
>>>
>>> --
>>>
>>> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>>>
>>> http://www.cscs.ch/
>>>
>>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>>>
>>> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>


From utkarsh.ayachit at kitware.com  Wed Oct 22 17:06:07 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 14:06:07 -0700
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <D06DCBF8.6C8D8%biddisco@cscs.ch>
References: <CADHSJjAQfZCK1LyuBsrJkmpuA+Owsxry-641LF0huaCqkPV+vQ@mail.gmail.com>
 <D06DCBF8.6C8D8%biddisco@cscs.ch>
Message-ID: <CADHSJjATVodDvY9EXe8HjeojQOoL0Ws1Ry+-u0F3ReL4Mgmo5w@mail.gmail.com>

On Wed, Oct 22, 2014 at 1:33 PM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Utkarsh,
>
> When I say the gears are broken ...
>
> If you go to the paraview/settings panel, the tabs with different options
> are half empty, until you enter a ?space? in the search box, and then
> suddenly all the properties appear.
>
> It?s like that on my mac and windows boxes. I only build pvserver on
> linux, so didn?t test there. I?m sure other people must have noticed it?
>
> JB
>
> On 22/10/14 20:11, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:
>
>>John,
>>
>>Speaking of the "gear" thingy -- while it's believable there are bugs,
>>it's less likely since it's widely used and no one reported any issues
>>with it so far. Just to make sure we're clear in our expectations from
>>it, let me explain some of the usage details:
>>
>>1. There are basically 2 types of properties -- advanced and default.
>>2. When the "gear" is pressed, all properties including the properties
>>labeled default or advanced are shown. When the "gear" is unpressed,
>>only the default properties are shown.
>>3. The search box is used to search for properties -- all properties,
>>including advanced and default, irrespective of the gear state. As
>>soon as you start typing, the gear gets disabled to indicate that it
>>doesn't matter what "mode" the panel was in, all properties are now
>>being searched.
>>4. The search matches the text typed with the label used for the
>>properties. Only those properties that have label text matching the
>>typed text will be shown, if there's non-empty text in the search box.
>>
>>Utkarsh
>>
>>
>>
>>On Wed, Oct 22, 2014 at 6:41 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>> John,
>>> You can submitted your patches to gerrit for review.
>>>
>>> http://www.paraview.org/Wiki/ParaView/Git/Develop
>>>
>>> Dan
>>>
>>>
>>> On Wed, Oct 22, 2014 at 6:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
>>> wrote:
>>>>
>>>> Dan, Utkarsh
>>>>
>>>>
>>>>
>>>> Thanks for the links. (I didn?t want to use a property widget as I need
>>>> the apply button feature in my own dock window etc).
>>>>
>>>>
>>>>
>>>> I?m of the opinion that the greyed out buttons (for view/display/etc)
>>>> should be invisible if the panel mode does not include them.
>>>>
>>>> Attached is a patch to hide them. #001
>>>>
>>>>
>>>>
>>>> I needed to subclass panel properties to override some methods so that
>>>>I
>>>> can intercept apply and other methods.
>>>>
>>>> Attached is a patch which makes a couple of functions virtual and also
>>>> adds a preapplied signal emitted before new properties are ?applied?.
>>>>#002,
>>>>
>>>>
>>>>
>>>> The gear search thingy seems very broken - I?ll submit a patch if and
>>>>when
>>>> I find what?s wrong.
>>>>
>>>>
>>>>
>>>> it?d be lovely if these patches could be applied to master.
>>>>
>>>>
>>>>
>>>> (PS. any news of when I can do this via a github #PR and have it part
>>>>of
>>>> the accepted means of contributing?)
>>>>
>>>>
>>>>
>>>> thanks very much, all seems to be working as before now, (subject to a
>>>>few
>>>> ongoing tweaks)
>>>>
>>>>
>>>>
>>>> JB
>>>>
>>>>
>>>>
>>>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>>>> Sent: 20 October 2014 16:28
>>>> To: Biddiscombe, John A.
>>>> Cc: paraview-developers at paraview.org
>>>> Subject: Re: [Paraview-developers] pqObjectInspector
>>>>
>>>>
>>>>
>>>> See also
>>>>
>>>>
>>>>
>>>>http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Prop
>>>>erties_Panel
>>>>
>>>>
>>>>
>>>> Dan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Oct 20, 2014 at 10:25 AM, Dan Lipsa <dan.lipsa at kitware.com>
>>>>wrote:
>>>>
>>>> Hi John,
>>>>
>>>> Not a direct answer to your question but I found the following wiki
>>>>entry
>>>> useful in adding/debugging entries in the properties panel.
>>>>
>>>> See especially the environment variable PV_DEBUG_PANELS
>>>>
>>>>
>>>>
>>>> http://www.paraview.org/Wiki/ParaView/Properties_Panel
>>>>
>>>>
>>>>
>>>> Dan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Oct 20, 2014 at 9:52 AM, Biddiscombe, John A.
>>>><biddisco at cscs.ch>
>>>> wrote:
>>>>
>>>> I managed to get something working with a pqPropertiesPanel and
>>>>creating
>>>> my own pqPipelineSource, so properties become visible.
>>>>
>>>>
>>>>
>>>> Question:
>>>>
>>>> My panel has SOURCE_PROPERTIES set, but I get two (of each) greyed out,
>>>> save and default buttons for (presumable) the view properties and
>>>>display
>>>> properties which I don?t need. Can I make them hidden?
>>>>
>>>>
>>>>
>>>> There appears to be a bug in the advanced properties gear button
>>>>thingy,
>>>> because one you type something in there, everything disappears and
>>>>never
>>>> comes back! (I noticed in the main preferences, lots of options are
>>>>hidden
>>>> until you enter a space in the search box, then tons appear - as if by
>>>>magic
>>>> - could there be something wrong with the property search feature?)
>>>>
>>>>
>>>>
>>>> ta
>>>>
>>>>
>>>>
>>>> JB
>>>>
>>>>
>>>>
>>>> From: Paraview-developers
>>>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of
>>>>Biddiscombe,
>>>> John A.
>>>> Sent: 17 October 2014 14:48
>>>> To: paraview-developers at paraview.org
>>>> Subject: [Paraview-developers] pqObjectInspector
>>>>
>>>>
>>>>
>>>> I used to use pqObjectInspector quite heavily, in fact my plugin has a
>>>> subclass of it which displays all the properties of my live-viz manager
>>>> class inside a window.
>>>>
>>>> Now that pqObjectInspector has gone, I tried to use a
>>>>pqPropertiesPanel,
>>>> but it does not have a setProxy method, and only seems to want
>>>> pqPipeLinesource objects.
>>>>
>>>>
>>>>
>>>> is there something I can use to display all my stuff and have an
>>>> accept/reset button like the old object inspector ?
>>>>
>>>>
>>>>
>>>> thanks
>>>>
>>>>
>>>>
>>>> JB
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>>>>
>>>> http://www.cscs.ch/
>>>>
>>>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>>>>
>>>> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Paraview-developers mailing list
>>>> Paraview-developers at paraview.org
>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>

From utkarsh.ayachit at kitware.com  Wed Oct 22 17:11:34 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 14:11:34 -0700
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <D06DCBF8.6C8D8%biddisco@cscs.ch>
References: <CADHSJjAQfZCK1LyuBsrJkmpuA+Owsxry-641LF0huaCqkPV+vQ@mail.gmail.com>
 <D06DCBF8.6C8D8%biddisco@cscs.ch>
Message-ID: <CADHSJjC7uqRPwzhhqu1_tiYT2+LGbq2RE62Q-gfaN6=FY=+fLw@mail.gmail.com>

John

> If you go to the paraview/settings panel, the tabs with different options
> are half empty, until you enter a ?space? in the search box, and then
> suddenly all the properties appear.

They are half empty, since we decided to show only a small subset of
the properties in the default view. Which properties get shown in the
"default" view is determined when defining the ServerManager XML. As I
mentioned earlier, typing " " is same as asking the panel to search
all property widgets that have " " in their labels, and hence you see
the list populated. If you press the gear (aka switch the panel to
advanced mode) instead  of typing " ", you'll see all the widgets.
Thus I don't see anything wrong with the use-case you mention. Unless
I am not understanding what you're saying or I am not explaining it
properly.


Utkarsh

From biddisco at cscs.ch  Wed Oct 22 18:13:23 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Wed, 22 Oct 2014 22:13:23 +0000
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <CADHSJjC7uqRPwzhhqu1_tiYT2+LGbq2RE62Q-gfaN6=FY=+fLw@mail.gmail.com>
Message-ID: <D06DF7D4.6CAA5%biddisco@cscs.ch>

Utkarsh

Sorry. I have lost my marbles. I completely forgot what the point of the
gear thingy is and the fact that advanced properties are supposed to be
hidden went right past me.

On my own panel, if I click the gear icon, everything disappears and
nothing I do brings my properties back, so I must have messed something
up, but I can fix that easily, by not clicking the gear icon :)

JB

On 22/10/14 23:11, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:

>John
>
>> If you go to the paraview/settings panel, the tabs with different
>>options
>> are half empty, until you enter a ?space? in the search box, and then
>> suddenly all the properties appear.
>
>They are half empty, since we decided to show only a small subset of
>the properties in the default view. Which properties get shown in the
>"default" view is determined when defining the ServerManager XML. As I
>mentioned earlier, typing " " is same as asking the panel to search
>all property widgets that have " " in their labels, and hence you see
>the list populated. If you press the gear (aka switch the panel to
>advanced mode) instead  of typing " ", you'll see all the widgets.
>Thus I don't see anything wrong with the use-case you mention. Unless
>I am not understanding what you're saying or I am not explaining it
>properly.
>
>
>Utkarsh


From utkarsh.ayachit at kitware.com  Wed Oct 22 18:55:10 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Oct 2014 15:55:10 -0700
Subject: [Paraview-developers] pqObjectInspector
In-Reply-To: <D06DF7D4.6CAA5%biddisco@cscs.ch>
References: <CADHSJjC7uqRPwzhhqu1_tiYT2+LGbq2RE62Q-gfaN6=FY=+fLw@mail.gmail.com>
 <D06DF7D4.6CAA5%biddisco@cscs.ch>
Message-ID: <CADHSJjDBRh05yFHedkrLbbadFgtsCL8Fkbe8jUv3_7wONwxWzQ@mail.gmail.com>

Phew, I was thinking I was loosing mine :).

Utkarsh

On Wed, Oct 22, 2014 at 3:13 PM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Utkarsh
>
> Sorry. I have lost my marbles. I completely forgot what the point of the
> gear thingy is and the fact that advanced properties are supposed to be
> hidden went right past me.
>
> On my own panel, if I click the gear icon, everything disappears and
> nothing I do brings my properties back, so I must have messed something
> up, but I can fix that easily, by not clicking the gear icon :)
>
> JB
>
> On 22/10/14 23:11, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:
>
>>John
>>
>>> If you go to the paraview/settings panel, the tabs with different
>>>options
>>> are half empty, until you enter a ?space? in the search box, and then
>>> suddenly all the properties appear.
>>
>>They are half empty, since we decided to show only a small subset of
>>the properties in the default view. Which properties get shown in the
>>"default" view is determined when defining the ServerManager XML. As I
>>mentioned earlier, typing " " is same as asking the panel to search
>>all property widgets that have " " in their labels, and hence you see
>>the list populated. If you press the gear (aka switch the panel to
>>advanced mode) instead  of typing " ", you'll see all the widgets.
>>Thus I don't see anything wrong with the use-case you mention. Unless
>>I am not understanding what you're saying or I am not explaining it
>>properly.
>>
>>
>>Utkarsh
>

From frank.tt at einseinself.org  Thu Oct 23 08:45:44 2014
From: frank.tt at einseinself.org (Frank TT)
Date: Thu, 23 Oct 2014 14:45:44 +0200
Subject: [Paraview-developers] Using vtkImageMarchingCubes as
 multithread process gives wrong output
In-Reply-To: <CADHSJjB+qeF61hDo6ndGysw0RXEHt-u6JUY085qhO8nsazzfJQ@mail.gmail.com>
References: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de>
 <CADHSJjB+qeF61hDo6ndGysw0RXEHt-u6JUY085qhO8nsazzfJQ@mail.gmail.com>
Message-ID: <c342a6c16576ec133bdeac95ee654d94@einseinself.org>

On 2014-10-22 20:58, Utkarsh Ayachit wrote:
> Frank,
> 
> Did you forget to attach the attachments.

Oh, yes. Sorry.




> 
> Utkarsh
> 
> On Wed, Oct 22, 2014 at 6:40 AM, Frank tt <frank.tt at einseinself.org> 
> wrote:
>> Hi,
>> 
>> I wrote a PV plugin based on vtkImageMarchingCubes.h. At my local
>> machine it's working fine. But at the server, when running with 
>> mpiexec
>> I get some wrong output of the createt surface. (See attachments)
>> 
>> Now I'm not sure if this depends on the vtkImageMarchingCubes.h or at
>> mpiexec.
>> 
>> I'm using at server:
>> * cuda-5.5
>> * gcc-4.7.1
>> * mesa-7.11.2 (selfbuild, like the superbuild)
>> * openmpi-1.8.1 (selfbuild)
>> * paraview-4.1.0 (selfbuild)
>> 
>> Has anybody any idea what I did wrong or what I can do?
>> 
>> I have the option to use the servers mpi installation
>> (parastation/gcc-mt-5.0.29). This is what I'm actually doing (I'm
>> waiting for the next proc slot a the server).
>> 
>> Greetings
>> 
>> Frank
>> 
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PV_local_MarchingCubes.2.png
Type: image/png
Size: 85476 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141023/92ac9210/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PV_judge_MarchingCubes.2.png
Type: image/png
Size: 78016 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141023/92ac9210/attachment-0003.png>

From Orlando.RIVERA at mtu.de  Thu Oct 23 10:12:05 2014
From: Orlando.RIVERA at mtu.de (RIVERA, Orlando)
Date: Thu, 23 Oct 2014 14:12:05 +0000
Subject: [Paraview-developers] Plugin based on vtkExtractBlock calls twice
	RequestData
Message-ID: <ACE279CCDDBEFA43BD2F0EE07671EA98A96281AD@memc022.de.mtu.corp>


Hi

I  have a plugin  based on  vtkExtractBlock  and  when executed   calls  RequestData twice   , and it is the second time when  actually does  what is supposed to be .   It work fine but I have no clue  why it is like that

Any Ideas ?

--
MTU Aero Engines AG
Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schrey?gg, Dr. Stefan Weingartner
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt
Sitz der Gesellschaft/Registered Office: Muenchen
Handelsregister/Commercial Register: Muenchen HRB 157206

Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese
E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet.

This e-mail and any attached documents are proprietary to MTU, confidential or protected by law.
If you are not the intended recipient, please advise the sender and delete this message and its attachments.
Any unauthorised storing, copying or distribution is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141023/63fc9852/attachment.html>

From sankhesh.jhaveri at kitware.com  Thu Oct 23 12:31:05 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Thu, 23 Oct 2014 09:31:05 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Wednesday, October 22 2014
Message-ID: <20141023163104.1B4358070D@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Win7x64-vs9-nightlymaster-shared-release 1
   [2]ubuntu-x64-nightlymaster 1
   [3]fedora-x64-icc-nightlymaster-debug 1
   [4]Win7x64-ninja-nightlymaster-static-release 1
   [5]ubuntu-x64-nightlymaster-static 1
   [6]Mac10.7.5-clang-nightlymaster-release 2
   [7]ubuntu-x64-nightlymaster 1
   [8]Master-Win64-vs9-shared-release 1
   [9]Mac10.7.5-gcc-nightlymaster-release 1
   [10]ubuntu-x64-nightlymaster-static-nogui 1
   [11]ubuntu-x64-nightlymaster-unified 1
   [12]ubuntu-x64-nightlymaster-kits 1
   -------------------- REPORT --------------------
   2 FAILURES
   [13]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-clang-nightlymaster-release']
   [14]vtkPVServerManagerCorePython-Settings , 12 ,
   ['Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster', 'fedora-x64-icc-nightlymaster-debug',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster-static',
   'Mac10.7.5-clang-nightlymaster-release', 'ubuntu-x64-nightlymaster',
   'Master-Win64-vs9-shared-release',
   'Mac10.7.5-gcc-nightlymaster-release',
   'ubuntu-x64-nightlymaster-static-nogui',
   'ubuntu-x64-nightlymaster-unified', 'ubuntu-x64-nightlymaster-kits']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [15]Win32-vs9-shared-release 1
   [16]Win7x64-vs9-nightlynext-static-release 1
   [17]Win7x64-ninja-nightlynext-shared-release 1
   [18]ubuntu-x64-nightlynext-nogui 1
   [19]ubuntu-x64-coverage 2
   [20]ubuntu-x64-nightlynext 1
   [21]ubuntu-x64-nightlynext-static-nogui 1
   [22]fedora-x64-icc-nightlynext-release 1
   [23]Win64-vs9-shared-debug-nocollab 1
   [24]Lion-gcc-pvVTK 1
   [25]ubuntu-x64-nightlynext-static 1
   [26]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   2 FAILURES
   [27]pvcs.XdmfReadRectilinearGrid , 1 , ['ubuntu-x64-coverage']
   [28]vtkPVServerManagerCorePython-Settings , 12 ,
   ['Win32-vs9-shared-release', 'Win7x64-vs9-nightlynext-static-release',
   'Win7x64-ninja-nightlynext-shared-release',
   'ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage',
   'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static-nogui',
   'fedora-x64-icc-nightlynext-release',
   'Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK',
   'ubuntu-x64-nightlynext-static', 'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-23&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  14. http://open.cdash.org/testSummary.php?project=9&date=2014-10-23&name=vtkPVServerManagerCorePython-Settings
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  26. http://open.cdash.org/index.php?project=ParaView&date=2014-10-23&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  27. http://open.cdash.org/testSummary.php?project=9&date=2014-10-23&name=pvcs.XdmfReadRectilinearGrid
  28. http://open.cdash.org/testSummary.php?project=9&date=2014-10-23&name=vtkPVServerManagerCorePython-Settings

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

From Joshua.Murphy at lasp.colorado.edu  Thu Oct 23 13:29:23 2014
From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy)
Date: Thu, 23 Oct 2014 11:29:23 -0600
Subject: [Paraview-developers] Cannot load field data into block table
Message-ID: <8D5C1B82EA40014E8B222E92B907632502135A8C55A6@MAILBOX.LASP.colorado.edu>

Hello,

I am trying to load some field data into a block data structure containing tables.  I am following the same procedure I do with the structured grid port on my reader (which works fine), but I cannot seem to actually load view the values in the table field data.

the attached screen shot shows the problem. The titles for the columns load fine, but the actual data does not.  I have printed out the contents of the vtkStringArrays and vtkDoubleArrays at the point where I am loading them in, and the values are, indeed present.  They just do not show up in Paraview (I have tried with version 4.1 and 4.2 on Linux 64 bit).

Does anyone have any idea why the values would not be loading?

Thanks,
Josh

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2014-10-23 11:22:42.png
Type: image/png
Size: 154402 bytes
Desc: Screenshot from 2014-10-23 11:22:42.png
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141023/b51932e8/attachment-0001.png>

From sankhesh.jhaveri at kitware.com  Fri Oct 24 12:31:08 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Fri, 24 Oct 2014 09:31:08 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Thursday, October 23 2014
Message-ID: <20141024163103.E5D567FF5E@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Mac10.7.5-clang-nightlymaster-release 1
   [2]ubuntu-x64-nightlymaster-kits 1
   [3]fedora-x64-icc-nightlymaster-debug 1
   [4]Master-Win64-vs9-shared-release 1
   [5]ubuntu-x64-nightlymaster 1
   [6]Win7x64-ninja-nightlymaster-static-release 1
   [7]Win7x64-vs9-nightlymaster-shared-release 1
   [8]ubuntu-x64-nightlymaster-static 1
   [9]ubuntu-x64-nightlymaster-static-nogui 1
   [10]ubuntu-x64-nightlymaster 1
   [11]Mac10.7.5-gcc-nightlymaster-release 1
   [12]ubuntu-x64-nightlymaster-unified 1
   -------------------- REPORT --------------------
   1 FAILURES
   [13]vtkPVServerManagerCorePython-Settings , 12 ,
   ['Mac10.7.5-clang-nightlymaster-release',
   'ubuntu-x64-nightlymaster-kits', 'fedora-x64-icc-nightlymaster-debug',
   'Master-Win64-vs9-shared-release', 'ubuntu-x64-nightlymaster',
   'Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-static',
   'ubuntu-x64-nightlymaster-static-nogui', 'ubuntu-x64-nightlymaster',
   'Mac10.7.5-gcc-nightlymaster-release',
   'ubuntu-x64-nightlymaster-unified']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]ubuntu-x64-nightlynext-static-nogui 1
   [15]ubuntu-x64-coverage 1
   [16]Win7x64-ninja-nightlynext-shared-release 1
   [17]fedora-x64-icc-nightlynext-release 1
   [18]ubuntu-x64-nightlynext 1
   [19]Win32-vs9-shared-release 1
   [20]Win7x64-vs9-nightlynext-static-release 1
   [21]ubuntu-x64-nightlynext 1
   [22]Lion-gcc-pvVTK 1
   [23]Win64-vs9-shared-debug-nocollab 1
   [24]ubuntu-x64-nightlynext-nogui 1
   [25]ubuntu-x64-nightlynext-static 1
   -------------------- REPORT --------------------
   1 FAILURES
   [26]vtkPVServerManagerCorePython-Settings , 12 ,
   ['ubuntu-x64-nightlynext-static-nogui', 'ubuntu-x64-coverage',
   'Win7x64-ninja-nightlynext-shared-release',
   'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext',
   'Win32-vs9-shared-release', 'Win7x64-vs9-nightlynext-static-release',
   'ubuntu-x64-nightlynext', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext-nogui',
   'ubuntu-x64-nightlynext-static']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
  12. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-24&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-24&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-24&name=vtkPVServerManagerCorePython-Settings

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

From sankhesh.jhaveri at kitware.com  Sat Oct 25 12:31:11 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Sat, 25 Oct 2014 09:31:11 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Friday, October 24 2014
Message-ID: <20141025163103.BE285806A4@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]Mac10.7.5-gcc-nightlymaster-release 1
   [2]Win7x64-ninja-nightlymaster-static-release 1
   [3]ubuntu-x64-nightlymaster 1
   [4]fedora-x64-icc-nightlymaster-debug 1
   [5]ubuntu-x64-nightlymaster-static 1
   [6]ubuntu-x64-nightlymaster-unified 2
   [7]ubuntu-x64-nightlymaster 1
   [8]ubuntu-x64-nightlymaster-kits 1
   [9]ubuntu-x64-nightlymaster-static-nogui 1
   [10]Mac10.7.5-clang-nightlymaster-release 1
   [11]Win7x64-vs9-nightlymaster-shared-release 1
   -------------------- REPORT --------------------
   2 FAILURES
   [12]pvcrs.CameraLink , 1 , ['ubuntu-x64-nightlymaster-unified']
   [13]vtkPVServerManagerCorePython-Settings , 11 ,
   ['Mac10.7.5-gcc-nightlymaster-release',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster', 'fedora-x64-icc-nightlymaster-debug',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster-unified',
   'ubuntu-x64-nightlymaster', 'ubuntu-x64-nightlymaster-kits',
   'ubuntu-x64-nightlymaster-static-nogui',
   'Mac10.7.5-clang-nightlymaster-release',
   'Win7x64-vs9-nightlymaster-shared-release']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]fedora-x64-icc-nightlynext-release 2
   [15]Win32-vs9-shared-release 2
   [16]Win7x64-vs9-nightlynext-static-release 1
   [17]ubuntu-x64-nightlynext-nogui 1
   [18]ubuntu-x64-coverage 1
   [19]Lion-gcc-pvVTK 1
   [20]ubuntu-x64-nightlynext-static 1
   [21]ubuntu-x64-nightlynext 1
   [22]ubuntu-x64-nightlynext-static-nogui 1
   [23]ubuntu-x64-nightlynext 1
   [24]Win7x64-ninja-nightlynext-shared-release 1
   [25]Win64-vs9-shared-debug-nocollab 1
   -------------------- REPORT --------------------
   2 FAILURES
   [26]pvcs-collab.CreateDelete , 1 , ['Win32-vs9-shared-release']
   [27]vtkPVServerManagerCorePython-Settings , 13 ,
   ['fedora-x64-icc-nightlynext-release',
   'fedora-x64-icc-nightlynext-release', 'Win32-vs9-shared-release',
   'Win7x64-vs9-nightlynext-static-release',
   'ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage',
   'Lion-gcc-pvVTK', 'ubuntu-x64-nightlynext-static',
   'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static-nogui',
   'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release',
   'Win64-vs9-shared-debug-nocollab']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-25&name=pvcrs.CameraLink
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-25&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  25. http://open.cdash.org/index.php?project=ParaView&date=2014-10-25&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  26. http://open.cdash.org/testSummary.php?project=9&date=2014-10-25&name=pvcs-collab.CreateDelete
  27. http://open.cdash.org/testSummary.php?project=9&date=2014-10-25&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141025/2249cabd/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Sun Oct 26 12:07:55 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 26 Oct 2014 12:07:55 -0400
Subject: [Paraview-developers] Using vtkImageMarchingCubes as
 multithread process gives wrong output
In-Reply-To: <c342a6c16576ec133bdeac95ee654d94@einseinself.org>
References: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de>
 <CADHSJjB+qeF61hDo6ndGysw0RXEHt-u6JUY085qhO8nsazzfJQ@mail.gmail.com>
 <c342a6c16576ec133bdeac95ee654d94@einseinself.org>
Message-ID: <CADHSJjDv955vzcSj6DdRr3+jruVCWAm_oGpp2tyk2X7sD5b_5g@mail.gmail.com>

The problem seems to be that the vtkImageMarchingCubes filter is not
designed to be used in cases where data is also partitioned among
ranks. It's RequestData(..) implementation directly uses WHOLE_EXTENT
to determine chunking for threaded executing, it should have been
using UPDATE_EXTENT.

Utkarsh

On Thu, Oct 23, 2014 at 8:45 AM, Frank TT <frank.tt at einseinself.org> wrote:
> On 2014-10-22 20:58, Utkarsh Ayachit wrote:
>>
>> Frank,
>>
>> Did you forget to attach the attachments.
>
>
> Oh, yes. Sorry.
>
>
>
>
>
>>
>> Utkarsh
>>
>> On Wed, Oct 22, 2014 at 6:40 AM, Frank tt <frank.tt at einseinself.org>
>> wrote:
>>>
>>> Hi,
>>>
>>> I wrote a PV plugin based on vtkImageMarchingCubes.h. At my local
>>> machine it's working fine. But at the server, when running with mpiexec
>>> I get some wrong output of the createt surface. (See attachments)
>>>
>>> Now I'm not sure if this depends on the vtkImageMarchingCubes.h or at
>>> mpiexec.
>>>
>>> I'm using at server:
>>> * cuda-5.5
>>> * gcc-4.7.1
>>> * mesa-7.11.2 (selfbuild, like the superbuild)
>>> * openmpi-1.8.1 (selfbuild)
>>> * paraview-4.1.0 (selfbuild)
>>>
>>> Has anybody any idea what I did wrong or what I can do?
>>>
>>> I have the option to use the servers mpi installation
>>> (parastation/gcc-mt-5.0.29). This is what I'm actually doing (I'm
>>> waiting for the next proc slot a the server).
>>>
>>> Greetings
>>>
>>> Frank
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers

From sankhesh.jhaveri at kitware.com  Sun Oct 26 12:31:13 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Sun, 26 Oct 2014 09:31:13 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Saturday, October 25 2014
Message-ID: <20141026163103.8E2FF80505@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster 1
   [2]Mac10.7.5-gcc-nightlymaster-release 1
   [3]Mac10.7.5-clang-nightlymaster-release 2
   [4]Win7x64-ninja-nightlymaster-static-release 1
   [5]ubuntu-x64-nightlymaster-static-nogui 1
   [6]ubuntu-x64-nightlymaster-static 1
   [7]ubuntu-x64-nightlymaster 1
   [8]ubuntu-x64-nightlymaster-kits 1
   [9]Master-Win64-vs9-shared-release 1
   [10]Win7x64-vs9-nightlymaster-shared-release 1
   [11]ubuntu-x64-nightlymaster-unified 1
   -------------------- REPORT --------------------
   2 FAILURES
   [12]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-clang-nightlymaster-release']
   [13]vtkPVServerManagerCorePython-Settings , 11 ,
   ['ubuntu-x64-nightlymaster', 'Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'Win7x64-ninja-nightlymaster-static-release',
   'ubuntu-x64-nightlymaster-static-nogui',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster',
   'ubuntu-x64-nightlymaster-kits', 'Master-Win64-vs9-shared-release',
   'Win7x64-vs9-nightlymaster-shared-release',
   'ubuntu-x64-nightlymaster-unified']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]ubuntu-x64-nightlynext-static 1
   [15]Win7x64-vs9-nightlynext-static-release 1
   [16]ubuntu-x64-nightlynext 1
   [17]ubuntu-x64-nightlynext 1
   [18]Win7x64-ninja-nightlynext-shared-release 1
   [19]Win32-vs9-shared-release 1
   [20]ubuntu-x64-nightlynext-static-nogui 1
   [21]ubuntu-x64-coverage 1
   [22]Lion-gcc-pvVTK 1
   [23]Win64-vs9-shared-debug-nocollab 1
   [24]ubuntu-x64-nightlynext-nogui 1
   -------------------- REPORT --------------------
   1 FAILURES
   [25]vtkPVServerManagerCorePython-Settings , 11 ,
   ['ubuntu-x64-nightlynext-static',
   'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-nightlynext',
   'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release',
   'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext-static-nogui',
   'ubuntu-x64-coverage', 'Lion-gcc-pvVTK',
   'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-nightlynext-nogui']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-26&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-26&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  25. http://open.cdash.org/testSummary.php?project=9&date=2014-10-26&name=vtkPVServerManagerCorePython-Settings

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

From mickey.phy at gmail.com  Sun Oct 26 15:07:55 2014
From: mickey.phy at gmail.com (Mickael Philit)
Date: Sun, 26 Oct 2014 20:07:55 +0100
Subject: [Paraview-developers] CGNS Plugin Integration
Message-ID: <544D468B.6040803@gmail.com>

Hello

I have developed a ParaView reader for CGNS file format (https://github.com/MicK7/CGNSReader_ParaView_Plugin).
I would like to integrate this plugin into the main ParaView repository.
In fact, this plugin is compiling well against ParaView master branch, and provide some enhancement compared to the visit cgns reader (see ParaView user mailing list).
My request is : can a developer pull the github code directly and integrate it ?
                 Otherwise, should I create a gerrit account as described here -> http://www.paraview.org/Wiki/ParaView/Git/Develop ?

Thanks for any help on the subject.

Mickael


From sankhesh.jhaveri at kitware.com  Mon Oct 27 12:31:17 2014
From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri)
Date: Mon, 27 Oct 2014 09:31:17 -0700 (PDT)
Subject: [Paraview-developers] Dashboard Status: Sunday, October 26 2014
Message-ID: <20141027163103.96109809B0@sanganak-ubuntu>

   Dashboard status for Nightly (master)

   -------------------- ANALYZING --------------------
   [1]ubuntu-x64-nightlymaster-static-nogui 1
   [2]ubuntu-x64-nightlymaster 1
   [3]Master-Win64-vs9-shared-release 1
   [4]ubuntu-x64-nightlymaster-unified 1
   [5]ubuntu-x64-nightlymaster-static 1
   [6]ubuntu-x64-nightlymaster 1
   [7]Mac10.7.5-gcc-nightlymaster-release 1
   [8]Mac10.7.5-clang-nightlymaster-release 2
   [9]ubuntu-x64-nightlymaster-kits 1
   [10]Win7x64-ninja-nightlymaster-static-release 1
   [11]Win7x64-vs9-nightlymaster-shared-release 1
   -------------------- REPORT --------------------
   2 FAILURES
   [12]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter ,
   1 , ['Mac10.7.5-clang-nightlymaster-release']
   [13]vtkPVServerManagerCorePython-Settings , 11 ,
   ['ubuntu-x64-nightlymaster-static-nogui', 'ubuntu-x64-nightlymaster',
   'Master-Win64-vs9-shared-release', 'ubuntu-x64-nightlymaster-unified',
   'ubuntu-x64-nightlymaster-static', 'ubuntu-x64-nightlymaster',
   'Mac10.7.5-gcc-nightlymaster-release',
   'Mac10.7.5-clang-nightlymaster-release',
   'ubuntu-x64-nightlymaster-kits',
   'Win7x64-ninja-nightlymaster-static-release',
   'Win7x64-vs9-nightlymaster-shared-release']

   Dashboard status for Nightly (next)

   -------------------- ANALYZING --------------------
   [14]Win7x64-vs9-nightlynext-static-release 1
   [15]ubuntu-x64-nightlynext-static-nogui 1
   [16]Lion-gcc-pvVTK 1
   [17]Win7x64-ninja-nightlynext-shared-release 1
   [18]ubuntu-x64-coverage 1
   [19]ubuntu-x64-nightlynext 1
   [20]Win64-vs9-shared-debug-nocollab 1
   [21]Win32-vs9-shared-release 1
   [22]ubuntu-x64-nightlynext-nogui 1
   [23]ubuntu-x64-nightlynext-static 1
   [24]ubuntu-x64-nightlynext 1
   -------------------- REPORT --------------------
   1 FAILURES
   [25]vtkPVServerManagerCorePython-Settings , 11 ,
   ['Win7x64-vs9-nightlynext-static-release',
   'ubuntu-x64-nightlynext-static-nogui', 'Lion-gcc-pvVTK',
   'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-coverage',
   'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab',
   'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext-nogui',
   'ubuntu-x64-nightlynext-static', 'ubuntu-x64-nightlynext']

   Issues with submitters
   The following expected submitters did not submit:
   amber12.kitware , Master-Win64-vs9-static-release

References

   1. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static-nogui
   2. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   3. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release
   4. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified
   5. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static
   6. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster
   7. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release
   8. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release
   9. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-kits
  10. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release
  11. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release
  12. http://open.cdash.org/testSummary.php?project=9&date=2014-10-27&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter
  13. http://open.cdash.org/testSummary.php?project=9&date=2014-10-27&name=vtkPVServerManagerCorePython-Settings
  14. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release
  15. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static-nogui
  16. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK
  17. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release
  18. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage
  19. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  20. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab
  21. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release
  22. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui
  23. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static
  24. http://open.cdash.org/index.php?project=ParaView&date=2014-10-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext
  25. http://open.cdash.org/testSummary.php?project=9&date=2014-10-27&name=vtkPVServerManagerCorePython-Settings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141027/1e9df7d5/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Mon Oct 27 14:41:19 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 27 Oct 2014 14:41:19 -0400
Subject: [Paraview-developers] CGNS Plugin Integration
In-Reply-To: <544D468B.6040803@gmail.com>
References: <544D468B.6040803@gmail.com>
Message-ID: <CADHSJjAPoDirUeWDUxFxf3sy3wEH=bShMSWn_8UfLo60ScXrPw@mail.gmail.com>

This is great. Mind pushing it to the gerrit (until we start accepting pull
requests on github directly -- which will happen within the next  year)?
That'll make it easier for me to put inline comments.

Thanks
Utkarsh

On Sun, Oct 26, 2014 at 3:07 PM, Mickael Philit <mickey.phy at gmail.com>
wrote:

> Hello
>
> I have developed a ParaView reader for CGNS file format (
> https://github.com/MicK7/CGNSReader_ParaView_Plugin).
> I would like to integrate this plugin into the main ParaView repository.
> In fact, this plugin is compiling well against ParaView master branch, and
> provide some enhancement compared to the visit cgns reader (see ParaView
> user mailing list).
> My request is : can a developer pull the github code directly and
> integrate it ?
>                 Otherwise, should I create a gerrit account as described
> here -> http://www.paraview.org/Wiki/ParaView/Git/Develop ?
>
> Thanks for any help on the subject.
>
> Mickael
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141027/20a9984f/attachment.html>

From maxim.glibin at gmail.com  Tue Oct 28 06:52:33 2014
From: maxim.glibin at gmail.com (=?UTF-8?B?0JzQsNC60YHQuNC8INCT0LvQuNCx0LjQvQ==?=)
Date: Tue, 28 Oct 2014 13:52:33 +0300
Subject: [Paraview-developers] How should I update data arrays if time step
	is changed?
Message-ID: <CAJrGgcOprpYbNRjWUdn2gmDUgG70EhFC0LztopGgZcP=eXhE1Q@mail.gmail.com>

Hello,

I am trying to implement filter which will be able to compute difference of
data arrays (for example 'temperature') between two specified time steps.
How can I get data array for certain time step?
For instance I have timesteps = [0, 0.01, 0.03,...] of 130 values.
And I would like to get data array of 'temperature' in time step = 0.4.

If someone have any idea how to implement it, please help me.

Best regards,
Maxi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141028/d22e776b/attachment.html>

From biddisco at cscs.ch  Tue Oct 28 07:00:31 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Tue, 28 Oct 2014 11:00:31 +0000
Subject: [Paraview-developers] Strange dockwindow problem (off topic)
Message-ID: <50320452A334BD42A5EC72BAD21450991902AC41@MBX110.d.ethz.ch>

In one (but not another) plugin I've developed for paraview. The application crashes as soon as I try to drag the dockwindow or move it in some way.

One dockwindow plugin works perfectly, the other will not allow me to move it. Resizing the various panels holding it is fine, but as soon as I start to drag the panel top bar for moving it, it dies.

This only happens on mac, on the windows machine the panel drags fine.

Is it possible that there's a mac specific  bug I'm encountering that maybe someone else has seen? (On mac I have qt 4.8.5 on windows I'm using 4.8.3 - could it be a 4.8.5 related issue?)

Thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

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

From Joshua.Murphy at lasp.colorado.edu  Tue Oct 28 22:48:43 2014
From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy)
Date: Tue, 28 Oct 2014 20:48:43 -0600
Subject: [Paraview-developers] Question on programmable filter
Message-ID: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu>

Hi all,

I am working with a scientist who is attempting to run a complex programmable filter that uses two inputs and produces one output.    The script generates a result for the first time step is applied on, but if you advance paraview to the next time step, the new result is NOT generated.  (no streamline update, no recalculation, nothing..)  I am not seeing why this is the case.  If you advance the time step, then force a re-apply of the filter, it will run, but that doesn't help for automated image generation.  I am sure the problem has to do with updating the pipeline, but I don't have enough experience with the programmable filter to say for sure what needs to be done.  If someone could take a look and let me know if there is a simple solution, I would be grateful.

I have tried this with the same result on PV4.0.1 and PV4.1.0.  I have not tried on PV4.2 as our reader plugin has not yet been compiled against 4.2.

Thanks,

Josh

The programmable filter script follows:

from paraview.vtk import dataset_adapter as DA
from paraview import vtk
from numpy import *

# get inputs and define output
# first input needs to define the grid used to provide the seed points to the stream tracer
# the second are the resulting stream lines
# the output is a modified version of the first input

in1 = self.GetInputDataObject(0,0)
in2 = self.GetInputDataObject(0,1)
pdo = self.GetOutputDataObject(0)

# get number of lines and total number of pts on the lines
#  note: paraview does the filed line integration first forward for all seed
#  points, then backward in the same order
#  ncells is twice the total number of field lines
 
ncells = inputs[1].GetNumberOfCells()
npts = inputs[1].GetNumberOfPoints()
nc2 = ncells/2

# figure out the location and and number of points in each line

numpts = zeros(ncells,dtype=int)
cellpointer = zeros(ncells,dtype=int)
for i in range(0,ncells):
    numpts[i] = in2.GetCell(i).GetNumberOfPoints()
print numpts
for i in range(1,ncells):
    cellpointer[i] = cellpointer[i-1] + numpts[i-1]

#for i in range(0,ncells):
#    print cellpointer[i],numpts[i],r2[cellpointer[i],:]

#
# put points into numpy arrays
#
r = inputs[0].Points
r2 = inputs[1].Points
rmag = mag(r2)
dR = r2[1:npts,:] - r2[0:npts-1,:]
dr = mag(dR)

#
# get variables needed for integration
#

B = inputs[1].PointData['Magnetic Field Vector']
den = inputs[1].PointData['Plasma Density']
csound = inputs[1].PointData['Sound Speed']
pressure = den*csound**2
b = mag(B)
binv = 1./b

#
# get midpoint values
#

bav = 0.5*(b[1:npts]+b[:npts-1])
denav = 0.5*(den[1:npts]+den[0:npts-1])
pav = 0.5*(pressure[1:npts]+pressure[0:npts-1])
print 'DR',dR.shape,r.shape
print numpts
print cellpointer

#
#   integrate along field lines
#
FTvolume = zeros(ncells)
FTden = zeros(ncells)
FTP = zeros(ncells)
print FTvolume
for i in range(ncells):
    for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1):
        FTvolume[i] = FTvolume[i] + binv[j]*dr[j]
        FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j]
        FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6
for i in range(nc2):
    FTvolume[i] = FTvolume[i] + FTvolume[i+nc2]
    FTden[i] = FTden[i] + FTden[i+nc2]
    FTP[i] = FTP[i] + FTP[i+nc2]
print FTvolume
print FTden
print FTP
#
# don't really need to reset the positions
#  but can be useful if we modify to plot in min B surface, say
#
    
newPoints = vtk.vtkPoints()
denout = zeros(ncells)
for i in range(0,nc2):
    xi = r2[cellpointer[i],0]
    yi = r2[cellpointer[i],1]
    zi = r2[cellpointer[i],2]
    denout[i] = b[cellpointer[i]]
    print i,xi,yi,zi,denout[i]
    newPoints.InsertPoint(i,xi,yi,zi)

print newPoints 
 

pdo.SetPoints(newPoints)

#
# add computed arrays
#

arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume')
pdo.GetPointData().AddArray(arrFTV)
print 'added stuff'
arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass')
pdo.GetPointData().AddArray(arrFTden)

arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy')
pdo.GetPointData().AddArray(arrFTP)

From maxim.glibin at gmail.com  Wed Oct 29 08:27:11 2014
From: maxim.glibin at gmail.com (=?UTF-8?B?0JzQsNC60YHQuNC8INCT0LvQuNCx0LjQvQ==?=)
Date: Wed, 29 Oct 2014 15:27:11 +0300
Subject: [Paraview-developers] How to compute difference of data arrays
	between two time steps for filter.
Message-ID: <CAJrGgcPbwHcimGMP1uDuvExobRi28buoqRcJXVP7N7JVkMFRng@mail.gmail.com>

Hello all,

It is necessary to extract only data array, compute difference between two
time steps and save obtained difference into output.
Who have any ideas how to implement it?

BR
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/9d138a6f/attachment.html>

From maxim.glibin at gmail.com  Wed Oct 29 08:28:53 2014
From: maxim.glibin at gmail.com (=?UTF-8?B?0JzQsNC60YHQuNC8INCT0LvQuNCx0LjQvQ==?=)
Date: Wed, 29 Oct 2014 15:28:53 +0300
Subject: [Paraview-developers] How should I update data arrays if time step
	is changed?
Message-ID: <CAJrGgcMqjv_MJ_vEQVcCxRKZ+SDxqShMy9RP88L8PsJr-+xG3w@mail.gmail.com>

Hello,

I am trying to implement filter which will be able to compute difference of
data arrays (for example 'temperature') between two specified time steps.
How can I get data array for certain time step?
For instance I have timesteps = [0, 0.01, 0.03,...] of 130 values.
And I would like to get data array of 'temperature' in time step = 0.4.

If someone have any idea how to implement it, please help me.

Best regards,
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/4eadd8f7/attachment.html>

From sebastien.jourdain at kitware.com  Wed Oct 29 11:23:37 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Wed, 29 Oct 2014 09:23:37 -0600
Subject: [Paraview-developers] Question on programmable filter
In-Reply-To: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu>
References: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu>
Message-ID: <CABObKxc92xLt5k_Yk1ELHG65Kbc9bqbVMytMpYB8t7Azzsiwsg@mail.gmail.com>

Hi Josh,

I've noticed that the default programmable filters does not advertise that
it handle time. To properly do that you can use the attached XML plugin.

Let us know if that fix the problem.

Seb

On Tue, Oct 28, 2014 at 8:48 PM, Joshua Murphy <
Joshua.Murphy at lasp.colorado.edu> wrote:

> Hi all,
>
> I am working with a scientist who is attempting to run a complex
> programmable filter that uses two inputs and produces one output.    The
> script generates a result for the first time step is applied on, but if you
> advance paraview to the next time step, the new result is NOT generated.
> (no streamline update, no recalculation, nothing..)  I am not seeing why
> this is the case.  If you advance the time step, then force a re-apply of
> the filter, it will run, but that doesn't help for automated image
> generation.  I am sure the problem has to do with updating the pipeline,
> but I don't have enough experience with the programmable filter to say for
> sure what needs to be done.  If someone could take a look and let me know
> if there is a simple solution, I would be grateful.
>
> I have tried this with the same result on PV4.0.1 and PV4.1.0.  I have not
> tried on PV4.2 as our reader plugin has not yet been compiled against 4.2.
>
> Thanks,
>
> Josh
>
> The programmable filter script follows:
>
> from paraview.vtk import dataset_adapter as DA
> from paraview import vtk
> from numpy import *
>
> # get inputs and define output
> # first input needs to define the grid used to provide the seed points to
> the stream tracer
> # the second are the resulting stream lines
> # the output is a modified version of the first input
>
> in1 = self.GetInputDataObject(0,0)
> in2 = self.GetInputDataObject(0,1)
> pdo = self.GetOutputDataObject(0)
>
> # get number of lines and total number of pts on the lines
> #  note: paraview does the filed line integration first forward for all
> seed
> #  points, then backward in the same order
> #  ncells is twice the total number of field lines
>
> ncells = inputs[1].GetNumberOfCells()
> npts = inputs[1].GetNumberOfPoints()
> nc2 = ncells/2
>
> # figure out the location and and number of points in each line
>
> numpts = zeros(ncells,dtype=int)
> cellpointer = zeros(ncells,dtype=int)
> for i in range(0,ncells):
>     numpts[i] = in2.GetCell(i).GetNumberOfPoints()
> print numpts
> for i in range(1,ncells):
>     cellpointer[i] = cellpointer[i-1] + numpts[i-1]
>
> #for i in range(0,ncells):
> #    print cellpointer[i],numpts[i],r2[cellpointer[i],:]
>
> #
> # put points into numpy arrays
> #
> r = inputs[0].Points
> r2 = inputs[1].Points
> rmag = mag(r2)
> dR = r2[1:npts,:] - r2[0:npts-1,:]
> dr = mag(dR)
>
> #
> # get variables needed for integration
> #
>
> B = inputs[1].PointData['Magnetic Field Vector']
> den = inputs[1].PointData['Plasma Density']
> csound = inputs[1].PointData['Sound Speed']
> pressure = den*csound**2
> b = mag(B)
> binv = 1./b
>
> #
> # get midpoint values
> #
>
> bav = 0.5*(b[1:npts]+b[:npts-1])
> denav = 0.5*(den[1:npts]+den[0:npts-1])
> pav = 0.5*(pressure[1:npts]+pressure[0:npts-1])
> print 'DR',dR.shape,r.shape
> print numpts
> print cellpointer
>
> #
> #   integrate along field lines
> #
> FTvolume = zeros(ncells)
> FTden = zeros(ncells)
> FTP = zeros(ncells)
> print FTvolume
> for i in range(ncells):
>     for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1):
>         FTvolume[i] = FTvolume[i] + binv[j]*dr[j]
>         FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j]
>         FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6
> for i in range(nc2):
>     FTvolume[i] = FTvolume[i] + FTvolume[i+nc2]
>     FTden[i] = FTden[i] + FTden[i+nc2]
>     FTP[i] = FTP[i] + FTP[i+nc2]
> print FTvolume
> print FTden
> print FTP
> #
> # don't really need to reset the positions
> #  but can be useful if we modify to plot in min B surface, say
> #
>
> newPoints = vtk.vtkPoints()
> denout = zeros(ncells)
> for i in range(0,nc2):
>     xi = r2[cellpointer[i],0]
>     yi = r2[cellpointer[i],1]
>     zi = r2[cellpointer[i],2]
>     denout[i] = b[cellpointer[i]]
>     print i,xi,yi,zi,denout[i]
>     newPoints.InsertPoint(i,xi,yi,zi)
>
> print newPoints
>
>
> pdo.SetPoints(newPoints)
>
> #
> # add computed arrays
> #
>
> arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume')
> pdo.GetPointData().AddArray(arrFTV)
> print 'added stuff'
> arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass')
> pdo.GetPointData().AddArray(arrFTden)
>
> arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy')
> pdo.GetPointData().AddArray(arrFTP)
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/a3d6e8a0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TemporalPythonProxy.xml
Type: text/xml
Size: 1018 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/a3d6e8a0/attachment-0001.xml>

From andy.bauer at kitware.com  Wed Oct 29 12:00:22 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 29 Oct 2014 12:00:22 -0400
Subject: [Paraview-developers] Question on programmable filter
In-Reply-To: <CABObKxc92xLt5k_Yk1ELHG65Kbc9bqbVMytMpYB8t7Azzsiwsg@mail.gmail.com>
References: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu>
 <CABObKxc92xLt5k_Yk1ELHG65Kbc9bqbVMytMpYB8t7Azzsiwsg@mail.gmail.com>
Message-ID: <CAMaOp+Ha_HbCAgcBJuFmH6XkDh=dpuaTTJG-GJftvboiiwZ_BQ@mail.gmail.com>

The Programmable Filter can handle time but it has to be done explicitly.
You'll need to do the proper calls in RequestUpdateExtentScript,
RequestInformationScript and Script. (i.e. RequestData). You can use inInfo
and outInfo to set the required information objections like
UPDATE_TIME_STEP, TIME_STEPS, etc.

Andy




On Wed, Oct 29, 2014 at 11:23 AM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Hi Josh,
>
> I've noticed that the default programmable filters does not advertise that
> it handle time. To properly do that you can use the attached XML plugin.
>
> Let us know if that fix the problem.
>
> Seb
>
> On Tue, Oct 28, 2014 at 8:48 PM, Joshua Murphy <
> Joshua.Murphy at lasp.colorado.edu> wrote:
>
>> Hi all,
>>
>> I am working with a scientist who is attempting to run a complex
>> programmable filter that uses two inputs and produces one output.    The
>> script generates a result for the first time step is applied on, but if you
>> advance paraview to the next time step, the new result is NOT generated.
>> (no streamline update, no recalculation, nothing..)  I am not seeing why
>> this is the case.  If you advance the time step, then force a re-apply of
>> the filter, it will run, but that doesn't help for automated image
>> generation.  I am sure the problem has to do with updating the pipeline,
>> but I don't have enough experience with the programmable filter to say for
>> sure what needs to be done.  If someone could take a look and let me know
>> if there is a simple solution, I would be grateful.
>>
>> I have tried this with the same result on PV4.0.1 and PV4.1.0.  I have
>> not tried on PV4.2 as our reader plugin has not yet been compiled against
>> 4.2.
>>
>> Thanks,
>>
>> Josh
>>
>> The programmable filter script follows:
>>
>> from paraview.vtk import dataset_adapter as DA
>> from paraview import vtk
>> from numpy import *
>>
>> # get inputs and define output
>> # first input needs to define the grid used to provide the seed points to
>> the stream tracer
>> # the second are the resulting stream lines
>> # the output is a modified version of the first input
>>
>> in1 = self.GetInputDataObject(0,0)
>> in2 = self.GetInputDataObject(0,1)
>> pdo = self.GetOutputDataObject(0)
>>
>> # get number of lines and total number of pts on the lines
>> #  note: paraview does the filed line integration first forward for all
>> seed
>> #  points, then backward in the same order
>> #  ncells is twice the total number of field lines
>>
>> ncells = inputs[1].GetNumberOfCells()
>> npts = inputs[1].GetNumberOfPoints()
>> nc2 = ncells/2
>>
>> # figure out the location and and number of points in each line
>>
>> numpts = zeros(ncells,dtype=int)
>> cellpointer = zeros(ncells,dtype=int)
>> for i in range(0,ncells):
>>     numpts[i] = in2.GetCell(i).GetNumberOfPoints()
>> print numpts
>> for i in range(1,ncells):
>>     cellpointer[i] = cellpointer[i-1] + numpts[i-1]
>>
>> #for i in range(0,ncells):
>> #    print cellpointer[i],numpts[i],r2[cellpointer[i],:]
>>
>> #
>> # put points into numpy arrays
>> #
>> r = inputs[0].Points
>> r2 = inputs[1].Points
>> rmag = mag(r2)
>> dR = r2[1:npts,:] - r2[0:npts-1,:]
>> dr = mag(dR)
>>
>> #
>> # get variables needed for integration
>> #
>>
>> B = inputs[1].PointData['Magnetic Field Vector']
>> den = inputs[1].PointData['Plasma Density']
>> csound = inputs[1].PointData['Sound Speed']
>> pressure = den*csound**2
>> b = mag(B)
>> binv = 1./b
>>
>> #
>> # get midpoint values
>> #
>>
>> bav = 0.5*(b[1:npts]+b[:npts-1])
>> denav = 0.5*(den[1:npts]+den[0:npts-1])
>> pav = 0.5*(pressure[1:npts]+pressure[0:npts-1])
>> print 'DR',dR.shape,r.shape
>> print numpts
>> print cellpointer
>>
>> #
>> #   integrate along field lines
>> #
>> FTvolume = zeros(ncells)
>> FTden = zeros(ncells)
>> FTP = zeros(ncells)
>> print FTvolume
>> for i in range(ncells):
>>     for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1):
>>         FTvolume[i] = FTvolume[i] + binv[j]*dr[j]
>>         FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j]
>>         FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6
>> for i in range(nc2):
>>     FTvolume[i] = FTvolume[i] + FTvolume[i+nc2]
>>     FTden[i] = FTden[i] + FTden[i+nc2]
>>     FTP[i] = FTP[i] + FTP[i+nc2]
>> print FTvolume
>> print FTden
>> print FTP
>> #
>> # don't really need to reset the positions
>> #  but can be useful if we modify to plot in min B surface, say
>> #
>>
>> newPoints = vtk.vtkPoints()
>> denout = zeros(ncells)
>> for i in range(0,nc2):
>>     xi = r2[cellpointer[i],0]
>>     yi = r2[cellpointer[i],1]
>>     zi = r2[cellpointer[i],2]
>>     denout[i] = b[cellpointer[i]]
>>     print i,xi,yi,zi,denout[i]
>>     newPoints.InsertPoint(i,xi,yi,zi)
>>
>> print newPoints
>>
>>
>> pdo.SetPoints(newPoints)
>>
>> #
>> # add computed arrays
>> #
>>
>> arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume')
>> pdo.GetPointData().AddArray(arrFTV)
>> print 'added stuff'
>> arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass')
>> pdo.GetPointData().AddArray(arrFTden)
>>
>> arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy')
>> pdo.GetPointData().AddArray(arrFTP)
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/bd7189e8/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Oct 29 12:14:25 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Oct 2014 12:14:25 -0400
Subject: [Paraview-developers] How should I update data arrays if time
 step is changed?
In-Reply-To: <CAJrGgcMqjv_MJ_vEQVcCxRKZ+SDxqShMy9RP88L8PsJr-+xG3w@mail.gmail.com>
References: <CAJrGgcMqjv_MJ_vEQVcCxRKZ+SDxqShMy9RP88L8PsJr-+xG3w@mail.gmail.com>
Message-ID: <CADHSJjDkUfzMw-2T3Bx9WJH6xFp2RrTRqBRRnKGB+TdxYyX7Pg@mail.gmail.com>

Look at vtkExtractArraysOverTime. In your request data, you can use
CONTINUE_EXECUTING to make the pipeline execute multiple times
ensuring each time you request that appropriate timestep and
internally cache, as needed.

Utkarsh

On Wed, Oct 29, 2014 at 8:28 AM, ?????? ?????? <maxim.glibin at gmail.com> wrote:
> Hello,
>
> I am trying to implement filter which will be able to compute difference of
> data arrays (for example 'temperature') between two specified time steps.
> How can I get data array for certain time step?
> For instance I have timesteps = [0, 0.01, 0.03,...] of 130 values.
> And I would like to get data array of 'temperature' in time step = 0.4.
>
> If someone have any idea how to implement it, please help me.
>
> Best regards,
> Maxim
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From utkarsh.ayachit at kitware.com  Wed Oct 29 12:29:34 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Oct 2014 12:29:34 -0400
Subject: [Paraview-developers] Specifying HiResLineSource to StreamTracer
In-Reply-To: <542D7E30.4020004@gmail.com>
References: <542D7E30.4020004@gmail.com>
Message-ID: <CADHSJjAahxPUYUCvvRv9YB5FKYyORf=txvuvuzW3WJxQF+Fk5A@mail.gmail.com>

Panos,

The "Source" property has a vtkSMProxyListDomain[1] which has proxies
for each of the options shown in the use. You can set the value of the
property using the proxies in that domain. You can get to the domain
using vtkSMProperty::FindDomain() method on the "Source" property.

[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxyListDomain.html



On Thu, Oct 2, 2014 at 12:32 PM, Panos Asproulis
<panos.asproulis at gmail.com> wrote:
> Hi all,
>
> I am trying to write code to create a streamline plot using the StreamTracer
> filter. The problem I have is the following: the StreamTracer filter
> receives as seed points a set of points created either by "PointSource"
> (extended_source) object or the "HiResLineSource" alternative. The default
> is "PointSource" so in the following code:
>
>   pqPipelineSource* streamFilter = builder->createFilter("filters",
> "StreamTracer", namedInputs,
>       paraview->getActiveServer());
>
>   pqSMProxy sourceProxy =
> pqSMAdaptor::getProxyProperty(streamProxy->GetProperty("Source"));
>
> std::cout << sourceProxy->GetXMLName() << std::endl;
>
> the object sourceProxy is indeed a "PointSource" object. How can I specify
> to the StreamTracer filter that I want it to use the "HiResLineSource"
> object instead? Do I need to create it? Is it available somewhere?
>
> Thanks in advance,
> Panos
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From utkarsh.ayachit at kitware.com  Wed Oct 29 12:31:22 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Oct 2014 12:31:22 -0400
Subject: [Paraview-developers] Cannot load field data into block table
In-Reply-To: <8D5C1B82EA40014E8B222E92B907632502135A8C55A6@MAILBOX.LASP.colorado.edu>
References: <8D5C1B82EA40014E8B222E92B907632502135A8C55A6@MAILBOX.LASP.colorado.edu>
Message-ID: <CADHSJjCGN6aVK+rG7dJAeYOXGt==dh4BNa-+a9YQYuTjpzBBgQ@mail.gmail.com>

Josh,

Do you have a sharable dataset to reproduce this? I use it's just
missing code somewhere.

Utkarsh

On Thu, Oct 23, 2014 at 1:29 PM, Joshua Murphy
<Joshua.Murphy at lasp.colorado.edu> wrote:
> Hello,
>
> I am trying to load some field data into a block data structure containing tables.  I am following the same procedure I do with the structured grid port on my reader (which works fine), but I cannot seem to actually load view the values in the table field data.
>
> the attached screen shot shows the problem. The titles for the columns load fine, but the actual data does not.  I have printed out the contents of the vtkStringArrays and vtkDoubleArrays at the point where I am loading them in, and the values are, indeed present.  They just do not show up in Paraview (I have tried with version 4.1 and 4.2 on Linux 64 bit).
>
> Does anyone have any idea why the values would not be loading?
>
> Thanks,
> Josh
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From utkarsh.ayachit at kitware.com  Wed Oct 29 12:49:45 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Oct 2014 12:49:45 -0400
Subject: [Paraview-developers] Plugin based on vtkExtractBlock calls
	twice RequestData
In-Reply-To: <ACE279CCDDBEFA43BD2F0EE07671EA98A96281AD@memc022.de.mtu.corp>
References: <ACE279CCDDBEFA43BD2F0EE07671EA98A96281AD@memc022.de.mtu.corp>
Message-ID: <CADHSJjAx=ZMqZcwebvPHot5ncaakc5cLdgNp+Tw_gPce8vDpcA@mail.gmail.com>

I don't follow. How do you mean by "second time when  actually does
what is supposed to be". What's the input when it gets executed the
first time? Try putting  a break point in the RequestData and see
where its getting called. If you can share a simple plugin code that
demonstrates the issue, that'd make it easier to identify the issue.
In general, filters are not expected to execute twice unless needed.

Utkarsh

On Thu, Oct 23, 2014 at 10:12 AM, RIVERA, Orlando <Orlando.RIVERA at mtu.de> wrote:
>
>
> Hi
>
>
>
> I  have a plugin  based on  vtkExtractBlock  and  when executed   calls
> RequestData twice   , and it is the second time when  actually does  what is
> supposed to be .   It work fine but I have no clue  why it is like that
>
>
>
> Any Ideas ?
>
>
>
> --
> MTU Aero Engines AG
> Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer
> Martens, Michael Schrey?gg, Dr. Stefan Weingartner
> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus
> Eberhardt
> Sitz der Gesellschaft/Registered Office: Muenchen
> Handelsregister/Commercial Register: Muenchen HRB 157206
>
> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder
> rechtlich geschuetzte Informationen.
> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den
> Absender und loeschen Sie diese
> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder
> Weiterleiten ist nicht gestattet.
>
> This e-mail and any attached documents are proprietary to MTU, confidential
> or protected by law.
> If you are not the intended recipient, please advise the sender and delete
> this message and its attachments.
> Any unauthorised storing, copying or distribution is prohibited.
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From shawn.waldon at kitware.com  Wed Oct 29 13:01:18 2014
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Wed, 29 Oct 2014 13:01:18 -0400
Subject: [Paraview-developers] Cannot load field data into block table
In-Reply-To: <CADHSJjCGN6aVK+rG7dJAeYOXGt==dh4BNa-+a9YQYuTjpzBBgQ@mail.gmail.com>
References: <8D5C1B82EA40014E8B222E92B907632502135A8C55A6@MAILBOX.LASP.colorado.edu>
 <CADHSJjCGN6aVK+rG7dJAeYOXGt==dh4BNa-+a9YQYuTjpzBBgQ@mail.gmail.com>
Message-ID: <CALSpCT3wzHMi5+3u2kgZozFx-QXPBarEBjk3Xe7OZ=y3XTJCfw@mail.gmail.com>

Josh,

I ran across a similar issue last week.  The fix was to patch the VTK that
ParaView builds against.  I've attached the patch that addresses the issue
with multi block data and field data, it is the second commit in this VTK
branch:

http://review.source.kitware.com/#/t/4899

Let me know if this solves your problem,

Shawn

On Wed, Oct 29, 2014 at 12:31 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Josh,
>
> Do you have a sharable dataset to reproduce this? I use it's just
> missing code somewhere.
>
> Utkarsh
>
> On Thu, Oct 23, 2014 at 1:29 PM, Joshua Murphy
> <Joshua.Murphy at lasp.colorado.edu> wrote:
> > Hello,
> >
> > I am trying to load some field data into a block data structure
> containing tables.  I am following the same procedure I do with the
> structured grid port on my reader (which works fine), but I cannot seem to
> actually load view the values in the table field data.
> >
> > the attached screen shot shows the problem. The titles for the columns
> load fine, but the actual data does not.  I have printed out the contents
> of the vtkStringArrays and vtkDoubleArrays at the point where I am loading
> them in, and the values are, indeed present.  They just do not show up in
> Paraview (I have tried with version 4.1 and 4.2 on Linux 64 bit).
> >
> > Does anyone have any idea why the values would not be loading?
> >
> > Thanks,
> > Josh
> >
> >
> > _______________________________________________
> > Paraview-developers mailing list
> > Paraview-developers at paraview.org
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141029/fb64e961/attachment.html>
-------------- next part --------------
diff --git a/IO/Legacy/vtkCompositeDataReader.cxx b/IO/Legacy/vtkCompositeDataReader.cxx
index 6861bfe..64506b8 100644
--- a/IO/Legacy/vtkCompositeDataReader.cxx
+++ b/IO/Legacy/vtkCompositeDataReader.cxx
@@ -18,6 +18,7 @@
 #include "vtkAMRInformation.h"
 #include "vtkDataObjectTypes.h"
 #include "vtkDoubleArray.h"
+#include "vtkFieldData.h"
 #include "vtkGenericDataObjectReader.h"
 #include "vtkHierarchicalBoxDataSet.h"
 #include "vtkInformation.h"
@@ -244,6 +245,7 @@ int vtkCompositeDataReader::RequestData(vtkInformation *, vtkInformationVector *
 bool vtkCompositeDataReader::ReadCompositeData(vtkMultiBlockDataSet* mb)
 {
   char line[256];
+
   if (!this->ReadString(line))
     {
     vtkErrorMacro("Failed to read block-count");
@@ -306,6 +308,12 @@ bool vtkCompositeDataReader::ReadCompositeData(vtkMultiBlockDataSet* mb)
       }
     }
 
+  if (this->ReadString(line) && strncmp(this->LowerCase(line),"field",5) == 0)
+    {
+    vtkSmartPointer< vtkFieldData > fd = this->ReadFieldData();
+    mb->SetFieldData(fd);
+    }
+
   return true;
 }
 
diff --git a/IO/Legacy/vtkCompositeDataWriter.cxx b/IO/Legacy/vtkCompositeDataWriter.cxx
index faa394a..bf1c3c7 100644
--- a/IO/Legacy/vtkCompositeDataWriter.cxx
+++ b/IO/Legacy/vtkCompositeDataWriter.cxx
@@ -173,6 +173,7 @@ bool vtkCompositeDataWriter::WriteCompositeData(ostream* fp,
     *fp << "ENDCHILD\n";
     }
 
+  this->WriteFieldData(fp, mb->GetFieldData());
   return true;
 }
 

From biddisco at cscs.ch  Thu Oct 30 08:27:49 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Thu, 30 Oct 2014 12:27:49 +0000
Subject: [Paraview-developers] How to compute difference of data
	arrays	between two time steps for filter.
In-Reply-To: <CAJrGgcPbwHcimGMP1uDuvExobRi28buoqRcJXVP7N7JVkMFRng@mail.gmail.com>
References: <CAJrGgcPbwHcimGMP1uDuvExobRi28buoqRcJXVP7N7JVkMFRng@mail.gmail.com>
Message-ID: <50320452A334BD42A5EC72BAD21450991905F471@MBX210.d.ethz.ch>

Maxim

vtkTemporalDifferenceFilter is what you want. If you google that, you should find the code.

JB

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of ?????? ??????
Sent: 29 October 2014 13:27
To: paraview-developers at paraview.org
Subject: [Paraview-developers] How to compute difference of data arrays between two time steps for filter.

Hello all,
It is necessary to extract only data array, compute difference between two time steps and save obtained difference into output.
Who have any ideas how to implement it?

BR
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141030/8433a471/attachment.html>

From biddisco at cscs.ch  Thu Oct 30 08:29:31 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Thu, 30 Oct 2014 12:29:31 +0000
Subject: [Paraview-developers] How to compute difference of
	data	arrays	between two time steps for filter.
In-Reply-To: <50320452A334BD42A5EC72BAD21450991905F471@MBX210.d.ethz.ch>
References: <CAJrGgcPbwHcimGMP1uDuvExobRi28buoqRcJXVP7N7JVkMFRng@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450991905F471@MBX210.d.ethz.ch>
Message-ID: <50320452A334BD42A5EC72BAD21450991906048E@MBX210.d.ethz.ch>

I beg your pardon, it?s not in a public repository.

I?ll create a new plugin and put it on github with the classes you need
(probably not before the end of the weekend though)

JB

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe, John A.
Sent: 30 October 2014 13:28
To: ?????? ??????; paraview-developers at paraview.org
Subject: Re: [Paraview-developers] How to compute difference of data arrays between two time steps for filter.

Maxim

vtkTemporalDifferenceFilter is what you want. If you google that, you should find the code.

JB

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of ?????? ??????
Sent: 29 October 2014 13:27
To: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
Subject: [Paraview-developers] How to compute difference of data arrays between two time steps for filter.

Hello all,
It is necessary to extract only data array, compute difference between two time steps and save obtained difference into output.
Who have any ideas how to implement it?

BR
Maxim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141030/ff4b2ba0/attachment-0001.html>

From redkite at virgin.net  Thu Oct 30 08:47:20 2014
From: redkite at virgin.net (r holbrey)
Date: Thu, 30 Oct 2014 12:47:20 +0000
Subject: [Paraview-developers] Plugin based on vtkExtractBlock calls
 twice RequestData
In-Reply-To: <CADHSJjAx=ZMqZcwebvPHot5ncaakc5cLdgNp+Tw_gPce8vDpcA@mail.gmail.com>
References: <ACE279CCDDBEFA43BD2F0EE07671EA98A96281AD@memc022.de.mtu.corp>
 <CADHSJjAx=ZMqZcwebvPHot5ncaakc5cLdgNp+Tw_gPce8vDpcA@mail.gmail.com>
Message-ID: <54523358.9060605@virgin.net>

Hi,

I had something like this at some point. I had a call in the filter 
code, something like

vtkSMProxy* proxy = .....
proxy->UpdateVTKObjects();

which I think was causing the filter to "auto-apply" ie run with default 
parameters. You might need to switch off "Auto-apply" too.

Richard


On 29/10/2014 16:49, Utkarsh Ayachit wrote:
> I don't follow. How do you mean by "second time when  actually does
> what is supposed to be". What's the input when it gets executed the
> first time? Try putting  a break point in the RequestData and see
> where its getting called. If you can share a simple plugin code that
> demonstrates the issue, that'd make it easier to identify the issue.
> In general, filters are not expected to execute twice unless needed.
>
> Utkarsh
>
> On Thu, Oct 23, 2014 at 10:12 AM, RIVERA, Orlando<Orlando.RIVERA at mtu.de>  wrote:
>>
>> Hi
>>
>>
>>
>> I  have a plugin  based on  vtkExtractBlock  and  when executed   calls
>> RequestData twice   , and it is the second time when  actually does  what is
>> supposed to be .   It work fine but I have no clue  why it is like that
>>
>>
>>
>> Any Ideas ?
>>
>>
>>
>> --
>> MTU Aero Engines AG
>> Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer
>> Martens, Michael Schrey?gg, Dr. Stefan Weingartner
>> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus
>> Eberhardt
>> Sitz der Gesellschaft/Registered Office: Muenchen
>> Handelsregister/Commercial Register: Muenchen HRB 157206
>>
>> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder
>> rechtlich geschuetzte Informationen.
>> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den
>> Absender und loeschen Sie diese
>> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder
>> Weiterleiten ist nicht gestattet.
>>
>> This e-mail and any attached documents are proprietary to MTU, confidential
>> or protected by law.
>> If you are not the intended recipient, please advise the sender and delete
>> this message and its attachments.
>> Any unauthorised storing, copying or distribution is prohibited.
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers


From maxim.glibin at gmail.com  Thu Oct 30 09:55:20 2014
From: maxim.glibin at gmail.com (=?UTF-8?B?0JzQsNC60YHQuNC8INCT0LvQuNCx0LjQvQ==?=)
Date: Thu, 30 Oct 2014 16:55:20 +0300
Subject: [Paraview-developers] How to compute difference of data arrays
 between two time steps for filter.
In-Reply-To: <50320452A334BD42A5EC72BAD21450991906048E@MBX210.d.ethz.ch>
References: <CAJrGgcPbwHcimGMP1uDuvExobRi28buoqRcJXVP7N7JVkMFRng@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450991905F471@MBX210.d.ethz.ch>
 <50320452A334BD42A5EC72BAD21450991906048E@MBX210.d.ethz.ch>
Message-ID: <CAJrGgcNwdv=6h2THSCbFmZ63YBBOYgAVyA1=hgY=Lh=HD5ThfA@mail.gmail.com>

Thank you, I look forward to receiving your reply.
BR

2014-10-30 15:29 GMT+03:00 Biddiscombe, John A. <biddisco at cscs.ch>:

>  I beg your pardon, it?s not in a public repository.
>
>
>
> I?ll create a new plugin and put it on github with the classes you need
>
> (probably not before the end of the weekend though)
>
>
>
> JB
>
>
>
> *From:* Paraview-developers [mailto:
> paraview-developers-bounces at paraview.org] *On Behalf Of *Biddiscombe,
> John A.
> *Sent:* 30 October 2014 13:28
> *To:* ?????? ??????; paraview-developers at paraview.org
> *Subject:* Re: [Paraview-developers] How to compute difference of data
> arrays between two time steps for filter.
>
>
>
> Maxim
>
>
>
> vtkTemporalDifferenceFilter is what you want. If you google that, you
> should find the code.
>
>
>
> JB
>
>
>
> *From:* Paraview-developers [
> mailto:paraview-developers-bounces at paraview.org
> <paraview-developers-bounces at paraview.org>] *On Behalf Of *?????? ??????
> *Sent:* 29 October 2014 13:27
> *To:* paraview-developers at paraview.org
> *Subject:* [Paraview-developers] How to compute difference of data arrays
> between two time steps for filter.
>
>
>
> Hello all,
>
> It is necessary to extract only data array, compute difference between two
> time steps and save obtained difference into output.
>
> Who have any ideas how to implement it?
>
>
>
> BR
>
> Maxim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141030/57523f17/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Oct 31 00:56:06 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 31 Oct 2014 00:56:06 -0400
Subject: [Paraview-developers] Gatekeeper Review (all topics reverted)
Message-ID: <CADHSJjAUAZaFit2gLAG2sxT8H=D5YODn4m61LAygceB4=KbC-w@mail.gmail.com>

Folks,

The dashboards had too many issues with multiple requests for
reverting various topics. As a result, I've just reverted all topics
on "next". Please validate your topics are merge those that are ready
for gatekeeper review again. The reverted topics are as follows:

Topics reverted from next:
  15078_fix_point_sprite
  cmake-warnings-20140922
  fix-xml-crash-on-close
  include-mpi-paths-as-system
  python_syntax_highlighting_bugs
  remove-else-and-endfoo-cmake-args
  remove-python-include-path
  text_updates
  update-vtk-20141030

Utkarsh

From reuterma at ornl.gov  Wed Oct 15 08:49:00 2014
From: reuterma at ornl.gov (Reuter, Michael A.)
Date: Wed, 15 Oct 2014 12:49:00 -0000
Subject: [Paraview-developers] Git-master and Windows
In-Reply-To: <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
References: <40513B88-F05F-4247-8422-B4CF33B90F11@ornl.gov>
 <CADHSJjBvOr4PVN4tnyDWZobpfrzvUKUfO6u0vHvxVFVcjsRQ9g@mail.gmail.com>
 <FDF9BB35-15EF-4B42-B70A-98D06579EC2C@ornl.gov>
 <CADHSJjA+zXf9m30ZHG6NunvcXRpxAJesf9z=KoAph2qQE7nG2A@mail.gmail.com>
 <6435380C-D8D9-4DEE-88CB-CA5EAEE29BD1@ornl.gov>
 <CADHSJjB9QWMA-g8_M15bmK2hR=MWLh5b0dUBxWes3wiEHrG4ww@mail.gmail.com>
 <6348957A-53FE-4B99-89E0-B39F73FF3420@ornl.gov>
 <CADHSJjDBYaWOV8r23VSKkdH92AaVj=7qqm9gK_QYDabAQWvi4A@mail.gmail.com>
Message-ID: <a06770f60eeb412d93935aeeac656349@EXCHCS33.ornl.gov>

I'm attaching the requested file. You are correct, it is just a straight (not Superbuild) source build of 4.2 with "system" libraries.

M

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Tuesday, October 14, 2014 11:26 AM
To: Reuter, Michael A.
Cc: paraview-developers at paraview.org
Subject: Re: [Paraview-developers] Git-master and Windows

I am still confused, but mind attaching your CMakeCache.txt? Let's see
if that shows anything. These issues are when simply building ParaView
4.2. (not Superbuild) with Python, Qt libraries already on the
machine, is that correct?

Utkarsh

On Tue, Oct 14, 2014 at 10:34 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
> I finally got ParaView (now using version 4.2.0) to give me a clue as to why startup was failing. I see:
>
> ImportError: No module named site
> [8854 refs]
>
> However, in the same shell window (environment) I tried to launch ParaView, I can launch python and do import site with no issues. It feels like a path is getting mangled or dropped somewhere inside ParaView?s startup, but I wouldn?t know where to begin looking. Any pointers?
>
> Thanks,
> M
>
>
> On Sep 19, 2014, at 10:57 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>
>> I am out of ideas at this point. Any Windows gurus out there?
>>
>> On Fri, Sep 19, 2014 at 10:55 AM, Reuter, Michael A. <reuterma at ornl.gov> wrote:
>>> The PYTHON27.DLL is coming from the expected location. That?s the only system Python library being reported by dependency walker.
>>>
>>>
>>> On Sep 19, 2014, at 12:40 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>
>>> The IESHIM thing can be ignored. It often shows up missing. Are the
>>> right Python dlls being loaded? Is it accidentally picking them up
>>> from some other path?
>>>
>>> On Thu, Sep 18, 2014 at 11:49 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov>> wrote:
>>> Ignore the red function points thing. Had other PV libs in the path. Cleaned that up, but the dependency thing still stands. The executable can find all the necessary libraries except IESHIMS.DLL.
>>>
>>> M
>>>
>>> On Sep 18, 2014, at 10:17 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com><mailto:utkarsh.ayachit at kitware.com>> wrote:
>>>
>>> Since you said you build with your own installation of Python, is
>>> Python in PATH? Try using the dependency walker[1] to see if it can
>>> find all the dependencies correctly.
>>>
>>> Utkarsh
>>>
>>> [1] http://www.dependencywalker.com/
>>>
>>> On Thu, Sep 18, 2014 at 9:57 AM, Reuter, Michael A. <reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>> wrote:
>>> Hi,
>>>
>>> I?m having a very strange issue with trying to use a git-master version of ParaView on Windows using ninja/VS2012. I can get the build to complete just fine, but running the paraview.exe does nothing. It thinks for a bit and then exits without any hit of an error. A debug build does the same thing. I can?t attach any debugging process since subsequent attempts at execution exit much faster. I think the issue has to do with Python because I?ve made a build using PARAVIEW_ENABLE_PYTHON=OFF and paraview.exe works fine in that case. I?ve been left scratching my head, so I?m willing to entertain any and all ideas about what further things I can look at to determine the problem.
>>>
>>> Thanks,
>>> M
>>>
>>> Dr. Michael Reuter
>>> Scientific Data Analysis Group
>>> Neutron Data Analysis and Visualization Division
>>> Oak Ridge National Laboratory
>>>
>>> Office: 1-865-241-7216
>>> Fax: 1-865-574-6080
>>> Email: reuterma at ornl.gov<mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov><mailto:reuterma at ornl.gov>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org><mailto:Paraview-developers at paraview.org>
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>>
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CMakeCache.txt
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20141015/4a161cac/attachment-0001.txt>