Kenneth Moreland 90c7e77075 Initialize DIY in vtkm::cont::Initialize ... This has the side effect of initialing MPI_Init (and will also call MPI_Finalize at program exit). However, if the calling code has already called MPI_Init, then nothing will happen. Thus, if the calling code wants to manage MPI_Init/Finalize, it can do so as long as it does before it initializes VTK-m.		2022-10-07 14:54:33 -06:00
..
1.3	docs: update gitlab links to include /-/ component	2020-05-26 14:48:49 -04:00
1.4	Add release notes for v1.4.0	2019-06-26 12:13:47 -04:00
1.5	Add release notes for v1.5.0	2019-10-15 13:40:46 -04:00
1.5.1	Add release notes for v1.5.1	2020-03-13 12:55:43 -04:00
1.6	1.6.0-rc1 is our 7th official release of VTK-m.	2021-04-06 18:28:53 -04:00
1.7	Add release notes for 1.7.0-rc1	2021-10-21 13:08:40 -04:00
1.7.1	Add release notes for 1.7.1	2022-01-28 18:16:04 -05:00
1.8	Update release notes for 1.8.0	2022-06-16 13:18:02 -04:00
1.9	release: 1.9.0-rc1 release notes	2022-09-27 16:02:37 -04:00
flying-edges-z-boundary-fix.md	Fix Flying Edges z-boundary condition with non-square input	2022-09-29 06:25:12 -06:00
mpi-init.md	Initialize DIY in vtkm::cont::Initialize	2022-10-07 14:54:33 -06:00