Document scaling of scenarios with change of situation_length

[StephanieKemna]

This might be user error .. but currently if you change situation length in encounter_settings.json, it does not properly scale the whole scenario.
To do:

• Check paper and code to understand how to change the operational range of each scenario (e.g. change it from a 5nm scenario to a 1nm scenario), and either fix or document.

[StephanieKemna]

What I believe influences this:

• in input .json files, change the time of encounter (encounters>vectorTime)
• in encounter_settings.json file, change the total situation length time, and evolve_time

To fix:

1. Update documentation
2. Edit (make new issue): make it possible to specify operational range (in time) as a param in generation

[tomarnepedersen]

I have merged what was done to dev. Now making a new branch based on dev to finalize the documentation around this.

[StephanieKemna]

If you merged dev into this branch, then there was no need to make a new branch? :)
Anyway, will look at your new branch then!