Was this page helpful?

Use of tags with duplicate IDs within a project

From $1

    If your project has two (or more) tags with the same ID, you must take extra steps to ensure
    detections of these tags will be unambiguous.  Taking these steps can allow you to safely use many pairs
    (or triples, or ...) of tags with the same ID.  (The guidelines also apply to some extent across
    multiple projects, but there the first issue doesn't usually arise.)

    1. Ensure the tags can be distinguished in the hand

    There is not much space on the nanotag body for adding extra characters to the label, so:

    • use a brightly-coloured indelible liquid to add a small dot to one of the tags, next to the label,
      so that it can be seen clearly by anyone reading the label.  This should be something which
      will not smear, peel off or fade in the sunlight.  Nail polish might work well for this.
    • if you have more than two tags with the same ID, add an additional dot to each consecutive tag,
      so that one tag has no dots, one tag has 1 dot, one tag has 2 dots, and so on.
    • make sure anyone handling the tags is aware of the significance of these dots
    • whenever you refer to this tag, add the number of dots as fractional digits after the ID#:
      • the first tag 312 in a project is given ID 312 and has no dots added to the label
        (this makes sense numerically: 312.0 = 312 and is the same as the usual situation
        where you have only one tag with ID 312).
      • the second tag 312 in a project is given ID 312.1 and has 1 dot on the label
      • the third tag 312 in a project is given ID 312.2 and has 2 dots, etc.
    • when you register the tag, be sure to use the dotted ID # in the filename; e.g.:
      • file for  1st tag 312 is tag312@166.380.wav
      • file for 2nd tag 312 is tag312.1@166.380.wav

    2. Ensure the tags can be distinguished by the SensorGnome

    Two tags with the same ID can be distinguished by a SensorGnome if they have different
    burst intervals and if at least two bursts are detected from each tag (which is almost always
    the case).  The registration process will verify whether burst intervals are sufficiently different,

    • register the tags with us, using dotted IDs in the filenames as shown above
    • if the tags are distinguishable, you will receive a tag database as usual; tag IDs
      will have dots and extra digits to match your physical tags
    • if we determine that tags are not distinguishable, you will receive a database with as many
      of the tags as can be distinguished, and a detailed message indicating which tags have
      been excluded and why.


    Distinguishing between tags in a dataset

    The id and fullID fields for tags in the same project with duplicate IDs will now appear as:

    id fullID
    312 Niles#312@166.38:7.1
    312.1 Niles#312.1@166.38:5.9

    The full ID shows why the tags are distinguishable: the burst intervals 7.1 and 5.9 seconds are
    different (and moreover, incompatible: even when small runs of consecutive bursts are
    missing, sequences of detection times for the two tags cannot be the same.)

    Seeing tags with the same ID in the SensorGnome live web interface

    • 2015 software release (upcoming) : IDs shown in the live detection window will include any dots
      and extra digits as described above.
    • 2014 software release: you will need to install a software update on an SG in order to distinguish between
      detections of different tags with the same ID in the live web interface for that SG.  This update is not required
      if you only wish to have these tags detected in raw data from that SG when these are processed by sensorgnome.org
    Was this page helpful?
    Tags: (Edit tags)
    • No tags
    Comments (0)

    Powered by MindTouch Core