Hi
Please consider joining the weekly Einstein Toolkit phone call at 10 am US central time on Mondays. As usual, you can find instructions how to join on the following web site:
http://einsteintoolkit.org/community/support/
In short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#.
Frank Loeffler
On Sun, Jun 15, 2014 at 10:16:25PM -0500, Frank Loeffler wrote:
Please consider joining the weekly Einstein Toolkit phone call at 10 am US central time on Mondays. As usual, you can find instructions how to join on the following web site:
Something I would like to quickly discuss is a small issue that I believe is still open concerning the repository rearrangement.
The current list can be found here:
https://docs.einsteintoolkit.org/et-docs/Repository_transition
The issue is that it is not clear (at least to me, and not in that list) what to do with thorns that have 'attachment/test' thorns, like
GRHydro / GRHydro_Init_Data MoL / TestMoL
From a developers point it would be nice to have them in the same repository - which would, in the current state of things mean in the same arrangement. However, logically they don't belong there (e.g. GRHydro_Init_Data does not belong in EinsteinEvolve).
Possible solutions would be (not sorted in any way, especially not my preference): - put things that technically belong together in one repository and use the symlink-hack to point from different arrangements to the same repository in repos. - put test thorns (GRHydro_Init_Data/TestMoL) into test repositories (CactusTest / EinsteinTest). - create arrangements for such units, and put all thorns in that. This would mean, e.g., arrangements/GRHydro/GRHydro and arrangements/GRHydro/GRHydro_Init_Data
Essentially it boils down to three questions: - Which arrangements should these thorns be in? - Which repositories should these thorns be in? - Should the first two be the same (then the repo could be directly checked out into arrangements/).
Frank
On Sun, Jun 15, 2014 at 10:16:25PM -0500, Frank Loeffler wrote:
Please consider joining the weekly Einstein Toolkit phone call at 10 am US central time on Mondays. As usual, you can find instructions how to join on the following web site:
Something else I didn't get around doing yesterday was looking at recent issue activity.
Within the last two weeks, 8 tickets were changed, and are still open [1]:
1) 1627: McLachlan rewrite branch: any update here? 2) 1628: enabling padding by default: are there news? 3) 1624: remove MOLDOESCOMPLEX from MoL: reviewed ok, "already implemented", but still open 4) 1629: Use DANE for server certificates. FL: In don't think this is useful enough to justify the trouble, for now: wontfix? 5) 1618: Compile with AMPI: Steve: is there an updated patch? 6) 1630: ML_BSSN harmonic shift is ill-posed: anyone interested in preparing a patch? 7) 1632: problem with compilation: waiting on user input, or a developer with an Ubuntu installation to try to reproduce 8) 1631: The dgfe branch for McLachlan generates NaNs: reviewed ok
Frank
[1] https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&a...
users@lists.einsteintoolkit.org