New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMPUA Issue #6646
Comments
If I make the second device XB=0.501,0.15 and the third -0.15,-0.501, then the mass in those devices goes to zero. It looks like some form of precision error in picking which wall cells belong to which devices (0.5 expressed in binary is actually going to be something that looks like 0.499999999 or 0.500000001). |
Thanks for the quick response. I have tried this method with a number of other cases and it still seems like there is an issue. I have also tried with larger gaps between the buckets of 0.01 m as seen below. With this, I am still running into this problem where there is more water in the sum of all the buckets (1-4) than what is actually being released by the sprinkler. I noticed this issue when upgrading from version 6.5.3 to 6.7.
|
I'll take a look at this. |
FDS Source: Issue #6646. Fix bug in SURFACE AREA stats
This was a bug. I fixed it, so that now the buckets add up to the right amount. |
I am running a simple sprinkler spray case and collecting the water using AMPUA with STATISTICS='SURFACE INTEGRAL'. Bucket 1 is located directly under the sprinkler and buckets 2 and 3 are located to the right and left of bucket 1. I also have a 4th larger bucket that encompasses the entire floor area. The spray is directed only into bucket 1. In the 3 seconds of spray, I am only discharging a total of 1 liter (1 kg) of water. The total bucket and the value in bucket 1 confirms that there is only 1 kg of water discharged. However, buckets 2 and 3 show 0.48 and 0.5 kg of water, respectively. This concludes that there was actually 2 kg of water discharged which is not the case. I have also decreased the mesh size and it still occurs but to a lesser degree. I appreciate any thoughts with this.
The text was updated successfully, but these errors were encountered: