Adventures with R
The good thing about sharing your knowledge with people is that you always find yourself strangely inspired. That’s what happened to me the other day in a meeting with colleagues where I were looking at some issues we were having with a reporting format we created in R Markdown. I was trying to explain to them in simple terms the little I knew about how R’s search path works and how it access objects along that path. I typed
search() and got this all too familiar output
Because of the size of my console window that day, I suddenly had an analogy for them.
I asked them to imagine that they were sitting at a desk with two drawers and suddenly started looking for a particular document. What would they do?
© mattbuck 2012
The first impulse would be to start from the tabletop first. This represents
View original post 70 more words
I found this easy-to-read blog on renaming git branches and just had to share…
The code may not render properly on this page, so I suggest you hop on over there and read it.
Multiple States Knowledge Base
If you have named a branch incorrectly AND pushed this to the remote repository follow these steps before any other developers get a chance to jump on you and give you shit for not correctly following naming conventions.
1. Rename your local branch.
If you are on the branch you want to rename:
If you are on a different branch:
2. Delete the old-name remote branch and push the new-name local branch.
3. Reset the upstream branch for the new-name local branch.
Switch to the branch and then:
View original post
In the introduction to his book R packages, Hadley Wickham provides a neat function for making sure that everything is set for writing your own R extensions, by simply running the
devtools::has_devel(), which, if all goes well, should evaluate to
This did not work out for me and I had to fix this problem on 2 different occasions so I felt I need to share this info in case there are others also stumped by this hurdle.
The fix I found – after a full sweaty day – was in this conversation on GitHub and I would like to break it down very quickly:
- Make sure you have installed Rtools from CRAN
- Make sure that Rtools/bin as well as Rtools/MinGW/x64/ are added to your system PATH (if you don’t know how, click here)
- In addition, it is recommended that you install LATEX (the link is also found on the Rtools page mentioned on No. 1)
- Run the following lines of code
install_github("hadley/devtools") # to get the latest 'pre-CRAN' package updates
has_devel() # output should be TRUE
Like I said, I had this problem on 2 different machines (Windows 7 and 10) and the same fix worked on both of them.
Well, I just have to share this with whosoever is desperately looking for a solution to this problem and happens to stumble across this post.
It’s not easy being a newbie in any thing, and computing is no exception.
I have written a small program that I will be using for my work in the office and which would also benefit a few staffers. I wrote it in C++ and compiled it using Visual Studio. However, I couldn’t find the executable file (*.exe) anywhere on my computer!
I went over to the MSDN site, as well as StackOverflow, looking for a solution but there was none in sight. To make matters worse, I discovered that MANY beginner programmers were facing the same issue.
Then I found this video on YouTube – and voilá! – problem solved. The answer to my question is ridiculously straightforward; indeed, ignorance is very costly.
If you’re in a bind like I was, I hope this works for you the way it did for me!