-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update vaegan.py #48
base: master
Are you sure you want to change the base?
Update vaegan.py #48
Conversation
Codecov Report
@@ Coverage Diff @@
## master #48 +/- ##
==========================================
- Coverage 72.40% 65.57% -6.83%
==========================================
Files 25 25
Lines 2551 2870 +319
==========================================
+ Hits 1847 1882 +35
- Misses 704 988 +284
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@WolfByttner does this need revisions or is ready to merge? |
This seems quite old. The models have been split up over several files, since they are used in both the AE and VAE models. |
@Saran-nns which style settings are you using? You changed all single quotes to double quotes. You also added implicit decimals. We need to define a style for this repo and set everyone up with it. |
I am using "black". Yes, it is an older version and is not compatible with the recent trainer as well due to the complexity compared to AE and VAEs. It is better to keep it as an independent module with its own trainer. |
Formatting with black is enforced with |
@WolfByttner Single to double quotes look reasonable since the dict keys have to be in double-quotes, but I never know formatter even cares about decimal point 0. --> 0.0 |
@WolfByttner do you have any updated instructions for this or can Saran focus on fixing the merge conflict? |
@JustinShenk, @Saran-nns not for VAEGAN itself. That model is still independent of everything else. If there are modifications to trainer, we should probably coordinate them. @Saran-nns, feel free to come up with a suggestion. |
@JustinShenk @WolfByttner Yes, vaegan requires intense patching over trainer. Current trainer seems to be good generalized module. To develop and maintain models like vaegan, we could have another sub directory "advanced_models" and drop such models (like Inverse RL) there with their own custom trainers. Somethnig as |
Do you have an estimate for when this will be updated @Saran-nns? |
This might take a month to update and test the vaegan network under the recent data loader. |
Okay, thanks for the update.
…On Tue, May 4, 2021 at 4:09 PM Saranraj Nambusubramaniyan < ***@***.***> wrote:
This might take a month to update and test the vaegan network under the
recent data loader.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#48 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOLMZH2RCH7MXP77OW4SFDTMBIABANCNFSM4W2ZFQBA>
.
|
@WolfByttner any feedback on the review? |
@JustinShenk This is not feature complete and need several compatibility checks. Self reviewed ;) |
Test run of the model is available at Notebook.
Todo: Update vaegan trainer to current traja trainer