Open fnrizzi opened 3 weeks ago
Therefore from a superficial look , it seems like extending support for say algorithm X in MUQ, involves (1) extending the paremeter choices in dakota to communicate with X and then (2) instantiate properly the components needed by the MCMC. But this only applies if the new methods need what the existing do, so maybe even if the interface needs updating.
need to make a list of the new methods needed in the SOW and make a list of what those require from the user
What Dakota currently supports
the latest release of dakota: https://dakota.sandia.gov/2024/05/15/dakota-6-20/ supports: "five MCMC algorithms from MUQ: metropolis_hastings, adaptive_metropolis, delayed_rejection, dram, and mala".
Dakota files where MUQ is being included/used
More specifically
We can see that the type of MCMC and parameters are set in the constructor:
and then we have: