Giter Site home page Giter Site logo

lupalab / posterior-matching Goto Github PK

View Code? Open in Web Editor NEW
2.0 1.0 0.0 622 KB

Official code for the NeurIPS 2022 paper "Posterior Matching for Arbitrary Conditioning".

Home Page: https://arxiv.org/abs/2201.12414

Python 62.99% Jupyter Notebook 37.01%
posterior-matching arbitrary-conditioning vae variational-autoencoder vdvae vqvae vade inpainting imputation density-estimation

posterior-matching's People

Contributors

rystrauss avatar

Stargazers

 avatar  avatar

Watchers

 avatar

posterior-matching's Issues

Mismatch between config variable names and network constructor arguments

Hi @rystrauss, thank you for such an amazing repository. I've found it very easy to begin working with this library after cloning it, so I really appreciate the time and effort spent in making it very usable (if anything getting JAX to work correctly with my GPU setup was the hardest part). While trying to recreate some of the paper's experiments, I noticed a bit of a strange behaviour when changing the network's encoder or decoder parameters in some of the configs in the repo. In short, it seemed like some of the results did not change when varying the configuration of the encoders and decoders for some of the configs.

After some digging, I noticed that in vae.py (and similarly for vade.py) the encoder's parameters are passed via the encoder_net_config argument and the decoder's parameters are passed via the decoder_net_config argument. However, several of the configs in this repository actually use encoder_config and decoder_config to pass these parameters, leading to the network constructors pretty much ignoring these parameters and using the default values instead. Because every argument in these constructors has a default value, it is hard to notice this is happening as no error would be thrown.

The configs that seem to be affected are:

$ grep -r -E '(encoder_config)|(decoder_config)' configs/ -l
configs/pm_vae_bsds.py
configs/pm_vae_gas.py
configs/pm_vae_hepmass.py
configs/pm_vae_miniboone.py
configs/pm_vae_power.py

Fixing this would just require a simple parameter name change in those configs so this is not a big issue. I am happy to fix it myself and make a PR but I wasn't sure what the contribution policy was for this repository. In the meantime, I thought that just raising a ticket may save time for others using this repository in case they stumble upon this issue. Thanks so much again for such a wonderful library!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.