Skip to content

Modified Gompertz fitting test: t_shift currently not tested #59

Description

@sambra95

Seems that there are multiple parameter combinations that make almost identical curves and the fitting function cannot distinguish between them well. This flat loss landscape causes some estimated parameters to blow up (in this case t_shift). Currently t_shift is removed from the test but we need to look into a more accurate fitting method here.

expected = { "mu_max": mu_max, "A": A, "N0": N0, "N0": N0, # "t_shift": t_shift, # removed t_shift from expected since it's not identifiable "alpha": alpha, "lam": lam, }

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions