File name with relative path and new test (writeFile + distFile)

[grapp1]

I've had issues with running the following excerpt of code, which was due to providing a relative path instead of the absolute path for file_to_write. We thought that this may be a useful test for calling writeFile and distFile consecutively.

import numpy as np
from parflowio.pyParflowio import PFData

file_to_write = './Flow_Barrier_X.pfb'

p = 1
q = 1
r = 1

FBx_data = np.full((20, 20, 20), 1.0)

for i in range(20):
    for j in range(20):
        FBx_data[i, j, 9] = 0.001

FBx_data_pfb = PFData(FBx_data)
FBx_data_pfb.writeFile(file_to_write)
FBx_data_pfb.close()
pfb_data = PFData(file_to_write)
pfb_data.distFile(p, q, r, file_to_write)

[arezaii]

Can you elaborate on the error you are having? I am able to perform this operation without error.

import numpy as np
from parflowio.pyParflowio import PFData

file_to_write = './Flow_Barrier_X.pfb'

p = 1
q = 1
r = 1

FBx_data = np.full((20, 20, 20), 1.0)

for i in range(20):
    for j in range(20):
        FBx_data[i, j, 9] = 0.001

# write pfb to disk
FBx_data_pfb = PFData(FBx_data)
FBx_data_pfb.writeFile(file_to_write)
FBx_data_pfb.close()

# load pfb from disk
pfb_data = PFData(file_to_write)
# distribute the file
pfb_data.distFile(p, q, r, file_to_write)

# read in the file we just wrote to disk
read_dist_data = PFData(file_to_write)
read_dist_data.loadHeader()
read_dist_data.loadData()

# make sure the data is equal
np.testing.assert_array_equal(read_dist_data.getDataAsArray(), pfb_data.getDataAsArray())
np.testing.assert_array_equal(read_dist_data.getDataAsArray(), FBx_data_pfb.getDataAsArray())
np.testing.assert_array_equal(read_dist_data.getDataAsArray(), FBx_data)

[grapp1]

When I run this using the relative path, I sometimes get an error reading the header of the PFB file. The error messages are usually either Error Reading Header: No such file or directory or Floating point exception: 8, where the PFB file seems to be written incorrectly (I've tried opening it in ParaView and get errors/crashing when I try to open it). However, the exact same script executes successfully sometimes, so I am not sure what the issue is. Changing the file path to the absolute path completely removes the error.

[jaredwhite547]

Hi,
I think this may have been related to #7, which is now fixed in the latest version on PyPi. I was also unable to reproduce this, both before and after the fix. Can you retry with the newer version please?

If the issue still persists, can you provide more info about what your directory structure looks like, and some basic OS/environment info?

[grapp1]

Hi Jared,
I updated parflowio to 0.0.3, and I am getting the same Floating point exception: 8 error when not using the absolute file path for file_to_write. It works the first time I run it, but when I run it again (i.e., when file_to_write already exists), I get the error.

I am running an older version of ParFlow (v3.3.1), using a virtual environment for Python. I'm running it on MacOS Mojave v10.14.5. I'm running the richards_FBx test case from the command line to test this.

I've tried to replicate the problem on a Docker container using Ubuntu 20.04 and ParFlow v3.7.0, and everything works fine. I'm happy to meet with you briefly to detail further if that helps. Thanks.