tedious managing of arguments in submission System (release 3)

[MTLehner]

Submission System Arguments

Problem:

The new submission system in branch (reworkSubSys2) PR #145 decreases the number of arguments for a job submission already drastically by using more members for all parameters that concern general submission and multiple jobs, but does not handle parameters for a single job. This leaves a lot of arguments in the actual submission function which are hard to reach when using preset modules

Proposed Solution

A small parameter class, storing all the relevant information for a job. This encapsulation should make job management easier and remove a lot of code duplication.

TODO

• [x] write class
  • [x] support all current arguments
  • [x] make backwards compatible
• [x] adjust submission functions
• [x] add Documentation
• [x] add test
• [x] make sure it's user friendly

[pultar]

The idea and implementation look good to me. It makes sense to have this class in PyGromosTools.

[MTLehner]

All tasks done and merged into release3 branch at merge #145