is there a way to yield multiple DynamicOutputs from an op I

Question

is there a way to yield multiple DynamicOutputs from an op I haven t been able to find anything in the docs and I m stumbling when trying to figure out what I would use for the `output defs` argument of the op generating the DynamicOutputs <https docs dagster io concepts ops jobs graphs dynamic graphs multiple outputs|this> section is a bit ambiguous but maybe seems related although I m suspecting the `multiple dynamic values` op used in the example is supposed to be an op that operates on DynamicOutputs not one that yields them

jamie · Answer

hi < Zach> i think this should be possible can you send me any code snippets of what you ve tried I can see about putting together a quick example too

Zach · Answer

sure ``` op name= args generator config schema= chroms Field str out= out1 DynamicOut str out2 DynamicOut str def generate args context OpExecutionContext for c in context op config chroms yield DynamicOutput c mapping key=c DynamicOutput c mapping key=f c 1 ```

Zach · Answer

this gives a `AttributeError args generator outputs object has no attribute map ` on compilation

jamie · Answer

can you also share where `generate args` is being called in a graph job

Zach · Answer

``` graph def example io graph generate args map do processing ```

jamie · Answer

ok great working on a repro now and i ll let you know what i find

Zach · Answer

ah I see that I can do ``` graph name= example io dnax def example io graph arg1 arg2 = generate args arg1 map do processing arg2 map do processing ``` so maybe if I need multiple values going to `do processing` they should just be passed as a dictionary or tuple I guess a refinement of the question would be whether arg1 and arg2 in the example above can be fed to `do processing` together or if by returning two DynamicOutputs you basically are creating two separate downstream branches in the dag

jamie · Answer

yeah i was about to send you a similar snippet conceptually i think of two DynamicOuts as creating separate branches in the dag like you mentioned we dont have a way to zip two lists of DynamicOuts together so they can be passed in pairs to downstream ops since you can just yield out tuples in your DynamicOuts instead

Zach · Answer

okay cool that makes sense and seems reasonable after walking through it thanks for your help