I have recently had many issues with my laptop when traveling. While everyone says I should buy a new one, I am more interested in a tablet, but tablets are not good for programming. One possible solution is to use a cloud instance with all my programming libraries and software on a remote server (amazon aws, google cloud, self-hosted, etc.). In this way, I could access this cloud computer from anywhere in the world from a tablet, laptop, or phone.
Using pandoc to convert files between different formats is great! However, there are some issues when you want to use it to convert scientific manuscripts from LaTeX to Microsoft Word. The most annoying of them for me is the lack of support to number equations, tables, and figures. In this post, I briefly summarize the way I solved this problem by customizing a pandoc filter (available here).
I have been struggling a lot with keeping my manuscripts updated after many rounds of revisions and several months after the first draft. I have decided to improve my work habits to help me, and others, keeping track of the manuscript, and its related scripts to gather data and generate results (figure and tables). Here, I summarize some tools useful to improve reproducibility. I also have some slides about this subject available here.
Paramiko is a python package that handles remotes connections using ssh protocol. With this approach, it's possible to submit jobs to a cluster from a local machine, copy, and send files. This enables us to create local routines that leave all the processing power to the cluster.
Emacs is my favorite text editor and I have been using it to write R scripts. In this post, I describe some basic steps to use emacs as an R editor and to allow emacs to detect regions as R studio would.
Shiny Apps are a great tool to share research results. In my first official post, I will walk you through the basic steps to design and publish a shiny app. I will use part of my research as an example.