Jump to content
Ornithology Exchange

Hendrik

General Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

0

Profile Information

  • Location
    Auckland
  • Country
    New Zealand
  1. Hi Eldar, thanks a lot for your comments. I will keep the on bird calibration in mind for future analysis! It improved things a lot with this data set! Again, many thanks and have a nice Sunday! Hendrik
  2. Hi Eldar, I am currently helping a friend to analyse data from mottled petrels breeding on Codfish Island, South of New Zealand. She used migrate technology tags, the same model (C-250) as I used on skua. Her light data looks very clean and she has a few days of 'rooftop' callibration from the study site. When running the model, it always comes out with a track that makes sense given what is known from previous tracking of the species. However, there are no confidence areas displayed on the lat lon graph (looking at the data, Min.lat, Max.lat and Medianlat/Lon values are all the same for
  3. Hi Mendez, how did you call dawn and dusk times before loading the data into FlightR. Have you used the BAStag package? If yes, were the missing dusk events correctly selected by the package for these tags? Did you possibly subset the data before using plot_slopes_by_location? Maybe something went wrong there? All the best and have a nice day! Hendrik
  4. Hi Devin, are you plotting the "mean" or "median" locations? If I recall right from another post, only the median will stick to the landmask. Try to plot median locations and see whether the problem is fixed. Let me know how it goes :-) Hendrik
  5. Hi Devin, "inf" stands for infinity, so, as far as I understand it, using “distance.from.land.to.use=c(-Inf, Inf)” will allow the locations to fall on the ocean. Try :“distance.from.land.to.use=c(-Inf, 0)”. It is all described in detail in the Cran pdf for Flight R. See description from the package below: distance.from.land.allowed.to.use - define how far from the shoreland animal could occur. Unit - km, negative values are for inland and positive for offshore directions. Inf stays for infinity. Hope that helps! Hendrik
  6. Hi Devin, I am using FlightR, too. You can access the data like this: write.csv(Result$Results$Quantiles, file="Nameofyourfile.csv",quote=FALSE, row.names=FALSE) The file contains means, medians of lon and lat as well as time stamps and confidence estimates. I hope that helps! :-) All the best, Hendrik
  7. Thanks Eldar, map.FLightR.ggmap works fine for me now. The plot_util_distr only caused me trouble on my macOS machine, turned out it works fine on windows. Thank you very much for your help Eldar, very much appreciated! Hendrik
  8. Dear Luke, I am also using FlightR to analyze Light Data from Migrate Technology, however I used them on skua and not on burrow nesting seabirds. I am not a modelling expert, but let me share my experience with you. For calibration, I have put all retrieved loggers post deployment in an open space for rooftop calibration. Ideally you have pre and post deployment calibrations, but the post calibration only seems to work fine for me. Ideally, you perform the calibration on each logger that was actually on the bird. However, I have tried using other logger's for calibration where only few or
  9. Dear Eldar, I am sorry for the double post, but I think this got lost in the end of a previous post that was already answered. I receive two error messages when using the functions map.FLightR.ggmap and plot_util_distr: 1. map.FLightR.ggmap map.FLightR.ggmap(Result) Error: longitude of center must be between -180 and 180 degrees. note ggmap uses lon/lat, not lat/lon. In addition: Warning message: In min(Result$Results$Quantiles$Medianlon[twilights.index][Result$Results$Quantiles$Medianlon[twilights.index] > : no non-missing arguments to min; returning Inf Inter
  10. Dear Eldar, I have a possibly related error message when running the plotting function: map.FLightR.ggmap(Result) Error: longitude of center must be between -180 and 180 degrees. note ggmap uses lon/lat, not lat/lon. In addition: Warning message: In min(Result$Results$Quantiles$Medianlon[twilights.index][Result$Results$Quantiles$Medianlon[twilights.index] > : no non-missing arguments to min; returning Inf Interestingly this only happens when using certain grid boundaries for the spatial extent. So far I could trigger the error as soon as I extended the right boundary abov
  11. HI Eli and Amelie, I just had a look at this post and have a question myself. As previously discussed, BasTag only marks deleted twillights as "deleted", but keeps them in the output file. Once converted into TAGS format, these twilights are marked as excluded = TRUE. Now my question is, will FlightR automatically exclude these twilights marked as "excluded" from the analysis? Thanks a lot for clarifying and have a good start in 2017! All the best, Hendrik
  12. I think I solved the problem already. I managed to edit the existing function "readMTdeg" the following way: readMTdeg2 <- function(file,skip=20) { ## Read csv file and add column names d <- read.table(file,header=FALSE,skip=skip, sep="\t",col.names=c("Date","Activity"), colClasses=c("character","numeric")) #Parse date # Use %I, since the Intigeo time data are provided as decimal hours (12 hour) d$Date <- as.POSIXct(strptime(d$Date,"%d/%m/%Y %I:%M:%S %p",tz="GMT")) #Return data frame. d } That seems to work well in case someone else comes across this issue. H
  13. Hi there and a belated merry Christmas, I was just looking into importing ".deg" files (immersion count data as provided by Intigeo loggers) into BAStag and was delighted to see that a function ("readMTdeg") has recently been added. However, something seems to be off, the description of the function states "Read Temperature data from a Migrate Technologies tag", which basically resembles the description of "readMTsst" which serves to importing ".SST" files (which contain temperature and conductivity data). Importantly, ".deg" files contain immersion count data only. When executing "readMT
  14. Hi Eli and Eldar, I have a question about FlightR that I was hoping you may help me with. I found in your 2015 movement ecology paper that the FlightR includes a spatial/behavioural mask that prevents a stationary state on over large water masses. This makes sense when studying most shorebirds, but I was wondering whether that applies when a seabird is the study species, which may sit on the water for a long time e.g., during moult. I was therefore wondering whether a stationary state above sea is prevented by default and if that's the case, whether there is a way to allow stationary state
×
×
  • Create New...