You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now babelmixr2 check to see if the times are optimized to see if time matching is needed. It would be helpful if this could be queried in the poped.db...
The text was updated successfully, but these errors were encountered:
poped.db$settings$optsw[2] should always be in the poped.db. Do you have an example where it is not?
Since the poped.db is editable and can be transformed by the user, including the user changing/updating sampling times, it seems dangerous to have a flag indicating if sample times have been optimized. Further, being optimized by one algorithm may not indicate optimality by another algorithm (D-optimal vs Ds-optimal for example).
I haven't looked at this for a bit, though I thought I encountered an example where it was not. Perhaps it was that it could be changed dynamically.
As it turns out, I don't think it is that critical. I found another way of matching that doesn't take too much time, so the time difference is minimal.
However, I do have differences in outcomes based on if I match times or not. I guess this isn't a surprise and is why many of your examples match the time.
Currently it seems to be here:
poped.db$settings$optsw[2]
But it isn't always in the poped.db.
Right now
babelmixr2
check to see if the times are optimized to see if time matching is needed. It would be helpful if this could be queried in thepoped.db
...The text was updated successfully, but these errors were encountered: