Closed PTRRupprecht closed 3 years ago
Fixed. This issue could have occurred when a version of h5py newer or equally new as 3.0 is installed. Now we enforce the installation of h5py==2.10.0, see the readme:
"conda create -n Cascade python=3.6 tensorflow==2.1.0 keras==2.3.1 h5py==2.10.0 numpy scipy matplotlib seaborn ruamel.yaml spyder"
Starting with tensorflow 2.5, this bug is likely to be fixed, and we will then update also the requirements.
There is a compatibility problem with the h5py package. h5py version 3.0 is incompatible with tensorflow/keras <=2.3. This should be mentioned in the install instructions and be tested.