An issue about the Abacus Document 'Easy Installation' part

[RenguangLiu]

Details

During my installation experience, I directly typed the codes mentioned in the document. And there was a mistake when I tried to use mpirun -n 4 abacus.

--------------------------------------------------------------------------
mpirun was unable to find the specified executable file, and therefore
did not launch the job.  This error was first reported for process
rank 0; it may have occurred for other processes as well.

NOTE: A common cause for this error is misspelling a mpirun command
      line parameter option (remember that mpirun interprets the first
      unrecognized command line token as the executable).

Node:       qhdx080-LEGION-REN7000K-26IRB
Executable: abacus
--------------------------------------------------------------------------

Later, I found that I needed to change the 'my-install-dir' with my own install location of abacus. At this part, it may be more clear to tell the reader where we can find the 'my-install-dir' location directly. Maybe a little example or a more obvious flag.

Run[](https://abacus.deepmodeling.com/en/latest/quick_start/easy_install.html#run)

If ABACUS is installed into a custom directory using CMAKE_INSTALL_PREFIX, please add it to your environment variable PATH to locate the correct executable.

export PATH=/my-install-dir/:$PATH

Have you read the online manual http://abacus.deepmodeling.com/en/latest/

• Yes, I have read the online manual.

Task list for Issue attackers (only for developers)

• Identify the specific section of the documentation with the issue.
• Investigate the issue and determine the root cause.
• Research best practices and potential solutions for the identified issue.
• Update the documentation to address the issue, following the suggested improvement.
• Ensure the updated documentation adheres to the project's documentation standards.
• Test the updated documentation to ensure it is clear and accurate.
• Review and incorporate any relevant feedback from users or developers.
• Publish the updated documentation and notify the issue reporter.