Added verboseComments option for RMG jobs.

If False (the default), RMG-Py will now discard the (often lengthy) kinetics
comments for estimated values in favor of much shorter strings with only the
most important information. This immediately frees up ~10% of the total
memory usage of an RMG job, as well as makes the saved output files much
smaller in size and easier to read. If True the full comments are retained,
as before. You set this in the options() block of an RMG-Py input file.

I implemented this inside CoreEdgeReactionModel.getKinetics() so that the
database always returns the long comment, and we only discard that comment
in RMG jobs. I don't think assembling the long comments is much of a CPU
penalty, so I've opted for a more modular design.
Added energy corrections for sulfur atoms to CanTherm.

Somehow the bond corrections for some sulfur-containing bonds got added, but
the atom corrections did not. Note that you currently must use CBS-QB3 or G3
for sulfur.
Added cantherm target for building CanTherm dependencies only.

This should hopefully enable people to download RMG-Py and compile it in a
mode that works for running CanTherm. In particular, we want to avoid the
tricky dependencies (e.g. OpenBabel). You'll still need all of the
dependencies that you would for a standalone CanTherm, of course: cython,
numpy, scipy, matplotlib, and maybe one or two others.
Added support for N, P, and S atoms in GaussianLog.loadGeometry().

This is needed to associate a mass with each atomic number.
Better checking for same reactants in KineticsFamily.__generateReactions().

The previous implementation no longer worked because we moved where we make
a temporary copy of the duplicate reactant. The new version uses an
isomorphism check, which is safer. I don't think the speed penalty will be
too significant.

This fixes some incorrect degeneracies, e.g. the disproportionation reaction
C2H5 + C2H5 -> C2H6 + C2H4.
Also check for rate rules with swapped template for R_Recombination reactions.

Rate rules could be specified in either the A + B or B + A order in the
database. I'm not aware of any particular convention for this (or even if
one could be enforced), so we need to check both when looking up the
kinetics. If only one of them gives an exact match, then we will keep that
one. If both are exact or both are estimates, then we keep the one in the
order given; although I don't think this is the best way to do it.

An example is H + CH3 -> CH4, which has an exact rule for (C_methyl,H_rad)
but not for (H_rad,C_methyl). Now you will get the exact rule no matter
which order you specify the template in.
Fix SimpleReactor to use isobaric model.

The new implementation uses total moles instead of concentration for the
y(t) vector. The volume is not stored in y(t) since it can be computed
directly via the ideal gas law from the total moles, and we don't need to
compute dV/dt in this formulation.

I think the previous implementation was actually isochoric instead of
isobaric. Note that the minimal example returns the same result in either
case.
Remove another wild 'import *'
An attempt to fix the "make minimal" target to just do the bare minimum cythoning.

Not sure it works.
Fix initialization of coreSpeciesConcentrations in SimpleReactor

Now that y represents mole numbers not concentrations, the initial
setting of coreSpeciesConcentrations needed to be fixed.
Updated conversion calculations in base solver class.

Now that y represents mole number not concentration, we can remove the 
forced assumption of ideal gas law and just calculate conversion directly
from the number of moles.