Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fixed the spectral normalization #115

Closed
wants to merge 2 commits into from
Closed

Fixed the spectral normalization #115

wants to merge 2 commits into from

Conversation

pevnak
Copy link
Contributor

@pevnak pevnak commented Nov 24, 2017

No description provided.

@MikeInnes
Copy link
Member

Can you give a simple usage example for this, and/or a general idea of how it should be used?

@pevnak
Copy link
Contributor Author

pevnak commented Dec 9, 2017 via email

@MikeInnes MikeInnes force-pushed the master branch 3 times, most recently from 86ae1fa to d222700 Compare February 18, 2018 12:51
@MikeInnes MikeInnes force-pushed the master branch 4 times, most recently from 027a922 to 5cc6813 Compare April 15, 2018 14:07
@ToucheSir
Copy link
Member

@pevnak are you still interested in pursuing this? I see the authors released a follow-up paper at https://arxiv.org/abs/1802.05957.

@CarloLucibello CarloLucibello mentioned this pull request Feb 12, 2021
92 tasks
@darsnack
Copy link
Member

Bump on this @pevnak. If this is too far in the rearview mirror, I'd suggest we open an issue and close this PR. That way it's clear what work is up for grabs.

@CarloLucibello
Copy link
Member

this type of normalization doesn't seem to be used in current practice, not worth opening an issue unless someone is interested into it

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants