Jump to content
Ornithology Exchange

Eldar

General Members
  • Content Count

    70
  • Joined

  • Last visited

Community Reputation

1 Has posted some good stuff

My Research

  • Google Scholar
    https://scholar.google.com/citations?user=rQQ5zTUAAAAJ&hl=en

Profile Information

  • Location
    Groningen
  • Country
    Netherlands

Contact Methods

  • Website URL
    eldarrak.github.io

Recent Profile Visitors

754 profile views
  1. This is strange. I have just tried installing from GitHub and got the 0.4.9... It is not on CRAN yet, so do not try there. Eldar
  2. Please note that there was a bug in FLightR 0.4.8 that creared weird resuls with point jumping all over the place - Please update FLightR to 0.4.9: devtools::install_github('eldarrak/FLightR') Eldar
  3. Hi Dan, I have discovered a bug in FLightR 0.4.8. Please reinstall from Grithub with devtools::install_github('eldarrak/FLightR') and report whether you still have problems. Sorry for the inconvenience. Eldar
  4. Hi Dan, rtools is not a package, so you should download it from here https://cran.r-project.org/bin/windows/Rtools/ and install manually. Hope this helps, Cheers, Eldar
  5. Hi Don-Jean, Looks like a bug... Could you please send me the RData and the script? I will have a look. Eldar
  6. Hi Don-Jean, I would suggest you reread the original file starting from the deployment date and plug the already created calibration into it. Hope this helps! Eldar PS Note that in many cases you get too clean results in case of rooftop calibration, so you might want to find the wintering site and recalibrate there to get reasonable uncertainty estimates.
  7. Hi Hendrik, Yes, we had this issue already with some other roof top calibrations. I must admit that on bird works better. The calibration consists of the two main parameters - slope (mean+- sd) of measured irradiance vs expected irradiance. Mean should be the same, but the sd differs between the roof top and the on bird. Hope this helps, Eldar
  8. Hi Allison, I can add a tag to FLightR to make it processing yur tags automatically. DO you have on bird calibration data from several tags? If so, sould you sent me those together with the calibration coordinates? I will try to have a look. Cheers, Eldar
  9. There was a bug in FLightR causing this error for tagging location above 65 but below 66 degrees N. Fixed now in FLightR >=0.4.8 (at the moment GitHub only).
  10. Hi Louise, There was a minor bug in FLightR. Fixed now, so install the latest version with devtools::install_github('eldarrak/FLightR') And go ahead. BUT note, that with the cutoff probability of 0.8 you are setting quite a high border probability and many small movement and stops may just disappear.
  11. Unfortunately this results of the new google rules for use of google maps. They want everyone to get the api key for google maps. In order to do this you should 1. go to https://cloud.google.com/maps-platform/?apis=maps get the key there 2. update you ggmap devtools::install_github("dkahle/ggmap") 3. then in each session in R try ggmap::register_google('your_api_key') Now FLightR ggmap related functions should work.
  12. Hi Camilo, Could you please save the objects you provide to make.prerun.object() function save(a, b, c, file='tmp.RData') and send them to me? I do not think one can locate the problem without the data in this case. Cheers, Eldar
  13. 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
  14. Hi Devin, Plug calibration from the working tag into all.in<-make.prerun.object(proc.data, Grid, Calibration=Calibration) Hope this helps, Eldar
×
×
  • Create New...