deepmodeling / deepmodeling/dpgen

[BUG] Mixed type format inconsistency in iter1 when training DPA-1 model

Open
#1,687 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
399
Forks
198
Avg merge
15d 11h
Merged PRs (30d)
44

Description

### Bug summary

When training a DPA-1 neural network potential using DP-GEN (v0.13.0) with TensorFlow backend, I encountered an error related to mixed type format inconsistency in iter1. While iter0 (including training-exploration-label stages) completed successfully, the training in iter1 failed due to data format mismatch. DP-GEN should automatically convert iter0.02.fp data to mixed type format, maintaining consistency with the initial data format.
In iter1, DP-GEN uses the standard format for iter0.02.fp data instead of maintaining the mixed type format from iter0, causing a format inconsistency error.

## Environment
- DP-GEN version: 0.13.0
- DeePMD-kit backend: TensorFlow
- Model type: DPA-1
- Data format: Multisystem mixed type

## Error Message
**AssertionError: if one of the system is of mixed_type format, then all of the systems should be of mixed_type format!**

Would appreciate any guidance on resolving this issue or confirmation if this is a bug that needs to be fixed.

### DP-GEN Version

0.13.0

### Platform, Python Version, Remote Platform, etc

_No response_

### Input Files, Running Commands, Error Log, etc.

No inputs.

### Steps to Reproduce

1. Initialize training data using multisystem mixed type dp data format
2. Run iter0 (completes successfully)
3. Enter iter1, where the error occurs

### Further Information, Files, and Links

The error suggests that DP-GEN is not properly carrying over the mixed type format configuration from iter0 to iter1's training data.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source files, tests, commands, input files, or error log are provided. Start by reproducing the iter0-to-iter1 workflow with DP-GEN 0.13.0, the TensorFlow backend, and multisystem mixed-type data, then trace where iter0.02.fp is prepared for iter1 training. Done means iter1 preserves the mixed-type format and no format inconsistency assertion occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, tensorflow
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.