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
#19 There seems to be still one bug remaining from aforementioned issue that was solved earlier. This appears when writing large files exceeding around 2 GB. For instance, when running the Taylor-Green vortex test case with polynomial order of 11 or more, horses3d will fail to write the initial solution and crash. The bug is in line 2981 of /Solver/src/libs/mesh/HexMesh.f90:
exceeds the value for a 32-bit integer and overflows because it has not been promoted to integer of type AddrInt yet. The solution seems simple, for instance, changing this line to
#19 There seems to be still one bug remaining from aforementioned issue that was solved earlier. This appears when writing large files exceeding around 2 GB. For instance, when running the Taylor-Green vortex test case with polynomial order of 11 or more, horses3d will fail to write the initial solution and crash. The bug is in line 2981 of /Solver/src/libs/mesh/HexMesh.f90:
pos = POS_INIT_DATA + (e % globID-1)*5_AddrInt*SIZEOF_INT + padding*e % offsetIO * SIZEOF_RP
What happens is that at some point, the value of
padding*e % offsetIO * SIZEOF_RP
exceeds the value for a 32-bit integer and overflows because it has not been promoted to integer of type AddrInt yet. The solution seems simple, for instance, changing this line to
pos = POS_INIT_DATA + (e % globID-1)*5_AddrInt*SIZEOF_INT + 1_AddrInt* padding*e % offsetIO * SIZEOF_RP
I have suggested the same in my pull request #224
The text was updated successfully, but these errors were encountered: