Util.py:
- introduced calculation of time per 1000 events for different job classes, where a job class is based on the G4DS configuration
- no electronics simulation currently included
- this function is called in MCTuningBase::NJobs()
- another utility function: fermigrid() to determine based on the hostname, whether I submitted to fermigrid or running locally for testing. Based on that environmental variables are set in main_script.py
- this file will likely expand in the future, housing more and more utility functions.

MCTuningBase.py:
- simple mode with few arguments in the constructor to get the configuration and the total number of jobs the parameter scan has to be split up into (this depends on the number of parameters, events and what simulation. This simple configuration is called in submit_jobsub.py, whereas the full configuration is called in main_script.py
- a jobindex variable was added, so that a parameter scan can be split in different jobs at Fermigrid (using the jobsub -N option)
- considerable changes were necessary to accomodate this splitting option, including the introduction of the self._valuelist_all, which is the list of values for the whole parameter scan, out of which then the _valuelist for this particular job is calculated using jobindex.
- the output of the analysis chain cannot be a directory it seems. jobsub complained. -> this was addressed in loop_1par()
- introduced NJobs(self)
pick up the  environmental variable and provide it to the constructor of the MCTuning-class family (other than MCTuning itself is not yet adapted). use Util.fermigrid() to determine whether this job is actually running on fermigrid or not.
- adapted the jobsub submission string: removed the -T (testing) and added the -N
- call the MCTuning class with a reduced set of arguments to determine the number of jobs to be submitted
- create the output directory in /ds50/data/