[gmx-developers] A minor bug in demux.pl

Piggot T. T.Piggot at soton.ac.uk
Mon Jul 8 11:08:08 CEST 2019


FYI I forgot to also say that the issue with demux.pl has been reported in published work too:

https://pubs.acs.org/doi/abs/10.1021/acs.jctc.5b00981

Cheers

Tom

On 07/07/2019 09:35, Piggot T. wrote:
Hi,

This is a known problem, see:

https://groups.google.com/forum/m/#!topic/plumed-users/XhB34MmSpjM<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fforum%2Fm%2F%23!topic%2Fplumed-users%2FXhB34MmSpjM&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=wDSHOK8gRVVHHgINz%2FtaJug3QqUEGv2QWy%2B9Dag%2Fos8%3D&reserved=0>

There’s also a modified script provided there too that I’ve used without problem for long trajectories.

I guess the script provided by GROMACS should be updated. It is probably worth reporting it on redmine.

Cheers

Tom

On 7 Jul 2019, at 07:05, Yong Wang <wyongciac at gmail.com<mailto:wyongciac at gmail.com>> wrote:

Hi,

We are running a normal REMD with 10 replicas and an exchange frequency of 0.2ps, and tried to use demux.pl<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdemux.pl&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=U4y9sZuuLMLGvDtLxeMXosz%2BhQYOPwqnuda6Lm8xGQY%3D&reserved=0> to get continuous trajectories. But we found the demuxed trajectories always become discontinuous after 100ns. After some frustrating debugging, we found the replica index file (replica_index.xvg) was not corrected generated by demux.pl<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdemux.pl&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=U4y9sZuuLMLGvDtLxeMXosz%2BhQYOPwqnuda6Lm8xGQY%3D&reserved=0>. For example, the output looks like this:


99998.8                 9    2    4    0    5    8    3    7    6    1

99999                   9    2    4    0    8    5    7    3    6    1

99999.2                 9    2    4    8    0    5    7    3    6    1

99999.4                 9    2    8    4    5    0    7    3    1    6

99999.6                 9    2    8    5    4    0    7    3    1    6

99999.8                 9    2    8    5    4    0    7    3    6    1

100000                  9    2    8    4    5    0    7    3    6    1

100000                  2    9    8    4    0    5    7    3    6    1

100000                  2    9    8    0    4    5    7    6    3    1

100001                  9    2    0    8    5    4    7    6    3    1

100001                  9    2    0    8    5    4    7    3    6    1

100001                  2    9    8    0    4    5    3    7    1    6

100001                  2    9    8    4    0    5    3    7    1    6

100001                  2    9    4    8    0    5    7    3    1    6

100002                  2    9    4    0    8    5    7    3    1    6

100002                  2    9    0    4    8    5    3    7    6    1

100002                  2    9    0    8    4    5    3    7    6    1

100002                  2    9    8    0    4    5    3    7    6    1

100002                  2    8    9    4    0    5    3    7    6    1

As you can see, the time information in the first column was confused after 100000 (corresponding to 100ns). So we tried to correct the time information, and the problem seems solved. In our case, we made minor modifications on the demux.pl<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdemux.pl&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=U4y9sZuuLMLGvDtLxeMXosz%2BhQYOPwqnuda6Lm8xGQY%3D&reserved=0> script by simplify replacing "%-20g" by "%-20.1f". And it works for us!

I don't know if this is the best solution but I am reporting this and hope it is helpful to others. And the issue can only occur when we use an exchange frequency smaller than 1ps and run the simulation longer than 100ns. Could you identify if this is a minor bug or just limited to our case? Thanks a lot!

Regards,
Yong

--

==========================
Yong Wang
Postdoc in Lindorff-Larsen Lab
Structural Biology and NMR Laboratory  &  Linderstrøm-Lang Centre for Protein Science
Department of Biology, University of Copenhagen
Ole Maaløes Vej 5, DK-2200 Copenhagen N, Denmark
https://scholar.google.com/citations?hl=en&user=LblGaZMAAAAJ&view_op=list_works&sortby=pubdate<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailtrack.io%2Ftrace%2Flink%2F01603ac90f476741fe794a895a94d4ee843620d6%3Furl%3Dhttps%253A%252F%252Fscholar.google.com%252Fcitations%253Fhl%253Den%2526user%253DLblGaZMAAAAJ%2526view_op%253Dlist_works%2526sortby%253Dpubdate%26userId%3D2367320%26signature%3D0578092a37df8130&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=JCuINH8xVSVpfQifwWZnEcbI9mtnqfcNH46oVs2yWAk%3D&reserved=0>

--
Gromacs Developers mailing list

* Please search the archive at https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.gromacs.org%2FSupport%2FMailing_Lists%2FGMX-developers_List&amp;data=01%7C01%7Ct.piggot%40soton.ac.uk%7C525a9452f6c6459d41ab08d702a113ed%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=lgH%2BS14i%2BHnim4JxJgHGfiy3U%2BteutjISmh7JqBuoEI%3D&amp;reserved=0<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.gromacs.org%2FSupport%2FMailing_Lists%2FGMX-developers_List&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=BwiiCVDkLfNgRXb0JMFl%2BgL2ioHqd9Q7gFuT%2FGu6H%2F8%3D&reserved=0> before posting!

* Can't post? Read https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.gromacs.org%2FSupport%2FMailing_Lists&amp;data=01%7C01%7Ct.piggot%40soton.ac.uk%7C525a9452f6c6459d41ab08d702a113ed%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=9dpj6GeQP7tWWUGNmMPJztQqLUqDSh4wscIgL75HNf0%3D&amp;reserved=0<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.gromacs.org%2FSupport%2FMailing_Lists&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Fofap8MPdoin12YNUUNUSCX0w4KO087LuokWp1OrpLQ%3D&reserved=0>

* For (un)subscribe requests visit
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaillist.sys.kth.se%2Fmailman%2Flistinfo%2Fgromacs.org_gmx-developers&amp;data=01%7C01%7Ct.piggot%40soton.ac.uk%7C525a9452f6c6459d41ab08d702a113ed%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=lFbi736ApQREhGcftoMN70UcJd9dEVqTF4UGVnhp8kI%3D&amp;reserved=0<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaillist.sys.kth.se%2Fmailman%2Flistinfo%2Fgromacs.org_gmx-developers&data=01%7C01%7Ct.piggot%40soton.ac.uk%7Ce60885b7a642493feb3008d702b623c5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=nb1W8eTcyGsPIpzbNANsra1O78oeGaH3ptedrfR6Dfo%3D&reserved=0> or send a mail to gmx-developers-request at gromacs.org<mailto:gmx-developers-request at gromacs.org>.




--
Dr Thomas Piggot
Visiting Fellow
University of Southampton, UK.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20190708/7c6dfe15/attachment-0001.html>


More information about the gromacs.org_gmx-developers mailing list