sensei issueshttps://gitlab.kitware.com/sensei/sensei/-/issues2021-06-08T10:32:20-04:00https://gitlab.kitware.com/sensei/sensei/-/issues/57VTKPosthocIO and PVD files (Unstructured Grid)2021-06-08T10:32:20-04:00Victor MateevitsiVTKPosthocIO and PVD files (Unstructured Grid)I have been working on instrumenting Nek5000 with SENSEI and have stumbled on an issue.
The data is Unstructured Grid, so in my GetMeshMetadata function, I have the following:
```
metadata->MeshType = VTK_UNSTRUCTURED_GRID;
meta...I have been working on instrumenting Nek5000 with SENSEI and have stumbled on an issue.
The data is Unstructured Grid, so in my GetMeshMetadata function, I have the following:
```
metadata->MeshType = VTK_UNSTRUCTURED_GRID;
metadata->CoordinateType = VTK_DOUBLE;
metadata->NumArrays = 2;
metadata->ArrayName = {"pressure", "velocity"};
metadata->ArrayCentering = {vtkDataObject::CELL, vtkDataObject::CELL};
metadata->ArrayComponents = {1, 3};
metadata->ArrayType = {VTK_DOUBLE, VTK_DOUBLE};
metadata->StaticMesh = 0;
````
If I use catalyst, the data gets rendered correctly using SENSEI.
However, if I switch to PosthocIO analysis, while I can see the *.vtu files being generated (and I can open them individually), the PVD file is as follows:
```
<?xml version="1.0"?>
<VTKFile type="Collection" version="0.1" byte_order="LittleEndian" compressor="">
<Collection>
</Collection>
</VTKFile>
```
Debugging to see why that happens, we can see in VTKPosthocIO.cxx (line 499) the following:
```
pvdFile << "<?xml version=\"1.0\"?>" << endl
<< "<VTKFile type=\"Collection\" version=\"0.1\""
" byte_order=\"LittleEndian\" compressor=\"\">" << endl
<< "<Collection>" << endl;
for (long i = 0; i < nSteps; ++i)
{
for (long j = 0, k = 0; j < mmd[i]->NumBlocks; ++j)
{
if (mmd[i]->BlockNumCells[j] > 0)
{
std::string fileName =
getBlockFileName("./", meshName, mmd[i]->BlockIds[j], i, blockExt);
pvdFile << "<DataSet timestep=\"" << times[i]
<< "\" group=\"\" part=\"" << k << "\" file=\"" << fileName
<< "\"/>" << endl;
++k;
}
}
}
```
The problem here is the `mmd[i]->NumBlocks` (which is zero), because there are no Blocks. Is this a bug or is it expected? Do I have to convert the Nek5000 data to Multiblock?
Thanks!
PS: For future reference, for similar issues are we using the issue tracker or discourse?https://gitlab.kitware.com/sensei/sensei/-/issues/54Missing possibility to set some metadata in ProgrammableDataAdaptor from python2020-11-27T08:25:18-05:00Christian WitzlerMissing possibility to set some metadata in ProgrammableDataAdaptor from pythonI could not find a way to set BlockExtents (https://github.com/Kitware/sensei/blob/master/sensei/MeshMetadata.h#L182) from python. On the C side of things it is a 'std::vector<std::array<int,6>>', but creating and using https://github.co...I could not find a way to set BlockExtents (https://github.com/Kitware/sensei/blob/master/sensei/MeshMetadata.h#L182) from python. On the C side of things it is a 'std::vector<std::array<int,6>>', but creating and using https://github.com/Kitware/sensei/blob/master/python/senseiSTL.i#L8 in a list doesn't help.
Running:
```
>>> import sensei
>>> md = sensei.MeshMetadata.New()
>>> md.BlockExtents
```
Shows the type of BlockExtents is:
`<Swig Object of type 'std::vector< std::array< int,6 >,std::allocator< std::array< int,6 > > > *' at 0x2aaaf286cb10>`
Another way to set this Metadata would be using https://github.com/Kitware/sensei/blob/master/sensei/VTKUtils.h, but that can not be reached from python either?
What would be the correct way to set this metadata from python?https://gitlab.kitware.com/sensei/sensei/-/issues/53Sensei with ParaView 5.8.x2021-02-01T19:10:54-05:00Christian WitzlerSensei with ParaView 5.8.xWhen trying to build Sensei with ParaView 5.8 the dependency to the component `ServerManagerRendering` is not found.
```
CMake Warning at CMake/catalyst.cmake:22 (find_package):
Found package configuration file:
/opt/paraview/lib...When trying to build Sensei with ParaView 5.8 the dependency to the component `ServerManagerRendering` is not found.
```
CMake Warning at CMake/catalyst.cmake:22 (find_package):
Found package configuration file:
/opt/paraview/lib64/cmake/paraview-5.8/paraview-config.cmake
but it set ParaView_FOUND to FALSE so package "ParaView" is considered to
be NOT FOUND. Reason given by package:
Could not find the ParaView package with the following required components:
ServerManagerRendering.
```
In ParaView 5.7 it is build here: https://github.com/Kitware/ParaView/blob/v5.7.0/ParaViewCore/ServerManager/Rendering/vtk.module
In ParaView 5.8 I can only find this: https://github.com/Kitware/ParaView/blob/v5.8.0/Remoting/ServerManager/vtk.module
Therefore this library seems to miss in 5.8. Is ParaView 5.8 supported?https://gitlab.kitware.com/sensei/sensei/-/issues/52libsenseiCore.so is missing libvtkIOXML as dependency2021-02-01T19:13:59-05:00Jens GoebbertlibsenseiCore.so is missing libvtkIOXML as dependencyWhen building SENSEI 3.2.0 I have to add
`-DCMAKE_SHARED_LINKER_FLAGS="-L$EBROOTVTK/lib64/ -lvtkIOXML-9.0"`
to ensure the symbol
`_ZN28vtkXMLUnstructuredGridWriter3NewEv`
can be resolved.
Without this addition the library `lib...When building SENSEI 3.2.0 I have to add
`-DCMAKE_SHARED_LINKER_FLAGS="-L$EBROOTVTK/lib64/ -lvtkIOXML-9.0"`
to ensure the symbol
`_ZN28vtkXMLUnstructuredGridWriter3NewEv`
can be resolved.
Without this addition the library `libsenseiCore.so` is missing the library dependency `libvtkIOXML`.https://gitlab.kitware.com/sensei/sensei/-/issues/48build w/ hdf5 enabled ubuntu 18.042019-11-07T12:07:13-05:00Burlen Loringbuild w/ hdf5 enabled ubuntu 18.04error message follows, seems that it is failing because it can't find HDF5 HL. I have all of the libhdf5 dev packages installed. I don't think we need to use HDF5 HL. Could it be that we simply need to exclude it? Also I see that it is f...error message follows, seems that it is failing because it can't find HDF5 HL. I have all of the libhdf5 dev packages installed. I don't think we need to use HDF5 HL. Could it be that we simply need to exclude it? Also I see that it is finding the serial version of HDF5 (needed by VTK). Both serial and parallel HDF5 are installed, I think that we need to handle this better, because we can't reasonably require that a user not have serial hdf5 installed if they need it.
```
-- HDF5: Using hdf5 compiler wrapper to determine C configuration
-- Found HDF5: /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libsz.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so (found version "1.10.0.1") found components: C
CMake Error at CMake/hdf5.cmake:5 (message):
Failed to locate parallel hdf5 installation
Call Stack (most recent call first):
CMakeLists.txt:15 (include)
CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find HDF5 (missing: HL) (found version "1.10.0.1")
Call Stack (most recent call first):
/usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
/home/in-situ-user/sensei_insitu/software/paraview/5.7.1/lib/cmake/paraview-5.7/vtk/patches/99/FindHDF5.cmake:920 (find_package_handle_standard_args)
/home/in-situ-user/sensei_insitu/software/paraview/5.7.1/lib/cmake/paraview-5.7/vtk/VTK-vtk-module-find-packages.cmake:125 (find_package)
/home/in-situ-user/sensei_insitu/software/paraview/5.7.1/lib/cmake/paraview-5.7/vtk/vtk-config.cmake:115 (include)
/home/in-situ-user/sensei_insitu/software/paraview/5.7.1/lib/cmake/paraview-5.7/paraview-config.cmake:41 (find_package)
CMake/catalyst.cmake:10 (find_package)
CMakeLists.txt:18 (include)
-- Configuring incomplete, errors occurred!
See also "/home/in-situ-user/sensei_insitu/software/sensei/builds/3.0.0-catalyst-shared/CMakeFiles/CMakeOutput.log".
See also "/home/in-situ-user/sensei_insitu/software/sensei/builds/3.0.0-catalyst-shared/CMakeFiles/CMakeError.log".
```Junmin GuJunmin Guhttps://gitlab.kitware.com/sensei/sensei/-/issues/45Ascent make runs with AMReX2021-02-01T19:13:44-05:00Burlen LoringAscent make runs with AMReXAs a validation of the Ascent back end make some runs on cori.
repeat the runs we did with IAMR Rayleigh-Taylor 2048 cores. Use the same camera settings and color tables. Configs found below.
## IAMR input deck
[inputs.3d.rt_2048](/up...As a validation of the Ascent back end make some runs on cori.
repeat the runs we did with IAMR Rayleigh-Taylor 2048 cores. Use the same camera settings and color tables. Configs found below.
## IAMR input deck
[inputs.3d.rt_2048](/uploads/c37ef2e3efe887223dde698547a93bc7/inputs.3d.rt_2048)
## VisIt Libsim configs
[visit_rt_contour.session](/uploads/8e646fbfbca933ebe7ff000f81a93000/visit_rt_contour.session)
[rt_contour.xml](/uploads/8e6d4e1a8b1aec04f74d76a73868a754/rt_contour.xml)
![rt_contour_00500](/uploads/c7a97f8a27bdf54cb17cea1afb9b460a/rt_contour_00500.png)DavidDavidhttps://gitlab.kitware.com/sensei/sensei/-/issues/44FLEXPATH cant send more than 1 block2021-02-01T19:15:17-05:00Burlen LoringFLEXPATH cant send more than 1 blockin many cases there are more blocks than ranks. ex AMR and Estelle's use case. she has 1 sender rank and wants to use many receiver ranks. Greg said that this is a "feature" of flexpath where they need to use a vector instead of a pointe...in many cases there are more blocks than ranks. ex AMR and Estelle's use case. she has 1 sender rank and wants to use many receiver ranks. Greg said that this is a "feature" of flexpath where they need to use a vector instead of a pointer. it may be an easy fix, and will affect adios 2 as well.
below we have 4 blocks with 1 sender and 2 receivers. this is from our regression tests, and can be used to reproduce.
**`ERROR: set_format: The Flexpath transport does not allow multiple writes using the same name in a single group, variable data_object_0/data_array_0/data is disallowed`**
```
$ testPartitionersDriver.sh "/usr/local/bin/mpiexec" "-n" "1" "2" "/Users/estelledirand/Software/Sensei/src/sensei/sensei/testing" "adios1_flexpath" "2" "2" "3" 1
Testing adios1_flexpath M=1 N=2 part_M=block part_N=block ... file=test.bp
rm -f $file ${file}_writer_info.txt
${mpiexec} ${npflag} ${nproc_write} python ${srcdir}/testPartitionersWrite.py "${srcdir}/${writer_analysis_xml}" ${nits} ${nblock_x} ${nblock_y} 16 16 -6.2832 6.2832 -6.2832 6.2832 0 6.2832
writePid=$!
[[ "${sync_mode}" == "0" ]]
[[ "${sync_mode}" == "1" ]]
echo "waiting for writer to start ${delay}"
waiting for writer to start 1
[[ -n True ]]
[[ -e "${file}_writer_info.txt" ]]
[[ ${maxDelay} -le 0 ]]
sleep ${delay}s
let maxDelay=${maxDelay}-${delay}
[[ -n True ]]
[[ -e "${file}_writer_info.txt" ]]
[[ ${maxDelay} -le 0 ]]
sleep ${delay}s
STATUS[0] : running nIts=3 with mesh parametersnblks=[2, 2] nx=[16, 16] dom=[-6.2832, 6.2832, -6.2832, 6.2832] dx=[0.3927, 0.3927] theta=[0.0, 6.2832] dt=3.1416
STATUS: [0][/Users/estelledirand/Software/Sensei/src/sensei/sensei/ConfigurableAnalysis.cxx:348][v2.1.1-103-gc44aede]
STATUS: Configured ADIOSAnalysisAdaptor "test.bp" method FLEXPATH
WARNING: [0][/Users/estelledirand/Software/Sensei/src/sensei/sensei/ADIOS1AnalysisAdaptor.cxx:96][v2.1.1-103-gc44aede]
WARNING: No subset specified. Writing all available data
let maxDelay=${maxDelay}-${delay}
[[ -n True ]]
[[ -e "${file}_writer_info.txt" ]]
break
${mpiexec} ${npflag} ${nproc_read} python ${srcdir}/testPartitionersRead.py "${srcdir}/${reader_analysis_xml}" "${srcdir}/${reader_transport_xml}"
STATUS[0] : initializing the transport layer
STATUS: [0][/Users/estelledirand/Software/Sensei/src/sensei/sensei/Partitioner.h:39][v2.1.1-103-gc44aede]
STATUS: Configured BlockPartitioner
STATUS: [0][/Users/estelledirand/Software/Sensei/src/sensei/sensei/ConfigurableInTransitDataAdaptor.cxx:143][v2.1.1-103-gc44aede]
STATUS: Configured "ADIOS1DataAdaptor
ERROR: set_format: The Flexpath transport does not allow multiple writes using the same name in a single group, variable data_object_0/data_array_0/data is disallowed
[MacEstelleD-J0539093:24003] *** Process received signal ***
[MacEstelleD-J0539093:24003] Signal: Segmentation fault: 11 (11)
[MacEstelleD-J0539093:24003] Signal code: Address not mapped (1)
[MacEstelleD-J0539093:24003] Failing at address: 0x0
```https://gitlab.kitware.com/sensei/sensei/-/issues/43disable adios1 tests that depend on pv if pv support isn't built2021-02-01T19:15:03-05:00Burlen Loringdisable adios1 tests that depend on pv if pv support isn't builtBurlen LoringBurlen Loringhttps://gitlab.kitware.com/sensei/sensei/-/issues/42update the ascent branch to sensei 3.02021-02-01T19:14:20-05:00Burlen Loringupdate the ascent branch to sensei 3.0sensei 3.0 has a new metadata model and major api changes. ascent branch is still using the 2.0 api and needs to be updated. The target branch for the merge should be `sensei_3_development`sensei 3.0 has a new metadata model and major api changes. ascent branch is still using the 2.0 api and needs to be updated. The target branch for the merge should be `sensei_3_development`DavidDavidhttps://gitlab.kitware.com/sensei/sensei/-/issues/36make sure stuff doesn't use MPI after finalize2021-02-01T19:14:47-05:00Burlen Loringmake sure stuff doesn't use MPI after finalizeuse new end point. Test with VTKPostHoc I/Ouse new end point. Test with VTKPostHoc I/Ohttps://gitlab.kitware.com/sensei/sensei/-/issues/35Improve the web site random image feature2021-02-01T19:18:55-05:00Burlen LoringImprove the web site random image feature@patrick\-oleary @ewbethel @dcthomp
The web site random image currently does a true random walk through the image collection. This is problematic because many duplicate images are displayed. For example the first image may appear multi...@patrick\-oleary @ewbethel @dcthomp
The web site random image currently does a true random walk through the image collection. This is problematic because many duplicate images are displayed. For example the first image may appear multiple times in the first few transitions.
A simple fix would be to apply an a fixed/pre-determined cyclic order on the images and pick the starting point at random. from the randomly chosen starting point, the predetermined cyclic order would be followed. this would maximize time between repeated images, and give all the images fair air time.https://gitlab.kitware.com/sensei/sensei/-/issues/34Add images to the web site2019-04-23T13:46:09-04:00Burlen LoringAdd images to the web site@dcthomp @patrick\-oleary @ewbethel
David Can you please make sure the following images get put on the web site. We had spoke on 10/26 about this, but with all the chaos around SC I think it fell off our radars. I'm moving our email co...@dcthomp @patrick\-oleary @ewbethel
David Can you please make sure the following images get put on the web site. We had spoke on 10/26 about this, but with all the chaos around SC I think it fell off our radars. I'm moving our email conversation to the issue tracker here so that we do not forget.
Thank you for your help
Burlen
In situ rendering of a Rayleigh-Taylor instability computed with the AMReX IAM compressible Navier-Stokes simulation code with 4 levels of refinement using 2048 cores on NERSC Cori.
![rt_contour_00500](/uploads/208fbddd90277d18c3f13947f9215ba5/rt_contour_00500.png)
![image_000500](/uploads/e37e1aae1f5ac8e5209de314e25d7c35/image_000500.png)
In situ rendering of relativistic Laser Plasma Accelerator(LPA) simulation with WarpX on NERSC Cori.
![beam_j_pin_00800](/uploads/62ecd9d16879c2068720aff678e91e95/beam_j_pin_00800.png)
![beam_j_catalyst_00800](/uploads/e0da059d16a89a897dd553c28ca42703/beam_j_catalyst_00800.png)David ThompsonDavid Thompsonhttps://gitlab.kitware.com/sensei/sensei/-/issues/33Catalyst Warning2021-02-01T19:15:38-05:00Burlen LoringCatalyst Warning@patrick\-oleary @ewbethel
Hi Patrick,
With the update to ParaView 5.6.0 I am seeing warnings every time Catalyst executes. We are passing the correct time step, ParaView warns that it only sees the previous value. However, the correc...@patrick\-oleary @ewbethel
Hi Patrick,
With the update to ParaView 5.6.0 I am seeing warnings every time Catalyst executes. We are passing the correct time step, ParaView warns that it only sees the previous value. However, the correct time value(the one we pass) is used by ParaView during the execution so that this is more of an annoyance. However, the AMReX folks use the output put streams for diagnostic and profiling data so this is a real problem for them.
It would be a big help if Kitware could help track down the problem. Is that something you can do?
```bash
STEP 22 starts ...
STEP 22 ends. TIME = 9.556420749e-15 DT = 4.343827613e-16
Walltime = 145.8195755 s; This step = 0.203643828 s; Avg. per step = 6.628162524 s
SENSEI Begin update...
Warning: In /work/SENSEI/ParaView/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 95
vtkPVTrivialProducer (0x1c35b100): Requesting time 9.12204e-15 but only 9.55642e-15 is available
SENSEI update complete (6.599138309 sec)
```https://gitlab.kitware.com/sensei/sensei/-/issues/32VTKPosthocIO create output dir if it does not exist2018-12-17T13:43:03-05:00Burlen LoringVTKPosthocIO create output dir if it does not existthis can be done in the initialize methodthis can be done in the initialize methodhttps://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/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/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/22segv in parallel3d with histogram2021-02-01T19:16:12-05:00Burlen Loringsegv in parallel3d with histogram```bash
$gdb --args ./bin/3D_Grid -g 1x1x1 -l 1x1x1 -f ../sensei_2/configs/3dgrid.xml
Global Dimensions 1X1X1: Local Dimensions 1X1X1
Total Blocks are 1X1X1
STATUS: [0][/home/sensei/sc17/software/sensei/builds/sensei_2/sensei/Configur...```bash
$gdb --args ./bin/3D_Grid -g 1x1x1 -l 1x1x1 -f ../sensei_2/configs/3dgrid.xml
Global Dimensions 1X1X1: Local Dimensions 1X1X1
Total Blocks are 1X1X1
STATUS: [0][/home/sensei/sc17/software/sensei/builds/sensei_2/sensei/ConfigurableAnalysis.cxx:198][v1.1.0-57-ga2bf4db]
STATUS: Configured histogram with 10 celldata array pressure on mesh mesh
STATUS: [0][/home/sensei/sc17/software/sensei/builds/sensei_2/sensei/ConfigurableAnalysis.cxx:198][v1.1.0-57-ga2bf4db]
STATUS: Configured histogram with 10 celldata array density on mesh mesh
STATUS: [0][/home/sensei/sc17/software/sensei/builds/sensei_2/sensei/ConfigurableAnalysis.cxx:198][v1.1.0-57-ga2bf4db]
STATUS: Configured histogram with 10 celldata array temperature on mesh mesh
Program received signal SIGSEGV, Segmentation fault.
0x000000000053c118 in sensei::VTKHistogram::Internals::operator()<double> (this=0xaa4340, array=...)
at /home/sensei/sc17/software/sensei/builds/sensei_2/sensei/VTKHistogram.cxx:115
115 ++this->Histogram[bin];
Missing separate debuginfos, use: dnf debuginfo-install libuuid-2.30-1.fc26.x86_64 python2-libs-2.7.13-11.fc26.x86_64
(gdb) where
#0 0x000000000053c118 in sensei::VTKHistogram::Internals::operator()<double> (this=0xaa4340, array=...)
at /home/sensei/sc17/software/sensei/builds/sensei_2/sensei/VTKHistogram.cxx:115
#1 0x000000000053a4ed in vtkDataArrayDispatcher<sensei::VTKHistogram::Internals, void>::Go (this=0x7fffffffccc0, lhs=0xaa3c10)
at /home/sensei/sc17/software/paraview/builds/ParaView/VTK/Common/DataModel/vtkDataArrayDispatcher.h:170
#2 0x00000000005393bd in sensei::VTKHistogram::Compute (this=0xaa3440, da=0xaa3c10, ghostArray=0x0)
at /home/sensei/sc17/software/sensei/builds/sensei_2/sensei/VTKHistogram.cxx:218
#3 0x0000000000538e70 in sensei::Histogram::Execute (this=0xaa2cb0, data=0xaa3020)
at /home/sensei/sc17/software/sensei/builds/sensei_2/sensei/Histogram.cxx:197
#4 0x000000000050145b in sensei::ConfigurableAnalysis::Execute (this=0xaa2c80, data=0xaa3020)
at /home/sensei/sc17/software/sensei/builds/sensei_2/sensei/ConfigurableAnalysis.cxx:741
#5 0x00000000004f8c62 in bridge_update (tstep=0, time=0) at /home/sensei/sc17/software/sensei/builds/sensei_2/miniapps/parallel3d/Bridge.cxx:59
#6 0x00000000004f37fa in main (argc=<optimized out>, argv=<optimized out>)
at /home/sensei/sc17/software/sensei/builds/sensei_2/miniapps/parallel3d/parallel_3D.c:162
(gdb) p bin
$12 = -2147483648
```https://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/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!