# Catalyst2 and ascent
**URL:** https://discourse.paraview.org/t/catalyst2-and-ascent/13223
**Category:** In Situ Support
**Tags:** catalyst
**Created:** [November 9, 2023, 10:22pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223 "2023-11-09T22:22:15Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 9, 2023, 10:22pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/1 "2023-11-09T22:22:15Z")
Hello
Is there an example of catayst2 working with an ascent backend?
---
### Author:  [@danlipsa](https://discourse.paraview.org/u/danlipsa)
#### Post date: [November 10, 2023, 1:24pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/2 "2023-11-10T13:24:28Z")
Are you asking if Ascent Insitu will support the catalyst2 API?
Ascent is a different project than ParaView, you may want to ask this on their discussion board.
Somewhat orthogonal to your question, we are working to build a catalyst2 backend inside paraview that responds to ascent actions.
---
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 10, 2023, 2:57pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/3 "2023-11-10T14:57:28Z")
Hi Dan
In Catalyst 2, there is "node[“catalyst\_load/implementation”] = “xxx”. Up to now, I’ve been using paraview for xxx. I’m wondering if “ascent” is now supported?
I heard that there was some work going on to support that and I was wondering what the status is and where I can get more information.
---
### Author:  [@danlipsa](https://discourse.paraview.org/u/danlipsa)
#### Post date: [November 10, 2023, 7:14pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/4 "2023-11-10T19:14:11Z")
Hi Pascal,
That was the first part of my answer. You should check that with Ascent developers.Seems this is where you could ask this question:
[https://github.com/Alpine-DAV/ascent/discussions](https://github.com/Alpine-DAV/ascent/discussions)
Dan
---
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 13, 2023, 4:52pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/5 "2023-11-13T16:52:42Z")
That sounds good. I’ll check there and come back here if there are issues.
---
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 15, 2023, 4:37pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/6 "2023-11-15T16:37:47Z")
I talked to Cyrus and found examples at: [https://github.com/Alpine-DAV/ascent/tree/v0.9.2/src/examples/ascent-catalyst-mpi](https://github.com/Alpine-DAV/ascent/tree/v0.9.2/src/examples/ascent-catalyst-mpi)
---
### Author:  [@danlipsa](https://discourse.paraview.org/u/danlipsa)
#### Post date: [November 15, 2023, 5:58pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/7 "2023-11-15T17:58:59Z")
Great. Thanks for sharing this. Good to know Ascent is providing a catalyst2 interface.
---
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 15, 2023, 6:19pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/8 "2023-11-15T18:19:19Z")
I am using the spack build of libcatalyst; `libcatalyst@2.0.0-rc3`, and it has the following libraries:
`libcatalyst-paraview.so libcatalyst-stub.so libcatalyst-vtk.so`
However, ascent is looking for` libcatalyst-ascent.so`.
I tried to build libcatalyst from [https://gitlab.kitware.com/paraview/catalyst](https://gitlab.kitware.com/paraview/catalyst) and that gave me:
`libcatalyst-double.so libcatalyst-external_conduit.so libcatalyst-internal_conduit.so libcatalyst-stub.so` in `install/lib64/catalyst`
How do I get ` libcatalyst-ascent.so`?
---
### Author:  [@danlipsa](https://discourse.paraview.org/u/danlipsa)
#### Post date: [November 15, 2023, 6:51pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/9 "2023-11-15T18:51:36Z")
While libcatalyst provides the API, the actual implementation would be provided by Ascent. So look inside an Ascent build or install dir.
---
### Author:  [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [November 20, 2023, 5:31pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/10 "2023-11-20T17:31:13Z")
Hey Pascal,
The way to generate `libcatalyst-ascent.so` is to build ascent with the necessary paths.
If you have installed Catalyst, then you’ll provide `-DCATALYST_DIR=` while building Ascent. Let me know if it works for you.
Unfortunately, I don’t think the Ascent built using Spack supports the backend yet. But, I’ll talk to Cyrus and get it added.
---
### Author:  [@zetwal](https://discourse.paraview.org/u/zetwal)
#### Post date: [November 20, 2023, 6:49pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/11 "2023-11-20T18:49:10Z")
Hi Abhishek
Having in Spack would be great!
For now, what I have done is run [build\_Ascent](https://ascent.readthedocs.io/en/latest/QuickStart.html#build-ascent-sh) and set build\_catalyst:=true in [https://github.com/Alpine-DAV/ascent/blob/develop/scripts/build\_ascent/build\_ascent.sh](https://github.com/Alpine-DAV/ascent/blob/develop/scripts/build_ascent/build_ascent.sh)
This builds libcatalyst and creates libcatalyst-ascent.so. This works with the catalyst example in ascent but I still need to try with one of my example programs.
---
### Author:  [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [November 20, 2023, 7:17pm UTC](https://discourse.paraview.org/t/catalyst2-and-ascent/13223/12 "2023-11-20T19:17:49Z")
Perfect! Please do let me know if you have any problems running Ascent scripts through Catalyst.
I’ll be publishing a blog post about it sometime this week and will be including more documentation.