Alpine-DAV / ascent

A flyweight in situ visualization and analysis runtime for multi-physics HPC simulations
https://alpine-dav.github.io/ascent/
Other
191 stars 65 forks source link

Multiple actions files #1207

Open yslan opened 11 months ago

yslan commented 11 months ago

Is it possible to have multiple actions files?

-
  action: "add_triggers"
  triggers:
    t1:
      params:
        condition: "cycle % 100 == 0"
        actions_file : "trigger_render1.yaml"
        actions_file : "trigger_render2.yaml"
        actions_file : "trigger_render3.yaml"

I guess the workaround is to have multiple triggers?

  action: "add_triggers"
  triggers:
    t1:
      params:
        condition: "cycle % 100 == 0"
        actions_file : "trigger_render1.yaml"
    t2:
      params:
        condition: "cycle % 100 == 0"
        actions_file : "trigger_render2.yaml"
    t3:
      params:
        condition: "cycle % 100 == 0"
        actions_file : "trigger_render3.yaml"
nicolemarsaglia commented 11 months ago

You cannot have multiple action files, without the workaround with triggers you suggest, but you can have multiple actions in one file. What is in your trigger yamls? My guess is they can probably be combined.

Here is a more complicated ascent_actions.yaml as an example. A number of pipelines, some with multiple filters, and then rendering multiple scenes. ascent_actions.yaml.txt

yslan commented 11 months ago

Right, I know how to use scenes to plot multiple images.

However, I have 3 images I want to plot and each of the images has more than 10 slices + clip. That's why I really don't want to put everything into a single file.

Just a suggestion here.

cyrush commented 11 months ago

thanks for the context:

perhaps we can add an actions_files option that takes a list for this case?

yslan commented 11 months ago

@cyrush That will be nice!