Jump to content
Ornithology Exchange


General Members
  • Content Count

  • Joined

  • Last visited

 Content Type 









OC Small Grants Applications

Journal Indexes

Grants & Awards

AOU/COS 2015 Travel & Presentation Award Applications


Everything posted by Eldar

  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
  15. Hi Devin, Yes, this happens often. In many cases (e.g. swifts) calibration twilights could be completely missing due to behaviour. Eldar
  16. 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
  17. This happens sometimes, no worries. Just do library(grid) before running this line. Cheers, Eldar
  18. We are looking for a venue in Vancouver as it seems we cannot have our workshop at the congress centre. Let us know, please, if you have any suggestions. Eldar
  19. Our apologies for the late notice but we want to announce that there will be a 1.5 day short course in geolocation analysis in association with the International Ornithological Congress in August. We have been unable to come to terms with the IOC organizers about the location of this course, but one way or another we will have it in Vancouver on August 19 (Noon to 6pm) and August 20 (8am to 5pm)—just before the conference. It is uncertain as to whether this course will be listed on the IOC website, so we wanted people to be aware of it as they make travel plans. Please share this announcement with anyone who may be interested. We have no intention of excluding anyone. For more details on the contents of the course, please see the attached description. If you are interested in attending the course please visit this signup page to provide your contact information and to answer a few quick questions about your coding background: https://goo.gl/forms/SduJiuMsJrpta2462 We will probably ask for a $20 fee at some point to cover any room rental fees and other expenses (and to discourage no-shows). We have limited the course size to 40 attendees. If you have any questions, feel free to contact any of the organizers. For those of you going to IOC we look forward to seeing you there. To everyone else, please excuse the intrusion. Sincerely, Eldar Rakhimberdiev (Author of FLightR) Simeon Lisovski (Author of GeoLight) Eli Bridge (Head Cheerleader)
  20. You can try automating it. Let's say left is replaced with right for the cases when right crosses 0 meridian. You can do then something like Left_corrected<-Left Right_corrected<-Right Left_corrected[condition when right is not correct]<-Right Right_corrected[condition when right is not correct]<-Left Hope this helps. Eldar
  21. Hi Cosme, I am not sure I can fully imagine what you are talking about, but expect you see some strange plotting around 0 meridian. This can definitely happen but it is likely not an error but incorrect assignment of Left and right CI while near 0 meridian. You can try to correct it by hand by swapping left and right CI for specific points. If it does not help, send me your result object and code by mail and I will have a look. Eldar
  22. Hi Tara, You have created an object called GeoLight2TAGS and it is function name in FLightR. Try removing this object and everything will go through. rm(GeoLight2TAGS) Cheers, Eldar
  23. Hi Louise, I do not think this is common, as I have seen many birds wintering around equator where geolocator inferred positions did not do jump. At the same time I have also seen many migrations within Africa during wintering from gps data, so it is common. The only suspicious thing is symmetrical movements in relation to autumn and spring equinoxes, if you have those - send me the lat-lon plots, please. Cheers, Eldar
  • Create New...