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 set an obst originally to be not present and use a timer device to make it appear in the domain later at t=0.75.
The slice for CELL PHASE still shows the obstacle at t=0. Same with the DEVC 'CellPhaseInObst', it shows a 1 (i.e. SOLID) at t=0 in the devc.csv file. Interestingly a BNDF does not show the obst surface temperature at t=0, probably a SMV trick.
I came across this as we are trying to streamline the connected zones, obst creation and removal and poisson matrix generation at setup time. Turns out the issue we are seeing today (geom_stretched_grid.fds) refers to DUMP_MESH_OUTPUTS being called before MESH_ZONE entries get generated (in GLOBAL_MATRIX_REASSIGN).
An option Ill try next is to move mesh and global dumps after the first call to GLOBAL_MATRIX_REASSIGN.
The text was updated successfully, but these errors were encountered:
Not sure if this is a bug or a feature. For the case:
I set an obst originally to be not present and use a timer device to make it appear in the domain later at t=0.75.
The slice for CELL PHASE still shows the obstacle at t=0. Same with the DEVC 'CellPhaseInObst', it shows a 1 (i.e. SOLID) at t=0 in the devc.csv file. Interestingly a BNDF does not show the obst surface temperature at t=0, probably a SMV trick.
I came across this as we are trying to streamline the connected zones, obst creation and removal and poisson matrix generation at setup time. Turns out the issue we are seeing today (geom_stretched_grid.fds) refers to DUMP_MESH_OUTPUTS being called before MESH_ZONE entries get generated (in GLOBAL_MATRIX_REASSIGN).
An option Ill try next is to move mesh and global dumps after the first call to GLOBAL_MATRIX_REASSIGN.
The text was updated successfully, but these errors were encountered: