Issue with large family

Question

Issue with large family

Timothep opened this issue 5 years ago · comments

Hi, I'm getting this error when working with a large family:

kingraph genealogy.yml > genealogy.svg

Error:

add_segment: error
add_segment: error
add_segment: error
add_segment: error
add_segment: error
add_segment: error
add_segment: error
failed at node 7167[0]
Assertion failed: np->cells[0], at: maze.c,313,chkSgraph at Error
at jsStackTrace (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:5:20800)
at stackTrace (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:5:20983)
at ___assert_fail (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:5:603049)
at PU (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:17:39811)
at LU (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:17:34738)
at Array.HU (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:17:28119)
at Object.y5 [as dynCall_iii] (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:21:32521)
at invoke_iii (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:5:632212)
at yP (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:10:66616)
at Mf (C:\Users\Tim\AppData\Roaming\npm\node_modules\kingraph\node_modules\viz.js\viz.js:11:132553)

I raised the Memory for viz.js as suggested by @momack2 in this other issue but it doesn't seem to help.

It seems to have to do with the family size among one house. This error occurs when it has more than 24 parent/children pairs.

Any idea what is going awry there?

Mason Juarez · Answer 1 · Sun Jun 28 2020 15:09:50 GMT+0800 (China Standard Time)

When I edit the vis.js file and use Notepad++ find and replace all function to replace 16777216 with 1677721600 I am able to generate large trees, 150+ node trees in my case.

Ata Türkoğlu · Answer 2 · Wed Jul 13 2022 05:19:48 GMT+0800 (China Standard Time)

Have you managed to fix this problem?

MollyM · Answer 3 · Wed Jul 13 2022 21:17:38 GMT+0800 (China Standard Time)

Iirc, there was some lower level environment variable I was able to increase that unblocked this - but unfortunately I don’t remember where exactly it was. If I remember correctly, dividing a family up into “houses” also helped mitigate some size issues.

…

On Tue, Jul 12, 2022 at 9:19 PM Ata Türkoğlu ***@***.***> wrote: Have you managed to fix this problem? — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEXAF6SVSCVBP5DZ2PRDZLVTXOP5ANCNFSM4IJ2PLGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Michael Vorburger · Answer 4 · Sun Sep 04 2022 06:14:44 GMT+0800 (China Standard Time)

I think this issue IS a duplicate of #6, and the simplest solution (to me) seems to me not to bother about tweaking vis.js memory settings, but simply to generate only the dot file with kingraph, and let Graphwiz produce the SVG and PDF. I have recommended this in the README of my fork.