Cyrus Harrison

Results 374 issues of Cyrus Harrison

### Describe the bug There are places were we index by an integer id, instead of a name. Here is one of them: https://github.com/visit-dav/visit/blob/91ff5211fbae8256bb8590688ca37106b24fef5c/src/databases/Blueprint/avtBlueprintFileFormat.C#L949 This causes a problem when the...

bug
reviewed
likelihood medium
impact medium

### Describe the bug A user passed a path that included dirs to the filename option in ExportDatabase options (like: mypath/to/output) They didn't touch the default dir name, which was...

bug
reviewed
asc
likelihood medium
impact medium
priority

### Describe the bug When trying to use a system python to launch VisIt, along with some complex setup logic that leverages h5py, `srun`ing the engine will hang (no output,...

bug
reviewed
asc
likelihood medium
impact medium

### Describe the bug User passed a numpy array as an input to `Query` and received a cryptic error message about not being able to parse arguments. (Also, it didn't...

bug
reviewed
asc
likelihood medium
impact medium
priority

### Describe the bug Updated to newer macOS (10.15.x catalina) and my visit cmake failed b/c the X11 path changed. I can reconfig from scratch and it will find the...

bug
reviewed
likelihood medium
impact medium

### Is your feature request related to a problem? Refactor logic that exists in these DB plugins for general use.

enhancement
reviewed
likelihood medium
impact medium

### Describe the bug I am using VisIt 3.2.1 release and can't open files from a few places. For our signing and release process - I thought we gave access...

bug
reviewed
impact high
likelihood high
priority

### Describe the bug VisIt 3.2.0 on macOS starts takes noticeably longer than other 3.x versions. (both cyrus and mark report seconds to launch ) ### Desktop - OS and...

bug
reviewed
likelihood medium
impact medium
priority

`ghost_indicator` differs from the default that ascent expects (`ascent_ghosts`) -- calling requires extra setup. Migrate to use ascent default.

Note: This is a reminder for me to do this in the future. We are using this logic downstream in a few AMReX codes, but it should be in AMReX...