<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mtsukanov</id>
	<title>DISI - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mtsukanov"/>
	<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Special:Contributions/Mtsukanov"/>
	<updated>2026-04-08T14:29:40Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16752</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16752"/>
		<updated>2025-07-15T21:59:34Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Fe and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
Code lives in GitLab, but will be deprecated soon due to Chemistry Commons.&lt;br /&gt;
 ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
 sudo docker restart redis&lt;br /&gt;
 sudo docker restart ab3&lt;br /&gt;
 sudo docker container ls&lt;br /&gt;
 sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
 /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16751</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16751"/>
		<updated>2025-07-15T21:59:12Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
Code lives in GitLab, but will be deprecated soon due to Chemistry Commons.&lt;br /&gt;
 ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
 sudo docker restart redis&lt;br /&gt;
 sudo docker restart ab3&lt;br /&gt;
 sudo docker container ls&lt;br /&gt;
 sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
 /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16750</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16750"/>
		<updated>2025-07-15T21:55:16Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
 ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
 sudo docker restart redis&lt;br /&gt;
 sudo docker restart ab3&lt;br /&gt;
 sudo docker container ls&lt;br /&gt;
 sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
 /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16749</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16749"/>
		<updated>2025-07-15T21:55:00Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
 ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
 sudo docker restart redis&lt;br /&gt;
 sudo docker restart ab3&lt;br /&gt;
 sudo docker container ls&lt;br /&gt;
 sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
* /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16748</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16748"/>
		<updated>2025-07-15T21:54:44Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
* ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
 sudo docker restart redis&lt;br /&gt;
 sudo docker restart ab3&lt;br /&gt;
 sudo docker container ls&lt;br /&gt;
 sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
* /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16747</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16747"/>
		<updated>2025-07-15T21:54:02Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
 /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
* ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
* sudo docker restart redis&lt;br /&gt;
* sudo docker restart ab3&lt;br /&gt;
* sudo docker container ls&lt;br /&gt;
* sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
* /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16746</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16746"/>
		<updated>2025-07-15T21:31:51Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
* /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the Google Docs guide for details about how to run Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
Look at the Google Sheets for details about previously run enumerations:&lt;br /&gt;
*https://docs.google.com/spreadsheets/d/1MYvCNoIxxluvPR1J7eVogw68ESWIoCRMYSvWh9FnFwc/edit?gid=1892642148#gid=1892642148&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
* ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
* sudo docker restart redis&lt;br /&gt;
* sudo docker restart ab3&lt;br /&gt;
* sudo docker container ls&lt;br /&gt;
* sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
==Chemistry Commons==&lt;br /&gt;
*To restart, rerun the runner on gitlab.docking.org &lt;br /&gt;
Ongoing bugs:&lt;br /&gt;
*AB3 data send failure.&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
The built molecules are stored in:&lt;br /&gt;
* /nfs/exk/copipeline&lt;br /&gt;
Use this guide to run Covalent 3D Building:&lt;br /&gt;
*https://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16745</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16745"/>
		<updated>2025-07-15T21:25:09Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
This is the directory in which all of Fe is located:&lt;br /&gt;
* /nfs/exj/Fe&lt;br /&gt;
Check out the ReadMe file for further details&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
Look at the google docs guide for details about Enumeration:&lt;br /&gt;
* https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
* ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
* sudo docker restart redis&lt;br /&gt;
* sudo docker restart ab3&lt;br /&gt;
* sudo docker container ls&lt;br /&gt;
* sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
* /nfs/exk/copipeline&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16733</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16733"/>
		<updated>2025-07-08T21:31:09Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== FE and Chemistry Commons ==&lt;br /&gt;
&lt;br /&gt;
* /nfs/exj/Fe&lt;br /&gt;
&lt;br /&gt;
== Enumeration ==&lt;br /&gt;
* Look at guide in https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
* ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
* sudo docker restart redis&lt;br /&gt;
* sudo docker restart ab3&lt;br /&gt;
* sudo docker container ls&lt;br /&gt;
* sudo docker logs --since 30m ab3&lt;br /&gt;
&lt;br /&gt;
== ZINC20 Loading ==&lt;br /&gt;
* https://wiki.docking.org/index.php/LoadingZINC21&lt;br /&gt;
&lt;br /&gt;
== Covalent 3D Building ==&lt;br /&gt;
* /nfs/exk/copipeline&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16732</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16732"/>
		<updated>2025-07-08T21:15:38Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* AB3 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;- Look at guide in https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
* sudo docker restart redis&lt;br /&gt;
* sudo docker restart ab3&lt;br /&gt;
* sudo docker container ls&lt;br /&gt;
* sudo docker logs --since 30m ab3&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16731</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16731"/>
		<updated>2025-07-08T21:15:22Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;- Look at guide in https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
== AB3 ==&lt;br /&gt;
&lt;br /&gt;
ssh epyc&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important commands&#039;&#039;&#039;&lt;br /&gt;
sudo docker restart redis&lt;br /&gt;
sudo docker restart ab3&lt;br /&gt;
sudo docker container ls&lt;br /&gt;
sudo docker logs --since 30m ab3&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Group_Meeting&amp;diff=16722</id>
		<title>Group Meeting</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Group_Meeting&amp;diff=16722"/>
		<updated>2025-06-12T18:43:05Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shoichet Lab Group Meetings = &lt;br /&gt;
