Opinie (Create ML Models with BigQuery ML: Challenge Lab)

40821 opinii

Krishna S. · Sprawdzono ponad rok temu

Maximillian Jonathan P. · Sprawdzono ponad rok temu

David L. · Sprawdzono ponad rok temu

Ulu Kagan B. · Sprawdzono ponad rok temu

Rupali P. · Sprawdzono ponad rok temu

Siddhartha G. · Sprawdzono ponad rok temu

Thangaraj S. · Sprawdzono ponad rok temu

Nigel Malino N. · Sprawdzono ponad rok temu

Sandy W. · Sprawdzono ponad rok temu

FRANCISCO JAVIER S. · Sprawdzono ponad rok temu

Narayana V. · Sprawdzono ponad rok temu

Andre G. · Sprawdzono ponad rok temu

Edgar D. · Sprawdzono ponad rok temu

damien c. · Sprawdzono ponad rok temu

Patricia M. · Sprawdzono ponad rok temu

good

Samrat N. · Sprawdzono ponad rok temu

Caio G. · Sprawdzono ponad rok temu

Patrick J. · Sprawdzono ponad rok temu

Srijan M. · Sprawdzono ponad rok temu

Srijan M. · Sprawdzono ponad rok temu

Christian O. · Sprawdzono ponad rok temu

Brian shahputera s. · Sprawdzono ponad rok temu

I had to use my head a little bit and I got a good feel of how I can use sql(BigQuery) to evaluate ML models on a dataset. I see that it can get very complex very fast. Thanks for keeping it simple. The lab has a nice UI and just the right amount of complexitity to test the system.

웅비 최. · Sprawdzono ponad rok temu

Kalman T. · Sprawdzono ponad rok temu

I found Task 4 of this lab to be misleading and frustrating. The instructions explicitly state that I need to "predict the average trip duration for all trips from the busiest bike sharing station in 2019 (based on the number of trips per station in 2019)." Based on these instructions, I wrote queries to: Calculate the busiest station in 2019 based on trip count Use that station to make predictions with the subscriber_type model Filter for Single Trip subscribers and 2019 data Calculate the average predicted duration However, the verification system would only accept a query that used a hardcoded station name '21st & Speedway @PCL', which is never mentioned anywhere in the instructions. This is problematic because: The instructions specifically tell us to base our solution on 2019 trip counts There's no indication we should use a pre-defined station The verification system contradicts the written instructions Students waste time trying to debug technically correct solutions A better approach would be to either: a) Update the instructions to specify using '21st & Speedway @PCL' if that's the required solution b) Or modify the verification system to accept solutions that correctly calculate and use the actual busiest station from 2019 data This discrepancy between instructions and verification criteria creates unnecessary confusion and doesn't reflect real-world data analysis practices where we would actually want to calculate the busiest station rather than assuming it.

Anshul K. · Sprawdzono ponad rok temu

Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.