<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Aug 31, 2018 at 3:56 PM Mahmood Naderan <<a href="mailto:nt_mahmood@yahoo.com">nt_mahmood@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:16px"><div><br></div><div><span>>You can add the -debug 1 option to get a lot of, largely <br></span></div><div><span>>unintelligible,
information printed to gmx.debug. -debug 2 <br></span></div><div><span>>will print even more, per
atom, information.</span></div><div><br></div><div><br></div><div><br></div><div>So, I ran <br></div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:16px"><div><div><br></div><div><span>gmx mdrun -debug 2 -nb gpu -ntmpi 1 -ntomp 16 -v -deffnm nvt</span></div><div><span><br></span></div><div><span>However, the information printed in the terminal and the log file are the same as before.</span></div></div></div></div></div></blockquote><div><br></div><div>As Berk said, "printed to gmx.debug" ie. not the places you have looked.</div><div><br></div><div>Mark</div></div></div>