# Up-to-date guide for Catalyst?
**URL:** https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337
**Category:** In Situ Support
**Tags:** catalyst
**Created:** [September 16, 2022, 10:23am UTC](https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337 "2022-09-16T10:23:26Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@CsatiZoltan](https://discourse.paraview.org/u/CsatiZoltan)
#### Post date: [September 16, 2022, 10:23am UTC](https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337/1 "2022-09-16T10:23:26Z")
As suggested by [Nicolas Vuaille](https://discourse.paraview.org/t/coprocessing-plugin-not-available/2587/5), I open a new thread for this question.
Several changes were made to Catalyst, including
- exporting the pipeline as a Python script is [no longer available from a plugin](https://discourse.paraview.org/t/coprocessingplugin-cannot-be-found-in-the-list-of-paraview-plug-ins/60/2), but from _File → Save Catalyst State_
- the [adaptor also changed](https://discourse.paraview.org/t/how-to-try-out-catalyst2/9008) significantly
These changes are documented e.g. [here](https://kitware.github.io/paraview-docs/latest/cxx/CatalystPythonScriptsV2.html), but an updated [user’s guide](https://www.paraview.org/files/catalyst/docs/ParaViewCatalystUsersGuide_v2.pdf) is still missing if I am not mistaken. On the other hand, according to
> [@CoProcessing plugin not available?](https://discourse.paraview.org/t/coprocessing-plugin-not-available/2587/2):
>
> you can safely use the nightly version of the Catalyst Guide.
an updated guide is supposed to exist. Where can I find it?
---
### Author:  [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [September 16, 2022, 12:46pm UTC](https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337/2 "2022-09-16T12:46:45Z")
I’ve been thinking a little about this as well this past week. There’s the generic [Catalyst API](https://catalyst-in-situ.readthedocs.io/en/latest/index.html) which is also implemented in ParaView Catalyst. So I think the Catalyst API and this documentation, in its generic form seems like it is fairly informative. Inside of ParaView this is being called the ParaView Catalyst2 implementation, as opposed to the legacy ParaView Catalyst implementation. To be a bit clearer on this, ParaView Catalyst2 use the generic Catalyst API while ParaView legacy Catalyst uses the internal ParaView Catalyst API that predates the generic Catalyst API.
What’s lacking is an up-to-date ParaView Catalyst guide, specifically with the ParaView Catalyst2 details.
My reply is trying to be as specific as possible here because Catalyst in some ways is becoming a vague concept with recent developments and just saying Catalyst will likely confuse what is being discussed.
---
### Author:  [@CsatiZoltan](https://discourse.paraview.org/u/CsatiZoltan)
#### Post date: [September 16, 2022, 12:54pm UTC](https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337/3 "2022-09-16T12:54:12Z")
Thank you. I have already met the linked Catalyst API, but I did not see how it fits into the global picture. As you mentioned, the name “Catalyst” is vague, maybe writing a glossary would be useful so that newcomers can see which guide corresponds to what.
---
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [September 19, 2022, 1:16pm UTC](https://discourse.paraview.org/t/up-to-date-guide-for-catalyst/10337/4 "2022-09-19T13:16:44Z")
> [@CoProcessing plugin not available?](https://discourse.paraview.org/t/coprocessing-plugin-not-available/2587/2):
>
> On the other hand, according to
>
> > [@CoProcessing plugin not available?](https://discourse.paraview.org/t/coprocessing-plugin-not-available/2587/2):
> >
> > you can safely use the nightly version of the Catalyst Guide.
>
> an updated guide is supposed to exist. Where can I find it?
My initial comment was about older versions of ParaView, 3 years ago. It mentions a guide about the legacy catalyst. This guide was sadly not upgraded for the newer Catalyst2 usage, and it is indeed a lack of documentation …