Samuel Lampa

@valentin-krasontovitsch > I'm not sure about the slurm library myself, have only looked at it shortly, but it seems like a mature project (just judging by the fact that they...

Just wanted to report that I think I have now seen the light regarding how to implement the required pluggability. It goes quite along the lines of your way of...

> Hey both. > > Just wondering if there was more traction made with this? I'm interested in running on a Torque cluster instead of Slurm. Any advise would be...

> Yep. The equivalent to salloc is qsub. Thanks I'll give it a go :) Great - Hope it works! :) Cheers

Should probably have a look at [this lib](https://github.com/Flaque/filet)

Well, I have been already playing with [afero](https://github.com/spf13/afero), which seems reasonable. The main question is whether to bring in a dependency, now that we just [got all remaining ones removed](https://github.com/scipipe/scipipe/releases/tag/v0.6)

Maybe this could be solved by using information packets (IPs) allowing a variable number of targets in them?

One solution to this is now implemented with the [FileSplitter](https://github.com/scipipe/scipipe/blob/master/proclib/file_splitter.go), and [Merger](https://github.com/scipipe/scipipe/blob/master/proclib/merger.go) components.

This could probably be implemented with a a field in the IP, containing a channel, that is used to read a sub-stream, until this "inner" channel is closed.

Excerpts from notes saved in my journal today: > Have been pondering this issue for several days now, without really getting anywhere ... until I realized now: > You have...