-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qcxms #421
Conversation
@zargham-ahmad please add a description for this PR shortly outlining the tool added and what was done for documentation purposes. |
done |
description_template: "{{ tool_name }} tool from the QCxMS package" | ||
suite: | ||
name: suite_qcxms | ||
description: tools from QCxMS are used for molecular geometry optimization and in silico calculation of mass spectra using quantum chemistry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tools are only for spectrum prediction
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
qcxms is failing for more trajectories with the following error but the compiled binary from qcxms github seems to be working fine
|
Hi, the conda forge version of the qcxms is failing with the below error. @bgruening @JayTheDog, do you have any idea? free(): invalid pointer Program received signal SIGABRT, Aborted. Program received signal SIGABRT: Process abort signal. Backtrace for this error: Program received signal SIGABRT, Aborted. |
At what point does this happen? I currently don't have the capability to check whether this problem occurs only for some trajectories, or for the entirety of the runs. @gorges has the capabilities for this, we should make him part of this conversation |
@zargham-ahmad you mentioned that it works with a single trajectory but not multiple, is that right? |
@JayTheDog @bgruening @gorges97 I think it is related to the compilation for conda-forge. I ran now 3 trajectories locally and the tool peaked at 61GB memory consumption using the binary from conda forge - probably some optimizations are not available or the compiler flags are not passed correctly? Or do you think the difference comes from the absence of the intel mkl and blas libraries? |
https://github.com/conda-forge/qcxms-feedstock/blob/main/recipe/build.sh What is missing here? |
Co-authored-by: Helge Hecht <[email protected]>
This PR includes the following: #419
TODO: