<html>#2747: Inclusion of sgrid importer in Einstein Toolkit
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Samuel Cupp</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2023_11</td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>GetComponents supports some very limited replacement variables in the <code>URL</code>, <code>AUTH_URL</code> and <code>REPO_PATH</code> variables, namely it will take the <code><ARRANGEMENT>/<THORN></code> entry of each thorn and will assign <code><ARRANGEMENT></code> to <code>$1</code> (ie the first thingy) and <code>$2</code> will be set to <code><THORN></code> (ie the second component). More or less like Perl with do when one used a pattern <code>m!([^/]*)/(.*)!</code>.</p>
<p>There is <em>also</em> some magic in how <code>REPO_PATH</code> behaves depending on whether it does or does not contain a <code>$1</code> or <code>$2</code>. </p>
<p>If it does contain a <code>$1</code> or <code>$2</code> then the relative path inside of the repository will be exactly as given by <code>REPO_PATH</code> (after variable expansion). If on the other hand no <code>$1</code> or <code>$2</code> is found, then the relative path in the repo is <code><REPOS_PATH>/<ARRANGEMENT>/<THORN></code>. </p>
<p>What needs to go into <code>REPO_PATH</code> thus hugely depends on the git repository layout. <code>$2</code> often works nicely because people tend to put all thorns into the root of the git repo. <code>..</code> is somewhat unusual.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2747/inclusion-of-sgrid-importer-in-einstein'>https://bitbucket.org/einsteintoolkit/tickets/issues/2747/inclusion-of-sgrid-importer-in-einstein</a></p>
</html>