short style parameters not working in .cfg files
cliff-bohm opened this issue · 7 comments
cliff-bohm commented
"NameSpace::Catagory-Parameter = value" style formatting (aka command line style parameter formatting) does not work in .cfg files. This does work on command line.
i.e.
% BRAIN
brainType = CGP
+ sheep::
brainType = Markov
- #sheep::
+ wolf::
brainType = Wire
+ smart::
brainType = LSTM
- #smart::
- #wolf::
should be idetical to:
%
BRAIN-brainType = CGP
sheep::BRAIN-brainType = Markov
wolf::BRAIN-brainType = Wire
wolf::smart::BRAIN-brainType = LSTM
see wiki for more examples:
github.com/Hintzelab/MABE/wiki/Parameters-Name-Space
cgnitash commented
Seems to be working just fine. You need a + before you open a namespace. I assume your + and - got turned into bullets.
cgnitash commented
Show the error you got, if it actually didn't work, and the exact settings that caused it.
cliff-bohm commented
if you create a settings.cfg file with these contents:
%
GLOBAL-updates = 90
the result is:
$ x64/Release/MABE.exe -f settings*
Error: unrecognised line
GLOBAL-updates = 90 in file settings.cfg
See https://github.com/Hintzelab/MABE/wiki/Parameters-Name-Space for correct usage.
cgnitash commented
Aah I see.
Is there any concept of nested categories? i.e, does it make sense to parse something like,
% AAA
BBB-val = 1
into AAA-BBB-val =1
cliff-bohm commented
No, because in reality, the parameter name is a CATAGORY and a (local) NAME
joined with a '-' dash.
Catagories exist primarily to make sure that we don't need to worry about
parameter name conflicts.
Secondarily, they provide a method to organize .cfg files.
When I want to make sub-categories, I simply create category names to
represent this.
e.g.
GENOME
GENOME_CIRCULAR
GENOME_MULTI
…On Sun, Apr 29, 2018 at 6:50 PM, cgnitash ***@***.***> wrote:
Aah I see.
Is there any concept of *nested* categories? i.e, does it make sense to
parse something like,
% AAA
BBB-val = 1
into AAA-BBB-val =1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#208 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AG78esHRDBYT6hjevZT9enop-0-OtFb3ks5ttkO_gaJpZM4Tre8h>
.
--
Cliff Bohm - Evolving Systems Technologist
BEACON Center for the Study of Evolution in Action
Michigan State University
cliff-bohm commented
nice! I'll take a look tomorrow morning.
btw, I'm having trouble with parseCSVLine using a non ',' separator.
any idea what might be going on? I'm a bit out of my depth (i.e. my normal
tricks are not working).
…On Sun, Apr 29, 2018 at 7:02 PM, cgnitash ***@***.***> wrote:
Ok, in that case #209 <#209> should
solve the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#208 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AG78ejVsXjudkYzeYauYc76lVSEa0cXIks5ttkafgaJpZM4Tre8h>
.
--
Cliff Bohm - Evolving Systems Technologist
BEACON Center for the Study of Evolution in Action
Michigan State University