Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #1581: Clean up ET web site menu
by Einstein Toolkit 24 Oct '17

24 Oct '17

#1581: Clean up ET web site menu -------------------------------------+-------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- The menu entries "support" and "issue tracker" should be separated from "wiki", "blog", and "seminars". The first two are about the code, the latter two about the community. I suggest to move the first two to the "download" section that currently has no sub-menus. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1581> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1547: issues with stampede
by Einstein Toolkit 24 Oct '17

24 Oct '17

#1547: issues with stampede ----------------------------+----------------------------------------------- Reporter: jchsma@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: ET_2013_11 Keywords: | ----------------------------+----------------------------------------------- Over the past few months, I have been using RIT's LazEv code with only minor hiccups on stampede (particularly, the unreproducible 'dapl_conn_rc' crashes that I'm sure other stampede users are familiar with). This checkout was of the previous release, ET_2013_05, and compiled with Intel MPI. Most of the jobs I ran took advantage of some symmetry, and I was able to run on 12-16 nodes at about 50-60% memory usage. After the sync issue was backported, I checked out the new release, ET_2013_11 and immediately ran into problems. The first issue was with the run performance and LoopControl, which, with the mailing lists help, we sorted out. The second was with crashes and checkpointing. With both Intel MPI and MVAPICH2 configurations, the code would hang (~50% of the time) when dumping checkpoints, and 100% when dumping a termination checkpoint. Further, the crashes seem more frequent, and I couldn't get a simulation to run for a full 24 hours without crashing (either by stalling on checkpointing or otherwise). So, I checked out a clean version of the toolkit, with only toolkit thorns, and removed any thorns specific to RIT. I compiled with both the Intel MPI and MVAPICH2 configurations in simfactory. In both cases, I can run the 'qc0-mclachlan.par' file to completion with no issues. So I edited the qc0 parfile to update the grid, remove the symmetries, and update the initial data to match my test parameter file. I ran the job on 20 nodes, and with either configuration, I was not successful in running the job to completion on any of my numerous attempts. Intel MPI runs die with the standard unhelpful "dapl_conn_rc" error at random times in the evolution, and the MVAPICH2 dies with: [c431-903.stampede.tacc.utexas.edu:mpispawn_7][readline] Unexpected End- Of-File on file descriptor 6. MPI process died? [c431-903.stampede.tacc.utexas.edu:mpispawn_7][mtpmi_processops] Error while reading PMI socket. MPI process died? [c431-903.stampede.tacc.utexas.edu:mpispawn_7][child_handler] MPI process (rank: 15, pid: 106620) terminated with signal 9 -> abort job [c429-501.stampede.tacc.utexas.edu:mpirun_rsh][process_mpispawn_connection] mpispawn_7 from node c431-903 aborted: Error while reading a PMI socket (4) The IMPI jobs died with the same dapl_conn_rc error at run times of 2 hours, 8 hours, and 21 hours. I also had one job that hung and did not exit until it was killed by the queue manager. The MVAPICH2 jobs died at around 3 hours and 8 hours with the error above. We've been in contact with TACC and they said it was a Cactus issue, so I am sending this report. Attached is the parameter file I used for the tests. They should work with a stock ET_2013_11 checkout. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1547> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #980: Remove support for the flesh-based MPI mechanism
by Einstein Toolkit 24 Oct '17

24 Oct '17

#980: Remove support for the flesh-based MPI mechanism -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- The flesh-based MPI mechanism has just been deprecated in favour of ExternalLibraries/MPI. Even though the latter is new, it is probably a good idea to completely disable the old mechanism since having any mixture of thorns/optionlists using the old and new mechanisms is completely untested and will likely lead to problems and confusion. It's better to give a useful fatal error message if someone still specifies "MPI = " in their optionlist than to have things break in other weird and wonderful ways. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/980> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #2082: Create an ET news page
by Einstein Toolkit 23 Oct '17

23 Oct '17

