Feature #349 adapt config after interviews

The idea is to have a simulation time around one long work day, as non-organisation helpers tend to go home or at least sleep at night and organisation helpers use other means of communication.

As non-organisation helpers spend a lot of time at one location, more events make sense as well as longer stays at events. The event file is based on the MediumDurationManyEvents file, with new start times, which are just random numbers between 0 and the scenario end time.

The area size seems to be about correct. Realistically, the area would change over time, i.e., because parts become flooded.

Ideally, we would have longer distances by car and more events where people continously help with small breaks.

SonarQube analysis reported no issues.

SonarQube analysis reported no issues.

added 1 commit

• d364771a - Increase help time from half an hour to 2h

Compare with previous version

SonarQube analysis reported no issues.

changed the description

added Needs Review Needs wiki documentation labels

assigned to @bheymann

added Needs Changes label

What is WIP about this still?

removed Needs Review label

I have tried to test out this scenario, and I'm not sure about the ranges used here. The event and safety ranges seem pretty large, while the max_range is not that large for some events so it's hard for hosts to detect them. What do you think?

Mhm, I checked how they were generated. The event_range is randomly between 0 and 300, the safe_range is twice the event_range, the max_range is three times the event_range.

My suggestion would be to keep the event_range as is (this is where all the local helpers will go, let's not make it too small). The safe_range could be the event_range plus a random number between 0 and 150. The max_range should be the safe_range times 5 or 6.

I would like to keep the resizing according to the "inner circle"

I'd be fine with event ranges between 0 and 300 (or even 150, as we look at the radius here, don't we?). However, some of the events here have a larger range. Safe_range sounds good.

However, I'm still not happy with the max_range. I think it should be possible to know about an event at least if you're one km away. With the event range as it is, a factor doesn't make sense then (e.g. event range of 10 m --> 100 times to get max range, doesn't scale well for 300m --> 30km...). Maybe make this constant + factor * event_range?

Oh, yeah, I overlooked, it's 300 times intensity times random value between 0 and 1. That can get really large. I'd say 50 times intensity plus an random number between 0 and 200?

I'd say for max_range 800 m plus a random value until 3 times event range?

added 1 commit

• 9f79e8bd - Make realistic scenario default scenario in allocsimulation.sh

Compare with previous version

SonarQube analysis reported no issues.

added 2 commits

• 746b7f08 - Change number of hosts to keep percentages correct
• c09111dc - Increase interval for BroadcastEventGenerator by 10/3

Compare with previous version

SonarQube analysis reported no issues.

added 1 commit

• 7ce49efe - Fix event generator interval and corresponding comments

Compare with previous version

SonarQube analysis reported 2 issues

• 🔽 2 minor

1. 🔽 Use isEmpty() to check whether the collection is empty or not. 📘
2. 🔽 Use isEmpty() to check whether the collection is empty or not. 📘

added 1 commit

• 8dfc6b45 - Adapt interval for DisasterData creation

Compare with previous version

SonarQube analysis reported 2 issues

• 🔽 2 minor

1. 🔽 Use isEmpty() to check whether the collection is empty or not. 📘
2. 🔽 Use isEmpty() to check whether the collection is empty or not. 📘

added 18 commits

• 8dfc6b45...8fe95184 - 17 commits from branch master
• aa46acae - Merge branch 'master' into feature-#349-adapt-config-after-interviews

Compare with previous version

SonarQube analysis reported no issues.

added 1 commit

• 4c16f726 - Adapt MulticastEventGenerator interval to new node amount

Compare with previous version

SonarQube analysis reported no issues.

mentioned in commit 8d5efebe

added 1 commit

• 8d5efebe - New realistic event file: No ends after simulation end, new ranges

Compare with previous version

SonarQube analysis reported no issues.

added Needs Review and removed Needs Changes labels

You shouldn't use a comma here, but a period. Same for all other numbers.

True, actually forgot to commit that yesterday. I just rounded all numbers now, I don't think we need to place hospitals with more than a meter of accuracy.

added Needs Changes label

The ranges / positions still don't look too good:

Many events are at the edge of the map, and almost no host is actually interacting with them.

I agree. I restricted the center coordinates to (2000, 20000), so they will be more in the map center.

The safe ranges also seem a little small?

How did you get this picture though? I'm trying to get an overview of all events at once. Did you just change all start times to 0?

added 1 commit

• b0101a68 - Change ranges and locations and remove decimal points from coordinates

Compare with previous version