| Date/time (local) | Occurrence | Latitude | Longitude | Notes |
|---|
| 03/12/26 00:17:24 | Detected | 43.1570 | -69.7360 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 00:32:24 | Detected | 43.1572 | -69.7351 | fin p1-2 - technically the different pulse trains only have 3 consecutive
classified in a row, but I'm going against protocol and marking as detected
because of good IPI and the very loud pulse in p1 that is not classified but
clearly fits with the pulse train |
| 03/12/26 01:17:24 | Detected | 43.1579 | -69.7323 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 01:32:24 | Detected | 43.1581 | -69.7314 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 02:16:10 | Detected | 43.1587 | -69.7292 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 02:47:24 | Detected | 43.1587 | -69.7312 | fin throughout section with technically at most 3 classified in a row, but there
are several very loud pulses with good IPI that were not classified (ie p15), so
going against protocol and marking as detected instead of possibly |
| 03/12/26 03:02:24 | Detected | 43.1577 | -69.7307 | detected p1-2 |
| 03/12/26 03:17:24 | Possibly detected | 43.1568 | -69.7303 | fin throughout section with technically no criteria met, but going against
protocol and marking as possibly due to several loud, isolated, classified pulses
with good IPI p7-8 |
| 03/12/26 03:32:24 | Possibly detected | 43.1559 | -69.7298 | possible fin p1-2 |
| 03/12/26 03:47:24 | Possibly detected | 43.1550 | -69.7294 | possible fin p1-3 |
| 03/12/26 04:17:24 | Detected | 43.1531 | -69.7285 | detected fin p3-4 |
| 03/12/26 04:32:24 | Possibly detected | 43.1522 | -69.7281 | possible fin p6 - third pulse is questionable but marking just in case |
| 03/12/26 04:45:13 | Detected | 43.1521 | -69.7279 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 05:17:24 | Detected | 43.1520 | -69.7275 | detected fin p11-12 |
| 03/12/26 05:32:24 | Detected | 43.1506 | -69.7268 | detected fin p11-13 |
| 03/12/26 06:17:24 | Detected | 43.1467 | -69.7248 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 06:32:24 | Possibly detected | 43.1454 | -69.7241 | possible fin p1 and 8 |
| 03/12/26 07:15:23 | Detected | 43.1424 | -69.7223 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 08:02:24 | Detected | 43.1404 | -69.7187 | detected fin p2-4 |
| 03/12/26 08:17:24 | Detected | 43.1389 | -69.7178 | detected fin criteria p9-11 |
| 03/12/26 08:32:24 | Detected | 43.1373 | -69.7169 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 09:17:24 | Detected | 43.1327 | -69.7142 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 09:32:24 | Possibly detected | 43.1327 | -69.7142 | possible fin p6-7 |
| 03/12/26 10:17:24 | Detected | 43.1294 | -69.7112 | fin throughout section with detected criteria p12-13; classified upcalls p3 and 6
are both background noise |
| 03/12/26 11:17:24 | Detected | 43.1253 | -69.7123 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 11:32:24 | Detected | 43.1242 | -69.7126 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 12:32:24 | Detected | 43.1235 | -69.7138 | fin throughout section with multiple occurrences of good IPI; classified humpback
p9 is background noise |
| 03/12/26 12:47:24 | Detected | 43.1240 | -69.7160 | detected fin p1-3; no classified humpback visible before data cutoff |
| 03/12/26 13:32:24 | Detected | 43.1256 | -69.7225 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 15:17:24 | Possibly detected | 43.1263 | -69.7345 | p15-16 possible fin |
| 03/12/26 15:32:24 | Possibly detected | 43.1265 | -69.7366 | possible fin p1-2; classified upcall p13 appears to be related to nearby faint
background noise - leaving as not detected but could see bumping to possibly since
it is not totally enveloped in the background noise and not a ton of LF noise
throughout section |
| 03/12/26 16:32:24 | Detected | 43.1274 | -69.7451 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 17:17:24 | Detected | 43.1262 | -69.7496 | classified upcall p10 appears to be an artifact; detected fin p13-15 |
| 03/12/26 18:32:24 | Detected | 43.1240 | -69.7593 | Criteria met for fin in P9 |
| 03/12/26 20:17:24 | Detected | 43.1200 | -69.7712 | P11 and P12 have multiple strong fin whale pulses. P11 has 4 consecutive pulses
with accurate INI, only missing one classified pulse so breaking protocol and
marking as detected. |
| 03/12/26 22:02:24 | Detected | 43.1165 | -69.7828 | Strong fin whale pulses in P5-6 that we have seen a lot of and they are not
usually marked by the detector. 4+ consecutive pulses with accurate INI, one is
classified so breaking protocol and marking as detected. |
| 03/12/26 22:17:24 | Possibly detected | 43.1164 | -69.7851 | Marking fin as possibly detected based on P12. 3 consecutive pulses, 2 are
classified and there is one other possible pulse in P11 but not convincing enough
to bump up to detected. Humpback in P13 looks like background noise so marking as
not detected. |
| 03/12/26 22:32:24 | Detected | 43.1162 | -69.7874 | P14-15 have strong fin pulses, three consecutive ones are classified with accurate
INI, only missing one classification so breaking protocol and marking as detected. |
| 03/12/26 22:47:24 | Detected | 43.1161 | -69.7897 | Criteria met for fin in P4-5 |
| 03/12/26 23:17:24 | Detected | 43.1158 | -69.7943 | Criteria met for fin in P9 |
| 03/12/26 23:32:24 | Detected | 43.1157 | -69.7966 | P15-16 have 4 classified pulses with accurate INI, only one pulse is in gray box
so breaking protocol and marking as detected. |
| 03/12/26 23:45:12 | Detected | 43.1156 | -69.7972 | Criteria met for fin in P4 |
| Date/time (local) | Latitude | Longitude | Notes |
|---|
| 03/12/26 00:17:24 | 43.1570 | -69.7360 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 00:32:24 | 43.1572 | -69.7351 | fin p1-2 - technically the different pulse trains only have 3 consecutive
classified in a row, but I'm going against protocol and marking as detected
because of good IPI and the very loud pulse in p1 that is not classified but
clearly fits with the pulse train |
| 03/12/26 01:17:24 | 43.1579 | -69.7323 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 01:32:24 | 43.1581 | -69.7314 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 02:16:10 | 43.1587 | -69.7292 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 02:47:24 | 43.1587 | -69.7312 | fin throughout section with technically at most 3 classified in a row, but there
are several very loud pulses with good IPI that were not classified (ie p15), so
going against protocol and marking as detected instead of possibly |
| 03/12/26 03:02:24 | 43.1577 | -69.7307 | detected p1-2 |
| 03/12/26 03:17:24 | 43.1568 | -69.7303 | fin throughout section with technically no criteria met, but going against
protocol and marking as possibly due to several loud, isolated, classified pulses
with good IPI p7-8 |
| 03/12/26 03:32:24 | 43.1559 | -69.7298 | possible fin p1-2 |
| 03/12/26 03:47:24 | 43.1550 | -69.7294 | possible fin p1-3 |
| 03/12/26 04:17:24 | 43.1531 | -69.7285 | detected fin p3-4 |
| 03/12/26 04:32:24 | 43.1522 | -69.7281 | possible fin p6 - third pulse is questionable but marking just in case |
| 03/12/26 04:45:13 | 43.1521 | -69.7279 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 05:17:24 | 43.1520 | -69.7275 | detected fin p11-12 |
| 03/12/26 05:32:24 | 43.1506 | -69.7268 | detected fin p11-13 |
| 03/12/26 05:47:24 | 43.1493 | -69.7261 | some classified fin p6-7 but the unclassified pulses are not convincing enough to
consider for possibly criteria |
| 03/12/26 06:17:24 | 43.1467 | -69.7248 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 06:32:24 | 43.1454 | -69.7241 | possible fin p1 and 8 |
| 03/12/26 07:15:23 | 43.1424 | -69.7223 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 08:02:24 | 43.1404 | -69.7187 | detected fin p2-4 |
| 03/12/26 08:17:24 | 43.1389 | -69.7178 | detected fin criteria p9-11 |
| 03/12/26 08:32:24 | 43.1373 | -69.7169 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 09:17:24 | 43.1327 | -69.7142 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 09:32:24 | 43.1327 | -69.7142 | possible fin p6-7 |
| 03/12/26 10:17:24 | 43.1294 | -69.7112 | fin throughout section with detected criteria p12-13; classified upcalls p3 and 6
are both background noise |
| 03/12/26 11:17:24 | 43.1253 | -69.7123 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 11:32:24 | 43.1242 | -69.7126 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 12:32:24 | 43.1235 | -69.7138 | fin throughout section with multiple occurrences of good IPI; classified humpback
p9 is background noise |
| 03/12/26 12:47:24 | 43.1240 | -69.7160 | detected fin p1-3; no classified humpback visible before data cutoff |
| 03/12/26 13:17:24 | 43.1250 | -69.7203 | p15 has 3 fin pulses ~10 sec apart in a row starting at 00:05, with two
classified, but given that the IPI has recently been ~15 sec, not confident these
are all from the same pulse train so leaving as not detected |
| 03/12/26 13:32:24 | 43.1256 | -69.7225 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 14:17:24 | 43.1269 | -69.7284 | classified upcall p15 appears to be background noise |
| 03/12/26 15:17:24 | 43.1263 | -69.7345 | p15-16 possible fin |
| 03/12/26 15:32:24 | 43.1265 | -69.7366 | possible fin p1-2; classified upcall p13 appears to be related to nearby faint
background noise - leaving as not detected but could see bumping to possibly since
it is not totally enveloped in the background noise and not a ton of LF noise
throughout section |
| 03/12/26 16:32:24 | 43.1274 | -69.7451 | fin throughout section with multiple occurrences of good IPI |
| 03/12/26 17:17:24 | 43.1262 | -69.7496 | classified upcall p10 appears to be an artifact; detected fin p13-15 |
| 03/12/26 17:32:24 | 43.1257 | -69.7516 | classified upcall p10 appears to be background noise, but the upsweep does stand
out a bit from the surrounding LF noise so could see bumping to possibly |
| 03/12/26 18:32:24 | 43.1240 | -69.7593 | Criteria met for fin in P9 |
| 03/12/26 19:32:24 | 43.1219 | -69.7646 | Criteria not met for fin |
| 03/12/26 20:02:24 | 43.1207 | -69.7690 | Data limited for fin |
| 03/12/26 20:17:24 | 43.1200 | -69.7712 | P11 and P12 have multiple strong fin whale pulses. P11 has 4 consecutive pulses
with accurate INI, only missing one classified pulse so breaking protocol and
marking as detected. |
| 03/12/26 20:32:24 | 43.1194 | -69.7733 | Data limited for fin |
| 03/12/26 22:02:24 | 43.1165 | -69.7828 | Strong fin whale pulses in P5-6 that we have seen a lot of and they are not
usually marked by the detector. 4+ consecutive pulses with accurate INI, one is
classified so breaking protocol and marking as detected. |
| 03/12/26 22:17:24 | 43.1164 | -69.7851 | Marking fin as possibly detected based on P12. 3 consecutive pulses, 2 are
classified and there is one other possible pulse in P11 but not convincing enough
to bump up to detected. Humpback in P13 looks like background noise so marking as
not detected. |
| 03/12/26 22:32:24 | 43.1162 | -69.7874 | P14-15 have strong fin pulses, three consecutive ones are classified with accurate
INI, only missing one classification so breaking protocol and marking as detected. |
| 03/12/26 22:47:24 | 43.1161 | -69.7897 | Criteria met for fin in P4-5 |
| 03/12/26 23:17:24 | 43.1158 | -69.7943 | Criteria met for fin in P9 |
| 03/12/26 23:32:24 | 43.1157 | -69.7966 | P15-16 have 4 classified pulses with accurate INI, only one pulse is in gray box
so breaking protocol and marking as detected. |
| 03/12/26 23:45:12 | 43.1156 | -69.7972 | Criteria met for fin in P4 |