PS: I wrote it in C 😅. A few years before I fell in love with Python.

🏃‍♂️Another thing I like are the disclaimers about when a specific feature is/was available. This is extremely important in a fast-changing environment, and very useful if you're not using the stable versions of Nextflow. See screen captures below for some examples.

After @jvfe.bsky.social's viva last week, with @nextflow.io front and center—just like the satisfaction of the examiners in acknowledging how far João Vitor has come on his journey. Congratulations, João!

Thanks, kickass Leibniz 😆. I love the @nextflow.io run names #Seqera #Nextflow #Pipelines #Bioinformatics

I understand. I just want to highlight that the free tier of the Seqera Platform supports this optimization technology I'm referring to. You can play with it in the community showcase. See the video below for a quick demo.

to calculate the change you want to make. It does get the job done, but it doesn't feel ideal. I'm happy to share with you that recently we got an upgrade to this 😎

Through the previousTrace attribute of the task object, you can now check exactly what were the resources attempted before

What if you wanted to always retry on failure or retry under certain circumstances *but prefer to change the resources based on the exit status code*? Increase memory if the task needs more memory. Increase time if the task needs more time. This feature highlights Nextflow's power to automatically

requested for subsequent attempts. Check the screen capture below. If this process instance (task) fails, Nextflow will retry as long as the exit status code is 140.

On the second attempt, it will multiply the original request for time and memory by two. On the third attempt, multiply by three.

I used to say that if I knew @nextflow.io and @nf-co.re when I did my masters, I’d have been able to do two masters in the same time. With these two in their current versions, with @seqera.io AI, and other Seqera technologies? Three 😅

4/ How to Use It?
Adding job arrays to your Nextflow pipeline is simple. No rewrites. No hassle.

4/ 🔧 Alternatively, you can configure these limits in a Nextflow configuration file:

3/ ⭐ The resourceLimits process directive allows you to set environment-specific limits for your task resource requests. Perfect for optimizing workflow efficiency!

🖥️ How it works: You can specify resource limits directly within your process. For example:

2/ While functional, its implementation required configuring parameters and calling the function into multiple parts of your workflow, which wasn't ideal. Recently, Nextflow introduced a native solution to this issue, offering a more streamlined and efficient approach.

1/ The @nextflow.io community has long sought an effective solution to address scenarios where resource requests exceed the capacity of the infrastructure. Some of you may be familiar with the check_max() Groovy function developed by the @nf-co.re community to tackle this challenge

More recently there have had some efforts to be more precise about these two words. Check here, for an example: https://help.tower.nf/23.2/getting-started/definitions/