Restructuring of rti_stub.py to use a configuration file

[wedi]

Dear Professor Patwari,

to foster the separation of concerns in your script rti_stub.py I’d like to propose a change to incorporate the use of a configuration file. This change would ease the process of keeping track of settings for certain setups without any duplication of the actual code.

A real life use case: working on my bachelor thesis I’m going to experiment with your rti calculation and different sensor setups. Having this change I could easily keep all data regarding a certain experiment (rti settings, sensor coordinates, raw data and output) self contained for later reference and replay.

My idea is to implement this feature using the Python built-in configparser module which uses the intuitive ini format well known on windows systems.

As this idea would require more changes to the codebase than my small pull request you accepted the other day, I wanted to discuss this idea in advance instead of just making a big pull request.

If you agree, I would start with making the script compatible with Python 3 which is the version I am using for my toolset.
As follow-up one could think about command line arguments to overwrite certain values on a case by case basis.

With kind regards,
Dirk Weise

[npatwari]

Dirk Weise,
I am so sorry I missed your message. That's a great idea. I really meant rti_stub.py to be replaced by something better in terms of managing multiple experiments, but I never got around to it. If you did this, I think it would be a great contribution. If you didn't end up doing this because of my lack of response, my apologies.
Regards,
Neal