-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drill down into the scoring process with more diagrams. #4
Comments
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 28, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 29, 2018
philderbeast
added a commit
that referenced
this issue
Jan 30, 2018
philderbeast
added a commit
that referenced
this issue
Jan 30, 2018
philderbeast
added a commit
that referenced
this issue
Jan 30, 2018
philderbeast
added a commit
that referenced
this issue
Jan 30, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
philderbeast
added a commit
that referenced
this issue
Jan 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The scoring process diagram is very high level. Could we show more of the process with further diagrams? I'm particularly interested in being explicit about what the inputs and outputs are for each step. This may show up intermediate outputs that we could be using for testing but are discarding.
First on my list would be showing how distance difficulty and leading are scored. How many passes are involved? What are the inputs and what are the intermediate data representations?
The text was updated successfully, but these errors were encountered: