Currently, legacy code means a mix of camel case and lower case names is being used. Decide on approach (Camel Case?), then use consistently.
Also, some legacy functions have unnecessarily protracted names (e.g. below). Update these to allow for cleaner code. can retain wrapper functions for core functions as a stopgap approach (e.g. as done for get_stats4RunDict_as_df versus older get_general_stats4run_dict_as_df).
AC.rm_fractional_troposphere() could be AC.rm_frac_trop()
This will make many external uses of AC_tools no longer back compatible. However, the older releases of the code can just be checked out to use older code bases.
Currently, legacy code means a mix of camel case and lower case names is being used. Decide on approach (Camel Case?), then use consistently.
Also, some legacy functions have unnecessarily protracted names (e.g. below). Update these to allow for cleaner code. can retain wrapper functions for core functions as a stopgap approach (e.g. as done for
get_stats4RunDict_as_dfversus olderget_general_stats4run_dict_as_df).AC.rm_fractional_troposphere()could beAC.rm_frac_trop()This will make many external uses of AC_tools no longer back compatible. However, the older releases of the code can just be checked out to use older code bases.