Skip to content

Specifying param priors is inconsistent #380

Open
@jllanfranchi

Description

@jllanfranchi

If you want to reference a param in config file from a param in another file, e.g.:

p1 = 1
p1.prior = ${ref:val.prior}

this works for uniform but spline requires an additional p1.prior.data = ... spec and this does not work with a Gaussian prior (you have to reference the value itself).

I think the best fix to this (that would also make switching among priors easier esp. when referencing priors from other files) would be to make the entire prior spec into a single line. E.g.:

p1.prior = gaussian: std_dev = 0.5
p2.prior = unform
p3.prior = spline: data = resource/location
p4.prior = None

then in another file, section (or in the same section) you can refer to all priors in a consistent one-line way:

p_a.prior = ${p1.prior}
p_b.prior = ${p2.prior}
p_c.prior = ${p3.prior}
p_d.prior = ${p4.prior}

It seems relatively easy to parse such param strings out, the biggest difficulty will be converting configs to use this convention.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions