eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

211
active users

#numerical

0 posts0 participants0 posts today
💧🌏 Greg Cocks<p>Escalation Of Caldera Unrest Indicated By Increasing Emission Of Isotopically Light Sulfur<br>--<br><a href="https://doi.org/10.1038/s41561-024-01632-w" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">doi.org/10.1038/s41561-024-016</span><span class="invisible">32-w</span></a> &lt;-- shared paper<br>--<br><a href="https://techhub.social/tags/GIS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GIS</span></a> <a href="https://techhub.social/tags/spatial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spatial</span></a> <a href="https://techhub.social/tags/mapping" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mapping</span></a> <a href="https://techhub.social/tags/geology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geology</span></a> <a href="https://techhub.social/tags/structuralgeology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>structuralgeology</span></a> <a href="https://techhub.social/tags/volcano" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>volcano</span></a> <a href="https://techhub.social/tags/vulcanism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulcanism</span></a> <a href="https://techhub.social/tags/caldera" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>caldera</span></a> <a href="https://techhub.social/tags/numerical" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>numerical</span></a> <a href="https://techhub.social/tags/model" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>model</span></a> <a href="https://techhub.social/tags/modeling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modeling</span></a> <a href="https://techhub.social/tags/eruption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eruption</span></a> <a href="https://techhub.social/tags/risk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>risk</span></a> <a href="https://techhub.social/tags/hazard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hazard</span></a> <a href="https://techhub.social/tags/seismicity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>seismicity</span></a> <a href="https://techhub.social/tags/deformation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deformation</span></a> <a href="https://techhub.social/tags/gases" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gases</span></a> <a href="https://techhub.social/tags/engineeringgeology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>engineeringgeology</span></a> <a href="https://techhub.social/tags/physicochemical" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>physicochemical</span></a> <a href="https://techhub.social/tags/monitoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>monitoring</span></a> <a href="https://techhub.social/tags/CampiFlegrei" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CampiFlegrei</span></a> <a href="https://techhub.social/tags/Italy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Italy</span></a> <a href="https://techhub.social/tags/sulfur" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sulfur</span></a> <a href="https://techhub.social/tags/fumaroles" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fumaroles</span></a> <a href="https://techhub.social/tags/hydrothermal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hydrothermal</span></a> <a href="https://techhub.social/tags/magma" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>magma</span></a> <a href="https://techhub.social/tags/dataanalysis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataanalysis</span></a> <a href="https://techhub.social/tags/global" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>global</span></a></p>
Olivier<p>I've been working with C++ numerical/scientific software for over 10 years, and one of my biggest grief is mishandling of numerical conversions. The <a href="https://en.cppreference.com/w/cpp/language/implicit_conversion" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.cppreference.com/w/cpp/lang</span><span class="invisible">uage/implicit_conversion</span></a> rules are confusing at best, and have undefined outcomes in too many cases. And the fact that static_cast will simply hush compiler warnings is both misleading and dangerous. Lastly, the std functions are an inconsistently named mess: round has lround, but not ceil, floor or trunc. Then there's the 27 easy flavours of rint and nearbyint that are almost the same except exceptions.</p><p>There have been some improvements recently though.</p><p>The cpp core guidelines have a gsl narrow that throws a catchable exception. However that's a very limited and limiting use case. Then there's gsl narrow_cast which is nothing more than a FIXME ("you asked for it," as they say).</p><p>C++26 is finally introducing <a href="https://en.cppreference.com/w/cpp/numeric/saturate_cast" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.cppreference.com/w/cpp/nume</span><span class="invisible">ric/saturate_cast</span></a> to convert between integer types without implicit truncation (or undefined behaviour).</p><p>I hope the C++ standards committee acknowledges and addresses this issue in a clean consistent way once and for all.</p><p><a href="https://sunny.garden/tags/cpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cpp</span></a> <a href="https://sunny.garden/tags/cplusplus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cplusplus</span></a> <a href="https://sunny.garden/tags/numerical" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>numerical</span></a> <a href="https://sunny.garden/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software</span></a> <a href="https://sunny.garden/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwaredevelopment</span></a></p>