Activity for Tulip
-
Roden Deng Luo posted a comment on discussion Help
Hi, I frequently face errors without much info. The call stack has only main and the algorithm runner (attached). This happens when there is something wrong in the Python plugin I developed. I wonder what is your development environment. Can I debug C++ and Python at the same time? It is fine if the whole process involves multiple IDEs or commandlines. Right now, if there is anything wrong in Python, I can only insert many print() to figure out why. Any help is much appreciated. Best, Roden
-
Hi, I wonder how open and what is the community development practice for Tulip (given most threads I see are quite outdated). And this is my first time thinking of developing on top of a SourceForge project, which I must say a great tool. I get a few questions. If I develop something can I merge to the main code base and will there be a reviewer? Can I get any (resonable amount) support? Are you thinking of moving to GitHub for example? Specifically, at the moment, I am adding more python bindings...
-
Patrick Mary created a blog post
Tulip 6.0.1 is available
-
Tulip updated /tulip/tulip-6.0.1/README.md
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Tulip 6.0.0 build errors and solutions on WSL2 Ubuntu 24.04.2 LTS
-
Thanks a lot for your report. Error 1 has been fixed in the current code line.
-
Tulip 6.0.0 build errors and solutions on WSL2 Ubuntu 24.04.2 LTS
-
Tulip 6.0.0 is available
-
-
-
-
-
-
-
-
-
Seems to be a good idea.
-
Melançon Guy posted a comment on ticket #898
I see, thanks for looking into this. I overlooked the parameter "original model" so I expected the original model to be executed ... May I suggest to set the default value of the "original model" parameter to true?
-
Underlying algorithm of Watts Strogatz random model
-
Thanks for your report. The algorithm works as you described when the “original” parameter is set to “true”. Unfortunately, in this configuration, the check of the parameters is wrong N < ln(k) (instead of k >= ln(N)) which causes an error to be returned, preventing the algorithm from being correctly executed. This will be fixed for the next Tulip release.
-
Underlying algorithm of Watts Strogatz random model
-
Sounds interesting Thanks
-
scls19fr posted a comment on ticket #160
thanks for your help. I will try to compile it myself to better understand why my input files are crashing Tulip.
-
Will Tulip still be open source?
-
From the beginning of Tulip development, its source code is available with the precompiled binaries of each Tulip release. See https://sourceforge.net/projects/auber/files/tulip Hope this helps.
-
Will Tulip still be open source?
-
GraphAR support
-
Tulip 5.7.4 is available
-
Tulip 5.7.4 is avilable
-
Tulip 5.7.3 is available
-
-
-
-
-
-
-
-
-
-
-
PushPopTest fail
-
This bug has already been corrected (see fix given in https://sourceforge.net/p/auber/bugs/894/) in the upcoming 5.7.4 version.
-
Guilhem saurel created ticket #897
PushPopTest fail
-
Up does it go, the Tulip Message Log window
-
Bug fixed in commit https://sourceforge.net/p/auber/code/12543/
-
dot grammar bug
-
The feature is only available since Tulip 5.6.3. Nothing more than image information is recorded in the snapshot.
-
Alain L'Hostis posted a comment on ticket #896
nice! any way to obtain an unstable current version? later than the current 573?
-
Sure this helps! 1. i suppose this does not apply in version 5.4, but only later versions (i do not see the "tooltips display parameters") 2. can I keep the feature in the static image generated (snapshot)?
-
AppImage 573 Segmentation fault (core dumped)
-
Hello Alain, this bug is already fixed, see https://sourceforge.net/p/auber/bugs/895/ and Tulip 5.7.4 should be available in March. Hope you're doing well too. Patrick
-
Tulip offers an approaching solution in some views through the display of a specific tooltip associated to every graph element. See the paragraph 'Augmented display' in https://tulip.labri.fr/Documentation/current/tulip-user/html/workspace.html#node-link-diagram-view Hope this helps.
-
possibly off topic: i would like to generate an image of my graph clickable, with info on nodes while hovering the image; I'm probably dreaming but who knows? Would we have a solution with tulip?
-
AppImage 573 Segmentation fault (core dumped)
-
Tulip 5.7.3 AppImage does not start on Ubuntu 22.04 with Intel iris graphics driver
-
Thanks you very much for your report. libglapi.so will be removed from the AppImage since it seems to be a specific dependency only induced by the local context of the tulip_perspective build.
-
Antoine Lambert posted a comment on ticket #895
To be noted, the crash occurs with the upstream version of the Intel drivers installed from a PPA, reverting back to the default one bundled by Ubuntu makes the crash goes away. Nevertheless, the libglapi.so should still be removed from the AppImage in order to use the one from the host system instead and avoid this crash on future Ubuntu releases.
-
Tulip 5.7.3 AppImage does not start on Ubuntu 22.04 with Intel iris graphics driver
-
Andre Maute posted a comment on ticket #893
Hi Antoine, I hope your GL_RENDERER hint is helpful ;-) my glxinfo doesn't provide any "GL_RENDERER" string but an "OpenGL renderer string" string (hint, as we see in a moment this is the one requested) perhaps there was a typo and it should have been "glinfo" but I couldn't find any reference to the glinfo tool within the Fedora biosphere https://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/g/glx-utils-9.0.0-4.fc40.x86_64.html mesa-23.3.2.tar.xz from mesa3d.org doesn't contain any reference...
-
I looked into that issue and managed to reproduce it as I have an old Intel NUC with legacy Intel HD Graphics GPU (same as you Andre I guess) that is taking the dust but is still functional. This looks like a bug in the mesa crocus driver when OpenGL rendering mode is set to GL_SELECT (used when selecting graph elements in views with the mouse). I also tested using the latest version of the driver on Ubuntu (using https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) and I still got the...
-
I looked into that issue and managed to reproduce it as I have an old Intel NUC with legacy Intel HD Graphics GPU (same as you Andre I guess) that is taking the dust but is still functional. This looks like a bug in the mesa crocus driver when OpenGL rendering mode is set to GL_SELECT (used when selecting graph elements in views with the mouse). I also tested using the latest version of the driver on Ubuntu (using https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) and I still got the...
-
Nevertheless thank you. I just verified it, that it is still broken and was not 'accidentally' fixed due to a library update. I needed a lot of clicking this time, approximately 50? clicks. But at the moment I can't debug this any further. Regards Andre
-
crash when double-clicking a graph node
-
I was unable to reproduce the your bug. As shown by the stack trace from call #2 to call #15, the problem does not seem to come from Tulip but rather from the crocus driver (/usr/lib64/dri/crocus_dri.so). Regards
-
-
-
-
Hi Perry, I followed the discussion you are having with Bruno, allow me to jump in. If I understand well, you are annoyed by the fact that the top level graph contains both the metanode you created and the nodes it contains, and would like to only have the metanode, the contained node being accessible by other means (double clicking the metanode in the GUI for instance). This however is not possible. The highest level graph in the hierarchy will necessarily contain the collection of all nodes that...
-
Can't compile Tulip with QT6 enabled
-
Perry Kloet posted a comment on discussion Help
I think I might not have made clear what I want. The above snippit works (assuming you ment g.createMetaNode instead of sub.createMetaNode), but when using saveGraph(graph, "test.tlp"), it will render the nodes n1 and n2 twice. Once inside the generated metanode and once outside the metanode. I would like the nodes to be only visible inside the metanode. Is this possible or am I misunderstanding what a metanode is supposed to do?
-
no it is still still somehow reproducible, QT6 doesn't help!
-
no it is still still somehow reproducible, QT6 doesn't help!
-
Looks like building with QT6 somehow fixes this issue?? see https://sourceforge.net/p/auber/bugs/894/
-
This worked, thank you very much And somehow I can't reproduce the Crash which I reported here https://sourceforge.net/p/auber/bugs/893/ any more.
-
I will be out of my office until the beginning of January. As we have only validated the Tulip build with Qt 6 up to the 6.4 version, I may just suggest you to try to replace the file library/tulip/gui/include/tulip/GlSimpleEntityItemModel.h by the one in attachment.
-
Can't compile Tulip with QT6 enabled
-
still crashes when self-compiled, using essentially tar xvfz tulip-5.7.3.tar.gz cd tulip-5.7.3 mkdir build cd build cmake .. cmake --build . make install
-
When compiling from source I see the following [ 64%] Building CXX object plugins/import/BibTeX/CMakeFiles/BibTeXImport-5.7.3.dir/ImportBibTeX.cpp.o In function ‘char* seq(char*)’, inlined from ‘std::string& forceUtf8String(std::string&)’ at /home/user/Downloads/tulip-5.7.3/plugins/import/BibTeX/ImportBibTeX.cpp:1001:16: /home/user/Downloads/tulip-5.7.3/plugins/import/BibTeX/ImportBibTeX.cpp:88:18: warning: storing the address of local variable ‘c4’ in ‘utf8seq’ [-Wdangling-pointer=] 88 | return...
-
crash when double-clicking a graph node
-
Tulip 5.7.3 is availablre
-
Bruno Pinaud posted a comment on discussion Help
This is working (Python, easier for testing) and tested: n1 = graph.addNode(); n2 = graph.addNode(); graph.addEdge(n1,n2); g = graph.addCloneSubGraph("g"); meta = graph.addCloneSubGraph("meta"); sub.createMetaNode(meta); - metanodes cannot be created on the root graph - subgraph g contains the resulting graph after the creation of the metanode. The content of the metanode should be inside it before the creation of the metanode - subgraph meta is the content of the metanodes. hope this helps
-
Thank you for your reply. Your code is quite similar to the code I gave in the second snippet, and has the same problem: the created metanode is empty. I also tried this: ~~~ Graph graph = newGraph(); Graph sub = graph->addSubGraph(); Graph* subGraph = sub->addSubGraph(); sub->createMetaNode(subGraph); node n1 = subGraph->addNode(); node n2 = subGraph->addNode(); sub->addEdge(n1,n2); ~~~ But that results in the nodes n1 and n2 being created twice, once inside the metanode and once outside the metanode...
-
-