Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow ntypes_model > ntypes_data (fix #261) #296

Merged
merged 1 commit into from
Nov 24, 2020

Conversation

njzjz
Copy link
Member

@njzjz njzjz commented Nov 20, 2020

Usually, the type number of the model should be equal to that of the data
However, nt_model > nt_data should be allowed, since users may only want to
train using a dataset that only have some of elements

Usually, the type number of the model should be equal to that of the data
However, nt_model > nt_data should be allowed, since users may only want to
train using a dataset that only have some of elements
@njzjz njzjz linked an issue Nov 20, 2020 that may be closed by this pull request
@amcadmus amcadmus merged commit 5d5b1ff into deepmodeling:devel Nov 24, 2020
@njzjz njzjz deleted the ntypes branch February 3, 2021 06:21
gzq942560379 pushed a commit to HPC-AI-Team/deepmd-kit that referenced this pull request Sep 1, 2021
njzjz pushed a commit to njzjz/deepmd-kit that referenced this pull request Sep 21, 2023
fix the bug of the units of taut and taup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ntypes error
2 participants