User Tools

Site Tools


other:amass:documentation:identification_using_links

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
other:amass:documentation:identification_using_links [2024/07/12 13:54] – created sgrangerother:amass:documentation:identification_using_links [2024/07/17 15:44] (current) – created sgranger
Line 1: Line 1:
-====== Identification_Using_Links_ ======+====== Identification Using Links  ======
  
 ==== Introduction ==== ==== Introduction ====
Line 38: Line 38:
 This section briefly describes the buttons in the **command area** that are used to identify segments using link information. This section briefly describes the buttons in the **command area** that are used to identify segments using link information.
  
-{{id_buttons.jpg}}+{{:id_buttons.jpg}}
  
   * ****ID frame**** This button __switches to a mode__ whereby each frame selected by the frame cursor is processed to compute segment identifications using the current link information. Each frame is treated independently of all other frames but all UIDs are preserved, i.e. the CIDs from any previous computation are first cleared. All resulting CIDs are shown in green.   * ****ID frame**** This button __switches to a mode__ whereby each frame selected by the frame cursor is processed to compute segment identifications using the current link information. Each frame is treated independently of all other frames but all UIDs are preserved, i.e. the CIDs from any previous computation are first cleared. All resulting CIDs are shown in green.
Line 54: Line 54:
 The **LINKS** mode button enables/disables alteration of the link data, and must be enabled if you wish to modify the link data that is currently resident in program memory. The **LINKS** mode button enables/disables alteration of the link data, and must be enabled if you wish to modify the link data that is currently resident in program memory.
  
-{{id_links.jpg}}+{{:id_links.jpg}}
  
   * ****Clear**** Clicking this button deletes all link data currently in memory.   * ****Clear**** Clicking this button deletes all link data currently in memory.
Line 166: Line 166:
 The numerical items must be separated by spaces. An example of a link file is: The numerical items must be separated by spaces. An example of a link file is:
  
-{{links.jpg}}+{{:links.jpg}}
  
 Note that the minimum and maximum distances used are not true values but may be modified by the program to remove outliers caused by measurement noise. Note that the minimum and maximum distances used are not true values but may be modified by the program to remove outliers caused by measurement noise.
Line 264: Line 264:
 The assignment can actually be made to any other unidentified point, however you will be presented with a message that there is a conflict in the assignment, and asked to resolve it. The assignment can actually be made to any other unidentified point, however you will be presented with a message that there is a conflict in the assignment, and asked to resolve it.
  
-{{overlap.jpg}}+{{:overlap.jpg}}
  
 In this case you can cancel the assignment (**Cancel**), apply the assignment and cancel the identification of the overlapped segment (**Reassign**), or apply the assignment and retain the overlapped assignment (**Assign also**). The last option should only be used in situations where the frame overlap is caused by an error in joining of segments during the tracking, and involves the overlap of at most a few frames. In this case you can cancel the assignment (**Cancel**), apply the assignment and cancel the identification of the overlapped segment (**Reassign**), or apply the assignment and retain the overlapped assignment (**Assign also**). The last option should only be used in situations where the frame overlap is caused by an error in joining of segments during the tracking, and involves the overlap of at most a few frames.
other/amass/documentation/identification_using_links.1720792499.txt.gz · Last modified: 2024/07/12 13:54 by sgranger