Skip to content
Discussion options

You must be logged in to vote

This means that the nnp-scaling executable could not be found in your executable path when AML tried to launch it. It is reported by /bin/sh because AML runs these commands in a shell, so it launches /bin/sh which then tries to launch nnp-scaling. Here, that step failed. The failure reported in the Python traceback shows that AML was not able to read the output. Better error reporting is eventually coming to the released version of the code.

You can address this by checking your environment and making sure nnp-scaling (and other nnp-* programs) can be launched in the same environment that AML is running in.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by OndrejMarsalek
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants