Open elbaraim opened 4 years ago
and/or to adapt the scale of the visualisation. e.g. visualise a log-transformed values on a log scale
in that case, it might be best to have an additional field in the pypesto.Problem class "x_scales", which takes the scale for each parameter. One just has to be aware that unlike in petab, in pypesto we assume all values to be scaled already, e.g. the nominal values and bounds. For optimization this is best this way, however when defining priors one will have to be a bit careful.
When petab problem is imported in pypesto would be good to update parameter names according to the scale:
lin
,log
orlog10
. In case beinglin
leave as it is. In case any of the others change during import to, e.g.,log(parameter_name)
orlog_{10}(parameter_name)