Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
mabraham
regressiontests
Repository navigation
Code
Pull requests
Actions
Projects
Wiki
Security and quality
Insights
More
items
Files
Expand file tree
master
Breadcrumbs
regressiontests
/
README.kernel
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
21 lines (16 loc) · 1.18 KB
master
Breadcrumbs
regressiontests
/
README.kernel
Copy path
Top
File metadata and controls
Code
Blame
21 lines (16 loc) · 1.18 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
These kernel directories contain Gromacs input files that have manipulated to only
call one type of interaction kernel per directory. Each directory will call both
the potential-and-force kernel (at steps 0 and 2) as well as the force-only
kernel (at step 1).
There is one caveat: When you run in parallel or with >1 thread, the domain
decomposition interferes a bit with the manipulation above, which results in more
kernels being called. This is not a problem in normal executions when the kernels
pass the test, since the vast majority of interactions will have been computed
by the specific kernel the directory is named after.
If a kernel fails, start your debugging by executing the gmxtest.pl script using
only a single thread (-nt 1). This will make sure each kernel only causes a failure
in a single directory. If you have an error you your potentials, the error must
be in the potential-and-force kernel. Similar, if you get errors in your forces
already at step 0, this too indicates the error is in the combined kernel.
If all properties match the reference values at step 0, but give incorrect results
for step 1 (this will only be the forces), the error is in the force-only kernel.
You can’t perform that action at this time.