tristantao / mvp2 Goto Github PK

When they plot 2 things, note that it overwrites the first plot.

Either tell them to plot one at a time, or also include how to go back to the last plot.

This is in the train and test viz, where we don't explain the bart plots enough.

I don't think we've added this yet? Just don't want to forget

In testVizDataScreen, when you do the [density] payload and go through its entirety what is return is the "Exiting Early!" text instead of the "You're done with this part..."

Go to: Data -> Test -> Test Visualize -> [density]

When a payload is being delivered, user presses enter to move onto the next payload. But users also need the option to enter "quit" and he/she should be returned to the previous screen without having to press enter many times to finish the tutorial and return.

Don't do this yet, I'll teach you how to "branch", so you can work on your copy of code (while keeping commit / main one fresh).

Will need to link the pages together, so they can add_var.

Pressing "back" more than twice, will not result in screen change, since that is the most recent "back", after the last back.

Instead of a single var to hold the most recent screen, the most recent screen/history of screens, needs to be a Stack.

It's a programming challenge, lemme know if you don't want to do it.

When you go through all the payloads by pressing ENTER you get to one that returns

+++++++++++++++++++++

And then an INFO "Your down with this part.." and you have to press ENTER again

Can we make it so you don't have to press ENTER three more times to get out of payloads?

For example, I significantly shortened the explanation of classification trees in the wiki. We can perhaps do this for more parts

instead of "view", people might enter "[view]", as Jeff did. If this is problematic, we either change the code to handle the bracket (and then notify user that they don't have to use it), or specify more clearly to begin with.

Will get bumped to Sprint 2 if we don't have an answer.

Users should be able to see their progress somehow.

Use the actual numbers when your explaining the error matrix and simplify explanation better.

lol not much we can do but it looks messy as shit.

The issue is being caused by quotes being escaped (check escaping when adding badges"

instead of entering "0" or "1", they should be able to enter the first few chars and be good.

When you go to data view and go through the "view" action, and finish the steps, pressing "back" after doesn't get you to backup immediately (have to "back" one more time. I'm suspecting that you're not checking if the most recent screen is the same screen as the current screen.
i.e. the following screen stack happens:
["screen1" => "screen2" => "screen3"]
*Now do a screen action, such as view, but "screen3" gets re-added", so your back-stack looks like this:
["screen1" => "screen2" => "screen3" => "screen3"]

So after you finish an action in "view", and you want to go back and visit "viz", you can't do so immediately.

I'm fixing this but I assigned you so you're aware.

This is something they can look up on Kaggle, but maybe we oughtta explain too.

Make code = blue, instructions = red, etc.

This is one of the questions Jeff bro brought up