Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix L7_ASSERT in L7_Update #11

Closed
samuelkgutierrez opened this issue Nov 5, 2013 · 4 comments
Closed

Fix L7_ASSERT in L7_Update #11

samuelkgutierrez opened this issue Nov 5, 2013 · 4 comments

Comments

@samuelkgutierrez
Copy link
Member

Hi Bob,

Are you seeing these?

$ mpirun -n 3 ./clamr_quo
System Info ###
Nodes: 1
NUMA Nodes: 0
Sockets: 1
Cores: 1
PUs: 1
MPI Procs on Node: 3
MPI_COMM_WORLD ranks in subComm: 0
rank: 0 is subComm rank: 0
Size comm world 3 subComm 1
--- num openmp threads: 1
Mass of initialized cells equal to 92652.9978195
CPU: setup time time was 0.1072 0.1077 0.1070 s
Memory used in startup 7832 7812 7808 kB
Memory peak in startup 7832 7812 7808 kB
Memory free at startup 1521316 1521316 1521316 kB
Memory available at startup 2043828 2043828 2043828 kB
Iteration 0 timestep n/a Sim Time 0.0 cells 17028 Mass Sum 92652.9978195
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
DEBUG -- cell 6117 lev 2

@brobey
Copy link
Member

brobey commented Nov 5, 2013

Yeah, I'm seeing it. It means it is getting the neighbors wrong. mpirun -n 4 ./clamr_quo is running fine. I'll work on it


From: Samuel K. Gutierrez [notifications@github.com]
Sent: Monday, November 04, 2013 8:21 PM
To: losalamos/CLAMR
Subject: [CLAMR] Fix L7_ASSERT in L7_Update (#11)

Hi Bob,

Are you seeing these?

$ mpirun -n 3 ./clamr_quo

System Info
Nodes: 1
NUMA Nodes: 0
Sockets: 1
Cores: 1
PUs: 1
MPI Procs on Node: 3

MPI_COMM_WORLD ranks in subComm: 0
rank: 0 is subComm rank: 0
Size comm world 3 subComm 1
--- num openmp threads: 1
Mass of initialized cells equal to 92652.9978195
CPU: setup time time was 0.1072 0.1077 0.1070 s
Memory used in startup 7832 7812 7808 kB
Memory peak in startup 7832 7812 7808 kB
Memory free at startup 1521316 1521316 1521316 kB
Memory available at startup 2043828 2043828 2043828 kB
Iteration 0 timestep n/a Sim Time 0.0 cells 17028 Mass Sum 92652.9978195
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
DEBUG -- cell 6117 lev 2


Reply to this email directly or view it on GitHubhttps://github.com//issues/11.

@brobey
Copy link
Member

brobey commented Nov 5, 2013

Fixed. At least partially. The l7 load balance handle was being freed before it was finished
being used.


From: Samuel K. Gutierrez [notifications@github.com]
Sent: Monday, November 04, 2013 8:21 PM
To: losalamos/CLAMR
Subject: [CLAMR] Fix L7_ASSERT in L7_Update (#11)

Hi Bob,

Are you seeing these?

$ mpirun -n 3 ./clamr_quo

System Info
Nodes: 1
NUMA Nodes: 0
Sockets: 1
Cores: 1
PUs: 1
MPI Procs on Node: 3

MPI_COMM_WORLD ranks in subComm: 0
rank: 0 is subComm rank: 0
Size comm world 3 subComm 1
--- num openmp threads: 1
Mass of initialized cells equal to 92652.9978195
CPU: setup time time was 0.1072 0.1077 0.1070 s
Memory used in startup 7832 7812 7808 kB
Memory peak in startup 7832 7812 7808 kB
Memory free at startup 1521316 1521316 1521316 kB
Memory available at startup 2043828 2043828 2043828 kB
Iteration 0 timestep n/a Sim Time 0.0 cells 17028 Mass Sum 92652.9978195
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:1] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:2] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
[pe:0] L7 Error L7_UPDATE (/home/samuel/devel/CLAMR/l7/l7_update.c:142[!(l7_id > 0)]) (l7_id <= 0) (-1)
DEBUG -- cell 6117 lev 2


Reply to this email directly or view it on GitHubhttps://github.com//issues/11.

@brobey
Copy link
Member

brobey commented Nov 5, 2013

Fixed. The L7 load balance handle was being freed before it was finished being used.

@samuelkgutierrez
Copy link
Member Author

Looks good from the l7 front (no more assertions). Thanks!

brobey pushed a commit that referenced this issue Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants