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
When reading binary data, I found that sometimes the reader exited early for boundary data. I think this is due to the fact that the } character is sometimes in binary OF data. In the function split_boundary_content this causes a wrong content range.
At line 172 of field_parser.py. I added an ugly fix which checks if the following line is long enough to still contain binary data:
if in_boundary_field:
#USER FIX
if (lc.rstrip() == b'}' and len(content[n+1])<30):
break
if in_patch_field:
if (lc.strip() == b'}' and len(content[n+1])<30):
The text was updated successfully, but these errors were encountered:
Thanks again for you valuable work. I have noticed that the reading field is still a problem with rotatingWall BC since there are parenthesis { } by imposing rotation \omega before the values , it is possible to find a way to fix it?
rotatingWall BC:
boundaryField
{
innerWall
{
type rotatingWallVelocity;
origin (0 0 0);
axis (0 0 1);
omega
{
type constant;
value 6.28318530718;
}
value nonuniform List
512
(.......
When reading binary data, I found that sometimes the reader exited early for boundary data. I think this is due to the fact that the
}
character is sometimes in binary OF data. In the functionsplit_boundary_content
this causes a wrong content range.At line 172 of
field_parser.py
. I added an ugly fix which checks if the following line is long enough to still contain binary data:The text was updated successfully, but these errors were encountered: