[ET Trac] #2747: Inclusion of sgrid importer in Einstein Toolkit

[Roland Haas]

#2747: Inclusion of sgrid importer in Einstein Toolkit

 Reporter: Samuel Cupp
   Status: new
Milestone: ET_2023_11
  Version: 
     Type: enhancement
 Priority: major
Component: EinsteinToolkit thorn

Comment (by Roland Haas):

GetComponents supports some very limited replacement variables in the `URL`, `AUTH_URL` and `REPO_PATH` variables, namely it will take the `<ARRANGEMENT>/<THORN>` entry of each thorn and will assign `<ARRANGEMENT>` to `$1` \(ie the first thingy\) and `$2` will be set to `<THORN>` \(ie the second component\).   More or less like Perl with do when one used a pattern `m!([^/]*)/(.*)!`.

There is _also_ some magic in how `REPO_PATH` behaves depending on whether it does or does not contain a `$1` or `$2`. 

If it does contain a `$1` or `$2` then the relative path inside of the repository will be exactly as given by `REPO_PATH` \(after variable expansion\). If on the other hand no `$1` or `$2` is found, then the relative path in the repo is `<REPOS_PATH>/<ARRANGEMENT>/<THORN>`. 

What needs to go into `REPO_PATH` thus hugely depends on the git repository layout. `$2` often works nicely because people tend to put all thorns into the root of the git repo. `..` is somewhat unusual.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2747/inclusion-of-sgrid-importer-in-einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einsteintoolkit.org/pipermail/trac/attachments/20230929/1a41a470/attachment.htm>