Book Image

Generative Adversarial Networks Cookbook

By : Josh Kalin
Book Image

Generative Adversarial Networks Cookbook

By: Josh Kalin

Overview of this book

Developing Generative Adversarial Networks (GANs) is a complex task, and it is often hard to find code that is easy to understand. This book leads you through eight different examples of modern GAN implementations, including CycleGAN, simGAN, DCGAN, and 2D image to 3D model generation. Each chapter contains useful recipes to build on a common architecture in Python, TensorFlow and Keras to explore increasingly difficult GAN architectures in an easy-to-read format. The book starts by covering the different types of GAN architecture to help you understand how the model works. This book also contains intuitive recipes to help you work with use cases involving DCGAN, Pix2Pix, and so on. To understand these complex applications, you will take different real-world data sets and put them to use. By the end of this book, you will be equipped to deal with the challenges and issues that you may face while working with GAN models, thanks to easy-to-follow code solutions that you can implement right away.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
About Packt
Dedication
Contributors
Preface
Dedication2
Index

Tools – do I need any unique tools?


This section will show you how to create the underlying infrastructure that allows you to use Large-Scale Scene Understanding (LSUN) data. This will make sure that you have created the right Docker container and that all of your folders are structured in the correct format. Here, we'll also begin the process of downloading the LSUN dataset for the DCGAN recipe.

 

 

Getting ready

This section will lay the groundwork for future coding sections. First, create the following folders for file storage:

DCGAN
├── data
│   └── README.md
├── docker
│   ├── build.sh
│   ├── clean.sh
│   └── Dockerfile
├── README.md
├── scripts

Make sure that you create a DCGAN directory in the $HOME directory in your Ubuntu installation. Many of the scripts we will develop are going to rely on this installation location when mapping volumes using Docker's commands. However, if you are comfortable with changing the mapped volumes in the run command, you won't need to install it in $HOME...