-
Notifications
You must be signed in to change notification settings - Fork 16
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
dimRed on CRAN #57
Comments
The issue is the following:
At the moment I am lacking the energy and time to sit down and redo the autoencoder properly. Is there a proper autoencoder in R now that we can wrap? I did the autoencoder myself back when I created the package mostly because there was no package that provided a good autoencoder implementation. |
Outside of h2o, I don't see anything ready-made for general problems. I've been using R's torch implementation, and you could translate it over (when you have time). I'm pinging our keras people to see if one of them can help out. If they don't get back to me in a day or so, I'd probably remove the function and go with what you have. |
resubmitted, let's see. some of the tests/examples are still failing but I think this is due to how the environment is set up. |
Tests fail on M1 Macs. It seems to be a numerical issue that I cannot debug. Any ideas? |
We'll take a look. We have seen some differences of results for this chip (especially early on). |
I cannot reproduce his issue. When testing
I would probably |
Thanks for testing. We don't have an free Macbook at work, so I have a colleague test it and then just do |
We saw this on 2015-01-12:
Is there a plan to put it back on CRAN? Is there anything that we can help with?
The text was updated successfully, but these errors were encountered: