# \[Catalyst V2\] Support for AMR data
**URL:** https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352
**Category:** In Situ Support
**Created:** [November 8, 2021, 5:46pm UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352 "2021-11-08T17:46:31Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [November 8, 2021, 5:46pm UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/1 "2021-11-08T17:46:31Z")
Hello, I have recently taken over maintaining and updating an old ParaView (V1) Catalyst implementation for a code that uses the Chombo libraries for [Berger-Oliger style] Adaptive Mesh Refinement ([Chombo - Software for Adaptive Solutions of Partial Differential Equations - Chombo Chombo](https://commons.lbl.gov/display/chombo/Chombo+-+Software+for+Adaptive+Solutions+of+Partial+Differential+Equations)). Since the data uses AMR, we used the corresponding VTK data structures (e.g. `vtkOverlappingAMR`).
I was looking at the new Catalyst (V2) API and I really like the supposed benefits of updating to use it. However, before I start porting our code to use it I thought it would be asking whether such datasets are supported. In particular, does the new ParaView Catalyst implementation supports AMR datasets via the Conduit Mesh protocol? Looking at the [Conduit documentation](https://llnl-conduit.readthedocs.io/en/latest/blueprint_mesh.html#examples), it seems it is possible to describe AMR data using [nesting sets](https://llnl-conduit.readthedocs.io/en/latest/blueprint_mesh.html#nesting-sets) but I wasn’t sure if the ParaView Catalyst code was able to handle this since I couldn’t see anything related to `nestsets` in the [ParaView Conduit VTK extension code](https://gitlab.kitware.com/paraview/paraview/-/tree/master/VTKExtensions/Conduit).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 10, 2021, 9:24am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/2 "2021-11-10T09:24:33Z")
@Francois_Mazen @nicolas.vuaille
---
### Author:  [@Francois\_Mazen](https://discourse.paraview.org/u/Francois_Mazen)
#### Post date: [November 24, 2021, 9:31am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/3 "2021-11-24T09:31:51Z")
Indeed, nesting sets and AMR are not currently supported by Catalyst V2. As a work around you may create many meshes for each level set. I agree this is not optimal.
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [November 24, 2021, 9:52am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/4 "2021-11-24T09:52:48Z")
Do you know if there is a plan to support this in the near future?
---
### Author:  [@Francois\_Mazen](https://discourse.paraview.org/u/Francois_Mazen)
#### Post date: [November 24, 2021, 10:06am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/5 "2021-11-24T10:06:03Z")
I’m not aware of such plan. @utkarsh.ayachit may have more information on Catalyst2 roadmap.
---
### Author:  [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [December 9, 2021, 4:03pm UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/6 "2021-12-09T16:03:24Z")
@coreylee - thoughts?
---
### Author:  [@coreylee](https://discourse.paraview.org/u/coreylee)
#### Post date: [April 11, 2022, 9:43pm UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/7 "2022-04-11T21:43:13Z")
The AMReX library has [conduit node support](https://github.com/AMReX-Codes/amrex/tree/development/Src/Extern/Conduit) (geared toward Ascent) which I used to create a Catalyst 2 compliant conduit node. It was fairly straightforward to do so, unfortunately I don’t have my example available, it’s in a closed repo. But you may glean some useful insight inspecting the AMReX implementation.
I know it’s not a perfect match, but that may give you a strong start!
As far as nesting sets and AMR, we don’t have an existing roadmap for support, but creating structured grids at each level isn’t a terrible approach.
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [April 12, 2022, 9:16am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/8 "2022-04-12T09:16:37Z")
Thanks for pointing out the conduit support in AMReX. I actually had found this a few months ago and was planning to use this as a guide for AMR with conduit before I abandoned this attempt and decided to just stick with the Catalyst v1 instrumentation.
Do you have a working Catalyst v2 insitu instrumentation with AMReX then? If so, how well does it work and how does it compare to a Catalyst v1 instrumentation in terms of its support for AMR?
---
### Author:  [@coreylee](https://discourse.paraview.org/u/coreylee)
#### Post date: [April 13, 2022, 4:57pm UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/9 "2022-04-13T16:57:15Z")
The Catalyst v2 instrumentation is in a science code based on AMReX (MFix-Exa), and given the existing conduit node support, the Catalyst v2 instrumentation was straightforward. However, it produces a partitioned dataset collection with structured grids for each level.
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [April 14, 2022, 9:08am UTC](https://discourse.paraview.org/t/catalyst-v2-support-for-amr-data/8352/10 "2022-04-14T09:08:43Z")
Thanks for the information. I don’t think it makes sense for me to migrate my Catalyst instrumentation but I hope proper support for AMR comes at some point.