Mike Voets

When it comes to AUC, we also experienced fluctuating results. We have for example experienced that it stopped at 0.60 AUC sometimes. Please run it a couple more times to...

Yes, in combination with applying a different seed with the `--seed` parameter. Otherwise there will be no difference between the distributions. In our study we did not redistribute though. We...

@fbmoreira You experience exactly the same as we experienced when we trained our models. Some are bad (around 0.70 AUC), most of them are ok-ish (~ 0.85 AUC), some are...

@Sayyam-Jain When you run `python train.py` twice, you'll train two different models. That's because the weights of the network are initialized different (randomly) every time. Because the starting points of...

Ah ok, excuse me for my misunderstanding! Regarding vertical flips in data augmentation: the objective of this project was to try to replicate the model and reproduce the results made...

As as a workaround, have you considered adding a custom resource lambda that creates the remaining databases?

> I'm still waiting for any reproduction example. So, I could debug and fix it @TheSmartnik We're also getting this error after updating to 0.21.0. In our case, when we...

@jaredbeck @TheSmartnik Sure thing! Here's the repro script. The only notable difference here is that the response is an array literal `[]` instead of a stringified array: ```ruby # frozen_string_literal:...

> Nope, been purely on specs for me. I am trying that fix too. I am personally of the opinion it would make sense to change it to be non...

This is the stacktrace: ``` gems/redis-4.8.1/lib/redis/client.rb:246:in `call_pipelined': ERR MULTI calls can not be nested (Redis::CommandError) from gems/redis-4.8.1/lib/redis/client.rb:200:in `block in call_pipeline' from gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect' from gems/redis-4.8.1/lib/redis/client.rb:198:in `call_pipeline' from gems/redis-4.8.1/lib/redis.rb:228:in `block in...