During an identification session with an interactive key, Lucid allows you to choose any character (i.e., a feature and its associated states) from the Features Available list at any time. However, "stepping" through the key in a structured and sensible way will make your task of identification more efficient. Below are recommendations for increasing your efficiency and decreasing the amount of time required for identifying an unknown specimen using Lucid Player.
The Lucid Player is designed so that, as you choose states, the entities left in Entities Remaining are ordered so that the entities that best match the chosen states are at the top. Note that this ordering will ONLY HAPPEN if you choose Lists at the bottom of the Entities Discarded panel. This ordering will NOT happen if you are viewing the default of Trees.
First, become familiar with the characteristics of the specimen you wish to identify. If you are also familiar with the Lucid key that you will use, then you may already know many of the specimen's characteristics. Briefly reviewing these characteristics before you start will make it easier for you to proceed through the identification.
In any key, some entities may possess particularly distinctive features and/or states. Use of these may allow the entity to be keyed out in a very few steps. At the very least, starting with any particularly distinctive or striking features your specimen may possess for the first features you select may quickly reduce the list of Entities Remaining.
Browse the list of Features Available and address easy features first. The principles of dichotomous keys, in which the couplets must be answered in a preset order, are very familiar to most key users who often automatically apply these principles to a matrix key. Although Lucid3 lists the features of a key in an initial sequence in the opening window, this does not mean that the features must be selected in that order. You can select any feature from any position in the list. (Note that in some keys, where positive dependencies are used, you may be forced to answer specific questions [features] before others become available.)
Most Lucid3 keys will have a wide variety of features, ranging from those dealing with obvious and simple features to those dealing with features that are minute, obscure, or difficult to interpret. Always start by browsing the list of Features Available for obvious features that you can quite quickly answer, rather than first choosing a difficult feature and potentially getting stuck. Lucid software is designed to overcome problems associated with difficult and obscure features.
In looking through the features, you may not be sure which state of a feature to choose, or a feature or state may not be clear on your specimen. Skipping the feature entirely in such cases is always an option.
As you work through the list of Features Available, you may find some features or feature states that you do not understand. If so, review any explanatory notes and illustrations that may be associated with the features and states. In fact, it is a good idea to check the notes and illustrations before using any feature for the first time, and to become familiar with these for all the features.
You can always choose multiple states (more than one state of a feature) if you are uncertain which state is the correct one to choose for a particular specimen. Lucid software is designed to allow you to choose as many states as you require from any one feature (if, for example, your specimen is in between two states, or exhibits two or more states). Within the program's logic, these states will be connected by an "or" link. This will cause Lucid to search for all entities with any of the states you select. As a general rule, if you are unsure which of two or more states your specimen has, then choose them all. That way, you can be sure that your target entity will remain in Entities Remaining. (Note that in the Lucid3 Player users can choose the matching method option of "all states" rather than the usual default of "any states". See Help for more information.)
When you have dealt with all the obvious features, use Lucid's "Best" function to suggest the best remaining feature that will give you the most efficient next step. The Best algorithm will assess which of the remaining features and states available will best reduce the list of Entities Remaining. The Lucid Player has two "Best" modes: "Find Best" and "Sort Best."
Find Best - In the Lucid3 Player, clicking the Find Best Feature button will cause the Player to move to and open the best available feature. Find Next Best Feature and Find Previous Best Feature buttons on the toolbar allow navigation through the Features list, if you have difficulty addressing the first feature nominated. If the list of entities in Entities Remaining changes after choosing a feature as suggested by Best, you should click the Find Best Feature button again to recalculate the next best feature to address.
Sort Best - Sort Best will reorder the Features Available list so that features are sorted from best to worst. After a Sort Best, scan the top of the list for features that you can answer most easily. (Note that Sort Best only works using List View, as a tree representation of features cannot be sorted.)
You may find other Lucid3 tools helpful while navigating feature choices, such as "Shortcuts," "Prune Redundant Features," and "Differences." Explanations about how to use these functions are available through the Lucid Help menu.
This will happen sooner or later in one of your Lucid sessions. If no entities are listed in the Entities Remaining window, then it simply means that no entities in the database match the selection of states you have made. Several explanations are possible, but some of the most common are:
Whichever of the above situations is suspected, you must very carefully review your chosen features and determine which ones you are uncertain about. Try unselecting uncertain states one by one to see what effect each has. One or more entities may move back into the Entities Remaining window. In difficult cases, you may need to "play" with the key, adding or deleting states progressively to try to find the best matching entity.
Never assume that you will always end up with one entity remaining; some entities in the key may be very hard to differentiate. Sometimes, after you have addressed all the features, you may have a short list of entities remaining instead of just one entity. You are still much closer to an identification than you otherwise would have been. You may then have to carefully check your specimen against associated information (descriptions, images, etc. for the remaining entities) or refer to more advanced or specialist reference sources.
In some cases, if you have a short list of entities remaining, but have not addressed all the features, it may be easier to check your specimen against information associated with these remaining entities. This can sometimes be a faster way to make an identification, than trying to find a feature that will discriminate among the remaining entities.
If your entity does not look similar to any of the entities remaining, you can use the same strategy described above, of unselecting states one by one, or "playing" with the key, to find the best matching entity.
Once you have made a preliminary identification, check the other information (such as notes, descriptions or images) provided for the entity. Getting a possible name for an entity from a key is not the end of an identification. You may have made errors, or your specimen may be an entity that is not in the key. In these cases, the key may have provided you with the wrong name. The associated information will often give you a good indication as to whether the answer is correct.
CPHST's Identification Technology Team Document (Release
1 - May 25, 2006)
Site last modified: February 4, 2011