Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2621: keep running into nan ,need help
by Artectek 23 Jul '22

23 Jul '22

#2621: keep running into nan ,need help Reporter: Artectek Status: new Milestone: ET_2022_05 Version: ET_2022_05 Type: task Priority: minor Component: EinsteinToolkit thorn Comment (by Artectek): @@{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} ，sorry to bother you again, but i tried your advice,setting dx=dy=dz=12,it still ran into nan at about the same time as before ``` INFO (NSTracker): Found star at (9.375,5.625,0) 139444 1307.287 | 61.5954977 | 0.0003189 0.0020122 | 0.0008347 | 1.4536858 | 0.0038059 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139448 1307.325 | 61.5964119 | 0.0003189 0.0020122 | 0.0008347 | 1.4639129 | 0.0038125 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139452 1307.362 | 61.5969842 | 0.0003189 0.0020122 | 0.0008347 | 1.4745400 | 0.0038180 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139456 1307.400 | 61.5976158 | 0.0003189 0.0020123 | 0.0008347 | 1.4825708 | 0.0038222 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139460 1307.438 | 61.5972051 | 0.0003189 0.0020123 | 0.0008347 | 1.4907403 | 0.0038258 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139464 1307.475 | 61.5980420 | 0.0003189 0.0020124 | 0.0008347 | 1.4315498 | 0.0038305 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139468 1307.513 | 61.5987091 | 0.0003189 0.0020124 | 0.0008347 | 1.4378927 | 0.0038341 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139472 1307.550 | 61.5993935 | 0.0003189 0.0020125 | 0.0008348 | 1.4155038 | 0.0038366 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139476 1307.588 | 61.5998317 | 0.0003189 0.0020125 | 0.0008348 | 1.4033181 | 0.0038379 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139480 1307.625 | 61.6007500 | 0.0003189 0.0020125 | 0.0008348 | 1.4024480 | 0.0038378 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139484 1307.662 | 61.6013809 | 0.0003189 0.0020126 | 0.0008348 | 1.4011666 | 0.0038363 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139488 1307.700 | 61.6020977 | 0.0003189 0.0020126 | 0.0008348 | 1.4000632 | 0.0038334 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139492 1307.737 | 61.6018872 | 0.0003189 0.0020126 | 0.0008348 | 1.3990310 | 0.0038290 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139496 1307.775 | 61.6028024 | 0.0003189 0.0020126 | 0.0008348 | 1.3982709 | 0.0038232 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,5.625,0) 139500 1307.812 | 61.6033686 | 0.0003189 0.0020126 | 0.0008348 | 1.2511643 | 0.0038163 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,5.625,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-5.625,0) INFO (NSTracker): Found star at (9.375,10.875,0) 139504 1307.850 | 61.6041180 | -nan 0.0014981 | 0.0006712 | 1.0485346 | 0.0019915 | 2345 INFO (CarpetTracker): Setting position of refined region #1 from surface #0 to (9.375,10.875,0) INFO (CarpetTracker): Setting position of refined region #2 from surface #1 to (-9.375,-10.875,0) INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 0 INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 1 INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 0 INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 1 INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 0 INFO (CarpetRegrid2): Enforcing grid structure properties, iteration 1 WARNING level 1 from host node2 process 0 in thorn CarpetLib, file /public/home/guolj/nr/etk/Cactus/configs/sim/build/CarpetLib/dh.cc:161: -> /public/home/guolj/nr/etk/Cactus/configs/sim/build/CarpetLib/dh.cc:971: [ml=0 rl=5 c=0] The following grid structure consistency check failed: Synchronisation and boundary prolongation: All points must have been received needrecv.empty() ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…

1 0

#2624: not possible to run tests *only* on 2 (or more) MPI ranks
by Roland Haas 22 Jul '22

22 Jul '22

#2624: not possible to run tests *only* on 2 (or more) MPI ranks Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): title: not possible to run tests *only* on 2 (or more) MPI ranks (was not possible to run tests *ony* on 2 (or more) MPI ranks) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2624/not-possible-to-r…

1 0

#2624: not possible to run tests *ony* on 2 (or more) MPI ranks
by Roland Haas 22 Jul '22

22 Jul '22

#2624: not possible to run tests *ony* on 2 (or more) MPI ranks Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus A while ago Cactus' testsuite system gained the ability to run tests with “N” MPI ranks along with those requiring “N\+1” \(or greater\) MPI ranks. This has the side effect that it is impossible to run only the tests requiring “N\+1” ranks, since the “N” rank tests will always be included. This is somewhat surprising and has lead to confusion about which tests are failing. A method to run only on the precise number of MPI ranks set in `CCTK_TESTSUITE_RPOCESSORS` \(or whatever it s name is\) should be provided, eg for use by the automated testing system \(which runs 1 and 2 ranks anyway to tests thorns that do not specify a preference for both numbers of MPI ranks\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2624/not-possible-to-r…

