# AbinitioRelax - Error with flags

2 posts / 0 new
AbinitioRelax - Error with flags
#1

Hi folks,

I am attempting to run the AbinitioRelax application and when I use the -abinitio:relax option it returns an error.

Here are my commands: /home/xxxx/Documents/rosetta/main/source/bin/AbinitioRelax.default.linuxgccrelease @flags

where flags file contains:

-in:file:fasta ./t000.fasta
-in:file:frag3 ./aat000_03_05.200_v1_3
-in:file:frag9 ./aat000_09_05.200_v1_3
-psipred_ss2 ./t000.psipred_ss2
-abinitio:relax
-nstruct 1
-abinitio::increase_cycles 10
-abinitio::rg_reweight 0.5
-abinitio::rsd_wt_helix 0.5
-abinitio::rsd_wt_loop 0.5
-use_filters true

-out:file:silent ./REn_silent.out

I then get an error:

File: src/utility/options/OptionCollection.cc:239
ERROR:

File: src/utility/options/OptionCollection.cc:443
ERROR:

File: src/utility/options/OptionCollection.cc:1324
Did you mean:
-abinitio:relax
-cm:hybridize:relax
-loops:relax
-mp:mutate_relax:relax
-relax

Exception :

Does anyone have any suggestions? I am rather stuck at this point as the source code contains the relax option for abinitio.

Thank you.

Post Situation:
Wed, 2018-11-21 17:36
jmschu

The first thing I'd check is if you have -relax by itself somewhere (versus the full -abinitio:relax) -- That's the sort of error message you see when you have a option (like -relax) without any of the parent categories, and where the option is ambigious.

The second thing I might try is running the options file through the dos2unix program. DOS-style line endings (used with Windows) have extra characters which mess up programs (like Rosetta) expecting Unix-style line endings.

A third thing to try is to remove any blank lines in the options file. This is a bit of a long-shot. I'm a little confused as to why the option which was not found in top level context is not being printed. I'm wondering if it might be because there's some issue with a blank line throwing the options parser. (It should be okay with blank lines, and I'm not sure where the relax is coming from, but if nothing else seems to be working, that might be worth a shot.)

As a final test, you can try re-typing (don't copy/paste!) the options into a new text file using your favorite Mac/Unix (not Windows) plain-text editor (not a word processor).  gedit and nano are popular ones if you're not familiar with vim or emacs.  The rationale behind this is that there may be some non-printing character or extended-set character in the option file which is messing things up. By retyping in a plain-text editor, you avoid inserting any such characters.

Fri, 2018-11-23 07:59
rmoretti