Jump to content
Ornithology Exchange (brought to you by the Ornithological Council)

Eldar

General Members
  • Posts

    77
  • Joined

  • Last visited

Everything posted by Eldar

  1. Good news, I managed to rewrtite the packages, so it will remain on CRAN and will run as before. The only difference is that it requires R >=4.1.0 now. Cheers, Eldar
  2. Dear geolocator users, As you might know R spatial architecure is going to change soon with main packages (sp, maptools, rgeos, rgdal) retiring. This means that our solar geolocation packages should be changed in order to stay on CRAN. At the moment I do not have enough time to work on FLightR package, so let me know if you have time or you know anyone, who might be interested in such a project (I can imagine this would be a nice MSc project). Any other ideas are welcome indeed, as I do not know how to proceed at the moment. Best wishes, Eldar
  3. Hi Beata, What kind of overlapping dates you get? It is likely that dates will overlap at the ends - around 90-95% percentile. Try adjusting prob.cutoff to e.g. 0.5 in the stationary.migration.summary. I think you should get the same results as from find.times.distribution then. Hope this helps, Eldar
  4. Hi Devin, This does not look good at all, sorry. What happens if you run the GeoLight on this tag? Do you get any stationary period? If so I would suggest you take start and end time from this period and use them to find potential stationary location. After that you can try use this location for calibration. Hope this helps at least a bit. Eldar
  5. Hi Devin, Plug calibration from the working tag into all.in<-make.prerun.object(proc.data, Grid, Calibration=Calibration) Hope this helps, Eldar
  6. Hi Devin, Yes, this happens often. In many cases (e.g. swifts) calibration twilights could be completely missing due to behaviour. Eldar
  7. Hi Devin, Absence of the slopes after start of migration is normal, so no worries here. But what I see in the graph is difference between slopes during dusk and dawn yo have in the summer. THis could happen because (1) the start coordianates are not correct, (2) bird moved to a new place (and thus you do not know where to calibrate you tag), (3) there is a specific bird behaviour, that makes this difference. I would suggest you double check the calibration location and if it was correct try try with calibration extracted from a tag that worked. For Intigeo tags that works well. Eldar
×
×
  • Create New...