Mailing Lists

    Version as of 16:20, 22 Sep 2019

    to this version.

    Return to Version archive.

    View current version

    To facilitate the communication between users and developers of GROMACS we have created different mailing lists that you can subscribe to. The lists are also archived on this web site, so you can browse previous messages for a solution to your question or problem. It might be a good idea to Search the mailing list archives before posting a new question!
    We strongly request you to post any questions to the appropriate e-mail list instead of mailing the developers directly! We do not have time for personal guidance for all users. Please refrain from mailing the developers unless your question is directly related to our published research. In addition when you use the mailing lists, more people will read your message and help you solve the problem faster, and the next time someone encounters the same situation they will be helped by the archived discussion! 
    The three mailing lists (see the menu items on the left) have slightly different purposes, and you might not be interested in subscribing to all of them:
    • gmx-announce has extremely low traffic and will only contain information from the GROMACS crew. Users can not post to this list, but we strongly recommend everyone to subscribe to it, so you get notice about new versions and severe bugs.
    • gmx-users is the normal discussion forum for installation, usage and all other questions not related to development. .
    • gmx-developers is the place for developers. Post all your questions, suggestions and code impromevents here!
    • gmx-revision is a private list for the developers where information about changes to the code are stored for use in creating lists of additions and bug fixes upon releasing new versions.
    • eden-users is the discussion forum for installation, usage and all other questions related to the EDEN crystallography software.

    Mailing List Etiquette

    When posting to the emailing list, it is important to remember that those on the emailing list are just fellow users of the software. They are not paid to answer your question. With that in mind, some things that will assist in improving the chance that you get some helpful response to your problem are:

    • use an informative title: Because people are not paid to answer questions, and have limited time, many experienced users only browse titles looking for topics they are intrigued by. If your title is, "This may be it, but what to do?" or similar, odds are many people won't bother reading it.
    • attempt to find the solution to the problem before posting to the emailing list, and demonstrate this by showing the other subscribers what you tried and why it didn't work. If you demonstrate that you're interested in helping yourself, you're much more likely to stimulate someone else to want to help you.
    • provide as much detailed information as possible on the problem. This can include the actual command line that was executed, an actual copy of the error produced, parameter files utilised by the script, log files generated etc. It is not sufficient to simply say something like "mdrun crashed, how can I solve that problem?" It is also better to provide actual copy-and-paste information, instead of filtering things through your brain and memory. If your understanding was good, then you might not be having this problem; accordingly, people trying to help with your problem are not all that interested in your deductions or assumptions... they want the facts.
    • do not attach Word documents, RAR,HQX,SIT,ACE or other weird archives (use tar and/or gzip for preference - it's your audience's convenience which matters, not yours), trajectory files, structure files, run input files, log files or anything else bulky. An .mdp file can be appropriate. If you need to supply a picture to describe what is going on, then please upload it to a web service like photobucket and provide a URL to the list.
    • do not suggest the problem is a bug unless you're really sure of yourself, i.e. you can almost post a code patch. What are the odds of a new-ish user being the first ever to find and report a particular bug, against the odds of that new-ish user doing something wrong, not reading the documentation, or not understanding a concept?
    • when you've solved the problem, please consider posting a reply to the list detailing what was wrong, your solution and how it worked. Not only might this help people in the future, but it might teach you more about the problem and the solution. However, it is overkill to reply to every email in response to yours to the list, merely expressing your thanks.

    A very good article for anyone who may be asking or answering questions on an emailing lists to read is How To Ask Questions The Smart Way.


    Important information

    To avoid spam and other commercial postings, the mailing list software checks your return address and only accepts postings from subscribed members. For this to work, it is important that you subscribe with your mail address exactly as it appears in the headers of the mails you send. If you don't, you will get a message about only subscribed members being allowed to post.


    If you don't like to have your mailbox flooded with messages you can choose a digest alternative and only get one larger mail per day. Please don't include the entire digest if you reply!
    Page last modified 14:39, 25 Sep 2009 by rossen