You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know that this used to work prior to the current version (don't remember which), but at the moment when I create an empty mask using a non-spatial criteria this error gets thrown:
Traceback (most recent call last):
File "/group/stsgrp2/adriana/swift-survey-2023/mass1to2/protoearth/protoearth0.91x0.455th30/compare_disk_quantities.py", line 713, in <module>
datamantle = apply_index(databnd, indmantle)
File "/group/stsgrp2/adriana/swift-survey-2023/mass1to2/protoearth/protoearth0.91x0.455th30/compare_disk_quantities.py", line 203, in apply_index
data2.gas.coordinates.convert_to_mks()
File "/home/apostema/.local/lib/python3.9/site-packages/swiftsimio/reader.py", line 1123, in getter
read_ranges_from_file(
File "/home/apostema/.local/lib/python3.9/site-packages/swiftsimio/accelerated.py", line 517, in read_ranges_from_file
return read_ranges(handle, ranges, output_shape, output_type, columns)
File "/home/apostema/.local/lib/python3.9/site-packages/swiftsimio/accelerated.py", line 418, in read_ranges_from_file_chunked
output = np.empty(output_shape, dtype=output_type)
ValueError: negative dimensions are not allowed
When I look at the dimensions that try to get broadcasted I get this: (-94633298979068, 3), which seems to be occurring because I'm applying a mask that doesn't contain any particles (something that happens regularly).
Somehow it looks like something gets passed in as an arbitrarily large value as part of ranges in read_ranges_from_file_chunked in accelerated.py.
Empty masks are something that used to be able to occur without a fatal error happening.
The text was updated successfully, but these errors were encountered:
Yes, looks like an overflow in the numba-ized part of the code. This should be tested for (we run the tests with numba's overflow protection on) but please let me know of a minimal example and we can add this to the test suite and fix it.
I know that this used to work prior to the current version (don't remember which), but at the moment when I create an empty mask using a non-spatial criteria this error gets thrown:
When I look at the dimensions that try to get broadcasted I get this: (-94633298979068, 3), which seems to be occurring because I'm applying a mask that doesn't contain any particles (something that happens regularly).
Somehow it looks like something gets passed in as an arbitrarily large value as part of
ranges
inread_ranges_from_file_chunked
in accelerated.py.Empty masks are something that used to be able to occur without a fatal error happening.
The text was updated successfully, but these errors were encountered: