-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adaptation Handler #80
Conversation
|
||
|
||
// ******************************************** | ||
void AdaptiveMCMCHandler::InitFromConfig(const YAML::Node& adapt_manager, const std::string& matrix_name_str, const int Npars) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given Npars won't change does it not make sense to make this a class attribute rather than calling it in every method?
if(total_steps>adaption_struct.end_adaptive_update || total_steps<adaption_struct.start_adaptive_update) return; | ||
|
||
int steps_post_burn = total_steps - adaption_struct.start_adaptive_update; | ||
if(total_steps>AdaptiveHandler.end_adaptive_update || total_steps<AdaptiveHandler.start_adaptive_update) return; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conceptually do we not want to leave this logic inside the adaption handler?
…t's use cmake to update it whenver we update it in cmake
Pull request description:
Currently All AMCMC related stuff in heavily integrated within CovarianceBase. This PR attempts to make full fledget adaption class which interfaces with Covariance base. If all adaptation is done via this handler then selcting different adaptation via polimorphism will be super easy.
There are still Adaptive funciton in covaraince. This will need to be adressed later. Will try do this when I have time again.
Changes or fixes: