You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is little built-in error checking in optitype_script.sh. For example, during development, there were several occasions where some steps silently errored and did not produce output, but did not stop the script, leading to confusing error messages further on as downstream tools tried to access nonexistent files, and in turn did not stop execution despite errors. Additionally, the script currently assumes each step is successful and removes inputs as soon as a step is complete, complicating debugging in the above situation. How should we reconfigure the script to be safer in these situations?
The text was updated successfully, but these errors were encountered:
Currently, there is little built-in error checking in optitype_script.sh. For example, during development, there were several occasions where some steps silently errored and did not produce output, but did not stop the script, leading to confusing error messages further on as downstream tools tried to access nonexistent files, and in turn did not stop execution despite errors. Additionally, the script currently assumes each step is successful and removes inputs as soon as a step is complete, complicating debugging in the above situation. How should we reconfigure the script to be safer in these situations?
The text was updated successfully, but these errors were encountered: