Beata
-
Posts
3 -
Joined
-
Last visited
Content Type
Forums
Events
Articles
Journals
Links
Jobs
Organizations
Books
Journal Indexes
Grants & Awards
Gallery
Downloads
Posts posted by Beata
-
-
On 11/13/2020 at 10:35 AM, karde said:
Hi all,
My concern is related to posts on “plot_slopes_by_location” .
I am currently working on GLS data (old BAS tags) on seabirds (albatross) deployed for 2-4 yrs and some of them are circumpolar navigating during the non-breeding period.
1) The first issue is that I do not have properly calibration data, then I tried to use approximate calibration from a very short period, different loggers et site ~ 80km from the deployment site.
I see that you suggest to use the calibration extracted from a tag that worked, but I failed to understand how you do that.
Hi,
before calling make.prerun.object you should load saved calibration file for a tag that worked (load(file= path to *Calibration.RData)
On 11/13/2020 at 10:35 AM, karde said:2) using my approximate calibration data, I process as follow:
start=c(77.53, -38.71)
log.light.borders=c(1.5, 9) # default values for Intigeo tag
log.irrad.borders=c(-3, 3) # default values for Intigeo tag
Calibration.periods<-data.frame(calibration.start=as.POSIXct("2010-01-01"),
calibration.stop=as.POSIXct("2020-01-01"),
lon=start[1], lat=start[2])
I think your calibration period is not properly set. Now it is 10 years used for calibration... You should use here only periods with known location of tag.
-
Hi,
I am performing gls analysis of Intigeo devices in FlightR. When I use stationary.migration.summary function I get overlapping dates for stationary period. So I decided to use find.times.distribution to find arrival/departure dates to/from stationary periods calculated by stationary.migration.summary. Now I am wondering what key should I use to unify this approach across all my birds? Any advise?
Here is a piece of my results of two stationary periods.
Meanlat SDlat Meanlon SDlon Dist2 Arrival.Q.50 Departure.Q.50
25.595678 2.4360796 -12.919237 1.0270114 453.1756 2019-09-28 07:40:58 2019-10-11 20:53:39
19.598708 2.1146732 -3.262447 0.6437934 1310.7202 2019-10-12 00:57:31 2020-03-16 08:01:10
Problem with arrival/departure dates for stationary periods
in Geolocator Discussion & Support
Posted
Hi Eldar,
thank you for a reply. I get overlaping median dates or they seem quite unrealistic (like those in first post where departure date is 11. October and arrival date to next stopover (over 1000 km) is 12. October.
I tried adjusting the probability cutoff. The maximum I was able to set was 0.3. If I set 0.5 I get message that the bird didn't move.