Call for content

[ebenolson]

@benanne @dnouri @craffel @f0k @skaae (and anyone else of course)

With first release imminent it would be nice to have a bit more here... I know a couple of you have stuff written up already, but I bet everyone has some suitable code lying around.

If you have anything you're willing to contribute, please open a PR... don't worry if it's not perfect, I can take care of making sure everything functions with the latest Lasagne.

[JeffreyDF]

I have some notebook from the recent Kaggle Diabetic Retinopathy competition loading some trained model and using it to predict on some images, get some activations, etc. But it's quite quickly written and a little messy, so it probably needs to be cleaned up a bit. Nevertheless, something quite applied like that might be interesting for some people, maybe?

[JeffreyDF]

Forgot to mention: it's built on top of an older version of Lasagne as well. At commit cf1a23c21666fc0225a05d284134b255e3613335. Same as my own fork.

[skaae]

I can write a spatial transformer example, when the layer is added.

I would need to clean up the transformer code and create a repeat layer similar to http://keras.io/layers/core/#repeatvector (which I think is quite usefull for encoder/decoder stuff)

I have code for combining a GRU with a spatial transformer network.

The output looks like:

I could also just rewrite the spatial transformer network results. What do people prefer?

[skaae]

btw I also have a Penntree example. The setup is similar to http://arxiv.org/abs/1409.2329 except that i would have to use a GRU because of a minor technical issue: craffel/nntools@f4d15ba#diff-48f9f9d93ed00587a6c49197b4d6e64eL992

Penntree example
https://github.com/skaae/nntools/blob/pentree_recurrent/examples/pentree.py

[ebenolson]

@JeffreyDF your notebook looks really interesting, but it seems like it's dependent on a lot other stuff in your repo, might be a quite a bit of work to move it.

Perhaps we should add an "External Resources" section to README.md with description and links to repos like yours? We could also try including it as a submodule.

@skaae I think the pentree example would be great, and spatial transformer as well once Lasagne/Lasagne#355 is resolved.

[f0k]

Perhaps we should add an "External Resources" section to README.md with description and links to repos like yours?

We also still have this wiki page for links to things that don't fit into Recipes (or were not turned into Recipes yet): https://github.com/Lasagne/Lasagne/wiki/3rd-party-extensions-and-code
We could just as well link that from somewhere (e.g., README.md).

[JeffreyDF]

@ebenolson Yes, you're right. But in essence, the same functionality can be achieved with just a few extra lines of code in the notebook, I think. It's mostly the DataLoader which only reads images and resizes them (at least for testing) and the custom metrics, iirc. I can try to clean that up a bit (a little busy at the moment but should be able to find some time in the week). But I'm totally fine if you would rather have it as a more "complete" project to maybe point to (or not!). It makes some sense to do that. :-)

[ebenolson]

We also still have this wiki page for links to things that don't fit into Recipes (or were not turned into Recipes yet): https://github.com/Lasagne/Lasagne/wiki/3rd-party-extensions-and-code
We could just as well link that from somewhere.

Yeah, I feel like not many people know about/visit the wiki though, it would be nice if we could increase visibility (although Recipes is in a similar state at the moment).

[JeffreyDF]

Ah, yes, extra remark: for my notebook I'm using these 80-90MB model dumps to load first. So yes ... that probably makes it a little more unsuitable to have here! Forgot about that.

[ebenolson]

@ebenolson Yes, you're right. But in essence, the same functionality can be achieved with just a few extra lines of code in the notebook, I think. It's mostly the DataLoader which only reads images and resizes them (at least for testing) and the custom metrics, iirc. I can try to clean that up a bit (a little busy at the moment but should be able to find some time in the week). But I'm totally fine if you would rather have it as a more "complete" project to maybe point to (or not!). It makes some sense to do that. :-)

If you've got time to package it, I think that would be great, I'm happy with either though. I would like to keep large binary files out of the repo (data, snapshots), so if you decide to rework it it would be good if you could host those on Dropbox/S3 or something similar.

[ebenolson]

Ah, yes, extra remark: for my notebook I'm using these 80-90MB model dumps to load first. So yes ... that probably makes it a little more unsuitable to have here! Forgot about that.

I do have an S3 bucket I made for Recipes stuff that I'm happy to put them in if you want.

[skaae]

I'll try to clean up the Penntree example and make it use GRU units instead of LSTM. I don't have access to a GPU before i return to Denmark in ~10 days so i can not test the results before then.

[ebenolson]

I'll try to clean up the Penntree example and make it use GRU units instead of LSTM. I don't have access to a GPU before i return to Denmark in ~10 days so i can not test the results before then.

Great, thank you!

[JeffreyDF]

@ebenolson Thank you! Will take that into account. Might do something with it in a little while. :-)

[benanne]

I will submit PRs for the highway networks and hidden factors of variation notebooks when I find some time. It's Hopefully soon! I'll also have a think about what else I could share. Maybe some of the cyclic pooling/rolling stuff (with custom CUDA kernels) would be useful to have on here as well.

I could also just rewrite the spatial transformer network results. What do people prefer?

@skaae please do both :D That cluttered MNIST example looks really cool by the way! Is this published anywhere?