Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should boostDM exceptions be handled as errors? #11

Open
koszulordie opened this issue May 6, 2024 · 0 comments
Open

Should boostDM exceptions be handled as errors? #11

koszulordie opened this issue May 6, 2024 · 0 comments
Labels
enhancement New feature or request running pipeline/build/test running

Comments

@koszulordie
Copy link
Collaborator

We might consider whether common boostDM exceptions are exited as errors or not.

For example, it is questionable whether an exception such as not finding a high enough quality model for a given gene-ttype pair should raise an error or, alternatively, just exit(0) the program with an appropriate logging.

Even though nextflow is told to ignore errors, every error in the pipeline produces an annoying printout. In the case of processes such as PredictSaturation where many exceptions are expected, the excessive amount of printouts can be disturbing, even if the run is completely fine.

@koszulordie koszulordie added enhancement New feature or request running pipeline/build/test running labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request running pipeline/build/test running
Projects
None yet
Development

No branches or pull requests

2 participants