This issue is from a Codex global scan of the repository.
Several files in examples/CH4-lebesgue are committed as plain one-line path stubs instead of usable example inputs. This makes the example invalid when users copy it or run JSON validation.
Evidence:
|
../run/dp2.x-lammps-vasp/param_CH4_deepmd-kit-2.0.1.json |
|
../machine/DeePMD-kit-2.x/lebesgue_v2_machine.json |
|
../run/dp1.x-lammps-vasp/CH4/INCAR_methane |
For example, examples/CH4-lebesgue/init.json contains only ../init/ch4.json, so python -m json.tool examples/CH4-lebesgue/init.json fails immediately. The same pattern appears in the machine and parameter JSON files, and one stub points to a path under ../run/dp1.x-lammps-vasp/CH4/INCAR_methane that does not exist in the current tree.
Expected behavior: these should be real symlinks if the intent is to reference other examples, or regular files with valid JSON/POSCAR/INCAR contents.
This issue is from a Codex global scan of the repository.
Several files in
examples/CH4-lebesgueare committed as plain one-line path stubs instead of usable example inputs. This makes the example invalid when users copy it or run JSON validation.Evidence:
dpgen/examples/CH4-lebesgue/init.json
Line 1 in 7af5246
dpgen/examples/CH4-lebesgue/param_CH4_deepmd-kit-2.0.1.json
Line 1 in 7af5246
dpgen/examples/CH4-lebesgue/lebesgue_v2_machine.json
Line 1 in 7af5246
dpgen/examples/CH4-lebesgue/CH4.POSCAR
Line 1 in 7af5246
dpgen/examples/CH4-lebesgue/INCAR_methane
Line 1 in 7af5246
For example,
examples/CH4-lebesgue/init.jsoncontains only../init/ch4.json, sopython -m json.tool examples/CH4-lebesgue/init.jsonfails immediately. The same pattern appears in the machine and parameter JSON files, and one stub points to a path under../run/dp1.x-lammps-vasp/CH4/INCAR_methanethat does not exist in the current tree.Expected behavior: these should be real symlinks if the intent is to reference other examples, or regular files with valid JSON/POSCAR/INCAR contents.