If the execute fails due to a python error in the extract script, it seems hard to clean up the filter graph.
[Error] Ascent::execute
{
"file": "/global/project/projectdirs/alpine/software/ascent/gnu/7.3.0/spack/var/spack/stage/ascent-develop-s3dhmko64soruskubazf5fbpn674dy6g/ascent/src/ascent/runtimes/ascent_main_runtime.cpp",
"line": 640,
"message": "Cannot add extract filter, extract named \"e1\" already exists"
}
I tried actions setups that look like:
define extract
execute
reset
and
reset
define extract
execute
Note: The simulation will continue to run just fine, the expected right behavior is to show the python error message each time, instead of an error about defining a dup extract for ever after the second exe.