Skip to main content

In Silico

When the “c” in cLogP Stands For “Crazy” (Update: Fixed!)

I don’t know how many readers out there use the cLogP function in ChemDraw, but you might want to take a look at the illustration here before you use it again. A reader alerted me to this glitch: drawing in explicit hydrogens sends it into an even stranger world of fantasy than most calculated logP values inhabit. There seems to be a limit, though, as that cyclopropane series illustrates. (Note that the “logP” function resists temptation).
PerkinElmer says that there are several logP calculating functions built in, but that cLogP is from BioByte. I don’t think that they got their money’s worth from them. Now, this isn’t the first glitch like this I’ve seen – a lot of chemical drawing and searching programs choke on details here and there. But this is the sort of thing you’d have thought would have been fixed by now.
Update: it has indeed been fixed, according to the fast-acting Phillip Skinner at PerkinElmer. But apparently many of us out in user-land aren’t using updated versions. For what it’s worth, I have ChemBioDraw Ultra 13.02 v. 3020 – are others getting more reliable numbers with newer software?
Note: here’s where the patch can be downloaded.

32 comments on “When the “c” in cLogP Stands For “Crazy” (Update: Fixed!)”

  1. Hap says:

    I like how putting the fourth explicit H on the cyclopropane restores ClogP to the correct value. Apparently there is a limit to the calculated enhancement of hydrophilicity by explicit H substituents (well, in the real plane, anyway).

  2. Anonymous says:

    Surely these calculations are all accurate and prove that our “common sense” is wrong?

  3. Nate says:

    And modellers wonder why the experimental people give them the side eye so often. You can wave your arms all you want but you are still making numbers up

  4. #3: Except that most modelers don’t use Chemdraw for calculating clogP. Experimental people do.

  5. Anonymous says:

    #3: Many modelers knew this issue long time ago, and have contacted ChemDraw people. At the company I’m working for, we’ve warned our chemists, and encourged them to use a webbased tool that standardize the structrues before ClogP calculation.

  6. Anonymous says:

    This seems to be ChemDraw’s implementation problem, not BioByte’s.

  7. Anonymous says:

    “standardize the structrues before ClogP calculation”
    Is that standardized with or without explicit hydrogens?

  8. ScientistSailor says:

    If you are using ChemDraw for cLogP calculations, you get what you deserve…

  9. @kayakphilip says:

    Hi Derek,
    Was this you or one of your readership? Whoever, you are either on an old version of the software or haven’t updated with relevant patches. This was an issue a while ago, and got fixed. I do not replicate this on my version (v13).
    We all wish software came out perfect, but that is rarely so. Software companies come out with fixes for stuff from time to time. Individuals and organizations do need to stay current on those fixes.

  10. watcher says:

    Very funny. Should ask my neice, who is taking organic right now, is she knows the difference in the structures. Of course, I’d be appauled if she tried to expain them each as unique as shown.

  11. @kayakphilip says:

    btw patches can be downloaded from here:

  12. Anonymous says:

    My version (v12) gives the results Derek lists. Do you know how can we obtain these patches you mention?

  13. newnickname says:

    “It’s not a bug. It’s a feature.”

  14. @kayakphilip says:

    @Anon #12 – patches are all available here:
    There is also access to our support there – and a knowledge base where you can often find a solution to common problems you may have. If there isn’t a solution to a problem you encounter then log a bug and it will get tracked and followed up on. We can’t fix things we don’t hear about – although the cLogP issue we had heard about, and fixed.
    Those on Twitter, you can also contact support there @PKI_InformatxTS
    @13 newnickname – no, it was a bug. It was fixed though.

  15. Konrad Koehler says:

    The problem originated with BioByte, but when I alerted them to the problem in the standalone ClogP program back in March of 2011, BioByte promptly fixed it and sent both me and PerkinElmer a bug fix. The problem is that PerkinElmer never included the bug fix in ChemDraw 12. I don’t have access to ChemDraw 13 so I don’t know if the bug was fixed in this version, but I have my doubts.
    For a discussion, see the following http: web link

  16. BTDT says:

    I swear by ACD labs (Toronto ) software to do clogP calculations. So does SciFinder.

  17. Anonymous says:

    @9 @Kayakphilip
    OK, after reading your post more carefully, apparently the bug fix was included in ChemDraw version 13, but as far as I can tell, a ClogP bug fix patch was never released for version 12. Also, if you have known about this problem for so long, why haven’t you alerted your users to this bug?

  18. David says:

    Can’t relay on it

  19. @17 Anonymous says:

    I personally can’t comment re v12 – I am trying to get a definitive answer to that. Sometimes fixes are only in the most recent release, sometimes they are back-ported to older releases, that is normal for all software.
    We typically notify people who report an issue when that issue is resolved and direct them to the appropriate fix. We can’t do that directly for people who don’t report issues. There are many ways to communicate with us about any issues – the best way is the support forum here: This allows you to track the progress of whatever you report.
    There are also public forums where common issues and solutions are discussed – useful examples from the portal are posted there for public availability. We also post announcements when new versions and new patches are released, and what those patches address. Here is an example:
    So, we don’t inform every user about every bug, nor about every fix. But we do try to provide relevant information, both generally (publicly) and proactively (direct to those who report).
    I will pass on any suggestions as to other ways of communicating anything the readership would think is useful though. We are keen to be communicative and part of the community, without bombarding people with emails.

  20. @kayakphilip says:

    I might owe you an apology – I was correct in that it is fixed in v13 on PC. There may be something wrong here on Mac. I apologize for leading you possibly astray – I, and another colleague, double checked your claims on our own systems but couldn’t replicate them but I only run PC. I’ve now got a colleague to replicate on a Mac. I will continue to update as I learn more.

  21. jbosch says:

    Yes, definitely the Mac V13.0.2.3020 does not include this patch and shows the wrong clogP.

  22. pessinest says:

    Out of curiosity has anyone seen any problems along these lines in marvin or marvinbeans?

  23. Morten G says:

    “(Note that the “logP” function resists temptation)”
    Shouldn’t the logP be experimental values from a table? The c in clogP is for computed/calculated, right? Or are you being facetious / making dad jokes?

  24. alig says:

    @23 Chemdraw reports two different calculated log Ps. One is labelled ClogP, the other is labelled logP, but it is still calculated.

  25. Pete says:

    At the risk of being pedantic it should be ClogP and not cLogP. A good test for logP predictors is how well do they handle different canonical forms like CN(=O)=O and C[N+](=O)[O-] (pentavalent nitrogen and ylid representations of nitromethane).

  26. Morten G says:

    @24 Thank you.
    That’s pretty misleading though 😉

  27. CS RNA says:

    Seems the issue fixed in the current version (13.0.2)

  28. TX raven says:

    Does it matter?
    I’m amazed at the value some folks give to cLogP calculations…
    Has anyone ever learned something from these calculations they did not know before running them?

  29. @kayakphilip says:

    This was a known issue that was resolved with the release of v13 for PC. The fix was not included in v13 for Mac, for which we apologize and thank Derek and the community for bringing this to our attention. We are now actively investigating a solution and I will report as soon as I have additional information for the community.
    In the meantime, users can avoid the issue of incorrect ClogP values by not drawing explicit hydrogens in structures to be analyzed.
    I would like to personally apologize for any confusion I caused with my comments. I wasn’t completely correct and hope this above clears up that confusion.
    Finally, we are always happy to engage on this forum and elsewhere. Readers know we have done so in the past and I’m happy to do so again. There is no substitute though for reporting issues via proper channels – so I encourage people to report and track any issues on our support portal and use the knowledge base that is there. We are also happy to engage on twitter (our product teams are @ChemDraw, @PKI_Informatics and our support team is @PKI_InformatxTS)

  30. newnickname says:

    @14 kayakphilip: “It’s not a bug. It’s a feature.”
    That, of course, is the classic response of all generic tech support to bug reports that many of us recognize as humor. But now you’ve irked me by not seeing it that way.
    I was talking to Rubenstein at the Camsoft booth at an ACS meeting (YEARS ago) and pointed out several bugs and glitches that he IMMEDIATELY argued did not exist, that I was wrong and that everything was fine and dandy and wonderful.
    We opened a ChemDraw and I showed him and he became a believer. One that I remember was a buggy “align on center” function. Anyone who wasn’t cross-eyed and had better than 20-200 vision could see that items were NOT properly centered both in the display AND in the printouts thus requiring manual aligning on the grids or ‘by eye’. Centering was fixed in the next release.
    There were also many problems with Camsoft’s implementation of encapsulated postscript. Every time I reported a problem, the initial response was a dismissive, “No, it works fine.” Only by providing specific examples and copies of files did they finally fix that. It was Camsoft’s implementation of the Adobe standards that got goofed up. That dragged on thru a couple of releases (because it was a low priority — to them).
    In the Mac OS, there was a way to write macros to run a series of commands within a program with a single command. In ChemDraw, I wanted to save my files in several formats: (“Save as [name].cdx; save as [name].eps; ” etc.). I could never get that to work. Apple said it was the Camsoft implementation. Camsoft support couldn’t get my examples to work, either. Bug or feature?
    In the Pipeline is about the DRUG pipeline. If we could sell drugs like software, the drug industry would be in great shape!
    “I took your drug and it nearly killed me.”
    Yes, but that’s not a bug, it’s a feature!

  31. Joe says:

    Is that 5th molecule with the triangle called anarchane?

  32. Mat Todd says:

    This bug still exists – Chemdraw 14 for Mac. Here’s me rediscovering it:

Comments are closed.