My question is about the difference between runtype "opt_vmc" and "vmc_opt". Would you please describe a little about the physics of "opt_vmc" and when is better to use this option. I looked at the casinohelp but I need more information.
Best regards,
Elaheh.
Runtype
-
- Posts: 239
- Joined: Thu May 30, 2013 11:03 pm
- Location: Florence
- Contact:
Re: Runtype
Hi Elaheh,
To quote the relevant bit of 'casinohelp runtype' output:
'vmc_opt' (perform VMC and optimization, alternately);
'opt_vmc' (perform optimization and VMC, alternately);
Perhaps for clarity that should read 'perform opt_cycles cycles of VMC and optimization, alternately' etc.
Each optimization phase requires you to have generated some VMC configs first (which will be in a 'config.in' file), and this is why vmc_opt is the normal option.
The 'opt_vmc' exists merely for the case where you have already generated the VMC config file. It's not really a question of 'physics'.
Best wishes,
Mike
To quote the relevant bit of 'casinohelp runtype' output:
'vmc_opt' (perform VMC and optimization, alternately);
'opt_vmc' (perform optimization and VMC, alternately);
Perhaps for clarity that should read 'perform opt_cycles cycles of VMC and optimization, alternately' etc.
Each optimization phase requires you to have generated some VMC configs first (which will be in a 'config.in' file), and this is why vmc_opt is the normal option.
The 'opt_vmc' exists merely for the case where you have already generated the VMC config file. It's not really a question of 'physics'.
Best wishes,
Mike
Re: Runtype
Hi Mike,
Thanks!
Best regards,
Elaheh.
Thanks!
Best regards,
Elaheh.