Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Plumed AlphaFold
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Martin Kurečka
Plumed AlphaFold
Commits
24cd194a
There was an error fetching the commit references. Please try again later.
Commit
24cd194a
authored
7 years ago
by
Gareth Tribello
Browse files
Options
Downloads
Patches
Plain Diff
Added description of bug fix to changelog
parent
264af882
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGES/v2.3.txt
+1
-0
1 addition, 0 deletions
CHANGES/v2.3.txt
with
1 addition
and
0 deletions
CHANGES/v2.3.txt
+
1
−
0
View file @
24cd194a
...
...
@@ -158,6 +158,7 @@ See branch \branch{v2.3} on git repository.
- Fixed bug in \ref HBONDS that used to apear when you used DONORNS and ACCEPTORS with same numbers of atoms
- Fixed bug in \ref DISTANCES that appears when using BETWEEN and link cells.
- Prevented users from causing segfaults by storing derivatives without LOWMEM flag. In these caess PLUMED crashes with meaningful errors.
- Fixed bug in \ref HISTOGRAM that causes nans when using KERNEL=DISCRETE option
For developers:
- plumedcheck validation has been made stricter. All the checks are now described in the developer manual.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment