<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 19, 2014 at 4:25 PM, Roland Haas <span dir="ltr"><<a href="mailto:roland.haas@physics.gatech.edu" target="_blank">roland.haas@physics.gatech.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hello all,<br>
<div class=""><br>
>>> I might be wrong, but didn't we want GRHydro+GRHydro_Initdata as one<br>
>>> "GRHydro" arrangement?<br>
>> I don't recall this decision. Do you have a pointer to the discussion?<br>
</div>There are notes on the wiki in the "repository transition" page, the<br>
closest thing to discussion notes are likely the minutes from 03/18/2014<br>
(BTW: any progress on getting links to the archived email into the<br>
mailing list email footers? This would be really helpful and there were<br>
some suggestions on how to make this work on the trac ticket).<br>
<br>
GRHydro_InitData would be treated as a "Test" thorn (not ID in there is<br>
actually used for a real simulation) and thus would be "related" to<br>
GRHydro. The two thorns are also very tightly coupled since<br>
GRHydro_InitData directly calls some of GRHydro's routines.<br></blockquote><div><br></div><div>I suggest to keep GRHydro in EinsteinEvolve, and to either have GRHydro_InitData there as well, or maybe to move it to EinsteinTest, and maybe rename it to GRHydro_Test.</div>
<div><br></div><div>-erik</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
>> I know that it is difficult to place GRHydro_InitData into a particular<br>
> arrangement, but at the same time, reducing the number of arrangements is<br>
> also important.<br>
><br>
> As far as I remember this was suggested because GRHydro is internally a git<br>
> repository, so it doesn't seem sensible to convert it to separate svn<br>
> repositories only to convert back to git and merge again. I think the<br>
> suggestion was to instead just directly use the GRHydro git repository.<br>
</div>As far as I know there is no GRHydro git repository. The svn repo in the<br>
ET is the official GRHydro thorn.<br>
<br>
There *is* a version of GRHydro that is in a git repository, namely the<br>
version in Caltech's Zelmani repository. This is actually where most<br>
development happens and for a long time I regularly would sync (by hand<br>
by cherry picking commits) the two repositories. Since I have not done<br>
so for a bit, I don't know how much they differ by now.<br>
<br>
Zelmani contains other things than GRHydro (eg a copy of RNSID) so it<br>
cannot be made public in its entirety. Also the version of GRHydro in<br>
Zelmani is "experimental" and contain some hacks the were rejected from<br>
the svn repo (and it *will* fail often since all of Caltech's<br>
development happens there and the group tries many things).<br>
<br>
So I would actually use the current svn repo as a starting point, then<br>
given that we may only want a single repo for all of it (which may not<br>
be feasible since eg some branches in Zelmani are used to provide a<br>
consistent set of thorns from *multiple* external repositories [eg<br>
McLachlan, LocalInterp]) make some branches for the Caltech and other<br>
stuff that will never make it into master.<br>
<br>
Given the amount of changes and experiments going on in Zelmani it is (I<br>
suspect) not possible to have a situation where before an ET release we<br>
"clean up" and "safeguard" experiments in GRHydro and make the result<br>
the released version (this would introduce many half-baked things into<br>
the released version).<br>
<br>
Yours,<br>
Roland<br>
<span class=""><font color="#888888"><br>
--<br>
My email is as private as my paper mail. I therefore support encrypting<br>
and signing email messages. Get my PGP key from <a href="http://keys.gnupg.net" target="_blank">http://keys.gnupg.net</a>.<br>
<br>
</font></span><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a>
</div></div>