Jump to content


Tag-Specific Boundaries for FLightR Analysis (log.light.borders etc.)


  • Please log in to reply
3 replies to this topic


  • General Members
  • 4 posts
  • Glendale, CO.,
  • United States

Posted 01 September 2016 - 06:25 PM

I am analyzing data from a couple of light-level geologgers that were attached to Western Bluebirds; I have been going back and forth between analyzing the data with the FLightR and Geolight R packages.  Now I'm having trouble picking the tag-specific parameters for the FLightR get.tags.data function.


These tags are the sort that record light intensity as values between 0 and 127; they take a light-level reading every minute and average the readings over each 10-minute period.  So, I used the log.light.borders and log.irrad.borders as for the Intigeo tags here: https://github.com/e...ific-boundaries.


My code: 


tag.612.FLightR.data <- get.tags.data("tag_612_twilights_TAGS_threshold_5.csv",
                                      log.light.borders = log(c(1, 127)), 
                                      log.irrad.borders = c(-3, 3), 
                                      saves = c("mean"), measurement.period = 60, 
                                      impute.on.boundaries = FALSE)
Is this correct?  And can somebody explain the difference between the log.light.borders and log.irrad.borders parameters?


#2 Eldar

  • General Members
  • 48 posts
  • Netherlands,
  • Netherlands

Posted 02 September 2016 - 07:48 AM

  Hi Morrijos,

 Am I right that you have some custom tags? If so it is hard to tell which values should be used for them. The main problem is log.irrad.borders as I do not know range of linear part of your sensor. General approach is to plot your calibration data and select linear period for log.irrad.values. You can try and see what will happen.

   For the log.light.borders I would exclude 127 and would make it log(c(1,126)). Do you have a stationary tag to make a calibration?



  • General Members
  • 4 posts
  • Glendale, CO.,
  • United States

Posted 06 September 2016 - 02:01 PM



Thanks for your reply. Yes, these are custom tags made by Dr. Bridge. I may have to contact him for the sensor specifics...


Unfortunately, I do not have a stationary tag to work with; however, the birds are (more or less) known to have stayed in a set location during the nesting season, so I can try to get some calibration info from the first weeks of logging.  

#4 brlikv

  • General Members
  • 1 posts
  • Czech Republic

Posted 05 February 2017 - 08:09 AM

Hi Morrijos, 


We are preparing a database for a meta-analysis of the effect of geolocators on migratory songbirds. I am writing you to kindly ask for some basic information regarding your geolocator project on Western Bluebirds. 


Could you be so kind and share with us the recapture rates of the geolocator-tagged and control birds? 


Thank you very much and kind regards, 



Also tagged with one or more of these keywords: Geolocator

0 user(s) are reading this topic

0 members(s), 0 guests(s) and 0 anonymous member(s)