I have downloaded and built haddock2.5 on my University’s supercomputer. I followed the installation documentation, but the cns does not seem to be compatible with my system. It gets built and i changed all the local paths etc, but when I try to run the executable I get:
[user@node067 source]$ ./cns_solve-2411121204.exe
%SETFPEPS Machine epsilon determined to be 0.494-323
%SETFPEPS error encountered: Machine epsilon value is too small
(CNS is in mode: SET ABORT=NORMal END)
WARNING: program encountered a fatal error.
However, in interactive mode, program execution
will continue. Proceed at your own risk.
Program will stop immediately.
============================================================
Maximum dynamic memory allocation: 0 bytes
Maximum dynamic memory overhead: 0 bytes
Program started at: on
Program stopped at: 13:04:54 on 12-Nov-2024
CPU time used: 0.0065 seconds
============================================================
Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
This error propogates to the implementation of haddock as the cns is linked to this executable. I have contacted my hpc admin and they have not been able to locate the issue as well. Is there any workaround for getting a working cns executable?
I got it working. What ended up solving this was copying the .f files from cns1.3 to the software/cns-1.3/source rather than in the software/cns-1.3/ directory so that they are read when making the software. Additionally just running “make install” rather than “make install compiler=gfortran” kept the make from using the gfortran in my anaconda python module that was loaded and used the gcc/9.3.0 as needed.
But when I try to run the calculation it yelds as follow. Ir indicates a problem in the executable but without point exactly what it is.
[2025-06-08 16:28:48] PDB_FILE1 protein1.pdb
[2025-06-08 16:28:48] PROT_SEGID_1 A
[2025-06-08 16:28:48] PDB_FILE2 protein2.pdb
[2025-06-08 16:28:48] PROT_SEGID_2 B
[2025-06-08 16:28:48] PROJECT_DIR /home/egil/testesHaddock/a4b1-test
[2025-06-08 16:28:48] RUN_NUMBER 1
[2025-06-08 16:28:48] Looking for existing files
[2025-06-08 16:28:48] There is a problem with the CNS executable defined in run.cns:
[2025-06-08 16:28:48] HADDOCK stopped
[2025-06-08 16:28:48] ##############################################################################
[2025-06-08 16:28:48] Finishing HADDOCK
[2025-06-08 16:28:48] Au revoir. Tot ziens. Bye bye.
I compiled cns using a conda env with gcc 9.3 .
I copied the files from ~/haddock2.5-2024-12/cns1.3 to ~/cns_solve_1.3
Ok - that looks promising. Next question is then how are you running HADDOCK? which queue command is defined in run.cns?
And if it fails, what is the content of the begin directory? Any out files in there? Check for error messages in those files (start at the end of the file)
At first I was using this ( I am assuming you are talking about that)
{===>} queue_1=“bash”;
{===>} cns_exe_1=“/home/egil/PROGRAMAS/cns_solve_1.3/intel-x86_64bit-linux/bin/cns”;
{===>} cpunumber_1=20;