Hi,
I’m using ducttape-0.3 with a modified version of the cdec tutorial, and am noticing unexpected behavior with plans.
Right now I have a plan like
plan P {
reach extract_gra via (ExtractSection: dev)
}
and am invoking it via the command line: ducttape workflow.tape -p P
. Strangely, it says it will run extract_gra
with ExtractSection:dev
(and its prerequisites), as well as a realization which I have not requested: ExtractSection:devtest
(the other branch of ExtractSection
). Am I misunderstanding how plans are supposed to work, or is that behavior unexpected?
The inputs to extract_gra
are:
< corpus=(DataSeg: plain=(ExtractSection: dev=$out@preproc_corpus[DataSection:dev] devtest=$out@preproc_corpus[DataSection:devtest]) mwe=(ExtractSection: dev=$mwetokenized@mwe_tokenize[DataSection:dev] devtest=$mwetokenized@mwe_tokenize[DataSection:devtest]))
< ini=$ini@index_training
I ran ducttape mtlab.tape -p P viz
to generate the attached graph; essentially I am wondering why the bottom left realization is ever reached under this plan.
Any insights?
Thanks,
Nathan
--
You received this message because you are subscribed to the Google Groups "ducttape-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ducttape-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sounds like a bug.
Nathan: Can you open an issue on github and attach the description and full workflow? Bonus points if you can find a minimal workflow that repros.
Sent from my Windows Phone