Skip to content

some notes on setting matrix constructors #147

@njtierney

Description

@njtierney

These could do some checks like:

  • all matrices have the same dimensions
  • all matrices have the same age breaks
  • a new matrix, 'all' should be constructed and be the sum of all the other matrices (if it doesn't already exist)

I think that there is still scope for a hierarchical class system here:

  1. Setting Matrices (a list of matrices with numeric values)
  2. Type of setting matrix (contact numbers, contact predictions, ngm, transmission probability)
  3. Remainder (setting models objects, setting data frames - unsure if these can be nested somehow under a 'setting' class or something)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions