Matt Larsen comments

Results 41 comments of


                                            Matt Larsen

Field filtering: if we remove all fields, verify fails

@cyrush What do you think about 1?

Field filtering: if we remove all fields, verify fails

Implementing #567 would resolve this.

logical grid filter

What is the filter name? `LogicalGridFilter`?

add additional surprise checking for actions scenes/filters/

Here is an example: ``` - pipelines: pipe1: f0: params: bins: "32" field: energy sample_rate: "0.05" type: histsampling ``` Generates: ``` [Error] Ascent::execute file: /global/u2/h/hazarika/projects/ALPINE_WORKFLOW/ascent/build/spack/var/spack/stage/spack-stage-conduit-develop-urrx5p6alo3c7rdfaza5mienalxjooid/spack-src/src/libs/conduit/conduit_node.cpp line: 12940 message: Cannot access...

dray import high order mesh w/o using mfem

Note: we use MFEM for projecting the basis functions to a positive basis as well.

Move verify to publish

@cyrush What do you think about this?

Add domain boundary plot

subset plot

pre-execute: traverse actions and determine set of fields involved

or copies

pre-execute: traverse actions and determine set of fields involved

so we have this, but we need to read the actions. one solution I implemented is to have one rank read the actions and broadcast the actions to all other...

pre-execute: traverse actions and determine set of fields involved

This would require us to 1) have all filters tell us about what they used (touching everything) 2) support a dry run We would still have the issue of filters...