| Date/time (local) | Occurrence | Latitude | Longitude | Notes |
|---|
| 02/18/26 09:47:24 | Detected | 43.1157 | -70.2474 | detected fin criteria p3-4 |
| 02/18/26 10:02:24 | Detected | 43.1153 | -70.2501 | detected fin criteria p13-14 |
| 02/18/26 10:17:24 | Detected | 43.1150 | -70.2527 | fin throughout section with good IPI p7-10 |
| 02/18/26 10:47:24 | Possibly detected | 43.1143 | -70.2580 | fin throughout section with good IPI p7-8, but no case of 4 consecutive pulses so
marking as possibly - might be a candidate to bump up to detected due to high
amplitude and isolation |
| 02/18/26 17:02:24 | Detected | 43.1117 | -70.2993 | fin throughout section with multiple instances of good IPI |
| 02/18/26 17:17:24 | Detected | 43.1121 | -70.3008 | fin throughout section with multiple instances of good IPI |
| 02/18/26 17:32:24 | Detected | 43.1125 | -70.3024 | fin throughout section with multiple instances of good IPI; classified upcall p2
is amidst background noise of similar amplitude, but the shape and duration of
the sound really stands out - marking as not detected for now but may be a
candidate for bumping to possibly due to its structure |
| 02/18/26 18:17:24 | Detected | 43.1133 | -70.3055 | fin throughout section with multiple instances of good IPI |
| 02/18/26 18:26:24 | Detected | 43.1133 | -70.3055 | a few fin pulse trains throughout section but most pulses unclassified, so no
criteria technically met - going against protocol and marking as detected due to
isolation, amplitude, and IPI evident in these pulses, particularly in p5-6 |
| 02/18/26 18:47:24 | Detected | 43.1136 | -70.3102 | fin with good IPI p6-7 |
| 02/18/26 19:02:24 | Possibly detected | 43.1138 | -70.3127 | in p1, the pulses in the gray were already included in the previous section, and
in this section it clearly is the same pulse train, but detected criteria was not
met due to an unclassified pulse in p1 + data cut off - may be a candidate for
bumping up to detected but following protocol and leaving fin as possibly for now |
| 02/18/26 19:17:24 | Detected | 43.1139 | -70.3152 | fin detected criteria met p1-2, 13-14 |
| 02/18/26 19:32:24 | Detected | 43.1141 | -70.3176 | classified sei singlet p12 has decent shape when compared to singlets in
protocol, but has nearby pts that suggest it could be background noise or a
different species - marking as possibly just in case since can't fully rule out
sei confidently; fin detected criteria p7 |
| 02/18/26 20:17:24 | Possibly detected | 43.1146 | -70.3251 | possible fin p15 |
| Date/time (local) | Latitude | Longitude | Notes |
|---|
| 02/18/26 00:02:24 | 43.1132 | -70.1692 | classified upcall not visible before data cut off |
| 02/18/26 00:17:24 | 43.1129 | -70.1717 | classified upcall p13 appears to be part of background noise |
| 02/18/26 01:47:24 | 43.1110 | -70.1854 | two unclassified upsweeps (p4, 7) with somewhat convincing shapes, but both are
very truncated/faint and don't meet criteria for possible NARW detection; lots of
LF noise throughout that is likely non-bio due to how loud, yet short the sounds
are |
| 02/18/26 02:17:24 | 43.1115 | -70.1872 | p10 has two classified pulses preceded by a very faint blip that may be a distant
pulse but is not convincing enough to consider as context, so leaving fin as not
detected |
| 02/18/26 02:32:24 | 43.1124 | -70.1893 | classified upcall p2 part of background noise |
| 02/18/26 02:47:24 | 43.1133 | -70.1915 | the three classified pulses in p6 do not have evenly spaced IPI so leaving fin as
not detected |
| 02/18/26 05:17:24 | 43.1175 | -70.2105 | classified sei p9 near background noise but on the fence since there is an
unclassified downsweep in p8 that may serve as context but that one also occurs
near background noise - keeping sei as not detected for now |
| 02/18/26 07:17:24 | 43.1169 | -70.2252 | classified upcall p9 appears to be part of background noise |
| 02/18/26 09:47:24 | 43.1157 | -70.2474 | detected fin criteria p3-4 |
| 02/18/26 10:02:24 | 43.1153 | -70.2501 | detected fin criteria p13-14 |
| 02/18/26 10:17:24 | 43.1150 | -70.2527 | fin throughout section with good IPI p7-10 |
| 02/18/26 10:47:24 | 43.1143 | -70.2580 | fin throughout section with good IPI p7-8, but no case of 4 consecutive pulses so
marking as possibly - might be a candidate to bump up to detected due to high
amplitude and isolation |
| 02/18/26 13:17:24 | 43.1088 | -70.2783 | classified upcall p4 part of background noise |
| 02/18/26 14:32:24 | 43.1079 | -70.2849 | classified upcall p12 part of background noise |
| 02/18/26 16:47:24 | 43.1113 | -70.2978 | classified upcall p6 appears to be background noise |
| 02/18/26 17:02:24 | 43.1117 | -70.2993 | fin throughout section with multiple instances of good IPI |
| 02/18/26 17:17:24 | 43.1121 | -70.3008 | fin throughout section with multiple instances of good IPI |
| 02/18/26 17:32:24 | 43.1125 | -70.3024 | fin throughout section with multiple instances of good IPI; classified upcall p2
is amidst background noise of similar amplitude, but the shape and duration of
the sound really stands out - marking as not detected for now but may be a
candidate for bumping to possibly due to its structure |
| 02/18/26 18:17:24 | 43.1133 | -70.3055 | fin throughout section with multiple instances of good IPI |
| 02/18/26 18:26:24 | 43.1133 | -70.3055 | a few fin pulse trains throughout section but most pulses unclassified, so no
criteria technically met - going against protocol and marking as detected due to
isolation, amplitude, and IPI evident in these pulses, particularly in p5-6 |
| 02/18/26 18:47:24 | 43.1136 | -70.3102 | fin with good IPI p6-7 |
| 02/18/26 19:02:24 | 43.1138 | -70.3127 | in p1, the pulses in the gray were already included in the previous section, and
in this section it clearly is the same pulse train, but detected criteria was not
met due to an unclassified pulse in p1 + data cut off - may be a candidate for
bumping up to detected but following protocol and leaving fin as possibly for now |
| 02/18/26 19:17:24 | 43.1139 | -70.3152 | fin detected criteria met p1-2, 13-14 |
| 02/18/26 19:32:24 | 43.1141 | -70.3176 | classified sei singlet p12 has decent shape when compared to singlets in
protocol, but has nearby pts that suggest it could be background noise or a
different species - marking as possibly just in case since can't fully rule out
sei confidently; fin detected criteria p7 |
| 02/18/26 20:17:24 | 43.1146 | -70.3251 | possible fin p15 |