Cannot read BOV

[StasJ]

1. Open 256d.bov
2. Create a renderer

Vapor with throw 5 error popups (which should be consolidated) and not render anything.
System: macOS

[sgpearse]

@StasJ Have you downloaded the binary data file as well, and have you pointed the .bov file to reference it?

[StasJ]

@StasJ Have you downloaded the binary data file as well, and have you pointed the .bov file to reference it?

Yes and yes.

[StasJ]

> ls BOV
256d.bin
256d.bov
256f.bin
256f.bov
256i.bin
256i.bov
multiTimeMultiVar

> cat 256d.bov
TIME: 1.1
DATA_FILE: ./256d.bin
DATA_SIZE: 256 256 256
# Allowable values for DATA_FORMAT are: BYTE,SHORT,INT,FLOAT,DOUBLE 
DATA_FORMAT: DOUBLE
VARIABLE: a
# Endian representation of the computer that created the data.
# Intel is LITTLE, many other processors are BIG.
DATA_ENDIAN: LITTLE
# Centering refers to how the data is distributed in a cell. If you # give “zonal” then it’s 1 data value per zone. Otherwise the data # will be centered at the nodes.
CENTERING: zonal
# BRICK_ORIGIN lets you specify a new coordinate system origin for # the mesh that will be created to suit your data.
BRICK_ORIGIN: 1e2 0. 0.
# BRICK_SIZE lets you specify the size of the brick.
#BRICK_SIZE: 10. 20. 5.
BRICK_SIZE: 100. 100. 100.

# BYTE_OFFSET is optional and lets you specify some number of
# bytes to skip at the front of the file. This can be useful for # skipping the 4-byte header that Fortran tends to write to files. # If your file does not have a header then DO NOT USE BYTE_OFFSET. 
#BYTE_OFFSET: 4000
# DIVIDE_BRICK is optional and can be set to “true” or “false”. # When DIVIDE_BRICK is true, the BOV reader uses the values stored # in DATA_BRICKLETS to divide the data into chunks that can be
# processed in parallel.
DIVIDE_BRICK: true
# DATA_BRICKLETS is optional and requires you to specify 3 integers # that indicate the size of the bricklets to create when you have
# also specified the DIVIDE_BRICK option. The values chosen for
# DATA_BRICKLETS must be factors of the numbers used for DATA_SIZE. 
DATA_BRICKLETS: 5 5 5
# DATA_COMPONENTS is optional and tells the BOV reader how many
# components your data has. 1=scalar, 2=complex number, 3=vector,
# 4 and beyond indicate an array variable. You can use “COMPLEX”
# instead of “2” for complex numbers. When your data consists of
# multiple components, all components for a cell or node are written # sequentially to the file before going to the next cell or node. 
DATA_COMPONENTS: 1

[sgpearse]

Thanks for posting that. This is a duplicate of #2784.