Skip to main content

Ring Plate Visualisation

One diagram I've often wanted to make was filled-in rings in molecules :
Mainly for the purposes of highlighting rings without highlighting the atoms involved. This image was made using the CDK renderbasic module, and a small toy AWTRenderingVisitor that fills in paths. I'm not sure if the current one does this...

The gist for the main drawing method is here but is really just stuff seen before. The custom generator for rings is probably more interesting - if very simple - and is here. Note that it doesn't look too nice with inner-ring double bonds:

and would look nicer if the double bonds were symmetric.

EDIT : Coloring by ring equivalence classes didn't do what I expected...


Shouldn't all the outer rings be in the same class? Steran is how I expect, though:

Comments

Nice!

It makes me think, despite that Margin bug, maybe there is enough new stuff here to write up that paper... what do you think?
Rich Apodaca said…
Interesting idea - what would be some applications?
gilleain said…
Egon: Margin bug? This:

http://sourceforge.net/tracker/index.php?func=detail&aid=3062137&group_id=20024&atid=120024

or? If so, this is the two-pass system, which is more than just a bug :)

If we can find a way of unit-testing graphics, then that could definitely be publishable, as I think that a tested chemical graphics library would be of interest.
gilleain said…
Rich : Well, for any ring-finding algorithm, I suppose. I don't know what it would look like if you filled in a large ring that had smaller ones inside it.

A simple extension of the code I posted might color different ring equivalence classes (the SSSRFinder calculates these).

In general, you can highlight a set of atoms in a ring without confusion. Something like coronene could have all the outer rings highlighted, without the inner one.
gilleain said…
See this gist : https://gist.github.com/1023824 for the ring equivalence class code...

Popular posts from this blog

Listing Degree Restricted Trees

Although stack overflow is generally just an endless source of questions on the lines of "HALP plz give CODES!? ... NOT homeWORK!! - don't close :(" occasionally you get more interesting ones. For example this one that asks about degree-restricted trees. Also there's some stuff about vertex labelling, but I think I've slightly missed something there.

In any case, lets look at the simpler problem : listing non-isomorphic trees with max degree 3. It's a nice small example of a general approach that I've been thinking about. The idea is to:
Given N vertices, partition 2(N - 1) into N parts of at most 3 -> D = {d0, d1, ... }For each d_i in D, connect the degrees in all possible ways that make trees.Filter out duplicates within each set generated by some d_i. Hmm. Sure would be nice to have maths formatting on blogger....

Anyway, look at this example for partitioning 12 into 7 parts:

At the top are the partitions, in the middle the trees (colored by degree) …

Common Vertex Matrices of Graphs

There is an interesting set of papers out this year by Milan Randic et al (sorry about the accents - blogger seems to have a problem with accented 'c'...). I've looked at his work before here.

[1] Common vertex matrix: A novel characterization of molecular graphs by counting
[2] On the centrality of vertices of molecular graphs

and one still in publication to do with fullerenes. The central idea here (ho ho) is a graph descriptor a bit like path lengths called 'centrality'. Briefly, it is the count of neighbourhood intersections between pairs of vertices. Roughly this is illustrated here:


For the selected pair of vertices, the common vertices are those at the same distance from each - one at a distance of two and one at a distance of three. The matrix element for this pair will be the sum - 2 - and this is repeated for all pairs in the graph. Naturally, this is symmetric:


At the right of the matrix is the row sum (∑) which can be ordered to provide a graph invarian…

Generating Dungeons With BSP Trees or Sliceable Rectangles

So, I admit that the original reason for looking at sliceable rectangles was because of this gaming stackoverflow question about generating dungeon maps. The approach described there uses something called a binary split partition tree (BSP Tree) that's usually used in the context of 3D - notably in the rendering engine of the game Doom. Here is a BSP tree, as an example:



In the image, we have a sliced rectangle on the left, with the final rectangles labelled with letters (A-E) and the slices with numbers (1-4). The corresponding tree is on the right, with the slices as internal nodes labelled with 'h' for horizontal and 'v' for vertical. Naturally, only the leaves correspond to rectangles, and each internal node has two children - it's a binary tree.

So what is the connection between such trees and the sliceable dual graphs? Well, the rectangles are related in exactly the expected way:


Here, the same BSP tree is on the left (without some labels), and the slicea…