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
At the moment, the analysis expects the same drug range for all observations, and data is imported in a "wide format" (responses next to each other).
However, some users have different dose ranges, which can only be solved by running multiple batches or introducing many NaNs in the wide format, which is also more of a hack than a solution.
The correct way would be to enable doses encoded in a "long format" input, and these doses must be accessible in the fitting procedure and the dashboard. This will require many changes in the backend + some new parser + toml argument which specified the input.
Perhaps do this after the next v06 release?
The text was updated successfully, but these errors were encountered:
At the moment, the analysis expects the same drug range for all observations, and data is imported in a "wide format" (responses next to each other).
However, some users have different dose ranges, which can only be solved by running multiple batches or introducing many NaNs in the wide format, which is also more of a hack than a solution.
The correct way would be to enable doses encoded in a "long format" input, and these doses must be accessible in the fitting procedure and the dashboard. This will require many changes in the backend + some new parser + toml argument which specified the input.
Perhaps do this after the next v06 release?
The text was updated successfully, but these errors were encountered: