Use any LEaP-style specified GB radii if no radii explicitly set for 'build' and 'sequence'#1183

Merged

drroe merged 7 commits into

Amber-MD:masterfrom

drroe:sequence.gbradii

May 7, 2026

Commits on May 7, 2026

Make having not all arguments processed in an EXE command an error unless noexitonerror was specified.
Daniel R. Roe
committed
Explain how to ignore the error in the error message
Daniel R. Roe
committed
For the build and sequence command, if no GB keyword specified try to use leap options if they were set.
Daniel R. Roe
committed
V7.8.0. Minor version bump for build and sequence using any leap options for GB radii if a GB keyword not specified. Also change default behavior to exit with an error for EXE commands if there is …
Daniel R. Roe
committed
There are currently too many commands which make internal copies of the argument list, leading to false positives for unhandled input. Will need to be handled in a future PR
Daniel R. Roe
committed
Make the default for gb radii leap options unknown so we know if it was set or not. Default will be set in GBparams::Init_GB_Radii()
Daniel R. Roe
committed
Merge branch 'master' into sequence.gbradii
Daniel R. Roe
committed