<html>#2377: Cactus::psync_error = yes without Cactus::use_psync = yes makes all GF unaccessible
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Carpet</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Pontially this could be solved by collapsin <code>use_psync</code>, <code>psync_error</code> and <code>psync_only</code> into a single KEYWORD parameter with like so:</p>
<div class="codehilite"><pre><span></span>KEYWORD presync_level "how strongly to check data access"
{
"no" :: "disable all runtime checks"
"check" :: "check allowed access and data correctness at runtime"
"sync" :: "automatically synchronize when needed"
"only" :: "disallow old-style boundary conditions and explicit synchronization"
} "no"
</pre></div>
<p>where “check” would be something like <code>psync_error=yes</code> and <code>use_psync=no</code> (so one needs to check that this actually works), while “sync” has them both on and “onyl” adds <code>psync_only</code>.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2377/cactus-psync_error-yes-without-cactus'>https://bitbucket.org/einsteintoolkit/tickets/issues/2377/cactus-psync_error-yes-without-cactus</a></p>
</html>