sensei issueshttps://gitlab.kitware.com/sensei/sensei/-/issues2017-10-10T13:18:50-04:00https://gitlab.kitware.com/sensei/sensei/-/issues/1Oscilators miniapp DIY deadlock2017-10-10T13:18:50-04:00Burlen LoringOscilators miniapp DIY deadlockDIY enters a deadlock when the miniapp is run with more MPI ranks than blocks. I was using this as a test case to be sure the ADIOS adaptors can work under such conditions. Commands to reproduce below, followed by backtrace.
Note that t...DIY enters a deadlock when the miniapp is run with more MPI ranks than blocks. I was using this as a test case to be sure the ADIOS adaptors can work under such conditions. Commands to reproduce below, followed by backtrace.
Note that the backtrace below shows that this issue is occurring in the destructor of the Autocorelation class. It is generally bad form to do anything but release resources in a destructor, and I suspect that this is the issue rather than a problem in DIY.
```xml
<sensei>
<analysis type="autocorrelation" array="data" association="cell"
window="10" k-max="3" enabled="1" />
</sensei>
```
```bash
mpiexec -np 2 ./bin/oscillator -b 1 -t 1 -f ./config.xml ../sensei/miniapps/oscillators/inputs/sample.osc
```
```C++
(gdb) bt
#0 0x00007fffc60c3b09 in mca_btl_vader_component_progress () at btl_vader_component.c:688
#1 0x00007fffd2678dea in opal_progress () at runtime/opal_progress.c:187
#2 0x00007fffd72862d5 in opal_condition_wait (c=<optimized out>, m=<optimized out>) at ../opal/threads/condition.h:78
#3 ompi_request_default_wait_all (count=2, requests=0x7fffffffba60, statuses=0x0) at request/req_wait.c:281
#4 0x00007fffc4e147a6 in ompi_coll_tuned_allreduce_intra_recursivedoubling (sbuf=<optimized out>, rbuf=0xd25650, count=10,
dtype=0x7fffd750d060 <ompi_mpi_float>, op=0x7fffd751db80 <ompi_mpi_op_sum>, comm=<optimized out>, module=0xc1d610) at coll_tuned_allreduce.c:245
#5 0x00007fffd7296efe in PMPI_Allreduce (sendbuf=0xd25860, recvbuf=0xd25650, count=10, e=0x7fffd750d060 <ompi_mpi_float>,
op=0x7fffd751db80 <ompi_mpi_op_sum>, comm=0x7fffd7514b20 <ompi_mpi_comm_world>) at pallreduce.c:109
#6 0x000000000052cff0 in diy::mpi::Collectives<float, add_vectors<float> >::all_reduce (comm=..., in=std::vector of length 10, capacity 10 = {...},
out=std::vector of length 10, capacity 10 = {...}) at /work/SENSEI/sensei/utils/diy/mpi/collectives.hpp:179
#7 0x000000000052cae6 in diy::mpi::all_reduce<float, add_vectors<float> > (comm=..., in=std::vector of length 10, capacity 10 = {...},
out=std::vector of length 10, capacity 10 = {...}, op=...) at /work/SENSEI/sensei/utils/diy/mpi/collectives.hpp:292
#8 0x000000000052c509 in diy::detail::AllReduceOp<std::vector<float, std::allocator<float> >, add_vectors<float> >::global (this=0x7fffb4000910, comm=...)
at /work/SENSEI/sensei/utils/diy/detail/collectives.hpp:26
#9 0x000000000051d8c0 in diy::Master::Collective::global (this=0x7fffb40009a0, c=...) at /work/SENSEI/sensei/utils/diy/master.hpp:350
#10 0x000000000051ed26 in diy::Master::process_collectives (this=0xc21ec0) at /work/SENSEI/sensei/utils/diy/master.hpp:1004
#11 0x000000000051eab8 in diy::Master::flush (this=0xc21ec0) at /work/SENSEI/sensei/utils/diy/master.hpp:974
#12 0x000000000051db31 in diy::Master::exchange (this=0xc21ec0) at /work/SENSEI/sensei/utils/diy/master.hpp:788
#13 0x0000000000566882 in sensei::Autocorrelation::PrintResults (this=0xc1d580, k_max=3) at /work/SENSEI/sensei/sensei/Autocorrelation.cxx:313
#14 0x00000000005654c6 in sensei::Autocorrelation::~Autocorrelation (this=0xc1d580, __in_chrg=<optimized out>)
at /work/SENSEI/sensei/sensei/Autocorrelation.cxx:210
#15 0x0000000000565524 in sensei::Autocorrelation::~Autocorrelation (this=0xc1d580, __in_chrg=<optimized out>)
at /work/SENSEI/sensei/sensei/Autocorrelation.cxx:212
#16 0x00007fffd8342820 in vtkObjectBase::UnRegisterInternal (this=0xc1d580, check=0) at /work/SENSEI/ParaView/VTK/Common/Core/vtkObjectBase.cxx:240
#17 0x00007fffd83426e6 in vtkObjectBase::UnRegister (this=0xc1d580, o=0x0) at /work/SENSEI/ParaView/VTK/Common/Core/vtkObjectBase.cxx:197
#18 0x00007fffd83796fb in vtkSmartPointerBase::~vtkSmartPointerBase (this=0xc1eb70, __in_chrg=<optimized out>)
at /work/SENSEI/ParaView/VTK/Common/Core/vtkSmartPointerBase.cxx:62
#19 0x0000000000549338 in vtkSmartPointer<sensei::AnalysisAdaptor>::~vtkSmartPointer (this=0xc1eb70, __in_chrg=<optimized out>)
at /work/SENSEI/ParaView/VTK/Common/Core/vtkSmartPointer.h:29
#20 0x000000000054a9e7 in std::_Destroy<vtkSmartPointer<sensei::AnalysisAdaptor> > (__pointer=0xc1eb70) at /usr/include/c++/5.3.1/bits/stl_construct.h:93
#21 0x000000000054a7d9 in std::_Destroy_aux<false>::__destroy<vtkSmartPointer<sensei::AnalysisAdaptor>*> (__first=0xc1eb70, __last=0xc1eb78)
at /usr/include/c++/5.3.1/bits/stl_construct.h:103
#22 0x000000000054a3f2 in std::_Destroy<vtkSmartPointer<sensei::AnalysisAdaptor>*> (__first=0xc1eb70, __last=0xc1eb78)
at /usr/include/c++/5.3.1/bits/stl_construct.h:126
#23 0x0000000000549e3f in std::_Destroy<vtkSmartPointer<sensei::AnalysisAdaptor>*, vtkSmartPointer<sensei::AnalysisAdaptor> > (__first=0xc1eb70,
__last=0xc1eb78) at /usr/include/c++/5.3.1/bits/stl_construct.h:151
#24 0x0000000000549877 in std::vector<vtkSmartPointer<sensei::AnalysisAdaptor>, std::allocator<vtkSmartPointer<sensei::AnalysisAdaptor> > >::~vector (
this=0xc21e90, __in_chrg=<optimized out>) at /usr/include/c++/5.3.1/bits/stl_vector.h:424
#25 0x00000000005493f6 in sensei::ConfigurableAnalysis::InternalsType::~InternalsType (this=0xc21e90, __in_chrg=<optimized out>)
at /work/SENSEI/sensei/sensei/ConfigurableAnalysis.cxx:99
#26 0x0000000000548728 in sensei::ConfigurableAnalysis::~ConfigurableAnalysis (this=0xc21e60, __in_chrg=<optimized out>)
at /work/SENSEI/sensei/sensei/ConfigurableAnalysis.cxx:501
#27 0x0000000000548770 in sensei::ConfigurableAnalysis::~ConfigurableAnalysis (this=0xc21e60, __in_chrg=<optimized out>)
at /work/SENSEI/sensei/sensei/ConfigurableAnalysis.cxx:502
#28 0x00007fffd8342820 in vtkObjectBase::UnRegisterInternal (this=0xc21e60, check=0) at /work/SENSEI/ParaView/VTK/Common/Core/vtkObjectBase.cxx:240
#29 0x00007fffd83426e6 in vtkObjectBase::UnRegister (this=0xc21e60, o=0x0) at /work/SENSEI/ParaView/VTK/Common/Core/vtkObjectBase.cxx:197
#30 0x00007fffd83796fb in vtkSmartPointerBase::~vtkSmartPointerBase (this=0x7fffffffc210, __in_chrg=<optimized out>)
at /work/SENSEI/ParaView/VTK/Common/Core/vtkSmartPointerBase.cxx:62
#31 0x00007fffd8379741 in vtkSmartPointerBase::operator= (this=0x8ceb58 <bridge::GlobalAnalysisAdaptor>, r=0x0)
at /work/SENSEI/ParaView/VTK/Common/Core/vtkSmartPointerBase.cxx:75
#32 0x00000000005313cd in vtkSmartPointer<sensei::ConfigurableAnalysis>::operator= (this=0x8ceb58 <bridge::GlobalAnalysisAdaptor>, r=0x0)
at /work/SENSEI/ParaView/VTK/Common/Core/vtkSmartPointer.h:58
#33 0x00000000005310c4 in bridge::finalize (k_max=3, nblocks=1) at /work/SENSEI/sensei/miniapps/oscillators/bridge.cpp:76
#34 0x00000000004eadeb in main (argc=8, argv=0x7fffffffd518) at /work/SENSEI/sensei/miniapps/oscillators/oscillator.cpp:267
```https://gitlab.kitware.com/sensei/sensei/-/issues/2clang warnings in osciallator miniapp2017-11-08T19:27:12-05:00Burlen Loringclang warnings in osciallator miniappclang reports use of static member variable that has not been initialized. here is a prototypical instance
```
In file included from /Users/bloring/sensei/miniapps/oscillators/oscillator.cpp:4:
/Users/bloring/sensei/miniapps/oscillators...clang reports use of static member variable that has not been initialized. here is a prototypical instance
```
In file included from /Users/bloring/sensei/miniapps/oscillators/oscillator.cpp:4:
/Users/bloring/sensei/miniapps/oscillators/include/format.h:589:25: warning: instantiation of variable 'fmt::internal::BasicData<void>::POWERS_OF_10_64' required here, but no definition is available [-Wundefined-var-template]
return t - (n < Data::POWERS_OF_10_64[t]) + 1;
^
/Users/bloring/sensei/miniapps/oscillators/include/format.h:568:25: note: forward declaration of template entity is here
static const uint64_t POWERS_OF_10_64[];
^
/Users/bloring/sensei/miniapps/oscillators/include/format.h:589:25: note: add an explicit instantiation declaration to suppress this warning if 'fmt::internal::BasicData<void>::POWERS_OF_10_64' is explicitly instantiated in another translation unit
return t - (n < Data::POWERS_OF_10_64[t]) + 1;
^
```
here is the class in question
```C++
563 // Static data is placed in this class template to allow header-only
564 // configuration.
565 template <typename T = void>
566 struct BasicData {
567 static const uint32_t POWERS_OF_10_32[];
568 static const uint64_t POWERS_OF_10_64[];
569 static const char DIGITS[];
570 };
```https://gitlab.kitware.com/sensei/sensei/-/issues/4test builds on ubuntu systems2017-11-13T15:54:29-05:00Burlen Loringtest builds on ubuntu systemsall of the sensei+back end combos need to be tested on apple and ubuntu.all of the sensei+back end combos need to be tested on apple and ubuntu.https://gitlab.kitware.com/sensei/sensei/-/issues/8Catalyst Adaptor does not use communicator2017-12-11T17:46:41-05:00Burlen LoringCatalyst Adaptor does not use communicatorCatalyst Adaptor does not use communicatorCatalyst Adaptor does not use communicatorhttps://gitlab.kitware.com/sensei/sensei/-/issues/12FindMPI4PY.cmake and FindNUMPY.cmake not python3 friendly2018-01-29T13:53:25-05:00Jean M. FavreFindMPI4PY.cmake and FindNUMPY.cmake not python3 friendlybuilding sensei with python3 fails to find numpy and mpi4pybuilding sensei with python3 fails to find numpy and mpi4pyhttps://gitlab.kitware.com/sensei/sensei/-/issues/6Handle non-composite data in VTKPosthocIO2018-04-16T18:17:29-04:00Burlen LoringHandle non-composite data in VTKPosthocIOHandle non-composite data in VTKPosthocIOHandle non-composite data in VTKPosthocIOhttps://gitlab.kitware.com/sensei/sensei/-/issues/10DataAdaptor API has no way of request specific meshes2018-04-16T18:19:28-04:00Burlen LoringDataAdaptor API has no way of request specific meshesWhen a simulation uses multiple meshes it is impossible to know which one is needed.
An motivating example is the Warp LPA simulation code, which computes the solution of a number of different particle species and has a Cartesian or blo...When a simulation uses multiple meshes it is impossible to know which one is needed.
An motivating example is the Warp LPA simulation code, which computes the solution of a number of different particle species and has a Cartesian or block structured AMR mesh for the solution of megnetic and electric fields. Particle species can be molecules or sub atomic particles such as porotons and electrons. There can be multiple species of the same sub atomic particle type, for instance electrons are kept in distict species identifying which molecules/atoms they derived from. The number of species present in given simulation is problem specific.
**Existing DataAdaptor API:**
```c++
virtual vtkDataObject* GetMesh(bool structure_only=false) = 0;
virtual bool AddArray(vtkDataObject* mesh, int association, const std::string& arrayname) = 0;
virtual unsigned int GetNumberOfArrays(int association) = 0;
virtual std::string GetArrayName(int association, unsigned int index) = 0;
virtual void ReleaseData() = 0;
```
Note that in AddArray we pass a VTK pointer in which could potentially be used as a key to identify which mesh data is being requested from. However, this might be highly inconvenient and potentially problematic in languages other than C++.
**Option 1:**
```c++
// Discover the number of meshes a simulation can provide
virtual int GetNumberOfMeshes(int &numMeshes) = 0;
// Discover the names of the meshes
virtual int GetMeshName(int id, const std::string &meshName) = 0;
virtual int GetMesh(const std::string &meshName, bool structure_only,
vtkDataObject *&mesh) = 0;
virtual int AddArray(vtkDataObject* mesh, const std::string &meshName,
int association, const std::string& arrayname) = 0;
virtual int GetNumberOfArrays(const std::string &meshName, int association,
unsigned int &numberOfArrays) = 0;
virtual int GetArrayName(const std::string &meshName, int association,
unsigned int index, std::string &arrayName) = 0;
virtual int ReleaseData(const std::string &meshName) = 0;
virtual int ReleaseData() = 0;
```
`meshName` identifies the mesh where necessary. In all API an `int` is returned, zero indicates success, non zero an error (see #9).
https://gitlab.kitware.com/sensei/sensei/-/issues/7VTKPosthocIO add arrays2018-05-09T19:58:03-04:00Burlen LoringVTKPosthocIO add arraysUse SENSEI's AddArray API, currently expects them to be presentUse SENSEI's AddArray API, currently expects them to be presenthttps://gitlab.kitware.com/sensei/sensei/-/issues/18update readme with new analysis adaptors2018-06-27T14:37:27-04:00Burlen Loringupdate readme with new analysis adaptorshttps://gitlab.kitware.com/sensei/sensei/-/issues/20master branch fails to build with ENABLE_PYTHON=OFF2018-07-10T13:40:18-04:00Silvio Rizzimaster branch fails to build with ENABLE_PYTHON=OFFmaster branch
commit ac2c52f94b1b7c5658ed614a9000bb0c9f86f101
With ENABLE_PYTHON=OFF I get the following error:
```
[ 64%] Building CXX object sensei/CMakeFiles/sensei.dir/ConfigurableAnalysis.cxx.o
/projects/visualization/srizz...master branch
commit ac2c52f94b1b7c5658ed614a9000bb0c9f86f101
With ENABLE_PYTHON=OFF I get the following error:
```
[ 64%] Building CXX object sensei/CMakeFiles/sensei.dir/ConfigurableAnalysis.cxx.o
/projects/visualization/srizzi/BUILDS/sensei/sensei/sensei/ConfigurableAnalysis.cxx(618): error: identifier "PythonAnalysis" is undefined
vtkNew<PythonAnalysis> pyAnalysis;
^
/soft/visualization/vtk/include/vtk-8.1/vtkNew.h(62): error: name followed by "::" must be a class or namespace name
vtkNew() : Object(T::New())
^
detected during instantiation of "vtkNew<T>::vtkNew() [with T=<error-type>]" at line 618 of "/projects/visualization/srizzi/BUILDS/sensei/sensei/sensei/ConfigurableAnalysis.cxx"
compilation aborted for /projects/visualization/srizzi/BUILDS/sensei/sensei/sensei/ConfigurableAnalysis.cxx (code 2)
sensei/CMakeFiles/sensei.dir/build.make:62: recipe for target 'sensei/CMakeFiles/sensei.dir/ConfigurableAnalysis.cxx.o' failed
make[2]: *** [sensei/CMakeFiles/sensei.dir/ConfigurableAnalysis.cxx.o] Error 2
CMakeFiles/Makefile2:286: recipe for target 'sensei/CMakeFiles/sensei.dir/all' failed
```https://gitlab.kitware.com/sensei/sensei/-/issues/21test with binary installs2018-07-10T13:49:42-04:00Burlen Loringtest with binary installsin #19 a user reported that sensei fails to build with debian and homebrew installed vtk. we should test those as this will lower the barrier to get startedin #19 a user reported that sensei fails to build with debian and homebrew installed vtk. we should test those as this will lower the barrier to get startedhttps://gitlab.kitware.com/sensei/sensei/-/issues/19VTK version requirements?2018-07-10T13:52:29-04:00Jefferson Amstutzjamstutz@nvidia.comVTK version requirements?(this is a duplicate issue with one I posed on GitHub)
Hi,
I'm trying to build SENSEI but it seems that even though CMake finds VTK (8.1.1), it claims that a huge list of targets are "not yet defined"....ultimately resulting in a SENSE...(this is a duplicate issue with one I posed on GitHub)
Hi,
I'm trying to build SENSEI but it seems that even though CMake finds VTK (8.1.1), it claims that a huge list of targets are "not yet defined"....ultimately resulting in a SENSEI CMake error. I've tried this with pre-build VTK packages both on Arch (via package manager) and macOS (via Homebrew).
Is there an expected recipe for building SENSEI and/or a compatible VTK?
CMake error below (macOS), same on both OS environments listed above:
-------------------
CMake Error at /usr/local/Cellar/vtk/8.1.1/lib/cmake/vtk-8.1/VTKTargets.cmake:37 (message):
Some (but not all) targets in this export set were already defined.
Targets Defined: vtk
Targets not yet defined:
vtksys;vtkCommonCore;vtkCommonCoreTCL;vtkCommonMath;vtkCommonMathTCL;vtkCommonMisc;vtkCommonMiscTCL;vtkCommonSystem;vtkCommonSystemTCL;vtkCommonTransforms;vtkCommonTransformsTCL;vtkCommonDataModel;vtkCommonDataModelTCL;vtkCommonColor;vtkCommonColorTCL;vtkCommonExecutionModel;vtkCommonExecutionModelTCL;vtkCommonComputationalGeometry;vtkCommonComputationalGeometryTCL;vtkFiltersCore;vtkFiltersCoreTCL;vtkFiltersGeneral;vtkFiltersGeneralTCL;vtkImagingCore;vtkImagingCoreTCL;vtkImagingFourier;vtkImagingFourierTCL;vtkalglib;vtkFiltersStatistics;vtkFiltersStatisticsTCL;vtkFiltersExtraction;vtkFiltersExtractionTCL;vtkInfovisCore;vtkInfovisCoreTCL;vtkFiltersGeometry;vtkFiltersGeometryTCL;vtkFiltersSources;vtkFiltersSourcesTCL;vtkRenderingCore;vtkRenderingCoreTCL;vtkfreetype;vtkRenderingFreeType;vtkRenderingFreeTypeTCL;vtkRenderingContext2D;vtkRenderingContextIIDTCL;vtkChartsCore;vtkChartsCoreTCL;vtkDICOMParser;vtklz4;vtkIOCore;vtkIOCoreTCL;vtkIOLegacy;vtkIOLegacyTCL;vtkIOXMLParser;vtkIOXMLParserTCL;vtkDomainsChemistry;vtkDomainsChemistryTCL;vtkEncodeString;vtkglew;vtkRenderingOpenGL2;vtkRenderingOpenGLIITCL;vtkDomainsChemistryOpenGL2;vtkRenderingChemistryOpenGLIITCL;vtkIOXML;vtkIOXMLTCL;vtkHashSource;vtkParallelCore;vtkParallelCoreTCL;vtkFiltersAMR;vtkFiltersAMRTCL;vtkFiltersFlowPaths;vtkFiltersFlowPathsTCL;vtkFiltersGeneric;vtkFiltersGenericTCL;vtkImagingSources;vtkImagingSourcesTCL;vtkFiltersHybrid;vtkFiltersHybridTCL;vtkFiltersHyperTree;vtkFiltersHyperTreeTCL;vtkImagingGeneral;vtkImagingGeneralTCL;vtkFiltersImaging;vtkFiltersImagingTCL;vtkFiltersModeling;vtkFiltersModelingTCL;vtkFiltersParallel;vtkFiltersParallelTCL;vtkFiltersParallelImaging;vtkFiltersParallelImagingTCL;vtkFiltersPoints;vtkFiltersPointsTCL;vtkFiltersProgrammable;vtkFiltersProgrammableTCL;vtkWrappingTools;vtkWrapHierarchy;vtkWrapTcl;vtkWrapTclInit;vtkWrapPython;vtkWrapPythonInit;vtkParseJava;vtkWrapJava;vtkWrappingPythonCore;vtkFiltersPython;vtkFiltersSMP;vtkFiltersSMPTCL;vtkFiltersSelection;vtkFiltersSelectionTCL;vtkFiltersTexture;vtkFiltersTextureTCL;vtkFiltersTopology;vtkFiltersTopologyTCL;verdict;vtkFiltersVerdict;vtkFiltersVerdictTCL;vtkmetaio;vtkIOImage;vtkIOImageTCL;vtkImagingHybrid;vtkImagingHybridTCL;vtkInfovisLayout;vtkInfovisLayoutTCL;vtkInteractionStyle;vtkInteractionStyleTCL;vtkImagingColor;vtkImagingColorTCL;vtkRenderingAnnotation;vtkRenderingAnnotationTCL;vtkRenderingVolume;vtkRenderingVolumeTCL;vtkInteractionWidgets;vtkInteractionWidgetsTCL;vtkViewsCore;vtkViewsCoreTCL;vtkproj4;vtkGeovisCore;vtkGeovisCoreTCL;vtkIOAMR;vtkIOAMRTCL;vtkIOEnSight;vtkIOEnSightTCL;vtkexoIIc;vtkIOExodus;vtkIOExodusTCL;vtkgl2ps;vtkRenderingGL2PSOpenGL2;vtkRenderingGLtoPSOpenGLIITCL;vtklibharu;vtkIOExport;vtkIOExportTCL;vtkIOExportOpenGL2;vtkIOExportOpenGLIITCL;vtkIOGeometry;vtkIOGeometryTCL;vtkIOImport;vtkIOImportTCL;vtkIOInfovis;vtkIOInfovisTCL;vtkIOLSDyna;vtkIOLSDynaTCL;vtkIOMINC;vtkIOMINCTCL;vtkoggtheora;vtkIOMovie;vtkIOMovieTCL;vtknetcdfcpp;vtkIONetCDF;vtkIONetCDFTCL;vtkIOPLY;vtkIOPLYTCL;vtkjsoncpp;vtkIOParallel;vtkIOParallelTCL;vtkIOParallelXML;vtkIOParallelXMLTCL;vtksqlite;vtkIOSQL;vtkIOSQLTCL;vtkIOTecplotTable;vtkIOTecplotTableTCL;vtkIOVideo;vtkIOVideoTCL;vtkImagingMath;vtkImagingMathTCL;vtkImagingMorphological;vtkImagingMorphologicalTCL;vtkImagingStatistics;vtkImagingStatisticsTCL;vtkImagingStencil;vtkImagingStencilTCL;vtkInfovisBoostGraphAlgorithms;vtkInfovisBoostGraphAlgorithmsTCL;vtkInteractionImage;vtkInteractionImageTCL;vtkRenderingContextOpenGL2;vtkRenderingContextOpenGLIITCL;vtkRenderingFreeTypeFontConfig;vtkRenderingImage;vtkRenderingImageTCL;vtkRenderingLOD;vtkRenderingLODTCL;vtkRenderingLabel;vtkRenderingLabelTCL;vtkRenderingTkTCL;vtkRenderingPythonTkWidgets;vtkRenderingVolumeOpenGL2;vtkRenderingVolumeOpenGLIITCL;vtkViewsContext2D;vtkViewsContextIIDTCL;vtkViewsInfovis;vtkViewsInfovisTCL;vtkCommonCorePythonD;vtkCommonMathPythonD;vtkCommonMiscPythonD;vtkCommonSystemPythonD;vtkCommonTransformsPythonD;vtkCommonDataModelPythonD;vtkCommonColorPythonD;vtkCommonExecutionModelPythonD;vtkCommonComputationalGeometryPythonD;vtkFiltersCorePythonD;vtkFiltersGeneralPythonD;vtkImagingCorePythonD;vtkImagingFourierPythonD;vtkFiltersStatisticsPythonD;vtkFiltersExtractionPythonD;vtkInfovisCorePythonD;vtkFiltersGeometryPythonD;vtkFiltersSourcesPythonD;vtkRenderingCorePythonD;vtkRenderingFreeTypePythonD;vtkRenderingContext2DPythonD;vtkChartsCorePythonD;vtkIOCorePythonD;vtkIOLegacyPythonD;vtkIOXMLParserPythonD;vtkDomainsChemistryPythonD;vtkRenderingOpenGL2PythonD;vtkDomainsChemistryOpenGL2PythonD;vtkIOXMLPythonD;vtkParallelCorePythonD;vtkFiltersAMRPythonD;vtkFiltersFlowPathsPythonD;vtkFiltersGenericPythonD;vtkImagingSourcesPythonD;vtkFiltersHybridPythonD;vtkFiltersHyperTreePythonD;vtkImagingGeneralPythonD;vtkFiltersImagingPythonD;vtkFiltersModelingPythonD;vtkFiltersParallelPythonD;vtkFiltersParallelImagingPythonD;vtkFiltersPointsPythonD;vtkFiltersProgrammablePythonD;vtkFiltersPythonPythonD;vtkFiltersSMPPythonD;vtkFiltersSelectionPythonD;vtkFiltersTexturePythonD;vtkFiltersTopologyPythonD;vtkFiltersVerdictPythonD;vtkIOImagePythonD;vtkImagingHybridPythonD;vtkInfovisLayoutPythonD;vtkInteractionStylePythonD;vtkImagingColorPythonD;vtkRenderingAnnotationPythonD;vtkRenderingVolumePythonD;vtkInteractionWidgetsPythonD;vtkViewsCorePythonD;vtkGeovisCorePythonD;vtkIOAMRPythonD;vtkIOEnSightPythonD;vtkIOExodusPythonD;vtkRenderingGL2PSOpenGL2PythonD;vtkIOExportPythonD;vtkIOExportOpenGL2PythonD;vtkIOGeometryPythonD;vtkIOImportPythonD;vtkIOInfovisPythonD;vtkIOLSDynaPythonD;vtkIOMINCPythonD;vtkIOMoviePythonD;vtkIONetCDFPythonD;vtkIOPLYPythonD;vtkIOParallelPythonD;vtkIOParallelXMLPythonD;vtkIOSQLPythonD;vtkIOTecplotTablePythonD;vtkIOVideoPythonD;vtkImagingMathPythonD;vtkImagingMorphologicalPythonD;vtkImagingStatisticsPythonD;vtkImagingStencilPythonD;vtkInfovisBoostGraphAlgorithmsPythonD;vtkInteractionImagePythonD;vtkRenderingContextOpenGL2PythonD;vtkRenderingImagePythonD;vtkRenderingLODPythonD;vtkRenderingLabelPythonD;vtkRenderingVolumeOpenGL2PythonD;vtkViewsContext2DPythonD;vtkViewsInfovisPythonD
Call Stack (most recent call first):
/usr/local/lib/cmake/vtk-8.1/VTKConfig.cmake:120 (include)
CMake/vtk.cmake:22 (find_package)
CMakeLists.txt:12 (include)
-- Configuring incomplete, errors occurred!https://gitlab.kitware.com/sensei/sensei/-/issues/9DataAadatpor API has no way to indicate method failed2018-07-20T16:59:19-04:00Burlen LoringDataAadatpor API has no way to indicate method failedIf the following methods fail there is no reliable way to let the caller know that his call has failed. Note that in the case of GetMesh it is valid to return a `nullptr`, for instance if the analysis is run on more cores than the simula...If the following methods fail there is no reliable way to let the caller know that his call has failed. Note that in the case of GetMesh it is valid to return a `nullptr`, for instance if the analysis is run on more cores than the simulation than some number of processes will return `nullptr`.
```C++
virtual vtkDataObject* GetMesh(bool structure_only=false) = 0;
virtual std::string GetArrayName(int association, unsigned int index) = 0;
```
How is the best way to indicate an error for this call? Could an adaptor not provide arrays? in that case 0 would not be an error. A negative return could indicate an error if the return type was signed.
```C++
virtual unsigned int GetNumberOfArrays(int association) = 0;
```https://gitlab.kitware.com/sensei/sensei/-/issues/23raise exceptions in DataAdaptor wrappers2018-08-13T19:33:50-04:00Burlen Loringraise exceptions in DataAdaptor wrappersThe API had to be massaged because Python doesn't do pass by reference at the expense of the error return code. Instead we can raise exceptions in DataAdaptor wrappers when an error occurs. currently we are reporting the error but raisin...The API had to be massaged because Python doesn't do pass by reference at the expense of the error return code. Instead we can raise exceptions in DataAdaptor wrappers when an error occurs. currently we are reporting the error but raising an exception.https://gitlab.kitware.com/sensei/sensei/-/issues/26fix broken vtkm accelerators2018-09-13T14:03:18-04:00Burlen Loringfix broken vtkm acceleratorslibraries are not linkedlibraries are not linkedhttps://gitlab.kitware.com/sensei/sensei/-/issues/28sensei + vtkm build fail2018-09-13T15:43:39-04:00Burlen Loringsensei + vtkm build fail```
In file included from /work/SENSEI/sensei/sensei/VTKmVolumeReductionAnalysis.cxx:1:
/work/SENSEI/sensei/sensei/VTKmVolumeReductionAnalysis.h:5:10: fatal error: vtkm/cont/Field.h: No such file or directory
#include <vtkm/cont/Field.h...```
In file included from /work/SENSEI/sensei/sensei/VTKmVolumeReductionAnalysis.cxx:1:
/work/SENSEI/sensei/sensei/VTKmVolumeReductionAnalysis.h:5:10: fatal error: vtkm/cont/Field.h: No such file or directory
#include <vtkm/cont/Field.h>
^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [sensei/CMakeFiles/senseiCore.dir/build.make:193: sensei/CMakeFiles/senseiCore.dir/VTKmVolumeReductionAnalysis.cxx.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:263: sensei/CMakeFiles/senseiCore.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
```https://gitlab.kitware.com/sensei/sensei/-/issues/27fix vtkm documentation2018-09-13T15:44:15-04:00Burlen Loringfix vtkm documentationREADME.md incorrectly implies that use3 of VTKm in sensei depends on VTK, we have also used a VTKm clone outside of VTK, and need to support that use case.README.md incorrectly implies that use3 of VTKm in sensei depends on VTK, we have also used a VTKm clone outside of VTK, and need to support that use case.https://gitlab.kitware.com/sensei/sensei/-/issues/25use interface library for vtkm dependencies2018-09-13T15:44:46-04:00Burlen Loringuse interface library for vtkm dependenciesIn `CMake/vtkm.cmake` define an interface library that encapsulates our usage of VTKm. Make sure that SENSEICOnfig includes the exported libnrary so that external projects can link to sensei built with VTKm features.
see for example `CM...In `CMake/vtkm.cmake` define an interface library that encapsulates our usage of VTKm. Make sure that SENSEICOnfig includes the exported libnrary so that external projects can link to sensei built with VTKm features.
see for example `CMake/vtk.cmake`, `CMake/mpi.cmake`, `CMake/adios.cmake` for examples of how this is done.https://gitlab.kitware.com/sensei/sensei/-/issues/29handle LINK_ONLY in sensei config2018-09-18T12:49:13-04:00Burlen Loringhandle LINK_ONLY in sensei configmany entries such this are showing up in the static catalyst versions
`:$<LINK_ONLY:vtkPythonInterpreter>`
I think these can be removedmany entries such this are showing up in the static catalyst versions
`:$<LINK_ONLY:vtkPythonInterpreter>`
I think these can be removedhttps://gitlab.kitware.com/sensei/sensei/-/issues/31using output_dir attribute in the VTKPostHoc writer breaks visit and pvd files2018-10-28T17:08:22-04:00Burlen Loringusing output_dir attribute in the VTKPostHoc writer breaks visit and pvd filesfix the pvd/visit file generationfix the pvd/visit file generation