Ashar25
commented
10 months ago I also ran into similar problem with the shape file I used for the domain. As you said it is the projection used in the MRMS. But then I used the domain as a box (by adding 360 to the longitudes) and I am running fine. This is something to do with how geopandas returns the min max of the shape file used. I never saw the second error. I believe it is something to do with the area type you are using. Looks like the cat mask is empty .Let me see the JSON file you are using and I can check it out.
On Fri, Sep 1, 2023, 13:05 Daniel Lassiter @.***> wrote:
Reprex:
- Dropbox folder https://www.dropbox.com/scl/fo/rf8t1xoexcywtzn80n6bh/h?rlkey=iwzv1undid3ttr4ukma0tmiul&dl=0 with input json, transposition domain, watershed, and 2015 MRMS data clipped down to a rectangle that spans a small transposition domain used for testing (it may take a while for this data to upload to Dropbox but should be available by the end of day on 9/1/23)
The MRMS data longitude is in positive degrees west (e.g., 285) and other functions, such as the Shapefile bbox function returns longitude in negative degrees west (e.g., -75). The first problem this causes is in the function RainyDay.findsubbox(inarea,variables,flist[0]):
Traceback (most recent call last): File "/project/quinnlab/dcl3nd/norfolk/stormy/stochastic_storm_transposition/RainyDay2/Source/RainyDay_Py3.py", line 882, in
rainprop.subextent,rainprop.subdimensions,latrange,lonrange=RainyDay.findsubbox(inarea,variables,flist[0]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/gpfs/gpfs0/project/quinnlab/dcl3nd/norfolk/stormy/stochastic_storm_transposition/RainyDay2/Source/RainyDay_utilities_Py3/RainyDay_functions.py", line 865, in findsubbox outrain[lon_name][0], outrain[lon_name][-1] .............................. (traceback stuff)IndexError: index 0 is out of bounds for axis 0 with size 0 This specific error can be resolved within the findsubbox function by adding 360 to longmin and longmax before defining the outrain variable, but that would just be a local solution to a more prevalent problem.
When I patched that issue, the next error cropped up by line 1040:
Traceback (most recent call last): File "/project/quinnlab/dcl3nd/norfolk/stormy/stochastic_storm_transposition/RainyDay2/Source/RainyDay_Py3.py", line 1040, in
xmin=np.min(np.where(np.sum(catmask,axis=0)!=0)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...................... (traceback stuff)ValueError: zero-size array to reduction operation minimum which has no identity I suspect this has to do with the mismatched coordinate systems, but I'm honestly not sure. I printed some of the variables to hopefully help identify where the problem is coming from:
bndcoords [283.41003418 284. 36.65000153 37.09000015]###################################rainprop<main.GriddedRainProperties object at 0x2b1e23c24090>###################################rainprop.subdimensions [45 60]###################################xdim45###################################ydim60###################################catmask.shape (45, 60)############################################catmask [[0. 0. 0. ... 0. 0. 0.] [0. 0. 0. ... 0. 0. 0.] [0. 0. 0. ... 0. 0. 0.] ... [0. 0. 0. ... 0. 0. 0.] [0. 0. 0. ... 0. 0. 0.] [0. 0. 0. ... 0. 0. 0.]]############################################np.sum(catmask,axis=0) [0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.
- 0.
- 0.]###############################################np.sum(catmask,axis=0)!=0 [False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False False]###############################################np.where(np.sum(catmask,axis=0)!=0) (array([], dtype=int64),)###############################################
P.S. I ran into another easily fixable bug: In my newer version of numpy, np.int and np.float have been deprecated. This resolves by replacing these with np.int32 and np.float32.
— Reply to this email directly, view it on GitHub https://github.com/Ashar25/RainyDay/issues/41, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYU4O4DWKWFZ5HOY7R5U73TXYIPXZANCNFSM6AAAAAA4H4Q4SA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
lassiterdc
Reprex:
The MRMS data longitude is in positive degrees west (e.g., 285) and other functions, such as the Shapefile bbox function returns longitude in negative degrees west (e.g., -75). The first problem this causes is in the function
RainyDay.findsubbox(inarea,variables,flist[0]):This specific error can be resolved within the findsubbox function by adding 360 to
longminandlongmaxbefore defining theoutrainvariable, but that would just be a local solution to a more prevalent problem.When I patched that issue, the next error cropped up by line 1040:
I suspect this has to do with the mismatched coordinate systems, but I'm honestly not sure. I printed some of the variables to hopefully help identify where the problem is coming from:
P.S. I ran into another easily fixable bug: In my newer version of numpy, np.int and np.float have been deprecated. This resolves by replacing these with np.int32 and np.float32.