Hi, we are two students trying to model a glass and steel structure that includes openings in Macroflo.
Once we go to Vistra Pro we encounter two problems when we want to visualize the arrows of the flows.
1) When we try to run this option for the whole model it appear this message: Out of memory
2) Then we try to divide the model into parts and run it again. The problem that appears is the following:
"There appears to be an issue with the Macroflo Arrow data on surface 6, in room - MCR0000.
The arrows have therefore not been drawn for this surface.
Please inspect the Hole data for this surface in the current .aps results file"
We would like to know how it is possible to identify this surface and how to rectify the problem.
Thank you in advance.
2 Problems in vista pro
Re: 2 Problems in vista pro
Hi,
If the model is too big (too many openings when running with MacroFlo) then you will hit an upper limit in apache or you will see memory limitations such as this. Other than switching off other programs at simulation time to try free up as much RAM as possible there's not much we can do here without reducing model size.
The message you are seeing in MacroFlo is usually caused by an internal hole in a room - often it is caused by Connecting rooms. As MacroFlo sees the same room on either side of the hole it flags up this error and does not draw arrows. You don't need to worry about this but if it is a problem for you then the only solution is to separate the rooms and re-run the simulation.
The message points you to the room affected (it gives room ID) and also the surface number (in the model browser tree expand the room and then you will see in ModelIT when you click any surface it has a surface number).
Phil
If the model is too big (too many openings when running with MacroFlo) then you will hit an upper limit in apache or you will see memory limitations such as this. Other than switching off other programs at simulation time to try free up as much RAM as possible there's not much we can do here without reducing model size.
The message you are seeing in MacroFlo is usually caused by an internal hole in a room - often it is caused by Connecting rooms. As MacroFlo sees the same room on either side of the hole it flags up this error and does not draw arrows. You don't need to worry about this but if it is a problem for you then the only solution is to separate the rooms and re-run the simulation.
The message points you to the room affected (it gives room ID) and also the surface number (in the model browser tree expand the room and then you will see in ModelIT when you click any surface it has a surface number).
Phil
IES Worldwide Technical Support
Re: 2 Problems in vista pro
Hi, I see now what is the problem. We created a room and then for that room in model IT we created a sloped roof, then we conected the room and the roof without partitions, so it creates a hole. However, for us is not a problem that it does not draw the arrows in that hole, the problem is that once it appears that message it does not crete any arrow.
The only solution is to saparate the rooms?
The only solution is to saparate the rooms?
Re: 2 Problems in vista pro
Yeah,
sounds like it's the connected room that has caused the error. I've asked in the past that when that error occurs we should still draw the arrows for the valid openings (i.e. external windows on the room since that's usually what we're interested in) but I don't know how easy that will be (what seems straight forward to me isn't always easy to code in practice I'm afraid).
I think for your model the only solution is to separate out the rooms.
Maybe you could try Merging the two zones rather than connecting them, I've seen in the past that Merge doesn't always work for complicated geometry so no guarantees here but it might just be the answer. Take a backup copy of the model before you start making these geometry edits...just in case anything goes terribly wrong
Phil
sounds like it's the connected room that has caused the error. I've asked in the past that when that error occurs we should still draw the arrows for the valid openings (i.e. external windows on the room since that's usually what we're interested in) but I don't know how easy that will be (what seems straight forward to me isn't always easy to code in practice I'm afraid).
I think for your model the only solution is to separate out the rooms.
Maybe you could try Merging the two zones rather than connecting them, I've seen in the past that Merge doesn't always work for complicated geometry so no guarantees here but it might just be the answer. Take a backup copy of the model before you start making these geometry edits...just in case anything goes terribly wrong
Phil
IES Worldwide Technical Support