Skip to content

Reported scores from optimising models with random effects way off #250

@lentinj

Description

@lentinj

See the hidden bit in #249

print(cbind(params.fixout$value, params.rndout$value))
print(c(
    fixout = attr(params.fixout, "summary")$score,
    # TODO: obj.fix$fn(obj.rnd$env$last.par.best) != attr(params.rndout, "summary")$score, even though newton trace reports the former?
    #       Some sublety post-inner-optimisation I've not figured out.
    rndout = attr(params.rndout, "summary")$score ))

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions