The Phase hypothesis identification node runs sequentially pharmacophore site creation, common pharmacophore perception and hypothesis scoring.
A set of pharmacophore feature definitions is applied to each ligand conformation to identify the positions of all pharmacophoric elements in that ligand.
During common pharmacophores identification all n-point pharmacophores from the input ligands are enumerated and filtered into a set of high-dimensional boxes. Pharmacophores that fall into the same box are similar enough to be considered equivalent. Boxes that receive at least one pharmacophore from a sufficient number of actives are said to "survive" the partitioning process. Each surviving box may be processed in the subsequent Score Actives step to identify a pharmacophore hypothesis from that box. Hypotheses are scored with respect to input ligands by assigning numerical rankings to the pharmacophores within each surviving box. The highest scoring pharmacophore in a given box is designated as a hypothesis, and the ligand giving rise to that pharmacophore is known as its reference ligand. The scoring function considers the quality of the alignments, of the oriented feature overlay and of the conformation volume overlap.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Schrödinger Extensions for KNIME from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.