-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Haddock3 online user manual #677
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's start! Nice.
I would also add sections about:
May-be as part of a general section about restraints in HADDOCK3 and this is also where the haddock-restraints part should be residing |
Question about flexibility options. It is about explaining how to make molecule/part of molecule flexible/semi-flexible in haddokc3, only practical things, right? |
In my opinion, it is more about explaining how to make molecules/segments flexible/semi-flexible. |
Basic instructions on how to define fully and semi-flexible segments + an example of each.
Co-authored-by: Raphaelle Versini <[email protected]>
Paratope correction Made by Marco !
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Victor Reys <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
Co-authored-by: Raphaelle Versini <[email protected]>
#### Using Molecular Dynamics for generating multiple conformations | ||
|
||
Proteins are not rock-solid and HADDOCK can handle flexibility of the interface to a certain extent. | ||
An elegant way how to account for larger conformational changes is ensemble docking of conformations generated by Molecular Dynamics (MD). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An elegant way how to account for larger conformational changes is ensemble docking of conformations generated by Molecular Dynamics (MD). | |
Ensemble docking of conformations generated by molecular dynamics (MD) is an elegant way to account for larger conformational changes. |
@@ -0,0 +1,127 @@ | |||
# Clustering methods implemented in Haddock3 | |||
|
|||
The clustering of conformations and complexes is a key step in most of the workflows, as it allows us to observe convergence, redundancies, or even remove noise coming from singlotons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The clustering of conformations and complexes is a key step in most of the workflows, as it allows us to observe convergence, redundancies, or even remove noise coming from singlotons. | |
Clustering of conformations and complexes is a key step in most workflows, as it allows us to observe convergence, redundancies, or even remove noise from singletons. |
- [`[rmsdmatrix]`](../modules/analysis.md#rmsdmatrix-module): Calculates of the RMSD matrix between all the models generated in the previous step. | ||
- [`[ilrmsdmatrix]`](../modules/analysis.md#ilrmsdmatrix-module): Calculates the Interface Ligand Root Mean Square Deviation (ILRMSD) matrix. | ||
|
||
Those two modules must be followed by the `[clustrmsd]` module, otherwise, only the pair-wise RMSD matrix will be computed, and clustering not performed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those two modules must be followed by the `[clustrmsd]` module, otherwise, only the pair-wise RMSD matrix will be computed, and clustering not performed. | |
Those two modules must be followed by the `[clustrmsd]` module; otherwise, only the pair-wise RMSD matrix will be computed, and clustering will not be performed. |
|
||
Full documentation about `[rmsdmatrix]` module is accessible [here](../modules/analysis.md#rmsdmatrix-module). | ||
|
||
### [ilrmsdmatrix] module |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a module created for ligands/small molecules and protein/receptor complex ? If so, I would say that it would be interesting to just add a sentence to introduce a general idea as to which cases it is most appropriate to use.
|
||
Clustering by Fraction of Comon Contacts does not rely on rotation and translations but simply on the analysis of contacts. | ||
This is therefore much faster. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a sentence about the most important parameters of clusfcc ? Since the other modules get a quick description, it would make sense to at least describe 'clust_cutoff' imo.
|
||
<hr> | ||
|
||
## RMSD clustering |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add somewhere here which units are used for the cutoffs/rmsd values outputed ? i know it's Angstrom but not every software uses Angstrom themselves, so it would be nice to have it written in my opinion.
</style> | ||
|
||
|
||
|<font size="4" color="#203A98">Parameter</font>|<font size="4" color="#203A98">run.cns name</font>| <font size="4" color="#203A98">default value</font>|<font size="4" color="#203A98">optimal value</font> | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the parameter column, shoud we add the name of the modules in haddock3 ? (especially for the MD steps, as new users might not know immediatelly which module we refer to)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file should be updated, it sill displays the haddock2.4 parameter names.
|
||
<img src="./interface.png" align="right" > | ||
|
||
#### 1.) Information about the interface is available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 1.) Information about the interface is available | |
### 1.) Information about the interface is available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am removing one # because of line 111
Co-authored-by: Raphaelle Versini <[email protected]>
Pull request related to the haddock3 user manual.
Contribute to the book
The book source code is located in
software/haddock3/src/
.From here, consider only relative paths for things to be functional.
Compile the book
This manual is ment to be compiled by
mdbook
.To generate it, mdbook must be installed (see how to install mdbook).
Then run the following command, once in the
software/haddock3/
directory:mdbook build haddock3-manual --dest-dir ../manual # or /Applications/mdbook build haddock3-manual --dest-dir ../manual
Summary
note: Check when reviewed
mdbook