IMP logo
IMP Manual  for IMP version 2.8.0
Related Pages
Here is a list of all related documentation pages:
[detail level 12]
oAutomated builds and checks
oApplying %IMP to a new biological system
oBug reports
oBuilding
oRuntime checks
oClose pairs lists
oCMake configuration options
oUsing command line tools
oCNMultiFit: solution of symmetric complexes using a cryo-EM density map
oCoding conventions
oContributing code back to IMP
oContributing to %IMP
oConventions
oCode coverage
oCross platform compatibility
oDependencies
oDeprecation
oDesign of %IMP
oDesign example
oDeveloping the %IMP source code
oDeveloper setup
oDirectory structure
oDocumenting your code
oEigen
oEMageFit: solution of a complex structure using subunit structures and EM class averages
oEvaluation
oAdding external dependencies
oFrequently asked questions (FAQ)
oFoXS: fitting structures against SAXS data
oGlossary
oGood programming practices
o%IMP gotchas
oIntegrative docking: combining experimental data with computational pairwise docking
oBuilding from source code on Windows
oInstallation
oInternals
oIntroduction to integrative modeling
oConformational sampling: sampling antibody conformations using the rapidly exploring random tree (RRT) algorithm
oExample of using the library
oThe %IMP C++/Python library
oOverview
oCopyright and licenses
oLogging
oMultiFoXS: determination of multi-state models
oMultiFit: solution of a complex structure using subunit structures and a cryo-EM density map
oWriting new code
oOpenMP
oParallelization
oProfiling your code
oPublications
oRMF
oModeling of complexes using IMP::pmi
|oStage 1 - Gathering of data
|oStage 2 - Representation of subunits and translation of the data into spatial restraints
|oStage 3 - Sampling
|oStage 4 - Analysis Part 1
|\Stage 4 - Analysis Part 2
oSAXSMerge: merging multiple SAXS profiles
oWorking with source control
ogit submodules and subtrees
oSupporting your code
oExporting C++ code to Python
oDebugging and testing your code
oUnits
oChimera tools and web services
oWriting examples
oTools for developers
\ChangeLog