-
Notifications
You must be signed in to change notification settings - Fork 28
CV_TOO_MUCH_WORK: Possible reasons and solutions
Clemens Kreutz edited this page Jan 31, 2023
·
2 revisions
Please add your experiences on this page:
CV_TOO_MUCH_WORK occured when fitting a model, which had 3 conditions:
- Wild-type condition for steady state calculation with no treatment
- Wild-type condition after treatment
- Knockout coundition after treatment
Accidentially I didn't comprehensively overwrite the dummy parameter "isKnockout" for specifiying wildtype (isKnockout=0) and knockout condition (isKnockout=1). So it occured in the parameter list (arPrint) and sensitivities were calculated.
After overwriting this parameter via conditions (or via values in the data table) the problem was gone.
- Installation and system requirements
- Setting up models
- First steps
- Advanced events and pre-equilibration
- Computation of integration-based prediction bands
- How is the architecture of the code and the most important commands?
- What are the most important fields of the global variable ar?
- What are the most important functions?
- Optimization algorithms available in the d2d-framework
- Objective function, likelhood and chi-square in the d2d framework
- How to set up priors?
- How to set up steady state constraints?
- How do I restart the solver upon a step input?
- How to deal with integrator tolerances?
- How to implement a bolus injection?
- How to implement washing and an injection?
- How to implement a moment ODE model?
- How to run PLE calculations on a Cluster?