Machine Learning with TensorFlow and Vertex AI Reviews

Sary H. · Reviewed over 4 years ago

Explanation is not quite clear. Difficult to follow

Thawatchai R. · Reviewed over 4 years ago

kamal o. · Reviewed over 4 years ago

Radwa S. · Reviewed over 4 years ago

Molk S. · Reviewed over 4 years ago

Samarth A. · Reviewed over 4 years ago

Salma S. · Reviewed over 4 years ago

Saheed A. · Reviewed over 4 years ago

Hasnaa M. · Reviewed over 4 years ago

Great

Vikram A. · Reviewed over 4 years ago

Its is not designed and explained

Vikram A. · Reviewed over 4 years ago

Update this lab or retire it! Everything seems obsolete (python 3.5, TF 1.14, ...). More time as well. Installations & updates etc... take almost 10 minutes, and the SSH is very slow. The instructions are also very difficult to follow.

Matthew J. · Reviewed over 4 years ago

Victor M. · Reviewed over 4 years ago

Jad Z. · Reviewed over 4 years ago

David M. · Reviewed over 4 years ago

Lee Y. · Reviewed over 4 years ago

Jad Z. · Reviewed over 4 years ago

more time to investigate the code would be nice

Dominik L. · Reviewed over 4 years ago

Very Tough one

Owais A. · Reviewed over 4 years ago

Andrew M. · Reviewed over 4 years ago

In Create minimal training and test datasets, repeated instruction and code chunk could be removed: Create the training data... rm full.csv` In Create a TensorFlow experimental framework in Python, the training model didn't execute correctly since my output was different from the expected: INFO:tensorflow:Saving dict for global step 200: accuracy = 0.89453167, accuracy_baseline = 0.72878134, auc = 0.88293874, auc_precision_recall = 0.946697, average_loss = 0.5809859, global_step = 200, label/mean = 0.72878134, loss = 290.5801, precision = 0.90075845, prediction/mean = 0.7678837, recall = 0.9611797, rmse = 0.3024143 To be: tensorflow.python.framework.errors_impl.InvalidArgumentError: assertion failed: [string_input_producer requires a non-null input tensor] [[{{node input_producer/Assert/Assert}}]] However, the job appears to execute seamlessly and with lots of Warning (148) and Error (32).

Moria W. · Reviewed over 4 years ago

Trivikram M. · Reviewed over 4 years ago

Sunit M. · Reviewed over 4 years ago

Ran out of time on the first try. Had to do it again, but even then, needed to blaze through it to get it all done in time. IMO, this lab would be better if it allowed for an hour and a half or even 2 hours, to give time to really understand the code and what is happening

Joe R. · Reviewed over 4 years ago

rozan w. · Reviewed over 4 years ago