bayesflow breaks existing tensorflow installation about bayesflow

[vpratz]

Ahh, ok. Is the error absent when you install TF 2.15.0 without BayesFlow? Or is there a version change with the BF installation?

As this seems a usual problem according to this issue, we probably have to find which TF-related dependency changes and introduces the problem, though I don't know whether we can resolve this. Could you try the following?

• Create a conda environment, install TF 2.15.0 with CUDA and check whether the errors occur (if they do, it's TF version and not BF related)
• save the environment using conda list --explicit > env-pre-bf.txt
• Install BayesFlow, check whether the errors occur (expecting that they will)
• save the environment using conda list --explicit > env-post-bf.txt
• diff env-pre-bf.txt env-post-bf.txt

The resulting diff may tell us something about the changes BF introduces to the TensorFlow installation, which might give us a lead on what we need to fix

[vpratz]

Thanks for reaching out! If I remember correctly, I have encountered those warnings/errors, but could use the GPU anyway. In the last line it says it is able to create a GPU device. What is the output of tf.config.list_physical_devices('GPU'), does a GPU show up there or is it an empty list?

Regarding the 2.16 version of TensorFlow: We are currently working on adapting BF to Keras 3, which will also enable using the newest TensorFlow version. As this is a bigger change, it will need a bit more time, you can track the progress in the PR #159

[ali-akhavan89]

I completely understand it is challenging, but it would be great if the new BF release could support tensorflow-cpu 2.16 too.

[stefanradev93]

Absolutely. The new release will support all recent tensorflow, pytorch, and jax versions.

[jgman86]

Hey Valentin, yes It finds the gpu - but from my searches the errors at the beginning indicate, that the libs are not used then, which results in slower training. and its also suspicious, that those errors are absent, before the bayesflow installtion ! yes I already track the streamline-backend branch and can't wait to finally use torch as backend ;-)