CADET not found (new thread September 2025)

CADET Troubleshooting
2

Hi AN_IA,

thanks for opening a new thread and for providing the detailed error messages.

As you probably already suspect, this is not a CADET issue but rather a matter of how you set up Conda environments, VS Code settings, and PATH variables. In a correctly activated environment with the right PATH, CADET autodetect works reliably.

If the problem persists, you are welcome to join our office hour, the next one is today at 3 pm CET.

Nonetheles, I am happy to share my ideas of what the issue might be and give you some pointers to try next:

  1. Check terminal activation and conda integration in VS Code

    conda : Die Benennung “conda” wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines
ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern
enthalten), und wiederholen Sie den Vorgang.
In Zeile:1 Zeichen:1

    Your log shows that conda was not found in the VS Code terminal. This means the environment was probably never activated. Please check that you can access and activate Conda environments from within VS Code.

  2. Select the correct environment in VS Code
    Use Ctrl+Shift+P → Python: Select Interpreter and choose your cadet_workshop environment. Otherwise VS Code may fall back to its default Python without CADET. If you cannot see the environment there, VS Code is not set up correctly to detect your Conda environments.

  3. Verify the environment in the terminal

    conda activate cadet_workshop
where python
where cadet-cli
cadet-cli --version

    All should point into your cadet_workshop environment.

When you made sure of all that, run .py files only from an activated environment with

conda activate cadet_workshop
python your_script.py

I suspect that Notebooks sometimes work because VS Code automatically handles Kernel activation, while .py scripts fail if you run them without activating the environment. Ensuring both the interpreter and the terminal use the same Conda environment should fix this.

Hope that helps!

All the best,
Hannah

1 Like