Skip to content
Snippets Groups Projects
Commit ba6fb80b authored by Giovanni Bussi's avatar Giovanni Bussi
Browse files

Merge branch 'v2.3' into v2.3-maxent

parents 6c55c4d2 782f7fc9
No related branches found
No related tags found
No related merge requests found
......@@ -336,6 +336,11 @@ void Atoms::setAtomsNlocal(int n){
gatindex.resize(n);
if(dd){
dd.g2l.resize(natoms,-1);
// Since these vectors are sent with MPI by using e.g.
// &dd.positionsToBeSent[0]
// we make sure they are non-zero-sized so as to
// avoid errors when doing boundary check
if(n==0) n++;
dd.positionsToBeSent.resize(n*5,0.0);
dd.positionsToBeReceived.resize(natoms*5,0.0);
dd.indexToBeSent.resize(n,0);
......
......@@ -30,7 +30,7 @@ help in taking the most by using PLUMED for your simulations.
- \subpage Neighbour
- \subpage Openmp
- \subpage Secondary
- \subpage Time
\page GMXGPU GROMACS and PLUMED with GPU
......@@ -210,6 +210,15 @@ The metric used to calculate the distance from ideal secondary structure element
the performances, try to use TYPE=OPTIMAL or TYPE=OPTIMAL-FAST instead of TYPE=DRMSD.
At last, try to reduce the number of residues in the calculation.
\page Time Time your Input
Once you have prepared your plumed input file you can run a test simulation, or use driver,
to see which collective variable, function, bias or analysis is consuming more time and can
thus be the target for a different definition (use less atoms, change relevant parameters,
or just use somenthing else)
To have an accurate timing of your input you can use the \ref DEBUG DETAILED_TIMERS.
*/
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment