Samuel Lampa

Hi @monkeybutter and thanks for very interesting input! It is interesting that you propose using a channel for the reduce operation. I had not even thought about that option, so...

> I've been thinking more about the concept of gather/reduce operations inside networks. My first approach was to think about networks as a long-lived processes in which IPs from different...

So a few relevant questions now seem to be: - How do the tagging operation look like, in practice? - How does a splitting component look like? - How does...

Optimally we would like to allow most of these operations, using the standard SciProcess type. With this in mind, this issue depends on #30 , and maybe another feature, of...

Update: It seems [go-xerror](https://brandur.org/fragments/go-xerror) is a promising alternative too.

Maybe rather: ``` go split := scipipe.NewFromShell("split", "split -d {i:infile} {g:splitfiles}") // Use new 'g' operator for glob patterns split.SetPathStatic("splitfiles", "output.txt_split") // Use the normal path setters to define the...

Some considerations I realized today: - The main problem is that you can't, or will not typically, specify the output files explicitly, but rather will provide a base name (optimally),...

Now with #41 implemented, it should be easy to support setting output patterns, like: ```go split := wf.NewProc("split", "split {i:in} some_prefix_") split.SetOut("split_files", "some_prefix_*") ```

It should also be noted that we now have the [FileGlobber component](https://pkg.go.dev/github.com/scipipe/scipipe/components#FileGlobber), although the use case above is to have it more integrated, and also being able to specify a...

> Find replacements for/configure Appveyor to handle GNU utilities like sed. Hmm, I wonder, is the idea to be able to run SciPipe in a POSIX-environment like Git-bash/MSYS2 or even...