ConfBuster-Macrocycle-Linear-Sampling.py not working

[Zax0NL]

I want to use ConfBuster to perform a macrocycle conformational sampling of a series of macrocyclic molecules. I installed Confbuster as described and wanted to test it running the examples.
The first step works fine after some fiddling with putting the script in my $PATH and correctly produces the .mol2 file
ConfBuster-Single-Molecule-Minimization.py -i macro-1w96.pdb
Then i decided to run the second step
ConfBuster-Macrocycle-Linear-Sampling.py -i macro-1w96.mol2 -n 5 -N 5 -r 0.5
which seems to do some calculation and completes the script without major errors but does not product any files except for the follow-macro-1w96.py.

full terminal output: https://pastebin.com/RDDyUGkB

running Ubunto v20.04

[subject-am]

I want to use ConfBuster to perform a macrocycle conformational sampling of a series of macrocyclic molecules. I installed Confbuster as described and wanted to test it running the examples. The first step works fine after some fiddling with putting the script in my $PATH and correctly produces the .mol2 file ConfBuster-Single-Molecule-Minimization.py -i macro-1w96.pdb Then i decided to run the second step ConfBuster-Macrocycle-Linear-Sampling.py -i macro-1w96.mol2 -n 5 -N 5 -r 0.5 which seems to do some calculation and completes the script without major errors but does not product any files except for the follow-macro-1w96.py.

full terminal output: https://pastebin.com/RDDyUGkB

running Ubunto v20.04

I hope you have succeeded as of now 😅 From your output, it seems the problem is that you're working with Python 3, instead of the 2.7 release. Try creating an environment with Python 2.7 and run the scripts there.

After trying it directly on my molecule and not having any results after running ConfBuster-Macrocycle-Linear-Sampling.py besides the file "Follow-XXX.py" and coming here, I thought we had the same issue - except mine didn't seem to work any calculations and the stdout was nothing like yours...
So, I ran the same test run as you and it worked fine. After actually reading your output, I found out your errors were tracing back to /usr/lib/python3/. Still it helped me come to the conclusion that my "problem" was actually not having any cleaving points, otherwise the script ran fine.