# Catalyst 2 API C++: Documentation and architecture

**URL:** https://discourse.paraview.org/t/catalyst-2-api-c-documentation-and-architecture/8991
**Category:** In Situ Support
**Tags:** catalyst
**Created:** [February 16, 2022, 10:28pm UTC](https://discourse.paraview.org/t/catalyst-2-api-c-documentation-and-architecture/8991 "2022-02-16T22:28:10Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![nicolas.vuaille](https://discourse.paraview.org/user_avatar/discourse.paraview.org/nicolas.vuaille/32/5873_2.png) [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [February 18, 2022, 10:46am UTC](https://discourse.paraview.org/t/catalyst-2-api-c-documentation-and-architecture/8991/9 "2022-02-18T10:46:54Z")

</div>

Also, I just created this tip based on our discussion. Feel free to add some feedback from your experience!

> [@How to try out Catalyst2](https://discourse.paraview.org/t/how-to-try-out-catalyst2/9008):
>
> Catalyst is an in-situ framework created as a part of ParaView a few years ago. With time and use, we saw the different drawbacks of our approach and then it was decided to create a new architecture, [Catalyst2](https://catalyst-in-situ.readthedocs.io/en/latest/index.html) With this new implementation, it is: easier to implement in your simulation (less knowledges required) easier to update from a version to another (less dependencies, binary compatibility) possible to activate Steering mode, where ParaView can modify simulation parameters at runtime A…

---

_[View the full topic](https://discourse.paraview.org/t/catalyst-2-api-c-documentation-and-architecture/8991)._
