646 use graph model with ABMs v3

[jubicker]

Changes and Information

Please briefly list the changes (main added features, changed items, or corrected bugs) made:

• add node property and edge property class for ABM graph simulation
• add model wrapper for abm that is used for ABM graph simulation and can handle persons that commute to other nodes
• add tests for new functionality
• add graph abm example

Merge Request - Guideline Checklist

Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.

Checks by code author

• Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
• New code adheres to coding guidelines
• No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
• Tests are added for new functionality and a local test run was successful (with and without OpenMP)
• Appropriate documentation for new functionality has been added (Doxygen in the code and Markdown files if necessary)
• Proper attention to licenses, especially no new third-party software with conflicting license has been added
• (For ABM development) Checked benchmark results and ran and posted a local test above from before and after development to ensure performance is monitored.

Checks by code reviewer(s)

• Corresponding issue(s) is/are linked and addressed
• Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
• Appropriate unit tests have been added, CI passes, code coverage and performance is acceptable (did not decrease)
• No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
• On merge, add 2-5 lines with the changes (main added features, changed items, or corrected bugs) to the merge-commit-message. This can be taken from the briefly-list-the-changes above (best case) or the separate commit messages (worst case).

[DavidKerkmann]

There are only a small things left to improve and one discussion item.

[DavidKerkmann]

We might have to add the new data members to this list.

[DavidKerkmann]

Ah, I see. Well now instead of the person index we have the rng index.

In all current use cases, we could use the other constructor of PersonalRNG that uses the index directly from its index in the world. However, when we want to construct the PersonalRNG inside the Person or anywhere where the world is not known, this is a problem.

Further, this rng_index needs to be updated each time a person is removed and added to a world, such that it uses the correct world index and doesn't clash with the same rng_index of another person.

Let's discuss in the next meeting.

[DavidKerkmann]

Thanks! Only one point left to discuss from my side.