Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Administered by:

Server stats:

248
active users

bolha.us: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#GPUSPH

0 posts0 participants0 posts today
Giuseppe Bilotta<p>One of the objectives with our <a href="https://fediscience.org/tags/GPUSPH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPUSPH</span></a> model is actually to build a sufficiently detailed 3D model that would allow us to explore these effects and hopefully derive simplified laws that can be applied back to the faster models used for short- and long-term hazard assessment. We're still far from this objective, and it's always a struggle, but we're inching our way forward. And if we can't get there, we'll at least have opened up the path for the next generation willing to tackle the problem.</p><p>One thing's for sure: very few things were more misplaced than my childhood fear that there would be nothing to discover when I'd grow up.</p><p>14/14</p>
Giuseppe Bilotta<p>It's out, if anyone is curious</p><p> <a href="https://doi.org/10.1002/cpe.8313" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">doi.org/10.1002/cpe.8313</span><span class="invisible"></span></a></p><p>This is a “how to” guide. <a href="https://fediscience.org/tags/GPUSPH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPUSPH</span></a>, as the name suggests, was designed from the ground up to run on <a href="https://fediscience.org/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPU</span></a> (w/ <a href="https://fediscience.org/tags/CUDA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CUDA</span></a>, for historical reasons). We wrote a CPU version a long time ago for a publication that required a comparison, but it was never maintained. In 2021, I finally took the plunge, and taking inspiration from <a href="https://fediscience.org/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SYCL</span></a>, adapted the device code in functor form, so that it could be “trivially” compiled for CPU as well.</p><p><a href="https://fediscience.org/tags/HPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HPC</span></a> <a href="https://fediscience.org/tags/GPGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPGPU</span></a></p>
Giuseppe Bilotta<p>Finally got the proofs for my manuscript about porting <a href="https://fediscience.org/tags/GPUSPH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPUSPH</span></a> to run on CPU (yes, we went the other way). The completely bungled up all the figures and listings. This will be a nightmare to fix because I have to comment on each of them to say “this figure goes there, and the figure that should be here is at that other place”, and I'm ready to bet they'll *still* mess it up after I'm done adding all the comments.</p><p>And they are getting paid big monies because gold open access!</p>
ExploreLive feeds
About