Create ML Models with BigQuery ML: Challenge Lab recensioni

Ruwini S. · Recensione inserita oltre 5 anni fa

Manideep d. · Recensione inserita oltre 5 anni fa

Tom D. · Recensione inserita oltre 5 anni fa

AKSHATA A. · Recensione inserita oltre 5 anni fa

Tom D. · Recensione inserita oltre 5 anni fa

Tom D. · Recensione inserita oltre 5 anni fa

Tom D. · Recensione inserita oltre 5 anni fa

BigQuery machine learning models have been created but not detected

Tom D. · Recensione inserita oltre 5 anni fa

(VJ) Vijaykumar J. · Recensione inserita oltre 5 anni fa

(VJ) Vijaykumar J. · Recensione inserita oltre 5 anni fa

Jorge L. · Recensione inserita oltre 5 anni fa

Naga D. · Recensione inserita oltre 5 anni fa

Tom D. · Recensione inserita oltre 5 anni fa

Got it on the third attempt with help from helpdesk. Apparently you need to hardcode the station name in the final query for task 5 busiest station. I was doing getting the same station with a WITH clause and join.

Vincent U. · Recensione inserita oltre 5 anni fa

Second attempt at this and still can't figure out how you want us to determine the busiest station in 2019 for final task. I've tried multiple ways using just start and also start and end station also with and without subscriber type. Does not make sense. Also, the second model is unclear whether stat time should be the timestamp or just the hour. Summary section and task detail have different wording. Just the hour works better by the way.

Vincent U. · Recensione inserita quasi 6 anni fa

Second model is unclear whether stat time should be the timestamp or just the hour. Summary section and task detail have different wording. Wording for last task is not clear. I ran the prediction a number of ways and can't determine what you are looking for.

Vincent U. · Recensione inserita quasi 6 anni fa

Sascha A. · Recensione inserita quasi 6 anni fa

Sascha A. · Recensione inserita quasi 6 anni fa

Great lab content but scoring system errors ruins the experience. To pass task 5 you have to use literally the name of the busiest station and use literally the name of the average value. If you use a nested query to find the busiest station or use a variable name different to the one the scoring system is expecting, you do not pass the score. Also the scoring system does not takes into account the fact that there are different spellings for Single Trip and the station names in the 2019 and 2018 datasets. I could pass it thanks to the always helpful support team.

Antonio M. · Recensione inserita quasi 6 anni fa

Abhishek P. · Recensione inserita quasi 6 anni fa

Antonio M. · Recensione inserita quasi 6 anni fa

Md S. · Recensione inserita quasi 6 anni fa

Karol T. · Recensione inserita quasi 6 anni fa

Shambhu S. · Recensione inserita quasi 6 anni fa

Shambhu S. · Recensione inserita quasi 6 anni fa