What steps will reproduce the problem?
1. Take the newest build from the repo
2. Take the configuration advice from the default-config.properties and specify:
instrument.micro.options.timingInterval=200ms (default is 500ms)
What is the expected output? What do you see instead?
I can see the that my parameter gets taken up when the config is loaded but it
also loads the default value (500 ms) of the same (runtime) property.
Configuration:
...
instrument.micro.runtime.timingInterval = 200ms
...
instrument.runtime.options.timingInterval = 500ms
...
At runtime only the runtime option is used. I can see that because I added the
following line to the constructor of RuntimeWorker:
System.out.println("Worker options: " +
Arrays.deepToString(workerOptions.entrySet().toArray()));
Only if I specify "instrument.runtime.options.timingInterval" the value gets
carried over to the experiment. So what is the purpose of the
"instrument.micro.runtime.timingInterval" option?
There is very little documentation on that.
What version of the product are you using? On what operating system?
Latest repo version which builds as caliper-1.0-beta. Note, the pre-packaged
version on the website does not work with the latest annotation code.
I'm running on Mac OS X Mavericks.
Please provide any additional information below.
Original issue reported on code.google.com by sebastia...@gmail.com on 28 Jul 2014 at 8:38
Original issue reported on code.google.com by
sebastia...@gmail.comon 28 Jul 2014 at 8:38