<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='margin-bottom:12.0pt'>Dear GROMACS developers,<span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal>We are currently in the process of benchmarking GROMACS5.1.2 on our local HPC systems. There are some nice results posted online (<a href="http://www.gromacs.org/@api/deki/files/240/=gromacs-5.0-benchmarks.pdf">http://www.gromacs.org/@api/deki/files/240/=gromacs-5.0-benchmarks.pdf</a>). I was wondering if anybody can kindly share the files (such as, pdbs, mdps, tops and tprs) used for those tests? We’d like to see if we could reproduce any of those results. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you in advance!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kevin Chen<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> gromacs.org_gmx-developers-bounces@maillist.sys.kth.se [mailto:gromacs.org_gmx-developers-bounces@maillist.sys.kth.se] <b>On Behalf Of </b>Mark Abraham<br><b>Sent:</b> Wednesday, July 6, 2016 10:07 AM<br><b>To:</b> gmx-developers@gromacs.org; gromacs.org_gmx-developers@maillist.sys.kth.se<br><b>Subject:</b> Re: [gmx-developers] Compilation Errors When Using GROMACS Headers/Library<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It is normal behaviour for installed headers intended for third-party development to expect to have their path prepended by the preprocessor, e.g.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>gcc -I/usr/local/gromacs/include yourfile.c -L/usr/local/gromacs/lib/whatever -lgromacs</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This means that the same header file can be used the same way when compiling libgromacs, so one gets some sanity for free. Otherwise, we'd also have to run some kind of script at "make install" time that copied the files and edited them, similar to what you have done with sed. Also, you'll have a harder time testing your code against multiple versions of GROMACS if you've hard-coded the path to the include files, perhaps in many places, directly in your code - the -I option is very much your friend.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Do also be aware that libxdrfile is a thing.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Mark<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Jul 6, 2016 at 4:53 PM Vladislav Martin <<a href="mailto:martin.vl@husky.neu.edu">martin.vl@husky.neu.edu</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Dear GROMACS developers,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>I am writing code in C utilizing the GROMACS 5.1.2 library. The purpose of the code is to read the binary data stored in GROMACS' XTC trajectory files into C data types for further analysis / manipulation of the data.<o:p></o:p></p></div><div><p class=MsoNormal>*NOTE*: In case this would be important information, I followed the <a href="http://manual.gromacs.org/documentation/5.1.2/install-guide/index.html#quick-and-dirty-installation" target="_blank">"Quick and Dirty Installation"</a> instructions for GROMACS 5.1.2 and all commands were executed in the terminal successfully.<o:p></o:p></p></div><div><p class=MsoNormal><br>Back to the C code. At the very top of my file, I include "/usr/local/gromacs/include/gromacs/fileio/xtcio.h" so that I may access the functions I need to read the XTC trajectory files. I ran into an odd error when attempting to compile my program. <o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>""<br>$ gcc -o read_trajectory read_trajectory.c -L /usr/local/gromacs/lib/x86_64-linux-gnu/ -lgromacs<br>In file included from read_trajectory.c:3:0:<br>/usr/local/gromacs/include/gromacs/fileio/xtcio.h:41:35: fatal error: gromacs/fileio/gmxfio.h: No such file or directory<br> #include "gromacs/fileio/gmxfio.h"<br> ^<br>compilation terminated.<br>""<o:p></o:p></p></div><p class=MsoNormal>I can fix this error by running a bash command that searches recursively through all header files in the "usr/local/gromacs/include/gromacs" directory and replaces 'gromacs/' (which only shows up in #include statements) with '/usr/local/gromacs/include/gromacs/' (or '/path/to/your/installation/gromacs/include/gromacs/'). I have included this bash command in case someone else experiences this compilation error and wants to fix it quickly:<br><br>'""<o:p></o:p></p></div><p class=MsoNormal>$ sudo find /usr/local/gromacs/include/gromacs/ -name '*.h' -type f -exec sed -i 's:gromacs/:/usr/local/gromacs/include/gromacs/:' {} \;<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'>""<o:p></o:p></p></div><div><p class=MsoNormal>Once I run this command, the program compiles successfully and I am able to run the resulting executable without any further errors.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>What confuses me is that this error could have been fixed when the GROMACS header files were created in the first place - I shouldn't have to fix the relative paths where the header files are supposed to look for & find the other GROMACS header files. From what I can tell (I read the <a href="http://manual.gromacs.org/documentation/5.1.2/dev-manual/includestyle.html" target="_blank">#include directives</a>), every header file is contained within the "/usr/local/gromacs/include/gromacs/" directory (or, more generally, "/path/to/your/installation/gromacs/include/gromacs/"). Within that directory there are modular directories that store related headers, like "fileio/". Knowing all of this, why does an #include statement referring to a GROMACS header file in that <u>same</u> directory say "gromacs/fileio/gmxfio.h" - which, as a relative path, would <u>never</u> point to the right directory - instead of "gmxfio.h" or "./gmxfio.h", which actually reflects this file hierarchy?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>In the end, my question is simple: did I miss something in the documentation that informs me on how to include GROMACS headers files properly so that I don't have to change the include statements myself? Otherwise, is this a syntax bug that will be fixed in later GROMACS versions?<br><br><o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Many thanks,<o:p></o:p></p></div><div><p class=MsoNormal>Vladislav Martin<br>Research Assistant<br>Center for Nanobiology and Structural Biology<o:p></o:p></p></div><div><p class=MsoNormal>Email: <a href="mailto:martin.vl@husky.neu.edu" target="_blank">martin.vl@husky.neu.edu</a><o:p></o:p></p></div></div><p class=MsoNormal>--<br>Gromacs Developers mailing list<br><br>* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br><br>* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br><br>* For (un)subscribe requests visit<br><a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<o:p></o:p></p></blockquote></div></div></body></html>