Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GROMACS GROMACS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 317
    • Issues 317
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 100
    • Merge requests 100
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GROMACS
  • GROMACSGROMACS
  • Issues
  • #2104
Closed
Open
Issue created Jan 26, 2017 by Paul Bauer@acmnpvMaintainer

gmx order -sl indexing out of bounds - Redmine #2104

Archive from user: Edgar Galicia

I am having problems when running “gmx_order” utility. When I give the command -sl to divide the box into slices the utility works properly only for certain values and for others not.

If option -sl 200 is selected the error presents but if a greater number as 250 is put in, the utility runs without any problem.

Hope to find a solution in the meanwhile by myself.

(from redmine: issue id 2104, created on 2017-01-26 by gmxdefault, closed on 2017-03-17)

  • Changesets:
    • Revision 48d68b70 by David van der Spoel on 2017-02-03T21:42:30Z:
Fixes SEGV in gmx order.

gmx order used a cumbersome floating point method to compute
an index in a histogram leading to index -1. The present code
is simpler and robust, in fact the old code was likely wrong.

Fixes #2104

Change-Id: Ic3c15917eebe6c4964cd5cb053dfa4f05781cb73
  • Uploads:
    • nvt3mix.tpr
    • order.ndx
    • nvt3mix.trr
Assignee
Assign to
Time tracking