Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Using the DP model to predict the energy of each frame structure in the LAMMPS trajectory

Open
#609 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by reproducing the DP energy prediction with the manually spliced LAMMPS trajectory containing clusters with differing atom counts or element types, and capture the complete error output. Compare that behavior with predictions from separate cluster trajectories; done means the requested batch workflow is defined and its behavior is covered for the reported trajectory structure.

Written by the indexing model from the issue text.

Description

enhancement lammps
Summary

I now have a lambps trajectory that contains many structures, but these structures are not the original lambps trajectory structure, but some extracted molecular clusters. Therefore, the number of atoms or types of elements in each frame may be different, but overall they are several elements contained in the original trajectory. But for this manually spliced lambps trajectory, the model's predicted code will report an error. One method is for me to extract each molecular cluster into a separate lambps trajectory, write a script to read each file, and achieve energy prediction, but the efficiency is too slow because I have tens of thousands of molecular cluster structures.

DeePMD-kit Version

2.1.5

TensorFlow Version

2.8.0

Python Version, CUDA Version, GCC Version, LAMMPS Version, etc

No response

Details

1091706144749_ pic
1101706144789_ pic

Dominant language
Python
Stars
254
Forks
159
Avg merge
8d 3h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deepmodeling/dpdata

All issues in deepmodeling/dpdata

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.