The initAnalysis() function was changed a long time ago to take the
analysis settings as a parameter, to make it easy to use those values in
initialization without storing them in local variables.
Do the same for initAfterFirstFrame(), now that there is a tool in
pipeline (gmx rdf) that would actually use this function and sees the
same issue there.
Change-Id: Ib10abb3790ac5472070edc76155cfa50cce96541
}
-void TrajectoryAnalysisModule::initAfterFirstFrame(const t_trxframe & /*fr*/)
+void TrajectoryAnalysisModule::initAfterFirstFrame(
+ const TrajectoryAnalysisSettings & /*settings*/,
+ const t_trxframe & /*fr*/)
{
}
*
* The default implementation does nothing.
*/
- virtual void initAfterFirstFrame(const t_trxframe &fr);
+ virtual void initAfterFirstFrame(const TrajectoryAnalysisSettings &settings,
+ const t_trxframe &fr);
/*! \brief
* Starts the analysis of frames.
// Load first frame.
common.initFirstFrame();
- module->initAfterFirstFrame(common.frame());
+ module->initAfterFirstFrame(settings, common.frame());
t_pbc pbc;
t_pbc *ppbc = settings.hasPBC() ? &pbc : NULL;