|
Size: 1342
Comment:
|
Size: 1762
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| * [[EMAN2DevFAQ|EMAN2 developer's FAQ]] * [[Eman2ProgQuickstart|EMAN2 programming quickstart]] |
* [[EMAN2PythonStyleGuide|EMAN2 Python Programming Style Guide]] * [[Eman2ProgQuickstart|EMAN2 python programming quickstart]] * [[Eman2CProgQuickstart|EMAN2 C++ programming quickstart]] |
| Line 12: | Line 13: |
| * [[EMAN2ImageFormats|Image Formats in EMAN2]] * [[Eman2PythonDoc|Documentation for the EMAN2 Python code]] |
|
| Line 17: | Line 20: |
==== Extend EMAN2's functionality by adding new algorithms or linking to external software ==== * [[Eman2ProgOverview|How to add new capabilities to EMAN2]] {{attachment:sphere_cylinder_dist_grey_c.png}} |
Documentation for Python or C++ Programmers
Parameters/Metadata for applications, not associated with a specific image, stored in bdb:project
Autogenerated Python/C++ Documentation (Doxygen)
- There are a LOT of classes in the automatic docs. Basic images are represented by the EMData class
- The EMData methods process, cmp, align, and project are modular methods with many available functions. Use dump_processors(), dump_cmps(), etc.
- There are a few classes like analyzers and reconstructors which are not methods of EMData
- Many utility functions are static members of EMUtil
Extend EMAN2's functionality by adding new algorithms or linking to external software
