Kenneth E. Jansen

kjansen@pfe27:/nobackup/kjansen/SeparatedBump/DNS/ReL_2M/MGEN/mner> file /home5/kjansen/SCOREC-core/buildMGEN_write3D/test/matchedNodeElmReader /home5/kjansen/SCOREC-core/buildMGEN_write3D/test/matchedNodeElmReader: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.0.0, not stripped

Yes, I am looking in both stdout and stderr. Yes, line 790 has what you show so I would expect that my lion_eprint statements are not being stopped by verbosity...

ok then I guess we would have to conclude that n is NOT > 100 M. I have made a code that makes every variable in this routing Gid and...

Confirmed. Gid for all integers in setCoords works for the small problem on the viz nodes. verify is not commented out so the mesh created seems is at least correct...

While I had the code there, I also modified it to trigger my debug statements when n > 10000 instead of 100M. At least on the viz nodes, this did...

So my lion_eprint produced 59 sensible statements (on 80 processes) and 21 core files that did not report their output. I think I need to throw a barrier before the...

Yep. I just added this if(n > 1000) { Gid sizeToSend=n*3*sizeof(double); lion_eprint(1, "setCoords int overflow of: self=%ld,mySize=%ld,total=%ld, n=%ld,to=%ld, quotient=%ld, remainder=%ld start=%ld, peers=%ld, sizeToSend=%ld, nvertsG=%ld, nverts=%u \n",self,mySize,total,n,to,quotient,remainder,start,peers,sizeToSend,nvertsG,nverts); // Gid peersG =...

That said, I don't see how our problem could be located here. Lets test this logic path: 1) this code streams in N mesh nodes from a single coordinates file...

Here is a sketch based on my guess (lacking coordinates) of the model but, as noted above, it seems odd that edges don't form a loop based on these coordinate...

So, if the order of the listed edges is not important and the extra numbers do not need to accurately reflect direction/usage then the attached file might work for a...