#2082: Create an ET news page -------------------------------------+-------------------------------------- Reporter: hinder | Owner: Type: task | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- This page could list things like: * New papers which use the ET * New releases * Technological developments * Workshops/conferences with an ET focus The idea is to show that the ET is an active project. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2082> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #2081: Provide a method to upgrade an ET checkout from one release to the next
by Einstein Toolkit 12 Oct '17

12 Oct '17

#2081: Provide a method to upgrade an ET checkout from one release to the next ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: GetComponents | Version: development version Keywords: | ---------------------------+------------------------------------------------ Currently, the ET release notes say to clone the new release from scratch. It would be good to be able to upgrade an existing ET checkout. Any solution should address the issue of what to do with existing committed and uncommitted changes in each repository (otherwise there is little benefit over checking out from scratch). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2081> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2079: NSTracker thorn not available for download
by Einstein Toolkit 12 Oct '17

12 Oct '17

#2079: NSTracker thorn not available for download --------------------------------------+------------------------------------- Reporter: figura.antonio@… | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | --------------------------------------+------------------------------------- The link to the thorn NSTracker present in http://einsteintoolkit.org/gallery/bns/nsnstohmns.th is not working and gives an error when downloading the thorn. I have solved by manually downloading the thorn from https://svn.cct.lsu.edu/repos/numrel/LSUThorns/NSTracker/. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2079> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #2070: shallow checkouts do not work with branches
by Einstein Toolkit 12 Sep '17

12 Sep '17

#2070: shallow checkouts do not work with branches ---------------------------+------------------------------------------------ Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: GetComponents | Version: development version Keywords: | ---------------------------+------------------------------------------------ Currently using both --shallow and a branch (rather than master) fails since GetComponents wants to first clone the full repo then switch to the requested branch which fails with a shallow clone. However newer versions of git (>=1.7) support a "-b" (branch) option for clone and that one works fine even with shallow clones. My recollection is that we could not use this method initially since there were clusters around that only offered git 1.6 (queenbee likely). This is no longer the case and all clusters in simfactory offer at least git 1.7. This pull request: https://github.com/gridaphobe/CRL/pull/6/files both fixes the problem and simplifies the code. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2070> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1817: Update LORENE library
by Einstein Toolkit 04 Sep '17

04 Sep '17

#1817: Update LORENE library -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: ET_2015_11 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- The current Lorene thorn isn't up to date with the version that is available from Meudon. A new version of a thorn containing a new version of Lorene is available here: https://einstein.pr.infn.it/svn/numrel/pub/arrangements/PRThorns/LORENE/tru… Diffs aren't available in the repo, but are attached as file here. That is quite large, but mostly due to necessary changes in the patches contained in the thorn (because the underlying files changed, not because the patches would have changed in functionality). Normaly, updates like this would not be an issue, but this update of Lorene changes (breaks) old Lorene files. This is nothing we could decide upon, this is the Meudon group's decision. I nevertheless propose to update to the new version. This would need to include updating the testsuites of depending thorns, which might mean re-creating their ID files. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1817> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 31

[Einstein Toolkit] #64: Refactory/redesign archiving
by Einstein Toolkit 29 Aug '17

29 Aug '17

#64: Refactory/redesign archiving ------------------------+--------------------------------------------------- Reporter: mthomas | Owner: mthomas Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- Implement archiving using archive machines with an iomethod key. Provide another key like rsync-excludes for people to exclude files from being archived. Provide a lightweight archive-like method for copying a simulation from one machine to another machine. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/64> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #2075: caol from LORENE2 requires RCS ident command
by Einstein Toolkit 28 Aug '17

28 Aug '17

#2075: caol from LORENE2 requires RCS ident command -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: LORENE2 | -----------------------------------+---------------------------------------- The coal (and init_bin) commands that are build along with LORENE2 call rcs's ident command but this dependency is neither checked for not tested for. I don't know if not having the command around causes any more harm than not having the rcs info written to log files or not. We cannot abort the Cactus build if ident is not found as it is perfectly fine to use LORENE2 with existing data files (in which case coal and init_bin are never used). We may consider not building the utilities if ident is missing and if the rcs output if considered important. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2075> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac