Skip to content

Rework Data Structure #1202

@HenrZu

Description

@HenrZu

Motivation / Current Behaviour

Currently, we have the following structure:
data

  • mobility
  • contacts
  • pydata (optional, only created if epidata is called)
    However, the existing data in mobility/contacts is also regional dependent (right now only valid for Germany) and also created partially (Commuter_mobility) created with the pycode.

Therefore, a better structure would be
data

  • Germany
    --- mobility
    --- contacts
    --- pydata
  • Country2
    .....

Enhancement description

see description

Additional context

No response

Checklist

  • Attached labels, especially loc:: or model:: labels.
  • Linked to project

Metadata

Metadata

Assignees

Labels

class::improvementCleanup that doesn't affect functionalityloc::data handlingThis issue concerns any kind of data handling.model::odeThis issue concerns any kind of ODE-based model.status::in progressThis issue is in progess.

Type

No type

Projects

Status

Done (Total)

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions