910 karma · joined January 15, 2019
>How might you have altered your third guess if you could try again?
Given the feedback provided up to the second guess, I had the following information:
apple: XXXOV slope: XVVOV Based on this information, I should have considered that the word contains "s," "o," and "e" in the right positions. I could have guessed a word that utilizes the "s" and "e" in the same positions and tries a new letter instead of the second "o."
If I could try again, I would change my third guess to:
sware This would help me gather more information about the other letters, while still using the correct positions for "s" and "e."
I think you're confused. slope: XVVOV means that there is no X in the word, do you see that? You are correct, I misunderstood the feedback. My apologies for the confusion. Based on the feedback provided up to the second guess:
apple: XXXOV slope: XVVOV We can deduce that the word has "l" and "e" in their correct positions, and "s" in a different position. Also, there is no "x" in the word. Given this information, my third guess should have been:
glare This guess takes into account the correct positions of "l" and "e" and the presence of "s" in a different position.
Yes, I understand the rules. Let's play Wordle! Here is my first guess:
apple
XXXOV
Thank you for the feedback. Here's my second guess:
slope
XVVOV
Thank you for the feedback. Based on the information provided, here's my third guess:
spore
XXVXV
Thank you for the feedback. Based on the information provided, here's my fourth guess:
savor
XXOOX
Thank you for the feedback. Based on the information provided, here's my fifth guess:
sofar
XOXXXX (I made a typo here)
Thank you for the feedback. Based on the information provided, here's my sixth and final guess:
solar
> Rule #34: In binary classification for filtering (such as spam detection or determining interesting emails), make small short-term sacrifices in performance for very clean data.
> In a filtering task, examples which are marked as negative are not shown to the user. Suppose you have a filter that blocks 75% of the negative examples at serving. You might be tempted to draw additional training data from the instances shown to users. For example, if a user marks an email as spam that your filter let through, you might want to learn from that.
> But this approach introduces sampling bias. You can gather cleaner data if instead during serving you label 1% of all traffic as "held out", and send all held out examples to the user. Now your filter is blocking at least 74% of the negative examples. These held out examples can become your training data.
> Note that if your filter is blocking 95% of the negative examples or more, this approach becomes less viable. Even so, if you wish to measure serving performance, you can make an even tinier sample (say 0.1% or 0.001%). Ten thousand examples is enough to estimate performance quite accurately.
[1] https://developers.google.com/machine-learning/guides/rules-...
I don't get it, don't all of those optimizers work via backprop?
That is not to say the layoffs were not needed or justified (I don't know) but the asymmetry exists because it's an asymmetric situation.
int compare(const void *a, const void *b) { return *(double*)a - *(double*)b; }