&#039;&#039;&#039;Google Calendarise the Shoichet Group Meeting schedule&#039;&#039;&#039; &lt;br /&gt;
&amp;quot;Shoichet Group Meetings&amp;quot; gCal is maintained by Jakki - Lab meetings and subgroup schedules are kept (mostly) up to date. This Wiki Page is updated ~1-2x a month. Calendar is shared with all lab members; individual invites are sent to those presenting in lab meetings.&lt;br /&gt;
&lt;br /&gt;
You can access the SGM schedule through your own Google calendar account by [http://www.google.com/calendar/render?cid=90hc5i060oggekk2s3c8sluf4g%40group.calendar.google.com clicking here].&lt;br /&gt;
&lt;br /&gt;
For the unfortunate souls that do not have a Google account and those rebellious ones that do not care, an HTML version is available [http://www.google.com/calendar/embed?src=90hc5i060oggekk2s3c8sluf4g%40group.calendar.google.com&amp;amp;pvttk=b015223b9cc576dce92e6cc7698935cd here].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GROUP MEETINGS ARE [[FRIDAYS AT 9:00-11:00 A.M. in MH-1406 until 6/13/25 (except 5/30, we&#039;re in BH-513)]].&lt;br /&gt;
{{TOCright}}&lt;br /&gt;
&#039;&#039;&#039;Social Hour starts at 10:30 A.M.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Subgroups &amp;amp; Misc ===&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Model Systems&#039;&#039;&#039; Tuesdays 2-3:20&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Aggregates / PLD Subgroup&#039;&#039;&#039; Wednesdays 9:30-10:20&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orphan GPCR Subgroup&#039;&#039;&#039; Wednesdays 10:30-11:20&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Drug Targets&#039;&#039;&#039; Wednesdays 11:30-12:50&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;John Irwin Office Hours&#039;&#039;&#039; Thursdays 11-12&lt;br /&gt;
&lt;br /&gt;
= &#039;&#039;&#039;MEETING SCHEDULE   =&lt;br /&gt;
&#039;&#039;&#039;(Updated 05/03/25 - JS)&#039;&#039;&#039;&lt;br /&gt;
*05/09/25 - Seth (MH-1406)&lt;br /&gt;
*05/16/25 - No Meeting&lt;br /&gt;
*05/23/25 - Olivier (MH-1406)&lt;br /&gt;
*05/30/25 - John (MH-1406)&lt;br /&gt;
*06/06/25 - No Meeting&lt;br /&gt;
*06/13/25 - Rotation Students (MH-1406)&lt;br /&gt;
*06/20/25 - Divya (GH-N114)&lt;br /&gt;
*06/27/25 - No Meeting&lt;br /&gt;
*07/04/25 - No Meeting, Happy America Day&lt;br /&gt;
&lt;br /&gt;
The following dates are not confirmed with BKS...&lt;br /&gt;
*07/11/25 - Philipp (GH-N114)&lt;br /&gt;
*07/18/25 - Sijie (GH-N114)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Disclaimer: Dates are subject to change based on BKS availability.&#039;&#039; &lt;br /&gt;
We do not meet on holidays or when BKS is not present. Please lmk if your date is a holiday or if your assigned date does not work for you, I&#039;ll make changes as needed!&lt;br /&gt;
&lt;br /&gt;
= Announcements =&lt;br /&gt;
&lt;br /&gt;
4/28-5/2 - BKS Out, no subgroups&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guest Speakers:&lt;br /&gt;
&lt;br /&gt;
None at the moment&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please mark on google calendar when you will not be in the lab&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Rotation Order =&lt;br /&gt;
New members join rotation list after first lab meeting attended. They will see the same person present twice before their first meeting.&lt;br /&gt;
&lt;br /&gt;
Rotation students will give a summary at end of rotation. Notify lab manager to schedule.&lt;br /&gt;
Second years will be added to rotation schedule such that they present in Winter Quarter after joining lab.&lt;br /&gt;
&lt;br /&gt;
If meetings are shuffled, we try to maintain rotation order unless it is egregiously messed up. &lt;br /&gt;
&lt;br /&gt;
*Yujin Wu&lt;br /&gt;
*Moira Rachman&lt;br /&gt;
*Lu Paris&lt;br /&gt;
*Brian Shoichet&lt;br /&gt;
*Xinyu Xu&lt;br /&gt;
*Joe Pepe&lt;br /&gt;
*Alina Arzamassky &lt;br /&gt;
*Andrii Kyrylchuk&lt;br /&gt;
*Katie Holland&lt;br /&gt;
*Zoey Dingman&lt;br /&gt;
*Zack Mawaldi&lt;br /&gt;
*Catherine Shin&lt;br /&gt;
*Makayla Freitas&lt;br /&gt;
*Seth Vigneron&lt;br /&gt;
*Divya Kranthi &lt;br /&gt;
*John Irwin&lt;br /&gt;
*Philipp Seemann&lt;br /&gt;
*Sijie Huang&lt;br /&gt;
*Brendan Hall&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Email Meeting Schedule to:&lt;br /&gt;
*yall-bkslab@googlegroups.com&lt;br /&gt;
*meetings-bkslab@googlegroups.com&lt;br /&gt;
*RS/guests if presenting&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following people are part of our meeting only email list: &lt;br /&gt;
*N/A&lt;br /&gt;
&lt;br /&gt;
= Group Meeting Food = &lt;br /&gt;
* 11/2024 - Katie places BearBuy orders for bagels and Andrii brings the coffee&lt;br /&gt;
&lt;br /&gt;
= Room Bookings = &lt;br /&gt;
&lt;br /&gt;
(Updated 05/03/25 - JS)&lt;br /&gt;
* In MH-1406 until June 13th&lt;br /&gt;
&lt;br /&gt;
* Summer quarter (June 16th - September 10th) in &#039;&#039;&#039;GH-N114&#039;&#039;&#039; EXCEPT 8/22 &amp;amp; 8/29, we&#039;re in MH-1406&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Fall quarter (September 11th - December 30th) reservations open 07/11&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* GH S536A is booked by Yvonne until through Alma Agorilla Friday&#039;s 9:30-11AM with no end date&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16558</id>
		<title>How to be Max</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_be_Max&amp;diff=16558"/>
		<updated>2025-02-11T21:08:12Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: Created page with &amp;quot;- Look at guide in https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;- Look at guide in https://docs.google.com/document/d/1b5BvlcbFbhpbc3ZJQ3ehd1ussrMTcd2UyMEk7yXi58I/edit?usp=sharing&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16243</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16243"/>
		<updated>2024-07-26T19:21:45Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/stest/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/stest/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
[http://commons.docking.org commons.docking.org]&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
==Accessing ChemspaceBB SMILES==&lt;br /&gt;
 /nfs/exj/Fe/Filtered/indexed/ChemSpaceBB/ChemspaceBB.smi&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16221</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16221"/>
		<updated>2024-06-28T20:02:12Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/stest/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/stest/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
[http://commons.docking.org commons.docking.org]&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16208</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16208"/>
		<updated>2024-06-25T14:06:13Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SGE ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
it is in the /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for Wynton ==&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /wynton/group/bks/CovalentBuilding/DOCK-3.7-trunk&lt;br /&gt;
 source /wynton/group/bks/CovalentBuilding/.csh_corina&lt;br /&gt;
 source /wynton/group/bks/CovalentBuilding/DOCK-3.7-trunk/env.csh&lt;br /&gt;
&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /wynton/group/bks/CovalentBuilding/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SLURM ==&lt;br /&gt;
SSH n-1-19&lt;br /&gt;
 ssh n-1-19 (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 setenv AMSOLEXE /nfs/soft/amsol/in-house/amsol7.1-colinear-fix/amsol7.1&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent_slurm.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16189</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16189"/>
		<updated>2024-06-15T17:44:04Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SGE ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
it is in the /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SLURM ==&lt;br /&gt;
SSH n-1-19&lt;br /&gt;
 ssh n-1-19 (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 setenv AMSOLEXE /nfs/soft/amsol/in-house/amsol7.1-colinear-fix/amsol7.1&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent_slurm.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16188</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16188"/>
		<updated>2024-06-15T17:40:54Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SGE ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 setenv AMSOLEXE /nfs/soft/amsol/in-house/amsol7.1-colinear-fix/amsol7.1&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
it is in the /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SLURM ==&lt;br /&gt;
SSH Epyc&lt;br /&gt;
 ssh epyc (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent_slurm.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16187</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16187"/>
		<updated>2024-06-14T19:26:01Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
[http://commons.docking.org commons.docking.org]&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16186</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16186"/>
		<updated>2024-06-14T19:25:13Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16185</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16185"/>
		<updated>2024-06-14T19:24:44Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* Organization in Fe Files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
Tab Separated Columns:&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16184</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16184"/>
		<updated>2024-06-14T19:24:20Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* Organization in Fe Files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
Tab separated:&lt;br /&gt;
 1st column: Enumerated compound&lt;br /&gt;
 2nd column: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd column: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ columns: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16183</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16183"/>
		<updated>2024-06-14T19:22:54Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* Useful Commands */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st item: Enumerated compound&lt;br /&gt;
 2nd item: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd item: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ items: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +3 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16182</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16182"/>
		<updated>2024-06-14T19:20:31Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
 1st item: Enumerated compound&lt;br /&gt;
 2nd item: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
 3rd item: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
 4+ items: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +2 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16181</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16181"/>
		<updated>2024-06-14T19:19:47Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
 there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
1st item: Enumerated compound&lt;br /&gt;
2nd item: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
3rd item: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
4+ items: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +2 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16180</id>
		<title>Fe database</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Fe_database&amp;diff=16180"/>
		<updated>2024-06-14T19:19:23Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Accessing Fe/Iron==&lt;br /&gt;
Fe, which is the Enumeration of the Hartenfeller and other reliable reactions, can be found &lt;br /&gt;
&lt;br /&gt;
on our cluster at &lt;br /&gt;
 /nfs/exj/Fe/&lt;br /&gt;
&lt;br /&gt;
Using Chemspace Building Blocks (480K) the enumerations are in &lt;br /&gt;
&lt;br /&gt;
 /mnt/nfs/exj/Fe/Chemspace0324/ChemspaceBB_enumerated&lt;br /&gt;
&lt;br /&gt;
there are also some in /mnt/nfs/exj/Fe/Chemspace0324/170split&lt;br /&gt;
&lt;br /&gt;
Some molecules are also available on Wynton&lt;br /&gt;
 /wynton/group/bks/iron-24/&lt;br /&gt;
 and /wynton/group/bks/Fe-stage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They are also available on AWS. &lt;br /&gt;
 aws:///zinc3d/Fe/&lt;br /&gt;
&lt;br /&gt;
==Reaction Codes==&lt;br /&gt;
You can find the corresponding reaction to reaction id in:&lt;br /&gt;
commons.docking.org&lt;br /&gt;
&lt;br /&gt;
==Organization in Fe Files==&lt;br /&gt;
1st item: Enumerated compound&lt;br /&gt;
2nd item: Generated enumerated compound ID consisting of reaction ID, library, and building block IDs used to make compound&lt;br /&gt;
3rd item: Tranch or HAC/logP of enumerated compound&lt;br /&gt;
4+ items: Starting building blocks&lt;br /&gt;
&lt;br /&gt;
==Useful Commands==&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print&lt;br /&gt;
Is a general command that can be used to find all the files with enumerated compounds at the top level directories&lt;br /&gt;
 find . -name &amp;quot;*.txt.gz&amp;quot; -print -exec zcat {} \; | tail -n +2 &amp;gt; all_files.txt&lt;br /&gt;
Is a command that is run to string the files all together into one. When zcating the first line is incorrect and this command foregoes the first incorrect line when cating them all.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Databases]]&lt;br /&gt;
[[Category:Chemical Space]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16155</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16155"/>
		<updated>2024-06-07T18:19:36Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SGE ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  3D Covalent Building for SLURM ==&lt;br /&gt;
SSH Epyc&lt;br /&gt;
 ssh epyc (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent_slurm.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16154</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16154"/>
		<updated>2024-06-07T18:18:26Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  Preparing ligands for SGE ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
==  Preparing ligands for SLURM ==&lt;br /&gt;
SSH Epyc&lt;br /&gt;
 ssh epyc (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent_slurm.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16137</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=16137"/>
		<updated>2024-06-04T20:39:27Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* Preparing ligands */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  Preparing ligands ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh /nfs/exk/copipeline/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=15884</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=15884"/>
		<updated>2024-05-21T19:46:51Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  Preparing ligands ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel (with s_ account)&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh ~elisfink/scripts/09-2022-ligbuild/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
== Updated version from Khanh ==&lt;br /&gt;
Note: I tried following the pipeline above. Although it worked great on gimel (a CentOS server), I have trouble running it on CentOS 7 servers due to AMSOL that it used which was compiled on a very out-of-date fortran complier. So I recompiled AMSOL and refactored the build3d pipeline to use Python3 (I know, another copy of DOCK that is untracked)&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
&lt;br /&gt;
This script only works on servers with GCC version 4+ (slurm nodes) and it won&#039;t work on our sge nodes running on CentOS 6&lt;br /&gt;
Example:&lt;br /&gt;
 ssh n-1-17&lt;br /&gt;
&lt;br /&gt;
 source /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/env.sh&lt;br /&gt;
&lt;br /&gt;
 // build covalent db2 file from smiles&lt;br /&gt;
 export SOURCE_FILE=input.smi&lt;br /&gt;
 bash $DOCKBASE/ligand/generate/build_database_ligand.sh --no-db --no-solv --no-mol2 --single --covalent -H 7.4&lt;br /&gt;
&lt;br /&gt;
 // build db2 from mol2&lt;br /&gt;
 bash /nfs/ex7/blaster/templates/build3d_mol2/dock37_pipeline/build_ligand.sh input.mol2 --name=&amp;quot;Name&amp;quot; --smiles=&amp;quot;SMILES&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=15638</id>
		<title>Covalent Library Preparation 2024</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Covalent_Library_Preparation_2024&amp;diff=15638"/>
		<updated>2024-02-20T22:15:53Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: Created page with &amp;quot;Modify warhead to covalent adduct with SiH3 added.  == Prepare “SMILES ID” file. ==   ssh n-1-17 (or another development node)  Source environment with RDkit  source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh   conda activate base3.7   python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi  This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Modify warhead to covalent adduct with SiH3 added.&lt;br /&gt;
&lt;br /&gt;
== Prepare “SMILES ID” file. ==&lt;br /&gt;
&lt;br /&gt;
 ssh n-1-17 (or another development node)&lt;br /&gt;
&lt;br /&gt;
Source environment with RDkit&lt;br /&gt;
 source /mnt/nfs/ex9/work/ttummino/miniconda/etc/profile.d/conda.sh&lt;br /&gt;
&lt;br /&gt;
 conda activate base3.7&lt;br /&gt;
&lt;br /&gt;
 python ~ak87/PROGRAM/convert_smiles_to_covalent.py ald bbv-cov-ald.smi bbv-cov-ald-test.smi&lt;br /&gt;
&lt;br /&gt;
This script enumerates all stereoisomers and converts SMILES to the covalent ones. Currently, only conversions for aldehydes and nitriles is supported. Usage: &lt;br /&gt;
&lt;br /&gt;
* First arg:    ald or nitr for aldehyde or nitrile&lt;br /&gt;
&lt;br /&gt;
* Second arg:    input smi file&lt;br /&gt;
&lt;br /&gt;
* Third arg:    output file name&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  Preparing ligands ==&lt;br /&gt;
SSH Gimel&lt;br /&gt;
 ssh gimel&lt;br /&gt;
Set to csh&lt;br /&gt;
 csh&lt;br /&gt;
Source Environments&lt;br /&gt;
 source ~elisfink/.csh_corina&lt;br /&gt;
 setenv DOCKBASE /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk&lt;br /&gt;
 source /nfs/soft/dock/versions/dock37/DOCK-3.7-trunk/env.csh&lt;br /&gt;
Run Script with input.smi as your prepared SMILES file&lt;br /&gt;
 csh ~elisfink/scripts/09-2022-ligbuild/0001_wrapper_queue_build_smiles_ligand_mod_corina_covalent.csh input.smi&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Covalent]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=AB3_Developer_Notes&amp;diff=15572</id>
		<title>AB3 Developer Notes</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=AB3_Developer_Notes&amp;diff=15572"/>
		<updated>2023-12-05T19:48:57Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;UNDER DEVELOPMENT&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The back-end and the front-end of this tool can be accessed at ABBB and AB3FrontEnd repositories at https://gitlab.docking.org, respectively. &lt;br /&gt;
&lt;br /&gt;
== Backend ==&lt;br /&gt;
The backend runs on Flask and has two main scripts running that do all the main calculations, which are BespokeAnaloging.py and arthorquery.py. The Bespoke Analoging script gets called in the routes section with the call_ABBB function. There we use a JSON file with all our reaction information as the first input and a smiles string as the second input which we get from the front-end. This script takes those inputs and runs the smiles against all those reactions and spits out building blocks if any of the reactions worked on the smiles. Those building blocks as well as a Tanimoto coefficient can then be used in the following script: arthorquery.py. The script takes all the building blocks that were derived from the first script and uses Arthor to find analogs of the building blocks using similarity against the Tanimoto coefficient and inclusion and exclusion rules as a basis.&lt;br /&gt;
&lt;br /&gt;
== Restarting ==&lt;br /&gt;
AB3 runs on the Epyc node. If AB3 is down first start by ssh-ing into Epyc. Use sudo docker logs --since 30m ab3 to see logs of AB3 and check to see if there was a reason for the crash. Then you can use the following commands &amp;quot;sudo docker restart redis&amp;quot; and &amp;quot;sudo docker restart AB3&amp;quot; to get AB3 back up and running. If that doesn&#039;t work replace &amp;quot;restart&amp;quot; with &amp;quot;start&amp;quot; and run those commands again.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15541</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15541"/>
		<updated>2023-09-21T19:57:44Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* Useful Resources */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
== Useful Resources ==&lt;br /&gt;
*http://rxnmapper.ai/demo.html?rxn=CC(C)S.CN(C)C%253DO.Fc1cccnc1F.O%253DC(%255BO-%255D)%255BO-%255D.%255BK%252B%255D%253E%253ECC(C)Sc1ncccc1C&amp;amp;selectedLayer=10&amp;amp;selectedHead=5&amp;amp;selectedTokenSide=null&amp;amp;selectedTokenInd=null&lt;br /&gt;
*https://smarts.plus/&lt;br /&gt;
*https://arthor.docking.org/index.html&lt;br /&gt;
[[Category: enumeration]]&lt;br /&gt;
[[Category: Commons]]&lt;br /&gt;
[[Category: AB3]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15540</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15540"/>
		<updated>2023-09-21T19:56:19Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
== Useful Resources ==&lt;br /&gt;
*http://rxnmapper.ai/demo.html?rxn=CC(C)S.CN(C)C%253DO.Fc1cccnc1F.O%253DC(%255BO-%255D)%255BO-%255D.%255BK%252B%255D%253E%253ECC(C)Sc1ncccc1C&amp;amp;selectedLayer=10&amp;amp;selectedHead=5&amp;amp;selectedTokenSide=null&amp;amp;selectedTokenInd=null&lt;br /&gt;
*https://smarts.plus/&lt;br /&gt;
*arthor.docking.org&lt;br /&gt;
[[Category: enumeration]]&lt;br /&gt;
[[Category: Commons]]&lt;br /&gt;
[[Category: AB3]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15539</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15539"/>
		<updated>2023-09-21T19:55:58Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
== Useful Resources ==&lt;br /&gt;
http://rxnmapper.ai/demo.html?rxn=CC(C)S.CN(C)C%253DO.Fc1cccnc1F.O%253DC(%255BO-%255D)%255BO-%255D.%255BK%252B%255D%253E%253ECC(C)Sc1ncccc1C&amp;amp;selectedLayer=10&amp;amp;selectedHead=5&amp;amp;selectedTokenSide=null&amp;amp;selectedTokenInd=null&lt;br /&gt;
https://smarts.plus/&lt;br /&gt;
arthor.docking.org&lt;br /&gt;
[[Category: enumeration]]&lt;br /&gt;
[[Category: Commons]]&lt;br /&gt;
[[Category: AB3]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15537</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15537"/>
		<updated>2023-09-21T19:53:57Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
&lt;br /&gt;
[[Category: enumeration]]&lt;br /&gt;
[[Category: Chemistry Commons]]&lt;br /&gt;
[[Category: AB3]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15536</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15536"/>
		<updated>2023-09-21T19:53:17Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
&lt;br /&gt;
[[Category: enumeration]]&lt;br /&gt;
[[Category: Chemistry Commons]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15535</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15535"/>
		<updated>2023-09-21T19:52:12Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;br /&gt;
&lt;br /&gt;
[[Category: enumeration]]&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15484</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15484"/>
		<updated>2023-08-10T19:21:20Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building Your Library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15483</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15483"/>
		<updated>2023-08-10T19:19:52Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just type &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the ones of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building your library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15482</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15482"/>
		<updated>2023-08-10T19:17:56Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
*Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. &lt;br /&gt;
*Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. &lt;br /&gt;
*Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
*After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. &lt;br /&gt;
*Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. &lt;br /&gt;
*Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . &lt;br /&gt;
*You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &lt;br /&gt;
*&amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the one of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save. &lt;br /&gt;
*Next, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building your library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15481</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15481"/>
		<updated>2023-08-10T19:14:48Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(&amp;quot;chemistry4biology at gmail dot com&amp;quot;) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email us at &amp;quot;chemistry4biology at gmail dot com&amp;quot; to help you get set up. Login into your cluster account and make sure you are in your home directory. Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the one of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save.vNext, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building your library ==&lt;br /&gt;
Congratulations you have completed the setup and are ready to run enumeration. All you need to do now is go into your reaction directory by using the command &#039;&#039;&#039;cd &amp;lt;name&amp;gt;&#039;&#039;&#039; and the run the script with &amp;quot;&#039;&#039;&#039;bash ../scripts/Etest.bash .&#039;&#039;&#039;&amp;quot;. After enumeration is completed cd into your results directly and your enumerated file should be located inside!&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15480</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15480"/>
		<updated>2023-08-10T19:04:49Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(mtsukanov at berkeley dot edu) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
After you have made your reaction you are ready to get them ready on the cluster. If you don&#039;t have an account on the cluster already please email our lab member Khanh Tang at khtang015 at gmail dot com to help you get set up. Login into your cluster account and make sure you are in your home directory. Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the one of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save.vNext, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building your library ==&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15479</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15479"/>
		<updated>2023-08-10T19:04:01Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(mtsukanov at berkeley dot edu) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
After you have made your reaction you are ready to run it on the cluster. If you don&#039;t have an account on the cluster already please email our lab member Khanh Tang at khtang015 at gmail dot com to help you get set up. Login into your cluster account and make sure you are in your home directory. Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. &amp;quot;&#039;&#039;&#039;cd &amp;lt;changed name&amp;gt;&#039;&#039;&#039;&amp;quot; into this directory to then change the parameters. To keep things simple you can just &amp;quot;&#039;&#039;&#039;vim Reaction&#039;&#039;&#039;&amp;quot; press &#039;&#039;&#039;i&#039;&#039;&#039; and then change the id&#039;s to the one of your reaction and in/exclusion rules. Then press &#039;&#039;&#039;esc&#039;&#039;&#039; and type &#039;&#039;&#039;:wq!&#039;&#039;&#039; to save.vNext, ssh into a node such as n-1-18(&amp;quot;&#039;&#039;&#039;ssh n-1-18&#039;&#039;&#039;&amp;quot;) so that you&#039;re able to meet the requirements to run the scripts and then source the environment by doing &amp;quot;&#039;&#039;&#039;source /nfs/home/ak87/exa/UCSF/SynthI/BESPOKE/arthor-env/bin/activate&#039;&#039;&#039;&amp;quot; to get all the necessary packages for the scripts run.&lt;br /&gt;
== Step 3. Running the Scripts and Building your library ==&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15478</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15478"/>
		<updated>2023-08-10T18:52:37Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Step 1. Coding the Reactions ==&lt;br /&gt;
Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(mtsukanov at berkeley dot edu) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Step 2. Setting Up ==&lt;br /&gt;
After you have made your reaction you are ready to run it on the cluster. If you don&#039;t have an account on the cluster already please email our lab member Khanh Tang at khtang015 at gmail dot com to help you get set up. Login into your cluster account and make sure you are in your home directory. Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. Next ssh into a node such as n-1-18 so that you&#039;re able to meet the requirements to run the scripts.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15477</id>
		<title>CLI Enumeration</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=CLI_Enumeration&amp;diff=15477"/>
		<updated>2023-08-10T18:51:56Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: Created page with &amp;quot;== Coding the Reactions == Step 1. Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recomme...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Coding the Reactions ==&lt;br /&gt;
Step 1. Pick out the reactions that you want to enumerate. This can be done either through already-made reactions that are in commons.docking.org or you can use those reaction SMARTS and inclusion/exclusion SMARTS as examples/guidelines to make your own reaction/s. We recommend using the daylight SMARTS as a resource if you plan on doing this: https://www.daylight.com/dayhtml/doc/theory/theory.smarts.html. Once you have your reaction we recommend testing the inclusion and exclusion SMARTS through our website which has many modules and tools called TLDR. We have a specific tool called BBfilter(https://tldr.docking.org/start/bbfilter) that outputs building blocks from a large database based on the inclusion and exclusion SMARTS that are provided. Based on the correctness of the molecules that are outputted, the in/exclusion SMARTS should be adjusted to fit your needs. Once all the SMARTS have been finalized you can either submit this reaction into our reaction database called ChemistryCommons at commons.docking.org and email us once you do or email the SMARTS directly to us(mtsukanov at berkeley dot edu) so that we can set your reaction up on the cluster.&lt;br /&gt;
== Setting UP ==&lt;br /&gt;
Step 2. After you have made your reaction you are ready to run it on the cluster. If you don&#039;t have an account on the cluster already please email our lab member Khanh Tang at khtang015 at gmail dot com to help you get set up. Login into your cluster account and make sure you are in your home directory. Next, you will need to make a directory in your home directory that will store the enumeration results: &amp;quot;&#039;&#039;&#039;mkdir &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot;. Then you will need to copy the necessary scripts over and this can be done by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/scripts .&#039;&#039;&#039;&amp;quot; . You will also need to copy an example reaction directory by doing: &amp;quot;&#039;&#039;&#039;cp /nfs/exj/Fe/Test .&#039;&#039;&#039;&amp;quot; . Use &amp;quot;&#039;&#039;&#039;mv Test &amp;lt;name&amp;gt;&#039;&#039;&#039;&amp;quot; to change the name into whatever you&#039;d like. Next ssh into a node such as n-1-18 so that you&#039;re able to meet the requirements to run the scripts.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15411</id>
		<title>Particle Shape Calculator for CCDC/Mercury</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15411"/>
		<updated>2023-05-23T21:25:02Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* VisualHabit */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial will introduce you to the morphology calculation features included&lt;br /&gt;
with Mercury under the CSD-Particle toolset, namely BFDH Morphology and&lt;br /&gt;
VisualHabit.&lt;br /&gt;
BFDH crystal morphology is an approximation based on crystallographic&lt;br /&gt;
geometrical considerations. For a given structure, the BFDH algorithm will predict&lt;br /&gt;
the habit or shape of a crystal using the corresponding unit cell and symmetry&lt;br /&gt;
operator information.&lt;br /&gt;
The VisualHabit tool calculates a morphology for your material based on its&lt;br /&gt;
crystal structure. Using a range of forcefields, we can calculate the intermolecular&lt;br /&gt;
interactions, or synthons, in a crystal structure; the sum of these gives the lattice&lt;br /&gt;
energy for that system. From these lattice energies, we can calculate slice energies&lt;br /&gt;
and, consequently, the attachment energy for each slice. Crystal growth rates&lt;br /&gt;
assumed to be proportional to these attachment energies and can be used to&lt;br /&gt;
predict crystal shapes. The VisualHabit tool is used to calculate and analyze these&lt;br /&gt;
energies and to visualize the resulting morphologies, an instrumental step in&lt;br /&gt;
enabling solid form and particle design for small molecule crystal structures&lt;br /&gt;
&lt;br /&gt;
==BFDH==&lt;br /&gt;
1. Open Mercury by double-clicking the Mercury icon on the desktop.&lt;br /&gt;
&lt;br /&gt;
2. In the Structure Navigator toolbar type the refcode KAXXAI10.&lt;br /&gt;
&lt;br /&gt;
3. We want to identify facets of interest in this morphology. We will first create&lt;br /&gt;
the morphology using the BFDH morphology feature.&lt;br /&gt;
&lt;br /&gt;
4. From the top-level menu select CSD-Particle &amp;gt; Morphology &amp;gt; BFDH… to&lt;br /&gt;
generate the morphology. BFDH morphology uses the unit cell to create the&lt;br /&gt;
morphology you see, therefore it does not account for the chemistry of the&lt;br /&gt;
structure.&lt;br /&gt;
&lt;br /&gt;
5. Rotate the structure to view the various facets that have been generated. If&lt;br /&gt;
you wish, explore options in the Morphology window.&lt;br /&gt;
&lt;br /&gt;
6. The morphology can be modified, for example, if you want to represent a&lt;br /&gt;
crystal observed from growth experiments. In the Morphology window, click&lt;br /&gt;
Save… and place the .cif file in a folder where you have permission.&lt;br /&gt;
&lt;br /&gt;
7. Using a text editor of your choice open the morphology .cif file. You will see&lt;br /&gt;
the data that corresponds to the HKLs and perpendicular distances. You can&lt;br /&gt;
modify these values to change the morphology. For the sake of example, we will&lt;br /&gt;
simply switch the values of some of the perpendicular distances. Note that&lt;br /&gt;
these changes are not based on experimental observation&lt;br /&gt;
&lt;br /&gt;
8. Back in Mercury, In the Morphology window click Open… and select your&lt;br /&gt;
modified .cif file to visualize your new morphology&lt;br /&gt;
&lt;br /&gt;
==VisualHabit==&lt;br /&gt;
&lt;br /&gt;
The shape of a crystal results from the relative growth rates in different&lt;br /&gt;
directions. Strong intermolecular interactions, or synthons, in one direction, can&lt;br /&gt;
result in elongated crystal shapes like needles forming. Needle-shaped crystals&lt;br /&gt;
are common in pharmaceuticals and are undesirable due to their poor processing&lt;br /&gt;
characteristics. Being able to predict needle formation from a crystal structure is&lt;br /&gt;
helpful to understand potential manufacturing challenges.&lt;br /&gt;
&lt;br /&gt;
1. Launch Mercury by clicking its icon. In the Structure Navigator toolbar,&lt;br /&gt;
type UREAXX to bring up the structure for urea.&lt;br /&gt;
&lt;br /&gt;
2. Click on the CSD-Particle menu, select Morphology, then select VisualHabit…&lt;br /&gt;
&lt;br /&gt;
3. In the VisualHabit dialogue box, you will see several options. On the left, you&lt;br /&gt;
will find options to change the calculation settings, such as which forcefield&lt;br /&gt;
is used and the limiting radius for the calculation. You can also choose&lt;br /&gt;
whether to add an electrostatic correction or not. On the right you will see&lt;br /&gt;
where the lattice energy results will appear once the calculation is complete.&lt;br /&gt;
For the purposes of this tutorial, we will keep the default options. These&lt;br /&gt;
typically work well for most situations, but if you know you are looking at&lt;br /&gt;
specific chemistry or a charged system, you may want to change these&lt;br /&gt;
settings.&lt;br /&gt;
&lt;br /&gt;
4. Click the Calculate button to start.&lt;br /&gt;
&lt;br /&gt;
5. The dialogue box will now update to show the results of the VisualHabit&lt;br /&gt;
calculation. The lattice energy results are shown in the section on the right in&lt;br /&gt;
kJ mol-1. From here, you can see the total lattice energy as well as the&lt;br /&gt;
contributions from the electrostatic, van der Waals, and hydrogen bonding&lt;br /&gt;
energy terms. It’s clear from these results that the lattice energy for urea is&lt;br /&gt;
dominated by the hydrogen bonding energy in the crystal structure.&lt;br /&gt;
&lt;br /&gt;
6. The convergence chart shows how the lattice energy changes over the course&lt;br /&gt;
of the calculation out to the limiting radius and gives an indication of whether&lt;br /&gt;
the calculation has converged successfully (indicated by the green tick at the&lt;br /&gt;
bottom of the chart). This chart tells us that the lattice energy comes close to&lt;br /&gt;
its final value in a small distance for this structure. Urea is a small molecule,&lt;br /&gt;
so this is what we would expect to see.&lt;br /&gt;
&lt;br /&gt;
7. If we look at the Mercury visualizer, we will see that the calculated&lt;br /&gt;
morphology for urea is now shown. VisualHabit calculates an elongated&lt;br /&gt;
morphology for urea where the long axis is aligned to the polar axis of the&lt;br /&gt;
urea molecule.&lt;br /&gt;
&lt;br /&gt;
8. We will now explore the reasons for this elongated shape by examining the&lt;br /&gt;
nature of the intermolecular interactions, or synthons, in more detail. Click&lt;br /&gt;
on the Synthons tab in the VisualHabit dialogue to change the information&lt;br /&gt;
that is shown.&lt;br /&gt;
&lt;br /&gt;
9. The synthons that contribute to the lattice energy, along with the centroid-centroid &lt;br /&gt;
distance and component energy terms, are now shown. Click on the&lt;br /&gt;
Interaction Energy header (you may need to scroll along to see it) to sort this&lt;br /&gt;
column from the strongest interaction to the weakest. Once again, you will&lt;br /&gt;
see that the lattice energy for urea is dominated by a small number of strong&lt;br /&gt;
hydrogen bonding interactions.&lt;br /&gt;
&lt;br /&gt;
10. Now let’s look at the two most important interactions. Click on one of the&lt;br /&gt;
rows in the table to highlight that interaction and show the synthon in the&lt;br /&gt;
Mercury visualizer. You can select multiple rows by holding down Ctrl and&lt;br /&gt;
clicking on the rows of interest. Holding down Shift and clicking will let you select&lt;br /&gt;
multiple rows at once. Select the top two interactions for UREAXX&lt;br /&gt;
(synthons 8 and 9).&lt;br /&gt;
&lt;br /&gt;
11. You will see in the Mercury visualizer that two other urea molecules have&lt;br /&gt;
appeared above and below the central molecule. The red dashed lines&lt;br /&gt;
between the molecules highlight the synthon, and the value beside the line&lt;br /&gt;
shows the interaction energy. You can clearly see that the strongest&lt;br /&gt;
interaction in urea aligns with the fastest growth direction.&lt;br /&gt;
&lt;br /&gt;
12. Click the Visualiser tab in the VisualHabit dialogue. From this tab you can&lt;br /&gt;
change the way that the morphology is displayed in Mercury, such as&lt;br /&gt;
changing the colour of the faces and the edges. You can also change how&lt;br /&gt;
synthons are displayed.&lt;br /&gt;
&lt;br /&gt;
13. Click the radio dial in the Synthons section to display Distance rather than&lt;br /&gt;
Energy.&lt;br /&gt;
&lt;br /&gt;
14. The Mercury visualizer will update to show the centroid-centroid distance of&lt;br /&gt;
the synthons in Å. These short, strong types of hydrogen bonds in the crystal&lt;br /&gt;
structure of urea are key to understanding its growth and the shape of its&lt;br /&gt;
crystals.&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
Crystal shape is governed by the relative growth rates in different directions.&lt;br /&gt;
Strong intermolecular interactions, or synthons, in one direction can result in&lt;br /&gt;
elongated morphologies. The crystal structure of urea is dominated by strong&lt;br /&gt;
hydrogen bonding interactions that occur in tapes that propagate along the&lt;br /&gt;
crystallographic c-axis. This results in an elongated morphology for urea.&lt;br /&gt;
&lt;br /&gt;
You should now know how to calculate a morphology using VisualHabit for a&lt;br /&gt;
CSD structure in Mercury and how to visualize and explore the key interactions&lt;br /&gt;
in that structure relative to the calculated crystal shape.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15410</id>
		<title>Particle Shape Calculator for CCDC/Mercury</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15410"/>
		<updated>2023-05-23T21:22:56Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* BFDH */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial will introduce you to the morphology calculation features included&lt;br /&gt;
with Mercury under the CSD-Particle toolset, namely BFDH Morphology and&lt;br /&gt;
VisualHabit.&lt;br /&gt;
BFDH crystal morphology is an approximation based on crystallographic&lt;br /&gt;
geometrical considerations. For a given structure, the BFDH algorithm will predict&lt;br /&gt;
the habit or shape of a crystal using the corresponding unit cell and symmetry&lt;br /&gt;
operator information.&lt;br /&gt;
The VisualHabit tool calculates a morphology for your material based on its&lt;br /&gt;
crystal structure. Using a range of forcefields, we can calculate the intermolecular&lt;br /&gt;
interactions, or synthons, in a crystal structure; the sum of these gives the lattice&lt;br /&gt;
energy for that system. From these lattice energies, we can calculate slice energies&lt;br /&gt;
and, consequently, the attachment energy for each slice. Crystal growth rates&lt;br /&gt;
assumed to be proportional to these attachment energies and can be used to&lt;br /&gt;
predict crystal shapes. The VisualHabit tool is used to calculate and analyze these&lt;br /&gt;
energies and to visualize the resulting morphologies, an instrumental step in&lt;br /&gt;
enabling solid form and particle design for small molecule crystal structures&lt;br /&gt;
&lt;br /&gt;
==BFDH==&lt;br /&gt;
1. Open Mercury by double-clicking the Mercury icon on the desktop.&lt;br /&gt;
&lt;br /&gt;
2. In the Structure Navigator toolbar type the refcode KAXXAI10.&lt;br /&gt;
&lt;br /&gt;
3. We want to identify facets of interest in this morphology. We will first create&lt;br /&gt;
the morphology using the BFDH morphology feature.&lt;br /&gt;
&lt;br /&gt;
4. From the top-level menu select CSD-Particle &amp;gt; Morphology &amp;gt; BFDH… to&lt;br /&gt;
generate the morphology. BFDH morphology uses the unit cell to create the&lt;br /&gt;
morphology you see, therefore it does not account for the chemistry of the&lt;br /&gt;
structure.&lt;br /&gt;
&lt;br /&gt;
5. Rotate the structure to view the various facets that have been generated. If&lt;br /&gt;
you wish, explore options in the Morphology window.&lt;br /&gt;
&lt;br /&gt;
6. The morphology can be modified, for example, if you want to represent a&lt;br /&gt;
crystal observed from growth experiments. In the Morphology window, click&lt;br /&gt;
Save… and place the .cif file in a folder where you have permission.&lt;br /&gt;
&lt;br /&gt;
7. Using a text editor of your choice open the morphology .cif file. You will see&lt;br /&gt;
the data that corresponds to the HKLs and perpendicular distances. You can&lt;br /&gt;
modify these values to change the morphology. For the sake of example, we will&lt;br /&gt;
simply switch the values of some of the perpendicular distances. Note that&lt;br /&gt;
these changes are not based on experimental observation&lt;br /&gt;
&lt;br /&gt;
8. Back in Mercury, In the Morphology window click Open… and select your&lt;br /&gt;
modified .cif file to visualize your new morphology&lt;br /&gt;
&lt;br /&gt;
==VisualHabit==&lt;br /&gt;
&lt;br /&gt;
The shape of a crystal results from the relative growth rates in different&lt;br /&gt;
directions. Strong intermolecular interactions, or synthons, in one direction, can&lt;br /&gt;
result in elongated crystal shapes like needles forming. Needle-shaped crystals&lt;br /&gt;
are common in pharmaceuticals and are undesirable due to their poor processing&lt;br /&gt;
characteristics. Being able to predict needle formation from a crystal structure is&lt;br /&gt;
helpful to understand potential manufacturing challenges.&lt;br /&gt;
&lt;br /&gt;
1. Launch Mercury by clicking its icon. In the Structure Navigator toolbar,&lt;br /&gt;
type UREAXX to bring up the structure for urea.&lt;br /&gt;
&lt;br /&gt;
2. Click on the CSD-Particle menu, select Morphology, then select VisualHabit…&lt;br /&gt;
3. In the VisualHabit dialogue box, you will see several options. On the left, you&lt;br /&gt;
will find options to change the calculation settings, such as which forcefield&lt;br /&gt;
is used and the limiting radius for the calculation. You can also choose&lt;br /&gt;
whether to add an electrostatic correction or not. On the right you will see&lt;br /&gt;
where the lattice energy results will appear once the calculation is complete.&lt;br /&gt;
For the purposes of this tutorial, we will keep the default options. These&lt;br /&gt;
typically work well for most situations, but if you know you are looking at&lt;br /&gt;
specific chemistry or a charged system, you may want to change these&lt;br /&gt;
settings.&lt;br /&gt;
4. Click the Calculate button to start.&lt;br /&gt;
5. The dialogue box will now update to show the results of the VisualHabit&lt;br /&gt;
calculation. The lattice energy results are shown in the section on the right in&lt;br /&gt;
kJ mol-1&lt;br /&gt;
. From here, you can see the total lattice energy as well as the&lt;br /&gt;
contributions from the electrostatic, van der Waals, and hydrogen bonding&lt;br /&gt;
energy terms. It’s clear from these results that the lattice energy for urea is&lt;br /&gt;
dominated by the hydrogen bonding energy in the crystal structure.&lt;br /&gt;
6. The convergence chart shows how the lattice energy changes over the course&lt;br /&gt;
of the calculation out to the limiting radius and gives an indication of whether&lt;br /&gt;
the calculation has converged successfully (indicated by the green tick at the&lt;br /&gt;
bottom of the chart). This chart tells us that the lattice energy comes close to&lt;br /&gt;
its final value in a small distance for this structure. Urea is a small molecule,&lt;br /&gt;
so this is what we would expect to see.&lt;br /&gt;
7. If we look at the Mercury visualizer, we will see that the calculated&lt;br /&gt;
morphology for urea is now shown. VisualHabit calculates an elongated&lt;br /&gt;
morphology for urea where the long axis is aligned to the polar axis of the&lt;br /&gt;
urea molecule.&lt;br /&gt;
8. We will now explore the reasons for this elongated shape by examining the&lt;br /&gt;
nature of the intermolecular interactions, or synthons, in more detail. Click&lt;br /&gt;
on the Synthons tab in the VisualHabit dialogue to change the information&lt;br /&gt;
that is shown.&lt;br /&gt;
9. The synthons that contribute to the lattice energy, along with the centroid-centroid &lt;br /&gt;
distance and component energy terms, are now shown. Click on the&lt;br /&gt;
Interaction Energy header (you may need to scroll along to see it) to sort this&lt;br /&gt;
column from the strongest interaction to the weakest. Once again, you will&lt;br /&gt;
see that the lattice energy for urea is dominated by a small number of strong&lt;br /&gt;
hydrogen bonding interactions.&lt;br /&gt;
10. Now let’s look at the two most important interactions. Click on one of the&lt;br /&gt;
rows in the table to highlight that interaction and show the synthon in the&lt;br /&gt;
Mercury visualizer. You can select multiple rows by holding down Ctrl and&lt;br /&gt;
clicking on the rows of interest. Holding down Shift and clicking will let you select&lt;br /&gt;
multiple rows at once. Select the top two interactions for UREAXX&lt;br /&gt;
(synthons 8 and 9).&lt;br /&gt;
11. You will see in the Mercury visualizer that two other urea molecules have&lt;br /&gt;
appeared above and below the central molecule. The red dashed lines&lt;br /&gt;
between the molecules highlight the synthon, and the value beside the line&lt;br /&gt;
shows the interaction energy. You can clearly see that the strongest&lt;br /&gt;
interaction in urea aligns with the fastest growth direction.&lt;br /&gt;
12. Click the Visualiser tab in the VisualHabit dialogue. From this tab you can&lt;br /&gt;
change the way that the morphology is displayed in Mercury, such as&lt;br /&gt;
changing the colour of the faces and the edges. You can also change how&lt;br /&gt;
synthons are displayed.&lt;br /&gt;
13. Click the radio dial in the Synthons section to display Distance rather than&lt;br /&gt;
Energy.&lt;br /&gt;
14. The Mercury visualizer will update to show the centroid-centroid distance of&lt;br /&gt;
the synthons in Å. These short, strong types of hydrogen bonds in the crystal&lt;br /&gt;
structure of urea are key to understanding its growth and the shape of its&lt;br /&gt;
crystals.&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
Crystal shape is governed by the relative growth rates in different directions.&lt;br /&gt;
Strong intermolecular interactions, or synthons, in one direction can result in&lt;br /&gt;
elongated morphologies. The crystal structure of urea is dominated by strong&lt;br /&gt;
hydrogen bonding interactions that occur in tapes that propagate along the&lt;br /&gt;
crystallographic c-axis. This results in an elongated morphology for urea.&lt;br /&gt;
&lt;br /&gt;
You should now know how to calculate a morphology using VisualHabit for a&lt;br /&gt;
CSD structure in Mercury and how to visualize and explore the key interactions&lt;br /&gt;
in that structure relative to the calculated crystal shape.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15409</id>
		<title>Particle Shape Calculator for CCDC/Mercury</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15409"/>
		<updated>2023-05-23T21:21:34Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* BFDH */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial will introduce you to the morphology calculation features included&lt;br /&gt;
with Mercury under the CSD-Particle toolset, namely BFDH Morphology and&lt;br /&gt;
VisualHabit.&lt;br /&gt;
BFDH crystal morphology is an approximation based on crystallographic&lt;br /&gt;
geometrical considerations. For a given structure, the BFDH algorithm will predict&lt;br /&gt;
the habit or shape of a crystal using the corresponding unit cell and symmetry&lt;br /&gt;
operator information.&lt;br /&gt;
The VisualHabit tool calculates a morphology for your material based on its&lt;br /&gt;
crystal structure. Using a range of forcefields, we can calculate the intermolecular&lt;br /&gt;
interactions, or synthons, in a crystal structure; the sum of these gives the lattice&lt;br /&gt;
energy for that system. From these lattice energies, we can calculate slice energies&lt;br /&gt;
and, consequently, the attachment energy for each slice. Crystal growth rates&lt;br /&gt;
assumed to be proportional to these attachment energies and can be used to&lt;br /&gt;
predict crystal shapes. The VisualHabit tool is used to calculate and analyze these&lt;br /&gt;
energies and to visualize the resulting morphologies, an instrumental step in&lt;br /&gt;
enabling solid form and particle design for small molecule crystal structures&lt;br /&gt;
&lt;br /&gt;
==BFDH==&lt;br /&gt;
1. Open Mercury by double-clicking the Mercury icon on the desktop.&lt;br /&gt;
&lt;br /&gt;
2. In the Structure Navigator toolbar type the refcode KAXXAI10.&lt;br /&gt;
&lt;br /&gt;
3. We want to identify facets of interest in this morphology. We will first create&lt;br /&gt;
the morphology using the BFDH morphology feature.&lt;br /&gt;
&lt;br /&gt;
4. From the top-level menu select CSD-Particle &amp;gt; Morphology &amp;gt; BFDH… to&lt;br /&gt;
generate the morphology. BFDH morphology uses the unit cell to create the&lt;br /&gt;
morphology you see, therefore it does not account for the chemistry of the&lt;br /&gt;
structure.&lt;br /&gt;
&lt;br /&gt;
5. Rotate the structure to view the various facets that have been generated. If&lt;br /&gt;
you wish, explore options in the Morphology window.&lt;br /&gt;
&lt;br /&gt;
6. In the following exercises you may decide to calculate the BFDH morphology&lt;br /&gt;
to compare the results.&lt;br /&gt;
&lt;br /&gt;
7. The morphology can be modified, for example, if you want to represent a&lt;br /&gt;
crystal observed from growth experiments. In the Morphology window, click&lt;br /&gt;
Save… and place the .cif file in a folder where you have permission.&lt;br /&gt;
&lt;br /&gt;
8. Using a text editor of your choice open the morphology .cif file. You will see&lt;br /&gt;
the data that corresponds to the HKLs and perpendicular distances. You can&lt;br /&gt;
modify these values to change the morphology. For the sake of example, we will&lt;br /&gt;
simply switch the values of some of the perpendicular distances. Note that&lt;br /&gt;
these changes are not based on experimental observation&lt;br /&gt;
&lt;br /&gt;
9. Back in Mercury, In the Morphology window click Open… and select your&lt;br /&gt;
modified .cif file to visualize your new morphology&lt;br /&gt;
&lt;br /&gt;
==VisualHabit==&lt;br /&gt;
&lt;br /&gt;
The shape of a crystal results from the relative growth rates in different&lt;br /&gt;
directions. Strong intermolecular interactions, or synthons, in one direction, can&lt;br /&gt;
result in elongated crystal shapes like needles forming. Needle-shaped crystals&lt;br /&gt;
are common in pharmaceuticals and are undesirable due to their poor processing&lt;br /&gt;
characteristics. Being able to predict needle formation from a crystal structure is&lt;br /&gt;
helpful to understand potential manufacturing challenges.&lt;br /&gt;
&lt;br /&gt;
1. Launch Mercury by clicking its icon. In the Structure Navigator toolbar,&lt;br /&gt;
type UREAXX to bring up the structure for urea.&lt;br /&gt;
&lt;br /&gt;
2. Click on the CSD-Particle menu, select Morphology, then select VisualHabit…&lt;br /&gt;
3. In the VisualHabit dialogue box, you will see several options. On the left, you&lt;br /&gt;
will find options to change the calculation settings, such as which forcefield&lt;br /&gt;
is used and the limiting radius for the calculation. You can also choose&lt;br /&gt;
whether to add an electrostatic correction or not. On the right you will see&lt;br /&gt;
where the lattice energy results will appear once the calculation is complete.&lt;br /&gt;
For the purposes of this tutorial, we will keep the default options. These&lt;br /&gt;
typically work well for most situations, but if you know you are looking at&lt;br /&gt;
specific chemistry or a charged system, you may want to change these&lt;br /&gt;
settings.&lt;br /&gt;
4. Click the Calculate button to start.&lt;br /&gt;
5. The dialogue box will now update to show the results of the VisualHabit&lt;br /&gt;
calculation. The lattice energy results are shown in the section on the right in&lt;br /&gt;
kJ mol-1&lt;br /&gt;
. From here, you can see the total lattice energy as well as the&lt;br /&gt;
contributions from the electrostatic, van der Waals, and hydrogen bonding&lt;br /&gt;
energy terms. It’s clear from these results that the lattice energy for urea is&lt;br /&gt;
dominated by the hydrogen bonding energy in the crystal structure.&lt;br /&gt;
6. The convergence chart shows how the lattice energy changes over the course&lt;br /&gt;
of the calculation out to the limiting radius and gives an indication of whether&lt;br /&gt;
the calculation has converged successfully (indicated by the green tick at the&lt;br /&gt;
bottom of the chart). This chart tells us that the lattice energy comes close to&lt;br /&gt;
its final value in a small distance for this structure. Urea is a small molecule,&lt;br /&gt;
so this is what we would expect to see.&lt;br /&gt;
7. If we look at the Mercury visualizer, we will see that the calculated&lt;br /&gt;
morphology for urea is now shown. VisualHabit calculates an elongated&lt;br /&gt;
morphology for urea where the long axis is aligned to the polar axis of the&lt;br /&gt;
urea molecule.&lt;br /&gt;
8. We will now explore the reasons for this elongated shape by examining the&lt;br /&gt;
nature of the intermolecular interactions, or synthons, in more detail. Click&lt;br /&gt;
on the Synthons tab in the VisualHabit dialogue to change the information&lt;br /&gt;
that is shown.&lt;br /&gt;
9. The synthons that contribute to the lattice energy, along with the centroid-centroid &lt;br /&gt;
distance and component energy terms, are now shown. Click on the&lt;br /&gt;
Interaction Energy header (you may need to scroll along to see it) to sort this&lt;br /&gt;
column from the strongest interaction to the weakest. Once again, you will&lt;br /&gt;
see that the lattice energy for urea is dominated by a small number of strong&lt;br /&gt;
hydrogen bonding interactions.&lt;br /&gt;
10. Now let’s look at the two most important interactions. Click on one of the&lt;br /&gt;
rows in the table to highlight that interaction and show the synthon in the&lt;br /&gt;
Mercury visualizer. You can select multiple rows by holding down Ctrl and&lt;br /&gt;
clicking on the rows of interest. Holding down Shift and clicking will let you select&lt;br /&gt;
multiple rows at once. Select the top two interactions for UREAXX&lt;br /&gt;
(synthons 8 and 9).&lt;br /&gt;
11. You will see in the Mercury visualizer that two other urea molecules have&lt;br /&gt;
appeared above and below the central molecule. The red dashed lines&lt;br /&gt;
between the molecules highlight the synthon, and the value beside the line&lt;br /&gt;
shows the interaction energy. You can clearly see that the strongest&lt;br /&gt;
interaction in urea aligns with the fastest growth direction.&lt;br /&gt;
12. Click the Visualiser tab in the VisualHabit dialogue. From this tab you can&lt;br /&gt;
change the way that the morphology is displayed in Mercury, such as&lt;br /&gt;
changing the colour of the faces and the edges. You can also change how&lt;br /&gt;
synthons are displayed.&lt;br /&gt;
13. Click the radio dial in the Synthons section to display Distance rather than&lt;br /&gt;
Energy.&lt;br /&gt;
14. The Mercury visualizer will update to show the centroid-centroid distance of&lt;br /&gt;
the synthons in Å. These short, strong types of hydrogen bonds in the crystal&lt;br /&gt;
structure of urea are key to understanding its growth and the shape of its&lt;br /&gt;
crystals.&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
Crystal shape is governed by the relative growth rates in different directions.&lt;br /&gt;
Strong intermolecular interactions, or synthons, in one direction can result in&lt;br /&gt;
elongated morphologies. The crystal structure of urea is dominated by strong&lt;br /&gt;
hydrogen bonding interactions that occur in tapes that propagate along the&lt;br /&gt;
crystallographic c-axis. This results in an elongated morphology for urea.&lt;br /&gt;
&lt;br /&gt;
You should now know how to calculate a morphology using VisualHabit for a&lt;br /&gt;
CSD structure in Mercury and how to visualize and explore the key interactions&lt;br /&gt;
in that structure relative to the calculated crystal shape.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15408</id>
		<title>Particle Shape Calculator for CCDC/Mercury</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Particle_Shape_Calculator_for_CCDC/Mercury&amp;diff=15408"/>
		<updated>2023-05-23T21:20:46Z</updated>

		<summary type="html">&lt;p&gt;Mtsukanov: /* VisualHabit */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This tutorial will introduce you to the morphology calculation features included&lt;br /&gt;
with Mercury under the CSD-Particle toolset, namely BFDH Morphology and&lt;br /&gt;
VisualHabit.&lt;br /&gt;
BFDH crystal morphology is an approximation based on crystallographic&lt;br /&gt;
geometrical considerations. For a given structure, the BFDH algorithm will predict&lt;br /&gt;
the habit or shape of a crystal using the corresponding unit cell and symmetry&lt;br /&gt;
operator information.&lt;br /&gt;
The VisualHabit tool calculates a morphology for your material based on its&lt;br /&gt;
crystal structure. Using a range of forcefields, we can calculate the intermolecular&lt;br /&gt;
interactions, or synthons, in a crystal structure; the sum of these gives the lattice&lt;br /&gt;
energy for that system. From these lattice energies, we can calculate slice energies&lt;br /&gt;
and, consequently, the attachment energy for each slice. Crystal growth rates&lt;br /&gt;
assumed to be proportional to these attachment energies and can be used to&lt;br /&gt;
predict crystal shapes. The VisualHabit tool is used to calculate and analyze these&lt;br /&gt;
energies and to visualize the resulting morphologies, an instrumental step in&lt;br /&gt;
enabling solid form and particle design for small molecule crystal structures&lt;br /&gt;
&lt;br /&gt;
==BFDH==&lt;br /&gt;
1. Open Mercury by double-clicking the Mercury icon on the desktop.&lt;br /&gt;
2. In the Structure Navigator toolbar type the refcode KAXXAI10.&lt;br /&gt;
3. We want to identify facets of interest in this morphology. We will first create&lt;br /&gt;
the morphology using the BFDH morphology feature.&lt;br /&gt;
4. From the top-level menu select CSD-Particle &amp;gt; Morphology &amp;gt; BFDH… to&lt;br /&gt;
generate the morphology. BFDH morphology uses the unit cell to create the&lt;br /&gt;
morphology you see, therefore it does not account for the chemistry of the&lt;br /&gt;
structure.&lt;br /&gt;
5. Rotate the structure to view the various facets that have been generated. If&lt;br /&gt;
you wish, explore options in the Morphology window.&lt;br /&gt;
6. In the following exercises you may decide to calculate the BFDH morphology&lt;br /&gt;
to compare the results.&lt;br /&gt;
7. The morphology can be modified, for example, if you want to represent a&lt;br /&gt;
crystal observed from growth experiments. In the Morphology window, click&lt;br /&gt;
Save… and place the .cif file in a folder where you have permission.&lt;br /&gt;
8. Using a text editor of your choice open the morphology .cif file. You will see&lt;br /&gt;
the data that corresponds to the HKLs and perpendicular distances. You can&lt;br /&gt;
modify these values to change the morphology. For the sake of example, we will&lt;br /&gt;
simply switch the values of some of the perpendicular distances. Note that&lt;br /&gt;
these changes are not based on experimental observation&lt;br /&gt;
9. Back in Mercury, In the Morphology window click Open… and select your&lt;br /&gt;
modified .cif file to visualize your new morphology&lt;br /&gt;
&lt;br /&gt;
==VisualHabit==&lt;br /&gt;
&lt;br /&gt;
The shape of a crystal results from the relative growth rates in different&lt;br /&gt;
directions. Strong intermolecular interactions, or synthons, in one direction, can&lt;br /&gt;
result in elongated crystal shapes like needles forming. Needle-shaped crystals&lt;br /&gt;
are common in pharmaceuticals and are undesirable due to their poor processing&lt;br /&gt;
characteristics. Being able to predict needle formation from a crystal structure is&lt;br /&gt;
helpful to understand potential manufacturing challenges.&lt;br /&gt;
&lt;br /&gt;
1. Launch Mercury by clicking its icon. In the Structure Navigator toolbar,&lt;br /&gt;
type UREAXX to bring up the structure for urea.&lt;br /&gt;
&lt;br /&gt;
2. Click on the CSD-Particle menu, select Morphology, then select VisualHabit…&lt;br /&gt;
3. In the VisualHabit dialogue box, you will see several options. On the left, you&lt;br /&gt;
will find options to change the calculation settings, such as which forcefield&lt;br /&gt;
is used and the limiting radius for the calculation. You can also choose&lt;br /&gt;
whether to add an electrostatic correction or not. On the right you will see&lt;br /&gt;
where the lattice energy results will appear once the calculation is complete.&lt;br /&gt;
For the purposes of this tutorial, we will keep the default options. These&lt;br /&gt;
typically work well for most situations, but if you know you are looking at&lt;br /&gt;
specific chemistry or a charged system, you may want to change these&lt;br /&gt;
settings.&lt;br /&gt;
4. Click the Calculate button to start.&lt;br /&gt;
5. The dialogue box will now update to show the results of the VisualHabit&lt;br /&gt;
calculation. The lattice energy results are shown in the section on the right in&lt;br /&gt;
kJ mol-1&lt;br /&gt;
. From here, you can see the total lattice energy as well as the&lt;br /&gt;
contributions from the electrostatic, van der Waals, and hydrogen bonding&lt;br /&gt;
energy terms. It’s clear from these results that the lattice energy for urea is&lt;br /&gt;
dominated by the hydrogen bonding energy in the crystal structure.&lt;br /&gt;
6. The convergence chart shows how the lattice energy changes over the course&lt;br /&gt;
of the calculation out to the limiting radius and gives an indication of whether&lt;br /&gt;
the calculation has converged successfully (indicated by the green tick at the&lt;br /&gt;
bottom of the chart). This chart tells us that the lattice energy comes close to&lt;br /&gt;
its final value in a small distance for this structure. Urea is a small molecule,&lt;br /&gt;
so this is what we would expect to see.&lt;br /&gt;
7. If we look at the Mercury visualizer, we will see that the calculated&lt;br /&gt;
morphology for urea is now shown. VisualHabit calculates an elongated&lt;br /&gt;
morphology for urea where the long axis is aligned to the polar axis of the&lt;br /&gt;
urea molecule.&lt;br /&gt;
8. We will now explore the reasons for this elongated shape by examining the&lt;br /&gt;
nature of the intermolecular interactions, or synthons, in more detail. Click&lt;br /&gt;
on the Synthons tab in the VisualHabit dialogue to change the information&lt;br /&gt;
that is shown.&lt;br /&gt;
9. The synthons that contribute to the lattice energy, along with the centroid-centroid &lt;br /&gt;
distance and component energy terms, are now shown. Click on the&lt;br /&gt;
Interaction Energy header (you may need to scroll along to see it) to sort this&lt;br /&gt;
column from the strongest interaction to the weakest. Once again, you will&lt;br /&gt;
see that the lattice energy for urea is dominated by a small number of strong&lt;br /&gt;
hydrogen bonding interactions.&lt;br /&gt;
10. Now let’s look at the two most important interactions. Click on one of the&lt;br /&gt;
rows in the table to highlight that interaction and show the synthon in the&lt;br /&gt;
Mercury visualizer. You can select multiple rows by holding down Ctrl and&lt;br /&gt;
clicking on the rows of interest. Holding down Shift and clicking will let you select&lt;br /&gt;
multiple rows at once. Select the top two interactions for UREAXX&lt;br /&gt;
(synthons 8 and 9).&lt;br /&gt;
11. You will see in the Mercury visualizer that two other urea molecules have&lt;br /&gt;
appeared above and below the central molecule. The red dashed lines&lt;br /&gt;
between the molecules highlight the synthon, and the value beside the line&lt;br /&gt;
shows the interaction energy. You can clearly see that the strongest&lt;br /&gt;
interaction in urea aligns with the fastest growth direction.&lt;br /&gt;
12. Click the Visualiser tab in the VisualHabit dialogue. From this tab you can&lt;br /&gt;
change the way that the morphology is displayed in Mercury, such as&lt;br /&gt;
changing the colour of the faces and the edges. You can also change how&lt;br /&gt;
synthons are displayed.&lt;br /&gt;
13. Click the radio dial in the Synthons section to display Distance rather than&lt;br /&gt;
Energy.&lt;br /&gt;
14. The Mercury visualizer will update to show the centroid-centroid distance of&lt;br /&gt;
the synthons in Å. These short, strong types of hydrogen bonds in the crystal&lt;br /&gt;
structure of urea are key to understanding its growth and the shape of its&lt;br /&gt;
crystals.&lt;br /&gt;
&lt;br /&gt;
==Conclusion==&lt;br /&gt;
Crystal shape is governed by the relative growth rates in different directions.&lt;br /&gt;
Strong intermolecular interactions, or synthons, in one direction can result in&lt;br /&gt;
elongated morphologies. The crystal structure of urea is dominated by strong&lt;br /&gt;
hydrogen bonding interactions that occur in tapes that propagate along the&lt;br /&gt;
crystallographic c-axis. This results in an elongated morphology for urea.&lt;br /&gt;
&lt;br /&gt;
You should now know how to calculate a morphology using VisualHabit for a&lt;br /&gt;
CSD structure in Mercury and how to visualize and explore the key interactions&lt;br /&gt;
in that structure relative to the calculated crystal shape.&lt;/div&gt;</summary>
		<author><name>Mtsukanov</name></author>
	</entry>
</feed>