ARRIVALS¶
Each row, taken together with the related EVENTS row, represents
an arrival or departure of an individual from the observation
conducted during a follow.
The related EVENTS row must be an arrival event; it must have an
EVENTS.Behavior value of ARR.
This related EVENTS row supplies arrival and departure time values,
and the ROLES role related to the event supplies information on the
individual arriving and departing.
The system will generate a warning when there are 2 different arrival
events for the same arriving individual, in the same follow, that have
an EVENTS.Certainty of 1, with
EVENTS.Start to EVENTS.Stop intervals that
overlap, endpoints included.
Arrivals that are not certain, those with an EVENTS.Certainty that is not 1, may overlap
each other, as well as arrivals that are certain, without any warning.
Care should be taken when using uncertain arrivals.
The system will generate a warning when there are 2 different arrival events for the same arriving individual, in the same follow, that have identical EVENTS.Certainty values, which span a contiguous time period. Spanning a contiguous time period means that the EVENTS.Stop value of the first arrival is one minute less than the EVENTS.Start value of second other interval, so that the first arrival stops just when the second starts. .. If necessary this warning can be adjusted so that it only reports .. on arrivals that are certain.
For further information, including additional data integrity rules, see the documentation of the EVENTS table.
ArID (Arrival ID)¶
A unique, automatically generated, positive integer which serves to
identify the row. The value of this column cannot be changed. This column may not be NULL.
EID (Event ID)¶
The EVENTS.EID identifying the arrival event that is related to the arrival or departure. The related event contains information on arrival and departure times.
This column may not be NULL.
Seq (Sequence)¶
An integer indicating the order in which an individual arrived, in the sequence of arrivals of a given individual, in a given follow.
This column records the ordering of the arrivals of a single
individual, within a given follow.
The values start with 1 and increase without gaps, each successive
arrival of an individual incrementing by one the value of the previous
arrival.
The order is determined by, first, the time the individual arrived in a given follow. Ties are broken by the time the individual left the follow. Ties remaining are broken by the time the row was inserted into the system, or, in the case of data imported from the old MS Access database, by that database’s FOLLOW_ARRIVAL.FA_seq_num column’s value.
The value of this column is automatically maintained by the system.
Values inserted into this column must be NULL (or the column may
be omitted from the INSERT statement).
The value of this column cannot be changed.
The value of this column is never NULL.
NestStart (in Nest at the Start time)¶
A boolean, whether or not the related participent, related
through EVENTS and ROLES, was in a nest at the time of arrival. This column may not be NULL.
NestStart (in Nest at the Stop time)¶
A boolean, whether or not the related participent, related
through EVENTS and ROLES, was in a nest at the time of departure. This column may not be NULL.
Cycle (Cycle state)¶
A CYCLE_STATES.Code value indicating the state of the arriving individual’s estrous cycle.
All indivdiuals, female or not, have a value in this column, to avoid tri-valued logic and therefore simplify querying. The value used for males and other non-cycling individuals is un-interesting.
This column may not be NULL.
DataSource (Data Source)¶
A unique, automatically generated, positive integer which serves to
identify the row. The value of this column cannot be changed. This column may not be NULL.
Page last generated: 2025-11-10 22:25:16 UTC