Improve initAfterFirstFrame() usability
authorTeemu Murtola <teemu.murtola@gmail.com>
Sun, 10 Aug 2014 04:24:06 +0000 (07:24 +0300)
committerTeemu Murtola <teemu.murtola@gmail.com>
Sun, 10 Aug 2014 07:12:40 +0000 (09:12 +0200)
commit0c9b289020f68ccfe2fa6a49d7d6cd4b237faebe
tree43165f0c672ee8339a28c63a60967cf6afe972f3
parent6f2a3703ee50529969a655aeec8bffd94c5dc8ab
Improve initAfterFirstFrame() usability

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
src/gromacs/trajectoryanalysis/analysismodule.cpp
src/gromacs/trajectoryanalysis/analysismodule.h
src/gromacs/trajectoryanalysis/cmdlinerunner.cpp