-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot calculate PK-Parameters of a population when one individual simulation failed #436
Comments
I would be ok with just ignoring these values. |
Ignoring is fine. Right now it crashes |
We already discussed this previously (Open-Systems-Pharmacology/OSPSuite.ReportingEngine#284) and proposed to define an failure_threshold (max. acceptable percentage of failed individuals per population). |
This is not what I am talking about, or at least it's not obvious to me that it is the same |
I agree with Michael on this. Threshold is a good idea but should be part of getResults or whatever we have there. If results are already there, the PK parameter should be calculated. |
ok, I see |
and when it takes many hours to run... THAT SUCKS :) |
@msevestre This cannot be solved in R, right? I am having the same issue now... Do you have some experience how to deal with it? |
What I did was identified the individual and swap it with another one. If you have multiple like this, or if some stuff is random...then it will be more complicated This is such a pain. I think we should fix this asap. I'll tackle this after relexp redesign |
How did you do that? |
I swap at the population level |
in hindsight: I would identify the wrong individual: for example 354 |
I think that I have it implemented. The PK Values will return NAN for an individual that was not calculated thus insuring that the array will have consistent length |
@Yuri05 @PavelBal
I believe this is a major issue and we should come up with a way to deal with this
Scenario:
We had this discussion for the RE. I think we should fix this as it can lead to a lot of frustration
The text was updated successfully, but these errors were encountered: