.. _variables:
Updating regression tests
-~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~
-Changes in |GROMACS| that require changes in regression-tests are notoriously hard,
+Changes in |Gromacs| that require changes in regression-tests are notoriously hard,
because a merge request that tests against the non-updated version of the
regression tests will necessarily fail, while updating regression tests while
the current change is not integrated into master, might cause other
``BUILD_DIR``, ``INSTALL_DIR``, ``CACHE_FALLBACK_KEY``, ...
Setting variables
-~~~~~~~~~
+~~~~~~~~~~~~~~~~~
Variables for individual piplelines are set in the gitlab interface under
-``CI/CD``→``Pipelines``. Then chose in the top right corner ``Run Piplelines``.
+``CI/CD``; ``Pipelines``. Then chose in the top right corner ``Run Piplelines``.
Under ``Run for``, the desired branch may be selected, and variables may be set
-in the fields below.
\ No newline at end of file
+in the fields below.
gmx_wallcycle* wcycle);
private:
- // The number of vsites that cross update groups, when =0 no PBC treatment is needed
+ //! The number of vsites that cross update groups, when =0 no PBC treatment is needed
const int numInterUpdategroupVirtualSites_;
- // PBC and DD information
+ //! PBC and DD information
const DomainInfo domainInfo_;
- // The interaction parameters
+ //! The interaction parameters
const ArrayRef<const t_iparams> iparams_;
- // The interaction lists
+ //! The interaction lists
ArrayRef<const InteractionList> ilists_;
- // Information for handling vsite threading
+ //! Information for handling vsite threading
ThreadingInfo threadingInfo_;
};
class ConvertTprInfo
{
public:
- static const char name[];
- static const char shortDescription[];
+ //! Name of the module.
+ static const char name[];
+ //! Short description what the module does.
+ static const char shortDescription[];
+ //! Instantiatiates the module.
static ICommandLineOptionsModulePointer create();
};