Protege setup for GO Eds
Protege setup for GO
Which Protege version:
Currently we are using Protege 5.1.0. Get this from protege.stanford.edu
Although older versions of Protege required a manual adjustment of memory, Protege 5.1.0 appears to handle regular GO editing tasks fine installed out of the box.
The info.plist file now has an Xss option which specifies the stack size. It was increased from the default to support reasoning with some particular biomedical ontologies (see https://github.com/protegeproject/protege/issues/457).
Protege needs at least 4G of RAM to cope with the GO. This is set by specifying the following -Xmx argument for the java. E.g. for 6G, specify -Xmx6000M. How to set this varies with the OS and Protege version. If launching from ./run.command, edit run.command to jre/bin/java -Xmx6000M. If running from Protege_n.app on a mac, you need to find and edit the -Xmx entry in an XML file called info.plist under Protege_n.app/.
Protege has a highly configurable layout and a plugin architecture. You can control which components are visible from the window menu. Selecting something from the view menu allows you to create a new subwindow in a tab with the component of your choice - just move the target icon to the location you want and click.
As many plugins come with the standard download, the default layout may be intimidating, but can easily be simplified: The following tabs are sufficient for GO work:
You'll have to create the OBO graph tab yourself. (see below, as part of the Installing Plugins section)
The following plugins should be installed from the Protégé menus: File>Check for plugins>
Search Annotations –search for terms and displays the list of matching results
This directory structure for P5 is Protege-5.1.0.app/Contents/Java/plugins/. To see the directory structure so that you can drag and drop files, you'll need to control-click/right click on the app icon, then select 'Show Package Contents' and drill down to the directory you want. Note there are two plugins folders. Make sure you use the correct one.
(In P5, the latest ELK can be found using File>Check for Plugins)
ELK OWL reasoner Make sure you choose a version appropriate to your Protege version.
(In P5, the OBO Annotation plugin can be found using File>Check for Plugins) Have this view show up by going to the Entities tab, selecting Window>Views>OBO Views>OBO Annotation. Drag the black circle that appears to the area where you want it and click. The panel will appear.
OBO Annotation – add and edit terms more easily
NEED TO CHECK THIS AT WORKSHOP
OBO Graph View Component – For all you hairball fans - this plugin displays an OBO-style connected graph of classification (is_a) and other relationship types. (Be careful what you wish for).
To make this a tab:
- Window > Create New Tab
- Window > Views > Ontology Views > OBO Graph View Component
- Take the black circle, put into the Tab you just created and click within it.
Obsoletion plugin - Once installed, you should see an "obsolete" option in your Edit menu. NEED TO CHECK THIS AT THE WORKSHOP
Setting ID range
Protege>Preferences>New Entities Tab
Click on Preferences under the main menu to get this window.
WARNING: The ID generator in Protege doesn't overwrite existing IRIs, but it can't cope with the OBO alt_id system - where losing IDs following a merge are stored in annotation properties This system is problematic for OWL translations as it leads to the loss or IRIs. Without IRIs, this ID generator doesn't know about the IDs and will stomp on them if they fall in the specified ID range. Until this is fixed,
We plan to move to a system in which obsolete classes with these IRIs are created for all alt_ids on OBO to OWL translation.
Setting username and auto-adding creation date
Broken in 5.0 See: https://github.com/protegeproject/protege/issues/283#issuecomment-177656593 Seems to work in 5.1
(The default settings may be fine, but details are included for reference)
Protege allows users to set the annotation property to be used for rendering OWL entities (classes, object properties, annotation properties, individuals) in graphs, trees and text etc. This should be set to rdfs:label, as follows:
Background on rendering. All entities in OWL are identified by an IRI. This includes annotation properties such as label. In the absence of an annotation to annotation property specified as suitable for rendering, the short form of this IRI (the bit following a '#' or a '/') is used.