Example fails to execute delineation step #22
Description
If a user runs the step in the Newman Canyon example to delineate the watershed but the machine they are using does not have enough ram to run the delineation the subsequent code will look for a file that should've been created but wasn't. This gives a simple "file not found error" but user will never see this file because it is temporary and gets deleted after the full workflow is ran. Recommend adding a check in the delineation step to check if temporary files exist before they are used. If they don't then provide an error message with some specifics as to why that might occur. Not sure what the best practice is for that kind of message.