Activity for Patrick Mary
-
Patrick Mary created a blog post
Tulip 6.0.1 is available
-
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 is available
-
Seems to be a good idea.
-
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.
-
Sounds interesting Thanks
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
Can't compile Tulip with QT6 enabled
-
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.
-
Tulip 5.7.3 is availablre
-
Add support for the trivial graph format .tgf
-
Thanks for letting us know about the "Trivial Graph Format". A plugin allowing to import a tgf file has been added in the current code line. I will be available in the next release.
-
missing text for property names for algorithm configurations when building with QT6 support
-
The fix for this bug will be integrated to the next release.
-
Thanks for your report. I reproduced the bug which seems to be a Qt6 bug. The parameter names are displayed but not visible. They become visible by proceeding as follows: - put the mouse in the left column on the line between two rows, - a double vertical arrow is then displayed, - press the mouse left button and scroll down to enlarge the above line and reveal the corresponding parameter name. I found nothing to ensure the parameter name visibility. So I think I have to find a workaround with a...
-
Tulip-5.7.2.AppImage crashes when selecting a layout algorithm within the GUI
-
Thanks to Antoine (the developer who integrated OGDF source in Tulip) for giving its 2 cents. And thanks to you Andre for your recent reports. So the AppImage build will be fixed for the next Tulip release.
-
I did the same in using VirtualBox instead of virt-manager. You can extract then run the appimage in doing this : cd /tmp path_to_appimage/Tulip-5.7.2.AppImage ./squashfs-root/AppRun
-
I'm really sorry but I was unable to reproduce the crash you reported. As I have no machine with your OS, I tried booting a virtual machine using Fedora-Workstation-Live-x86_64-38-1.6.iso, then lauching Tulip-5.7.2.AppImage on your cairo.graphml file. Every layout plugin I applied worked as expected.
-
Can't compile Tulip 5.7.2 on Fedora 38
-
Thanks a lot for your input. We made a lot of cmake configuration changes in the current code line in using cmake 3.12 as minimal cmake version. In cmake/TulipPython.cmake FIND_PACKAGE(PythonInterp 3.7 REQUIRED) has been replaced by FIND_PACKAGE(Python 3.7 REQUIRED COMPONENTS Interpreter Development) which does the correct check.
-
Random General Tree Algorithm
-
It seems to be an old bug. Its fix will be available in the next Tulip release. Can you tell me more about the number of requested leaves in a new feature request.
-
Here is a new version of library/tulip-python/src/ConsoleUtilsModule.cpp. If its compilation fails again, I will be really interested by the cpython/object.h file used to compile it (must be in /usr/include/python.../cpython). Thanks in advance
-
Here is a new version of library/tulip-python/src/ConsoleUtilsModule.cpp, I successfully compiled using Python 3.7 to 3.12. Tell me if it works for you.
-
Can't compile Tulip 5.7.2 on Fedora 38
-
The first error is already fixed in the current code line. For the second one, I suppose you tried to compile with Python 3.12 which is not supported in Tulip 5.7.2 code line. The support of Python 3.12 will be added in the next Tulip release.
-
ambiguous call to QWebEngineView(std::nullptr_t)
-
This bug is now fixed in the Tulip code line. Thanks again for your input.
-
missing cstdint include
-
This bug is now fixed in the Tulip code line. Thanks a lot for your input.
-
Tulip 5.7.2 is available
-
The GML export does not support the export of user defined properties; in the GML format the name of a property (called attribute) is restricted to be a 7-bit ASCII key ([a-zA-Z][a-zA-Z0-9]*) while it is a UTF-8 delimited string for Tulip. Then only Tulip "view" properties are exported using their GML equivalent attribute.
-
inducedSubgraph method adding nodes multiple times ?
-
Finally, the error was not in the inducedSubGraph optimized code, which was perfectly legitimate, but it revealed a problem in a much older code.
-
My bad. This is due to an old optim replacing a set by a vector. It will be fixed soon.
-
Eccentricity Plugin returns -1 diameter when selecting unnormalized values
-
Fixed in Tulip 5.7
-
Typo in tulip-python documentation
-
Asap is now.
-
Well seen. It will be fixed asap.
-
Here is the file.
-
Lucky guy, here is the fixed version of your Tulip project. Remember to not use a Tulip version prior to 5.6.2
-
I'll try to do my best as soon as possible. Patrick
-
Hello Alain, the lines #6 to #20 of the reported call stack shows that the problem comes from the graphics driver ( /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so, gallium3d driver) used at your office. So try to use another one compatible with your office graphics card. Hope this helps. Patrick
-
Hello Volodymyr, I don't know pybind11 and I suppose that when saying "register the function with Sphinx", you mean SIP, which is the software we use to implement the Tulip python bindings. From my point of view, the only immediate way to apply a generic c++ code to a graph in python, is to make this c++ code a tulip plugin of type "Algorithm". Supposing you have created a plugin named "my algorithm", here is a small example to invoke it: # import stuff, which should also load "my algorithm" plugin...
-
Tulip 5.7.1 is available
-
Tulip 5.7 is available
-
I cannot reproduce the problem you described with Tulip 5.6.3. The crash report you posted indicates you were using Tulip 5.6.1.
-
I patched the graph structure at load time with a version of Tulip under debugger, in order to renumber the subgraph having an incorrect id and ensure the graph could load. Then I just had to save the Tulip project.
-
I fixed the graph structure. Here is a new version of your tlpx file.
-
I can see that one of the subgraph has an incorrect id. Is it possible for you to "attach" your tlpx file to this discussion ?
-
The graph diameter computation corresponds to the search for the eccentricity max value. This search is necessary in the normalized = true case; but it is not and is therefore avoided in the normalized = false case. In this last case, if the call to the 'Eccentricity' plugin is done via python, the diameter of the graph can then be obtained by a call to getNodeMax() method on the metric. Nevertheless, I will code a new version, using the "graph diameter" parameter as an input parameter to force,...
-
The graph diameter computation corresponds to the search for the eccentricity max value. This search is necessary in the 'normalized = true'; but it is not and is therefore avoided in the 'normalized = false' case. In this last case, if the call to the 'Eccentricity' plugin is done via python, the diameter of the graph can be obtained by a call to getNodeMax() method on the metric. Nevertheless, I will code a new version, using the "graph diameter" parameter as an input parameter to force, when its...
-
[Tulip software] Access denied - cannot open Tulip
-
OK
-
Tulip 5.6.3 is available
-
Thank you for finding the regression bug related to commit 933aad9. I just integrated the fix. However, given the dates of the first two posts, this one is unrelated to the problem initially reported.
-
Sorry I missed this problem. It is probably related to the path to the python installation that cannot be found. Add it to the PATH system variable. Hope this helps.
-
Tulip 5.6.2 is available
-
Tulip 5.6.1 has been released today. It has been successfully tested on macOS Big Sur and Monterey. cheers
-
Tulip 5.6.1 is available
-
This problem is macOS Big Sur specific and due to a Qt bug (QTBUG-87014). As a temporary workaround, you can replace the file ~/Desktop/Tulip-5.6.0.app/Contents/MacOS/Tulip by the one in attachment. We are currently testing a correct fix/workaround, and plan to release a Tulip 5.6.1 version as soon as possible. Hope this helps.
-
Tulip 5.6 is available
-
I finally found the original source files of the plugin mentioned in the paper. I think it is based on Tulip 3.1 Hope this helps.
-
Tulip 5.5.1 is available
-
It seems that to be able to do a vertical reshape, right after clicking on the Resize menu item, the first mouse move must be upwards.
-
I am really sorry but I tested the launch of the Tulip 5.5 AppImage on a fresh install of Ubuntu 20.04 and it works as expected (see attached file). You can try a right click in the window title bar to have access to the 'Resize' menu item and/or use the split handle separating the 'Algorithms' and 'Graphs' panels. Hope this helps. PS: can you give me your screen resolution ?
-
Tulip 5.5.0 installers for MacOS have been replaced
-
Tulip 5.5.0 installers for Windows have been replaced
-
Sorry for the delayed response, but I was not at my office until yesterday. The buggy windows installers have been replaced today.
-
Tulip 5.5.0 installers for Windows have been replaced
-
As the Tulip AppImage is a bundle, none of its components has to be extracted for reuse. The right way to use Tulip from a python interpreter, is to compile and install Tulip on your Linux OS (see https://github.com/Tulip-Dev/tulip/blob/master/README.md) and to refer to the paragraph Setting up the environment from the Tulip software installation (in the doc you mentioned) for the python module search path configuration. Hope this helps
-
It seems that you mixed the use of the tulip-python package through the Python packaging Index (installation through pip), and the use of the tulip-python package provided through the Tulip software installation. If you just want to use the tulip-python package installed with pip you have no need to setup the the PATH variable. See https://tulip.labri.fr/Documentation/current/tulip-python/html/gettingstarted.html#installing-the-tulip-python-modules-from-the-python-packaging-index for more details....
-
Graph splatting is implemented through a non standard Node-Link Diagram interactor whose code has not yet been ported on Tulip 5.4 version. We will do our best to make it available in the next version of Tulip.
-
Sorry, I just upload them on pypi.
1 >
