The amount of work is amazing. And then to document all of that.. btw, will you include error handling? I always feel its a big thing, weather you want to round to integer or positive number if the user puts size = -8 or 8.5 for example, or just fail the function. Its a subtle difference between being too explicit and treat the user like a baby. I guess it depends on WHO is the expected user (programmer? Scientist? Student?). Would love to see your ideas of error handling and how you will perfom it in a concise manner across all your user-exported functions ! Y
Oooh. Good point! We'll definitely have to come back to error checking before it's all said and done. From our experience developing mothur we've come to appreciate how users can use a tool in ways we never could have imagined :)
Anyone in microbiology ecology should watch this series. Now I understand what's going on behind the scenes when I am classifying my sequences with a Naive Bayes classifier. Question: on line 155 in the video you use apply() but I think your Github code on line 156 has: "probabilities
Wonderful! You jumped ahead in the stream of commits/episodes :) I'll eventually change from multiplying the probabilities to adding the log of the probabilities to prevent generating numbers that are smaller than the computer can handle. The repository at the end of this episode can be found in the show notes. github.com/riffomonas/phylotypr/tree/7a5cac20692406321bf982b2046f947daf45a84f
@@Riffomonas Cool! That's a good idea. I'm curious to see how those two approaches compare. BTW, I've been coding along with you but using Python (hope you don't mind 🙂). This is such a super inspiring project.
The amount of work is amazing. And then to document all of that.. btw, will you include error handling? I always feel its a big thing, weather you want to round to integer or positive number if the user puts size = -8 or 8.5 for example, or just fail the function. Its a subtle difference between being too explicit and treat the user like a baby.
I guess it depends on WHO is the expected user (programmer? Scientist? Student?).
Would love to see your ideas of error handling and how you will perfom it in a concise manner across all your user-exported functions !
Y
Oooh. Good point! We'll definitely have to come back to error checking before it's all said and done. From our experience developing mothur we've come to appreciate how users can use a tool in ways we never could have imagined :)
Anyone in microbiology ecology should watch this series. Now I understand what's going on behind the scenes when I am classifying my sequences with a Naive Bayes classifier. Question: on line 155 in the video you use apply() but I think your Github code on line 156 has: "probabilities
Wonderful! You jumped ahead in the stream of commits/episodes :) I'll eventually change from multiplying the probabilities to adding the log of the probabilities to prevent generating numbers that are smaller than the computer can handle. The repository at the end of this episode can be found in the show notes. github.com/riffomonas/phylotypr/tree/7a5cac20692406321bf982b2046f947daf45a84f
@@Riffomonas Cool! That's a good idea. I'm curious to see how those two approaches compare. BTW, I've been coding along with you but using Python (hope you don't mind 🙂). This is such a super inspiring project.
@@csalt3689 that's awesome! I'd love to see how your python code compares to my R code (and our earlier C++ code)