MantisBT - Rosetta
View Issue Details
0000343Rosetta[All Projects] Input Handlingpublic2014-06-26 14:112014-06-26 14:46
All platformsAnyAny
antibody_designer.linuxclangrelease -in:path antibody_designer @flags
0000343: Options file do not use -in:path directory locations
Options file loading should use set paths for locating files.
Use a cmd line where your flags file is in a different directory; pass -in:path to that directory
No tags attached.
Issue History
2014-06-26 14:11jadolfbrNew Issue
2014-06-26 14:11jadolfbrStatusnew => assigned
2014-06-26 14:11jadolfbrAssigned To => jadolfbr
2014-06-26 14:46rmorettiNote Added: 0000349

2014-06-26 14:46   
This is a little cart-before-the-horse, as you would need to be able to use the option system before/when you're actually loading the options.

I guess it might be possible, so long as you specify -in:path on the command line before you specify the options file (so "antibody_designer.linuxclangrelease -in:path antibody_designer @flags" might be workable, "antibody_designer.linuxclangrelease @flags -in:path antibody_designer" wouldn't be, at least without changing options loading semantics.)

To make the first case work, you'd probably have to alter OptionCollection::load_option_from_file() in src/utility/options/ to specifically introspect the -in:path option and uses those paths as fallbacks. The general -in:path loading mechanism that usually happens through izstream won't work, as that doesn't get set until the options loading is finished.