-
Notifications
You must be signed in to change notification settings - Fork 23
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
Request for feedback #22
Comments
Awesome!
In any case, I would consider re-phrasing what you write in the yellow boxes to something like this:
In general, I'm still really surprised that Python's t-tests etc. do not provide confidence intervals. Could be worth some MORE yellow boxes but you decide :-)
Other ideas for the Python notebook:
Ideas for the cheat sheet:
|
Thanks for the feedback @lindeloev!
I also came across that solution, but I'd prefer not to use it. The last release of I guess the best thing to do would just be to leave notes in the yellow boxes.
Done!
Probably not! I've written a short note describing the lack of CIs (it's when I first actually use a
I'm not sure how to achieve this in statsmodels, but I've added this as a comment to the code.
I think it's better to leave them in. As you say, its not language-specific content, so there's no reason to keep them separate: it would be a pain to have to click around two web pages to read those sections!
I admit that I skimped on the effort for the cheatsheet! I'm not a big fan of cheatsheets, but it could definitely be better and prettier. I'll look into writing it up better |
Cheatsheets fixed (b962693)! I quickly gave up on LaTeX - I forget what a nightmare it is to write in LaTeX. I'm not sure if adding the Python logo is wise - it might clutter the sheet even more, and it's already jam-packed with information! I think it should be obvious which cheatsheet it is, depending on how the viewer finds it (i.e. either through your blog or mine). I think this might be ready to release and publicize - what do you think @lindeloev? |
This all sounds reasonable and the updated cheat sheet looks great! My major worry re the cheat sheet was that when your python version (hopefully!) goes viral, that people would think the "N/A"s mean "not possible in theory" when it is just a technical limitation of the Python modules right now. How about either:
In addition, I just added links to your Python version in the R cheat sheet: Maybe you could do the same below the title in "your" cheat sheet, pointing to the R version? (Also added links to the Python version in my Notebook). With this, I think it's ready for prime time! |
Ah, valid concerns! I suppose I don't spend enough time thinking about what how things could be misconstrued. I've fixed up the "N/A" comments on the cheatsheet, and also linked back to the original R version. I've also released this as v1.0.0. Would you do the honors of publicizing it? You're the original author, after all! 🚀 EDIT: my Twitter handle is @_eigenfoo, if you'd prefer to tweet it out. |
I'd be very happy to tweet it with all sorts of praise for your work here! Will do it this afternoon. https://eigenfoo.xyz/tests-as-linear/ does not seem to include the update cheat sheet, though, so I'll hold off until then (if this is the link to be shared?). |
Only if you feel like it is worth the time: Consider making a Twitter Card to show the cheat sheet: https://cards-dev.twitter.com/validator. This is the HTML I used to do so: https://github.com/lindeloev/tests-as-linear/blob/master/include/twitter_card.html (change it to your Twitter handle too). I haven't played with HTML in ipython notebooks or the export. |
Master Twitter user! I'll do this once I get back to a keyboard. I'll let you know! |
Hmm, it seems to be working for me. Could you refresh the link again? |
Twitter card created! I just embedded the HTML tags directly into the Nevertheless, I think everything is ready for prime time!
Yes! https://eigenfoo.xyz/tests-as-linear/ would be perfect. |
It took me a few hours to find not-too-ugly ways to do share buttons, twitter/facebook/linkedin cards, etc. From now on, I'll just copy-paste the header of the notebook you ported :-) But it's worth it because people use it quite a lot and it's fun to get Twitter mentions so that you can follow the spread of your work. You should definitely put some share buttons on your blog/website :-) |
I'll try to find some time to take a look at that! In any case, thanks so much for your time! Perhaps we'll bump into each other again sometime. |
Hello @lindeloev!
Following up from lindeloev/tests-as-linear#16, the port is ready for you to take a look - any feedback you have would be fantastic! You can view the page here: https://eigenfoo.xyz/tests-as-linear/.
Some specific notes for you:
Your cheatsheets are licensed under CC-BY 4.0. Can I assume that the entire R post is similarly licensed? I've gone ahead and licensed this project the same way, citing your post as the source work.
I've learnt that the Python statistics ecosystem really doesn't compare to R!
scipy
andstatsmodels
don't support:a. Two-way ANOVA
b. ANCOVA
c. One-way ANOVAs on GLMs
I've just left these code snippets un-ported, with appropriate warning boxes.
I haven't ported your simulations/appendices - hopefully somebody else will pick up Port appendices/simulations to Python #14.
I'm not sure about how to implement Welch's t-test with a linear model: you don't go into details about how to do that in your original post. Do you know of anywhere I can read up on that?
The text was updated successfully, but these errors were encountered: