Oliver Kullmann

Thanks a lot! Somehow I missed the Stellarium User Guide, which seems a good read. Now downloading both DE430/431. It was just to tempting to go to the year -50000 and imagine how that was. And then forward to +50000!

Hello, since three years I got into astronomy, with a small telescope and binoculars. A few months ago I found Stellarium, and find it very useful. For me also the educational aspect is very important, and so I use going back and forth in time, which I find fascinating. I watched especially the moon over the time scale as provided by Stellarium (-10^5 to +10^5 years), and found interesting phenomena, which however I couldn't locate in the literature. Just bought a quite detailed book on the (earth-)moon,...

Hello, on the file Test.tlp with the content (tlp "2.3" (nb_nodes 2) (nodes 1..2) (edge 2 1 2) ) the Tulip-app version 5.2 fails with the error message Error when parsing '' at line 4 When using (nodes 1..3) instead, then parsing succeeds. This looks like a clear bug to me? Oliver

Hello, beginning of semester here, everything takes it s time. Currently it seems actually most useful to us if we compute the colouring of nodes (and edges) ourselves, putting that already into the tree given to the Tulip-application. We can easily compute anything we want and put into into the data given to Tulip. That seems indeed easier for us, and we have full control over that. Leaving then the display and all of that to Tulip. Our own program is C++. Now it would be great if there would be...

Ha, that's fun -- Dan is just next door :-) So that should solve indeed the problem! Thanks Benjamin Concerning that hacking-business: As I said, I worked with properties, in a more generic (powerful) setting, in the Boost (C++) Graph library. From a complexity point of view it's a hack -- but that doesn't mean that it isn't useful! The whole Linux is kind of a hack, and it is useful. And perhaps that hack here is very hard to make better, in general. You might then not call it a "hack", but I didn't...

Hi Guy, today I am fully busy with teaching and admin, so can continue properly only tomorrow. But just some quick remarks: 1. We definitely need a lot of experimentation, and thus need much (all) of the functionality available in the Tulip 5.2 application. When you write "script", is this some form of plug-in to that application? 2. What seems fully sufficient would be to add the field "selection" (as you have it for "To labels") to the algorithm "Color Mapping". Then we could compute the colouring...

You write: "There are several options: associate the whole tuple at once or spread them over different properties (it makes sense since the tuples all have the same size and k may be fixed)." Yes, but that's just a technicality. Having it as single properties is perhaps better, since then you have proper names for it. You write: "I believe your problem is to propermy define a colormap so you don't need to inspect individual values but rather get an overview of how values distribute over nodes. Am...

You write: "There are several options: associate the whole tuple at once or spread them over different properties (it makes sense since the tuples all have the same size and k may be fixed)." Yes, but that's just a technicality. Having it a single properties is perhaps better, since then you have proper names for it. You write: "I believe your problem is to propermy define a colormap so you don't need to inspect individual values but rather get an overview of how values distribute over nodes. Am...