Currently there's no way to easily start a minimization based on a yaml using "post" importance sampling (so grid scripts --importance-minimize also not implemented). I think this would be quite easy from the post run's .updated.yaml (just changing sampler), but the combined_info in updated.yaml calculation is enmeshed in post() and not easily accessible until after the post run has run. So we could either try to refactor so that things can be run in any order, or just try to support it if the post importance filtering chains have been generated.
Currently there's no way to easily start a minimization based on a yaml using "post" importance sampling (so grid scripts --importance-minimize also not implemented). I think this would be quite easy from the post run's .updated.yaml (just changing sampler), but the combined_info in updated.yaml calculation is enmeshed in post() and not easily accessible until after the post run has run. So we could either try to refactor so that things can be run in any order, or just try to support it if the post importance filtering chains have been generated.