uo-ec607 / lectures Goto Github PK

The twitter link to the 'long-running joke' about Stata's reshape command no longer works (Scott Imberman seems to have changed his handle and deleted past tweets?). The link's on slide 42 of lecture 5.

Thank you for sharing these materials: it's hugely appreciated!

I could be wrong, but I think you need update the seed setting for furrr and future (future.apply) functions. furrr functions want an additional argument .options = future_options(seed = T), and future (future.apply) functions want a similar argument future.seed = T.

Thank you very much for sharing your course material!

I just saw a typo in the first line of page 40 when I was reading lecture note 2. There are two "and" instead of one. This is not misleading anyway. But you probably can change it very easily and quickly.

Line endings ("invisible characters") aren't added by Git; they're always there, whether you're in a Git repo or not. Most people don't notice them under normal circumstances because their text editors handle it seamlessly. It only comes up with Git because, by default, Git considers "stuff\r\n" and "stuff\n" to be different lines.

(These slides are great, by the way!)

Sorry to bother you, and thanks for putting the course online!
I followed along with L3, and installed WSL in PowerShell using wsl --install
I rebooted my computer and the fan has been going mental as it typically does when running large simulations.
I've uninstalled ubuntu using the walkthrough here, but the laptop is still whirring. Just wondering if you had any advice? It may settle down overnight, but grateful if there's a way to fully undo the action that wsl --install did.

Thank you! And apologies again.

I was looking through your shell slides and they are awesome!!!

As I was reading I had a couple comments, which are below. Feel free to ignore (some of these are stylistic). Thanks again for posting these slides!

• I find it important to know that in a man page /term will search for term.
• You might want to suggest single quotation marks when suggesting quoted names or else people will get confused when special symbols end up breaking things (eg in your sed commands you use single quotes)
• On slide 36 /n should be \n
• Not sure you want to bring it up, but head and tail also have a character mode that is often useful for files with long lines (head -c 1000)
• In a bit of a pain that always comes up when I teach this stuff: Mac installs the BSD utilities instead of GNU utilities. So if people start exploring grep and sed, they’re probably going to hit issues pretty quick https://unix.stackexchange.com/questions/13711/differences-between-sed-on-mac-osx-and-other-standard-sed

Hi,

Many thanks for making this amazing course public, I'm learning a lot! I just wanted to point out that you titled slides 42-43 of your second lecture ".gitgnore" (you missed the second "i"). I thought maybe it could be misleading in some situations.

Best,

Pierre