It is mostly about how tasks are generated by a workflow system. In pull based systems, the outputs invoke the steps by dependency matching (e.g make). In push based (dataflow) systems, the inputs trigger the cascade. (for ref : academic.oup.com/gigascience…)
🧬 Why didn't Go break into Bioinformatics on a large scale, when it has had a phenomenal growth outside the field? 🧬
I wrote a short post on this question and on using #golang for #bioinformatics in general 👇
bionics.it/posts/golang-for-…
Wohoo! We're happy to see that we just reached 1000 @github ⭐️:s! Thank you all for the support! 🤩 And... expect some work on fixes and improvement in the summer! #sciworkflowsgithub.com/scipipe/scipipe
Looking for #Bioinformatics courses on #GitHub? 🧐 You're in luck! 🍀@choup@P_Palagi and I from @ISBSIB have created #Glittr (glittr.org): a webapp that helps you find and compare awesome training materials. 🎉
How does it work? And how can you join us? Read on! 👇
We're glad to see SciPipe being used to explore properties of #dataflow in this nice paper by Andrei Paleyes & Neil Lawrence @lawrennd
It makes a strong case for how the #dataflow paradigm adds key causal info already at the design stage #sciworkflowsarxiv.org/abs/2304.11987
“We've generated a humongous amount of data and it's available for everybody in the world” says @KltLab, after analyzing genomes of 240 mammals, in international research project led by @UU_University and @broadinstitute in collaboration with SciLifeLab.
scilifelab.se/news/scilifela…
🎉 Hooray, after learning it is still used at some major companies, I just pushed a new release of SciLuigi [1] tonight, for the first time in ~3 years 🎉
github.com/pharmbio/sciluigi…
[1] Wrapper around @bernhardsson's Luigi, allowing dep defs outside of tasks & more #sciworkflows