fix split shuffle
This commit is contained in:
@@ -205,12 +205,14 @@
|
||||
"source": [
|
||||
"### User Signup\n",
|
||||
"To create a new must call this endpoints in order:\n",
|
||||
"1. Generate Keypad\n",
|
||||
"2. Set User NKode\n",
|
||||
"3. Confirm User NKode\n",
|
||||
"1. Generate a randomly shuffled keypad\n",
|
||||
"2. Set user nKode\n",
|
||||
"3. Confirm user nKode\n",
|
||||
"\n",
|
||||
"#### Generate Keypad\n",
|
||||
" For the server to determine the users nkode, the user's keypad must be dispersable. To make the keypad dispersable, the server will randomly drop properties sets to the number of properties is equal to the number of keys. In our case, the server drops 1 properties set to give us a 5 X 5 keypad with possible index values ranging from 0-29.\n",
|
||||
" For the server to determine the users nkode, the user's keypad must be dispersable.\n",
|
||||
" To make the keypad dispersable, the server will randomly drop properties sets to the number of properties is equal to the number of keys.\n",
|
||||
" In our case, the server drops 1 properties set to give us a 5 X 5 keypad with possible index values ranging from 0-29.\n",
|
||||
" - Run the cell below over and over to see it change. Notice that values never move out of their columns just their rows.\n",
|
||||
" - each value in the keypad is the index value of a customer properties\n",
|
||||
" - the user never learns what their \"real\" properties is. All they do is specify an index in the customer keypad\n"
|
||||
@@ -248,7 +250,12 @@
|
||||
"cell_type": "markdown",
|
||||
"source": [
|
||||
"#### Set nKode\n",
|
||||
"The user identifies properties in the keypad they want in their nkode. Each properties in the gui has an index value. Below the user has selected 16, 9, 6, 19. Graphically represent with anything. The only requirement is that the graphical properties must be associated with the same index value everytime the user goes to login. If the user wants to change anything about their keypad(the number of keys, properties or graphical properties), they must also change their nkode."
|
||||
"The user identifies properties in the keypad they want in their nkode.\n",
|
||||
"Each properties in the gui has an index value.\n",
|
||||
"Below the user has selected 16, 9, 6, 19.\n",
|
||||
"Graphically represent with anything.\n",
|
||||
"The only requirement is that the graphical properties must be associated with the same index value everytime the user goes to login.\n",
|
||||
"If the user wants to change anything about their keypad(the number of keys, properties or graphical properties), they must also change their nkode."
|
||||
]
|
||||
},
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user