Fixes for ``gmx`` tools
^^^^^^^^^^^^^^^^^^^^^^^
+Fix periodic boundary conditions in analysis framework tools
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+There was a bug in the trajectory analysis framework which caused
+molecules that were broken over PBC not to be made whole. This would
+usually lead to obviously incorrect outliers in analysis output.
+
+:issue:`3900`
+
Fix range checking bug in gmx covar
"""""""""""""""""""""""""""""""""""
* Copyright (c) 1991-2000, University of Groningen, The Netherlands.
* Copyright (c) 2001-2004, The GROMACS development team.
* Copyright (c) 2013,2014,2015,2016,2017 by the GROMACS development team.
- * Copyright (c) 2018,2019,2020, by the GROMACS development team, led by
+ * Copyright (c) 2018,2019,2020,2021, by the GROMACS development team, led by
* Mark Abraham, David van der Spoel, Berk Hess, and Erik Lindahl,
* and including many others, as listed in the AUTHORS file in the
* top-level source directory and at http://www.gromacs.org.
int i;
rmpbc_graph_t* gr;
- if (pbcType == PbcType::No || nullptr == gpbc || nullptr == gpbc->idef || gpbc->idef->ntypes <= 0)
+ if (pbcType == PbcType::No || nullptr == gpbc
+ || (nullptr == gpbc->interactionDefinitions && (nullptr == gpbc->idef || gpbc->idef->ntypes <= 0)))
{
return nullptr;
}