Things that make my work easier

This is a list of some of the tools that I use on a regular basis that have come to be an essential part of my workflow.

Writing papers

I use LaTeX for typesetting, and TexStudio for typing. References are managed using Bibtex. I also use JabRef, which is a simple GUI frontend for Bibtex files. Ideas with references are organized using Docear.

Most papers are kept in private repositories on [email protected] and Bitbucket. My coauthors and I use Git to allow us to work remotely on a paper and merge our changes. If a coauthor is not comfortable with Git, papers are kept on Dropbox.

Reading papers

I keep abreast of the literature using Inoreader (an RSS feed reader) with subscriptions to about a dozen arXiv and journal feeds. I have a few alerts set up on Google Scholar, which I also use for finding specific papers. See the post on Searching the Scientific Literature.

Presentations and multimedia

Lately, I write most presentations in Powerpoint. I use texpoint to typeset equations onto slides.
For drawn diagrams and graphics, I use Omnigraffle and Inkscape.

For 3D modeling and animations, I am starting with Blender and used Pov-Ray before due to my colleagues.


Most of my coding is done with Matlab because most of collaborators use it and my university–UNM–provides it for free to me as the original home of Matlab. I also use the following:

  1. The Jupyter notebook (formerly IPython and IJulia notebook). For interactive running and debugging. And for organizing, recording, and sharing code with animations and mathematics.
  2. Github and BitBucket. For collaborative code development.
  3. Eclipse for C and Java programming IDE. Used once for Arduio and others.
  4. Vim for plain programming.


Matlab, Matplotlib and VisClaw.

[comment] # (## Teaching)

[comment] # ( 1. SageMathCloud) [comment] # ( 2. The Jupyter notebook (formerly IPython notebook).)

Notes and productivity

  1. OneNote from MicroSoft.
  2. NValt. For managing plain-text notes.
  3. Omnifocus. For managing all the non-research stuff I do.
  4. Gitit. Wiki software could be useful for internal collaboration within a group.


  1. Jekyll. For building this website and a few others on GitHub.
  2. Coda.
  3. Wordpress. For the CQuIC website I participated to build.


Being a quantum information scientist, I have been developing a deep interest in both software and hardware of computers and artificial intelligence. Sometimes, I also need to do hard computing jobs on nanophotonics and many-body quantum simulations. So, I run Linux on Lenovo Thinkpads, workstations from my work place, cloud servers and clusters. The reason I use Thinkpads as my personal computers is mainly because it has a strong traditional Linux community support. Otherwise, running Linux will be extremely painful to handle hardware driver issues and to optimize performance. Specifically, I run Ubuntu on my personal computers for work. I also use OneNote on Windows to take notes and synchronize them on OneDrive. My current working machines include a Thinkpad P50 mobile workstation (CPU i7-6700HQ, GPU M1000M, 64GB RAM) and a Thinkpad Tablet 2 (for notes taking mainly). I use a 64GB RAM for simulating large quantum systems and for virtual machines to run Windows OS (Windows Insider free preview version) inside of Linux sometimes in case of editing my notes and synchronizing my Youdao wordbook. In the past or as backups, I also have convenient Thinkpad X61 Tablet (fixed from a trashed one in a low cost and worked like a tank) and X200 Tablet to combine the notes taking, travelers’ computer and hard-computing functions in one.

To reduce power consuming and increase battery life using Linux on Thinkpads, I use TLP on top of acpi_call (you may want tp-smapi instead if the CPU was produced earlier than the Ivy Bridge times) and acpi-bat to set up battery charging thresholds and save power usage. I only need to edit the TLP config file at /etc/default/tlp, run sudo tlp start for the first time and forget about it. I was also using powertop with the --auto-tune switch and disabled a few options for power saving on battery (see the corresponding notes on the system administration page). Linux kernel is not very good on power management and driver compatibility for closed-source designed hardware, and there is usually a delay of support on most advanced hardware. For example, Skylake mobile CPUs were not supported until Linux kernel v4.4 (half a year after the CPU release) and continuously get worse performance than under Windows OS on deep-sleeping optimization of mobile device modules for a long time (you can find the PC-state using powertop). Be sure to consider this factor when you want to install Linux on a new computer.

For workstations, I have configured a Dell Precision 7910 computer for CQuIC (machine is purchased from Dell that the university policy allows). There may be better choices. Again, Ubuntu OS was installed for its being popular in the research center. TORQUE/PBS was installed to manage computing job submissions and scheduling. I have also experiences of using CentOS on a cluster in the earlier days which along side with Scientific Linux OS may be a better choice for dedicated high-performance computing.

Some notes on computer system administration and tool using can be found here.