-
Notifications
You must be signed in to change notification settings - Fork 66
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
errors when run BuoyancyTest with chrono #45
Comments
Sorry I failed to past the picture and I am trying to upload it. |
Hi, Have you managed to run your case? Best regards, |
Hello, the issue seems to be due to a mismatch between what GPUSPH thinks the binary layout of a Chrono object is, versus what the library thinks. A possible reason for this could be that Chrono and GPUSPH are being compiled with different compilers (or different versions of the same compiler). Can you verify if GPUSPH is being compiled with the same (host) compiler and version as what was used with Chrono? |
Yes I have run the test successfully, your suggestiogn is useful anges. These days I am busy with my test so pologize for my response not in time。 |
@Oblomov Can you send your email to me , I have some question about the GPUSPH and want to get your help. In Github the communication is not in time. |
@agnesLeroy |
@agnesLeroy |
Hi! |
@agnesLeroy |
Hi, |
@agnesLeroy |
I suggest that you look at the BuoyancyTest example of GPUSPH to sort out your problem. |
OK I will try and post my question if I have. Thanks for your patience. |
@agnesLeroy |
Both reasons. The coding restriction is that the fluid and object number are encoded in the same area, using 4 bits for the fluid and 12 bits for the object number, so in theory it would be possible to have up to 2^4 = 16 fluids and 2^12 = 4096 objects. However, since some shared memory allocations are fixed, the number of fluids is limited to 4 and the number of objects is limited to 16. It should be possible to increase these limits up to the maximum allowed by changing the corresponding defines (MAX_FLUID_TYPES and MAX_BODIES in src/particledefine.h) We could also consider a build time parameter (e.g. |
@Oblomov |
Hello @Dongxueyang Releasing the limit altogether, or moving to 32-bit for the object it, would require much more extensive changes to the code. I think allowing custom configurations would be the first step anyway. But yes, please open a separate issue for this, so we can address it on its own. |
@Oblomov But the curve is different between each other and the experiment curve and theorical curve. |
@agnesLeroy |
Hello @Dongxueyang SPH, like any numerical method, approximates the analytical solution, with an approximation that is better (i.e. closer to the correct one) as the resolution grows. The plot seems to confirm this, as finer resolutions (smaller dp) provide solutions that are closer to both the experimental and theoretical line. So in general you should try running your simulations at the highest possible resolution. At any given resolutions, there are also a few parameters that you can try tuning to get better results. For example, using a higher speed of sound will give a stiffer (less compressible) fluid. Also, if you are using the artificial viscosity model you can try lowering the artificial viscosity coefficient, or switch to a different viscous model (e.g. SPS). |
Hi
I have compiled the gpusph successfully and can run some examples in src/problems. But when I run the example BuoyancyTest and Objects I got such errors with chrono
I think the error is related to the chrono. but I donnot know what:
1.I install the chrono successful but what can I do to make a link between chrono and GPUSPH
2.when I install chrono,at step cmake which mudule should be set "ON" to support basic functions of GPUSPH.I see all the modules should be set "OFF" from the install document of GPUSPH.
3.In my computer, I have install another program which is linked to chrono.So if will there be conflects when i use chrono in GPUSPH. The error is seems to related to another program"Yade-Dual4.3"
all regards
The text was updated successfully, but these errors were encountered: