Skip to content

Compilation Error When Enabling NEP Calculation in ABACUS v3.9.0.21 #6800

@xuan112358

Description

@xuan112358

Describe the bug

Describe the bug

When compiling the latest version of ABACUS (v3.9.0.21) with NEP calculation enabled via the toolchain, a compilation error occurs due to missing ewald.h header file.

Error Message

In file included from /home/mhchen_pkuhpc/mhchen_coe/lustre3/software/abacus-max/abacus-develop-v3.9.0.21/source/source_esolver/esolver_nep.h(6),
                 from /home/mhchen_pkuhpc/mhchen_coe/lustre3/software/abacus-max/abacus-develop-v3.9.0.21/source/source_esolver/esolver.cpp(21):
/home/mhchen_pkuhpc/mhchen_coe/lustre3/software/abacus-max/abacus-develop-v3.9.0.21/toolchain/install/NEP_CPU-main/include/nep.h(19): catastrophic error: cannot open source file "ewald.h"
  #include "ewald.h"
                    ^

compilation aborted for /home/mhchen_pkuhpc/mhchen_coe/lustre3/software/abacus-max/abacus-develop-v3.9.0.21/source/source_esolver/esolver.cpp (code 4)

Possible Root Cause

It seems the NEP repository has undergone recent changes that added the ewald.h file, but the ABACUS interface (which includes nep.h from the NEP repo) has not been updated accordingly to adapt to these changes.

Expected behavior

No response

To Reproduce

  1. Obtain the latest ABACUS version (v3.9.0.21)
  2. Configure the toolchain to enable NEP calculation with intel
  3. Start compiling Abacus
  4. Encounter the above compilation error

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

  • Verify the issue is not a duplicate.
  • Describe the bug.
  • Steps to reproduce.
  • Expected behavior.
  • Error message.
  • Environment details.
  • Additional context.
  • Assign a priority level (low, medium, high, urgent).
  • Assign the issue to a team member.
  • Label the issue with relevant tags.
  • Identify possible related issues.
  • Create a unit test or automated test to reproduce the bug (if applicable).
  • Fix the bug.
  • Test the fix.
  • Update documentation (if necessary).
  • Close the issue and inform the reporter (if applicable).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions