|
Size: 3310
Comment:
|
Size: 3575
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| {{attachment:emen2logo.png|EMEN2|width=250}} | {{attachment:emen2logo.png|EMEN2|width="250"}} |
| Line 3: | Line 3: |
| == EMEN2 == |
= EMEN2 = |
| Line 7: | Line 6: |
| Please note, this is NOT the related [[EMAN2]] image processing system. | Structural and computational biologists frequently work with complex data sets assembled from diverse experimental sources, public resources, and analysis methods. Archiving and mining these data sets with their complicated interrelationships remains a persistent challenge, particularly with “open science” initiatives to make entire workflows, including all raw and intermediate data, available with publications. |
| Line 9: | Line 8: |
| Structural and computational biologists frequently work with complex data sets assembled from diverse experimental sources, public resources, and analysis methods. Archiving and mining these data sets with their complicated interrelationships remains a persistent challenge, particularly with “open science” initiatives to make entire workflows, including all raw and intermediate data, available with publications. To address these needs, we have developed EMEN2, an object-oriented scientific database and electronic notebook. EMEN2 uses a flexible schema based on plain text descriptions of experimental protocols. These protocols may be local and describe techniques and data within a single lab group, reference published ontologies (e.g. GO, NCBO BioPortal), or contain links to external resources (PDB, GenBank, etc.). Similarly, an EMEN2 installation can itself act as a resource, providing public access to selected protocols and data. While originally developed to serve the needs of the cryo-EM community, we believe EMEN2’s architecture provides an excellent foundation for many other scientific endeavors. |
To address these needs, we have developed EMEN2, an object-oriented scientific database and electronic notebook. EMEN2 uses a flexible schema based on plain text descriptions of experimental protocols. These protocols may be local and describe techniques and data within a single lab group. An EMEN2 installation can itself act as a resource, providing public access to selected protocols and data. While originally developed to serve the needs of the cryo-EM community, we believe EMEN2’s architecture provides an excellent foundation for many other scientific endeavors. |
| Line 15: | Line 12: |
| A full ontology for cryo-EM has been established for internal use and has been in active use at the NCMI for ~3 years. It is used to archive all data at the center, and currently provides services for over 750 users, with over 16 terabytes of data in 460,000 records. As an example of its extensibility and ontology mapping capabilities, we have developed a module for harvesting the database and producing PDB compliant XML files which can be used to seed a structure deposition to EMDatabank.org. |
You can read about EMEN2 in the manuscript: |
| Line 18: | Line 14: |
| [[http://www.ncbi.nlm.nih.gov/pubmed/23360752|Rees, I., Langley, E., Chiu, W., & Ludtke, S.J. (2013). EMEN2: an object oriented database and electronic lab notebook. Microsc Microanal 19, 1-10]] Please note, this is '''not''' the related [[EMAN2]] image processing system. == EMEN2 Mailing List == * [[http://groups.google.com/group/emen2|EMEN2 mailing list]] Please feel free to join the mailing list and ask questions, submit bug reports, or share results. |
|
| Line 20: | Line 24: |
| Line 23: | Line 26: |
| http://ncmi.bcm.edu/publicdata/db/home/ | * http://ncmi.bcm.edu/publicdata/ |
| Line 28: | Line 31: |
| * [[http://pypi.python.org/pypi/emen2|EMEN2 download]] | |
| Line 29: | Line 33: |
| * [[EMEN2/Dependencies|Dependencies]] | * [[EMEN2/Dependencies|Dependencies]] |
| Line 31: | Line 35: |
| * [[EMEN2/Install|Installation]] | * [[EMEN2/Install|Installation]] |
| Line 33: | Line 37: |
| * [[EMEN2/Startup|Starting EMEN2 server at boot]] | * The [[EMEN2/emen2ctl|EMEN2 control script (emen2ctl)]] and [[EMEN2/Startup|starting the server at boot]] * [[EMEN2/Hardware|Planning hardware requirements]] == EMEN2 Guides == * [[EMEN2/Public_Data_Server|Basic EMEN2 overview]] * [[EMEN2/Backups|Backups and recovery]] == EMEN2 API == * [[EMEN2/api|Public API documentation]] * [[EMEN2/rpc|Remote API access]] * [[EMEN2/Extensions|Writing EMEN2 extensions]] |
| Line 36: | Line 54: |
| * [[http://pypi.python.org/pypi/emdash|EMDash download]] | |
| Line 37: | Line 56: |
| * [[EMEN2/emdash/Install|Install EMDash]] | * [[EMEN2/emdash/Install|EMDash installation]] |
| Line 39: | Line 58: |
| * [[EMEN2/emdash/Tutorial|EMDash tutorial]] * [[EMEN2/emdash|EMDash microscope client]] |
* [[EMEN2/emdash/Tutorial|EMDash tutorial]] |
EMEN2
An extesible, object-oriented electronic lab notebook
Structural and computational biologists frequently work with complex data sets assembled from diverse experimental sources, public resources, and analysis methods. Archiving and mining these data sets with their complicated interrelationships remains a persistent challenge, particularly with “open science” initiatives to make entire workflows, including all raw and intermediate data, available with publications.
To address these needs, we have developed EMEN2, an object-oriented scientific database and electronic notebook. EMEN2 uses a flexible schema based on plain text descriptions of experimental protocols. These protocols may be local and describe techniques and data within a single lab group. An EMEN2 installation can itself act as a resource, providing public access to selected protocols and data. While originally developed to serve the needs of the cryo-EM community, we believe EMEN2’s architecture provides an excellent foundation for many other scientific endeavors.
EMEN2 is developed using all open-source technologies. The core database is written in the Python programming language, with BerkeleyDB providing a robust embedded database back-end. The infrastructure is highly modular, permitting new ontologies to be fully implemented using only it’s “Web 2.0” interface. In addition, there is a remote API available for client applications. The included EMDash program is a standalone GUI tool for equipment integration, currently used to upload data transparently from our electron microscopes as it is being collected, as well as integrate with other lab equipment. The EMEN2 server itself can be extended in a similar way by writing custom Python modules, which can expose additional views to the Web interface, or new methods to the API.
You can read about EMEN2 in the manuscript:
Please note, this is not the related EMAN2 image processing system.
EMEN2 Mailing List
Please feel free to join the mailing list and ask questions, submit bug reports, or share results.
EMEN2 Demo
There is a publicly accessible, read-only EMEN2 installation for accessing the NCMI's public datasets:
An overview document has been created to introduce new users to the EMEN2 web interface. It includes a number of screenshots.
EMEN2 Installation and Configuration
EMEN2 Guides
EMEN2 API