Trac July 2022

trac@lists.einsteintoolkit.org

1 participants
70 discussions

#2549: inlcude FLRWSolver in ET
by Roland Haas 28 Jul '22

28 Jul '22

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2022_05 Version: development version Type: enhancement Priority: major Component: Changes (by Roland Haas): responsible: [] (was []) assignee: Zach Etienne (was helvi witek) Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} assigning to you as the new reviewer. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2601: Add four more parameters for carpet
by Roland Haas 26 Jul '22

26 Jul '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: resolved Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#2601: Add four more parameters for carpet
by Roland Haas 26 Jul '22

26 Jul '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: new Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Comment (by Roland Haas): Applied as git hash [8d84af01](https://bitbucket.org/eschnett/carpet/commits/8d84af01db56441e124… "Carpet: update comments for split interior" of [carpet](https://bitbucket.org/eschnett/carpet) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#2601: Add four more parameters for carpet
by Liwei Ji 24 Jul '22

24 Jul '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: new Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Comment (by Liwei Ji): Hi Roland. I have update the pull request according to the discussion we had before. Could you please take a look again? thanks -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac July 2022