1 0

#2499: New machine thornyflat at WVU
by Roland Haas 22 Jul '22

22 Jul '22

#2499: New machine thornyflat at WVU Reporter: Erik Schnetter Status: duplicate Milestone: Version: development version Type: enhancement Priority: minor Component: SimFactory Changes (by Roland Haas): status: duplicate (was open) Comment (by Roland Haas): Duplicate of #2598. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2499/new-machine-thorn…

1 0

#2623: Colons in parent's parent directory name causes build failure
by Roland Haas 22 Jul '22

22 Jul '22

#2623: Colons in parent's parent directory name causes build failure Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): autoconf is the one using absolute paths. I tried getting rid of them once \(for spaces on windows\), see: [https://bitbucket.org/cactuscode/cactus/branch/rhaas/spaces](https://bitbuc… So the absolute paths are not going away so easily. That colons also cause issues is new and something that may be fixable \(the spaces are an issue b/c make really cannot handle spaces in paths, “just don’t use them” is what the official solution boils down to\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2623/colons-in-parents…

1 0

#2621: keep running into nan ,need help
by Artectek 22 Jul '22

22 Jul '22

#2621: keep running into nan ,need help Reporter: Artectek Status: new Milestone: ET_2022_05 Version: ET_2022_05 Type: task Priority: minor Component: EinsteinToolkit thorn Comment (by Artectek): thanks,I will try that right away -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…

1 0

#2621: keep running into nan ,need help
by Roland Haas 22 Jul '22

22 Jul '22

#2621: keep running into nan ,need help Reporter: Artectek Status: new Milestone: ET_2022_05 Version: ET_2022_05 Type: task Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): kind: task (was bug) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…

1 0

#2621: keep running into nan ,need help
by Roland Haas 22 Jul '22

22 Jul '22

#2621: keep running into nan ,need help Reporter: Artectek Status: new Milestone: ET_2022_05 Version: ET_2022_05 Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Two items were brought up: 1. the resolution may well be too low. The gallery example \(which your parfile dns.par seems to be base on\) sets the resolution to a very coarse value, namely 18Msun on the coarsest level and 18Msun/2^6 = 0.28 for the level that covers the star\(s\) initially. This corresponds \(using Msun ~~ 1.48km\) to a resolution of 416m which is too coarse for any serious simulation. It should be no more than about 280m so all resolutions should be scaled to dx=dy=dz=12 2. Looking at your log output then at t=0 there is: “INFO \(CarpetTracker\): Setting position of refined region #1 from surface #0 to \(13.5,0,0\)” indicating that the star was found with center at x=13.5 however you initial grid structure for the refined regions \(the CarpetRegrid2::position\_x parameters\) centers the boxes around x=22.5 which is not correct \(probably not the cause for the failure at the end but incorrect and will lead to an initially incorrect grid structure\). You can open eg 2D output files \(hydrobase-rho.xy.h5\) in VisIt and add a “Mesh” plot to check what things look like at iteration=0. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…

1 0

#2623: Colons in parent's parent directory name causes build failure
by Zach Etienne 21 Jul '22

21 Jul '22

#2623: Colons in parent's parent directory name causes build failure Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Zach Etienne): I suppose I’m most confused by the fact that the make config scripts are using full paths and not relative paths. Seems a bit flaky… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2623/colons-in-parents…

1 0

#2623: Colons in parent's parent directory name causes build failure
by Zach Etienne 21 Jul '22

21 Jul '22

#2623: Colons in parent's parent directory name causes build failure Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: Steps to reproduce \(on Ubuntu 22.04, and I’ve reproduced this on Rocky Linux 8 as well\). Go to `/tmp/` , create a directory named `ETK_builds/Riemann:test:sed` Go to this directory: `cd /tmp/ETK_builds/Riemann:test:sed` . Download the latest Toolkit release \(Riemann\), following the official instructions: ``` curl -kLO https://raw.githubusercontent.com/gridaphobe/CRL/ET_2022_05/GetComponents chmod a+x GetComponents ./GetComponents --parallel https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2022_05/einsteintoolk… ``` Copy the config scripts attached to this ticket to `Cactus` and go into `Cactus`. Upon running the `make blah-config`, you will get errors of the form ``` creating make.config.defn sed: can't read /tmp/ETK_builds/Riemann: No such file or directory sed: can't read /tmp/ETK_builds/Riemann:test:sed/Cactus/lib/make/test: No such file or directory sed: can't read /tmp/ETK_builds/Riemann:test:sed/Cactus/lib/make/sed/Cactus/lib/make/make.config.defn.in: No such file or directory ``` … and you will be unable to build the Toolkit. attachment: make_config-runmefirst (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: ubuntu-gcc.cfg (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2623/colons-in-parents…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac