On Sun, Jan 5, 2014 at 6:02 PM, David Rosenberg <[email protected]> wrote:
>
> The load_parallel_results_split_on_newline you sent didn't seem to work for
> me... In any case, here's my first approach. I'm returning a matrix instead
> of a data.table, since everything's the same type.
>
> load_parallel_results_split_on_newline <- function(filenametable) {
Much faster than mine. Great.
>> >> load_parallel_results_split_to_columns(filenametable)
>> >
>> > I'm happy to write these, though I'm limited on time. Could you could
>> > write
>> > a generator for test data?
>>
>> parallel --results my/results/dir --header : echo FOO={foo}
>> BAR={bar}';'seq {bar} :::: <(echo foo; seq 1000) <(echo bar; seq 10)
>>
> Can we do with multiple columns?
parallel --results my/resu/dir --header : 'printf
"FOO={foo}\\tBAR={bar}\\n";paste <(seq {bar}) <(seq {bar} -1 1)' ::::
<(echo foo; seq 100) <(echo bar; seq 10)
> Does every directory generated by parallel always has both stdout and
> stderr?
Yes. They can be empty, but they are always created.
/Ole
