I have been trying to implement your virtual-flow system. I appreciate your efforts in setting this up and showing that it can work.
One of my barriers to implementing it for my system is a lack of definitions in the documentation.
Terms like ‘step’, ‘collection’, ‘queue’, ‘job’ all appear to be important to know how to set variables in the all.ctrl file, yet I haven’t been able to find the exact definition for these terms. I have spent the past several weeks guessing at what they may mean based on posted examples but haven’t made much progress.
Perhaps a page of very well described definitions and suggested guidelines for ranges on these variables would be helpful here. I realize that some of this available as comments throughout the file - but these are easy to miss and for some when I have inquired it seems that they have no consequence. It has been a little bit frustrating trying to understand what should be changed.
Many thanks for your contribution to open-source highthroughput screening and looking forward to more great work from the virtual-flow team.
Thank you very much for the feedback, we appreciate it.
We recognize that some terms used in the documentation could be explained more clearly.
“Job” and “step” are terms which come from the batch system (e.g. SLURM), and were not created by us. There is a lot documentation about these terms provided by the SLURM developers, but by testing and using the SLURM cluster and can get also a better feeling by experience what exactly these terms mean. If you are new to computer clusters and supercomputers, it is normal that this process takes a bit of time.
