Juri Solodenko

not in v9 :)

>only common expression profiles will be added automatically. Otherwise, they will be removed I think we should not remove expression profiles, because this would change existing populations within the merged...

>A view will be shown listing the selected population as well as the base individual that will be used for this I wonder if we should only allow merging of...

General question: is merged population a COPY of used populations or just a bracket around them? So if one of the used populations is modified **after** merging: does this impact...

>I'd love to say it's a copy. That would be much easier. But then no snapshot... Everything else (besides the snapshot) can be achieved already now by merging via CSV...

A completely different approach to think about: instead of merging populations - allow selection of **multiple** populations when creating a simulation (with the same restrictions as discussed above: e.g. only...

The simplest solution: create a "csv-merged" population. Thus in the background just export all input populations to temporary csv and reimport them into one merged pop in the same way...

>Good point. Maybe one can work with MOLECULE (similar as in MoBi). Agree. >PK-Sim has to treat such parameters as compound parameters with regard to commit and update. So, in...

@sfrechen Can you please list all use cases of "compound=>simulation parameters overwriting" which have occurred so far? E.g. when looking at the qualification plans where this have been used, I...

How about this: * We identify all simulation parameters which have been "overwritten" by a compound so far * In PK-Sim, for each of those parameters we define a **new...