Using the marbl_ prefix for the stand-alone driver designed for testing is a little confusing; it's unclear what subroutines called from the driver are in the MARBL library rather than the driver itself. @klindsay28 and I discussed this, and a better approach would be to use driver_ instead of marbl_ for the driver; modules like marbl_init_drv.F90 should either be driver_init.F90 or driver_init_test.F90 (I'm leaning towards the former).
Using the
marbl_prefix for the stand-alone driver designed for testing is a little confusing; it's unclear what subroutines called from the driver are in the MARBL library rather than the driver itself. @klindsay28 and I discussed this, and a better approach would be to usedriver_instead ofmarbl_for the driver; modules likemarbl_init_drv.F90should either bedriver_init.F90ordriver_init_test.F90(I'm leaning towards the former).