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

Mendez

General Members
  • Posts

    14
  • Joined

  • Last visited

Profile Information

  • Location
    Newark, Delaware
  • Country
    United States

Recent Profile Visitors

918 profile views

Mendez's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi all, Following Eldars advice above I was able to get the other units to work using the calibration of another geo (Thanks again Eldar!). I'm still having difficulties with this one unit and i'm not really sure why. Whenever I run this unit through FlightR it appears that the bird never returned to the breeding ground in the 2010 season, which is possible since we never relocated or captured it, I just think that it's highly unlikely. My first thought was that this unit contains two years of data so I tried splitting it. Once the unit was converted into TAGS format I tried splitting the data in half to make it similar to a geo that had a single year of data. This seemed to work slightly better than trying to run it as a single unit, but the results were still scattered everywhere. All of these failed attempts I was using a different geo for the calibration, I cant run the calibration otherwise. I'm not sure what else to do, any advice would be greatly appreciated!
  2. I am still having some difficulties analyzing some of the geolocators that have differences between slopes in dawn and dusk. I have tried using the find.stationary.location function, but it provides me with a location that is way different than the original coordinates. All of the geos i'm having difficulties with are females from 2012-2013 and i'm imagining the problem is a lot of shading events on the breeding site which I have been using for the calibration periods. Even when plotting the slopes with the derived location from the find. stationary.location there is still a lot of differences between the slopes. In the tool help it says that it does not work well with shaded data which i believe is the case. Eldar recommended above to use the calibration extracted from a tag that worked. Should I try using a calibration file that was extracted from the same year? Also while using the calibration file from another geo i'm still not confident that i'm doing it correctly. I took the proc.data from a working geo and calibrated it normally. I would then plug in the proc.data from the geo that did not possess a calibration period into make.prerun.object with the calibration file from the working geo. Is this the correct workflow? I used this method with one of the problem geos and it appeared to work, but upon closer observation the dates did not align at all with the units previously analyzed.
  3. Hi Eldar, I double checked the start coordinates and they are correct. I went ahead and used the calibration from a tag that worked and I was able to get consistent results. The geos that I was having trouble with were attached to females. I was thinking that since the females spend the majority of their time on their nests during the times that I was using for the calibration period that it may cause extreme shading resulting in the unit believing that it was in another location leading to the calibration of the unit being wrong. Is this a viable hypothesis for these birds? Thanks again, Devin
  4. Hi all, I have a few geolocator files that I have not been able to process ( The location estimates are scattered all across the specified grid) and I believe it has something to do with the plot_slopes_by_location function. I know that this function is just to determine whenever the bird leaves the study site, however, in the graph it revealed that there are no dusk estimates after September (see attached picture). All of the geolocators that I have been unable to analyze have this similar problem. I'm not sure if that's actually the root of my problems or if its something else, this is just my best guess. Is anybody aware if this could be the problem and if it is is there anyway to correct for this problem? Thanks, Devin
×
×
  • Create New...