You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from PIDGAN v0.2.0 most of the classes and corresponding methods provided by the algorithms and players modules have been revisited to be compatible with Keras 3. The major difference with respect to the previous PIDGAN versions is the "role" of the build() method for the GAN algorithms: the order with which one calls the custom model for the first time and compiles it becomes important. In particular, if one build the model before having compiled it results with making the model to ignore the metrics eventually passed during compilation procedure. To avoid the problem, it is crucial to move the first model calling after the compile() method.
Such difference should be highlighted in the tutorials available at mbarbetti/pidgan-notebooks and properly commented within the notebooks prepared in replacement of a dedicated package documentation.
The text was updated successfully, but these errors were encountered:
Starting from PIDGAN v0.2.0 most of the classes and corresponding methods provided by the
algorithms
andplayers
modules have been revisited to be compatible with Keras 3. The major difference with respect to the previous PIDGAN versions is the "role" of thebuild()
method for the GAN algorithms: the order with which one calls the custom model for the first time and compiles it becomes important. In particular, if one build the model before having compiled it results with making the model to ignore the metrics eventually passed during compilation procedure. To avoid the problem, it is crucial to move the first model calling after thecompile()
method.Such difference should be highlighted in the tutorials available at mbarbetti/pidgan-notebooks and properly commented within the notebooks prepared in replacement of a dedicated package documentation.
The text was updated successfully, but these errors were encountered: