Go-to for submitting runs on AWS
What do you like best about the product?
Run submission on AWS & cost tracking
Being able to help out others without sending around error logs.
Being able to help out others without sending around error logs.
What do you dislike about the product?
Deletion of runs and clean up is cumbersome
What problems is the product solving and how is that benefiting you?
We use Tower both for submission to AWS and for supervision of runs on an HPC. On AWS, we use it to create and manage our compute environments, submit pipeline jobs, and track cost. It simplifys cloud usage in comparison to setting it up manually and saves us lots of time. In addition, the new cost tracking feature has been great to pinpoint expenses for each run.
In addition, we are using it within the nf-core community to tests pipelines. It allows us to easily track pipeline runs and possible errors, even though we are globally spread out.
On our local setup, we use it to track our own pipeline runs, but also support each other more easily when something fails.
In addition, we are using it within the nf-core community to tests pipelines. It allows us to easily track pipeline runs and possible errors, even though we are globally spread out.
On our local setup, we use it to track our own pipeline runs, but also support each other more easily when something fails.
There are no comments to display