Fix unbound SED for cron commands in the launch script

[chan-hoo]

DESCRIPTION OF CHANGES:

To fix the issue on the launch script when 'USE_CRON_TO_RELAUNCH'="TRUE", 'source_util_funcs.sh' is sourced in the script.

TESTS CONDUCTED:

WE2E tests on WCOSS_DELL_P3:

• grid_RRFS_CONUS_25km_ics_FV3GFS_lbcs_FV3GFS_suite_GFS_v15p2
• grid_RRFS_CONUS_13km_ics_FV3GFS_lbcs_FV3GFS_suite_GFS_v15p2
• grid_RRFS_CONUS_3km_ics_FV3GFS_lbcs_FV3GFS_suite_GFS_v15p2
• MET_ensemble_verification

ISSUE:

Fixes issue mentioned in #605

[gsketefian]

@chan-hoo I think the fix you're implementing will cause the workflow to break on MACOS. We should define SED as in other scripts, which is by sourcing source_util_funcs.sh. You can do that by including the following lines in the launch script right after where scrfunc_dir is defined (I haven't debugged this though!):

homerrfs=${scrfunc_dir%/*}
ushdir="$homerrfs/ush"
. $ushdir/source_util_funcs.sh

This is the same approach as, for example, in run_WE2E_tests.sh. Thanks! @mkavulich

[chan-hoo]

@gsketefian , modified as suggested and tested successfully.

[gsketefian]

@chan-hoo Thanks for fixing. Can you also update the PR message before merging so it doesn't say "$SED" was changed to "sed" but instead that source_util_funcs.sh was sourced? Thanks.

[mkavulich]

Thanks for suggesting this change @gsketefian, I can confirm this is needed for the launch script to work on MacOS (though right now we do not test this since we run the stand-alone scripts there). I am not sure why the old code passed tests before (I guess the failure was in removing old crontab entries and I didn't notice?), but this fix looks good.