You are here

RosettaDesign error with Option file open failed

5 posts / 0 new
Last post
RosettaDesign error with Option file open failed

Dear users and developers,

I was running RosettaDesign and an error was reported as "[FILE]: src/utility/options/

[LINE]: 536


Option file open failed for: '/**/general_FD.flags'".  

This flag file worked on other server previously. Is this an error with compiling Rosetta or with the flag file? Could anyone please give some suggestions about how to fix this? Thank you so much.



Post Situation: 
Sun, 2020-04-19 01:56

How are you specifying your parameters?

The presence of asterisks in the filename indicates to me that you might have a wildcard escaping issue. Rosetta itself doesn't do any sort of wildcard expansion (or similar things like tilde expansion). It relies instead on the shell you're using to do the expansion. As such, if you pass in a filename to Rosetta like "/**/general_FD.flags", Rosetta expects there to be a directory off of the root directory with the literal name of "**" (two literal asterisks). If that's supposed to be a shorthand for something, it's the shell which is supposed to do the shorthand substitution.

This sort of thing happens most often when you move parameters into options files (Rosetta is the one reading the option file, and will not do the wildcard expansion), or when you add quotes to your commandline, and thus bypass your shell's expansion proceedures.

Sun, 2020-04-19 12:13

Thank you so much for your reply. Sorry I omiited the full pathway in the post. It was "

"[FILE]: src/utility/options/

[LINE]: 536


Option file open failed for: '/home/export/online1/systest/swjnu/mengzhang/BB/BBDisgn/general_FD.flags'". " Attached please find the Rosetta Crash .log file.

File attachments: 
Sun, 2020-04-19 19:01

Does the file /home/export/online1/systest/swjnu/mengzhang/BB/BBDisgn/general_FD.flags exist? Can it be opened (with that full path) in a text editor?

Also, what is the full command line you're using to launch Rosetta?

Mon, 2020-04-20 06:03

Problem solved. It was my mistake that I put the wrong path. It works now.

Thanks a lot. I really appreciate your help.

Tue, 2020-04-21 19:10