Properties File Handling

[GoogleCodeExporter]

Properties file housekeeping.  Now that we are running lots of experiments we 
have the challenge of keeping all of the properties files organized.  The 
simplest/cleanest thing I can think of is that it would be handy if we could 
append a number after the filename that is ignored for parsing purposes.  So, 
we could have a repository folder with “rhythm.properties-1”  
“rhythm.properties-2” “rhythm.properties-3” etc.  Then when we want to 
run a particular one, we can just move that file into the correct directory and 
the program will use those properties.  So all we need terms of a feature is 
just the “ability” to ignore a number after the “rhythm.properties” 
part of the file name. 

Original issue reported on code.google.com by guse...@datamininglab.com on 2 Oct 2013 at 3:32

• Blocking: #13

[GoogleCodeExporter]

I'm guessing that the requested change may already be the case . . . we need to 
verify this.

Original comment by guse...@datamininglab.com on 2 Oct 2013 at 3:33

[GoogleCodeExporter]

Original comment by guse...@datamininglab.com on 2 Oct 2013 at 4:27

• Now blocking: #13

[GoogleCodeExporter]

Original comment by guse...@datamininglab.com on 2 Oct 2013 at 4:30

• Added labels: Milestone-Transition

[GoogleCodeExporter]

We can add an ignore for filename parsing, however it might make things easier 
for future use if we add the properties file as something to specify on the 
setup screen. 

This would allow a user to browse to wherever the properties file is being 
kept, thus avoiding manually moving properties files for each experiment. 

Original comment by zach.br...@datamininglab.com on 9 Oct 2013 at 6:48

• Changed state: Need_Info

[GoogleCodeExporter]

That is a great suggestion!  It would be helpful if we could include a number 
in the properties file (i.e. "rhythm.properties-1") as well as a "properties 
file specification appendage" (or something with a better name!) on the setup 
screen.  So, for example when we enter things like the subject number, etc. 
there would be another box for "Properties file ID" into which we would enter 
values like "1" or "23" and then the program would pull the properties from 
"rhythm.properties-1" or "rhythm.properties-23" 

Original comment by schutz.m...@gmail.com on 18 Oct 2013 at 1:08

[GoogleCodeExporter]

Zach -

Let's use 3 fields for this, wrapped in a box with name "Properties File":
1) binary option (radio buttons) --> Directory: () Use Data Directory  () Use 
Specified Directory
2) file browse field (text + browse button) enabled by second option above --> 
[         ] [Browse...]
3) text field --> Properties File Version: [      ]

For the 3rd item, file names would satisfy: [experiment 
name].properties-[version], where "version" could be any text

Original comment by guse...@datamininglab.com on 18 Oct 2013 at 1:27

[GoogleCodeExporter]

Original comment by guse...@datamininglab.com on 18 Oct 2013 at 1:27

• Changed state: Accepted

[GoogleCodeExporter]

Properties file selection added in r191 - r195 builds. 

Selection through new panel on setup screen. Loads a default properties file if 
one is not specified. 

Original comment by zach.br...@datamininglab.com on 17 Mar 2014 at 6:33

• Changed state: Fixed