When the code was first written, we were extremely conservative about what sorts of input and config types were allowed to be passed in the bal_config to ensure that we were doing things correctly.
However, this is too conservative: It leads to some unexpected and unnecessary compatibility issues when doing simple tests using typical galsim types.
We should change all of the allowed_types into safe_types or supported_types and only warn the user if using one of the unsupported types. This shifts some of the responsibility to the user to do reasonable things, but this is an ok compromise for flexibility.
When the code was first written, we were extremely conservative about what sorts of input and config types were allowed to be passed in the
bal_configto ensure that we were doing things correctly.However, this is too conservative: It leads to some unexpected and unnecessary compatibility issues when doing simple tests using typical
galsimtypes.We should change all of the
allowed_typesintosafe_typesorsupported_typesand only warn the user if using one of the unsupported types. This shifts some of the responsibility to the user to do reasonable things, but this is an ok compromise for flexibility.