Open megbedell opened 5 years ago
Here is an example of wobble working on Google colab.
Colab supports several external data sources, including Google Drive, which I've used here. Unfortunately that means that the hardcoded data path is expecting your Google Drive to possess the 600 MB HDF5 file in the same place, which requires users to intervene. Ideally I would modify this line to expect data on one of the other supported external locations such as a local file, or Google Cloud Storage.
Another hiccup: the optimizer failed and interrupted the kernel when it got to the optimization step. As a workaround, tturning on hardware acceleration in the Notebook settings
made the error message go away. It's a waste to turn on the GPU, and then not use it, but c'est la vie.
Otherwise everything works as expected. I would recommend adding a bit more explanatory material and maybe a few more plots of the results object, etc, but here is a demo that works on colaboratory, with the provisos above.
This might be a way of allowing users who are having TF issues on their personal computers to still use wobble (or at least give it a test run).