Nevitt, Lucy, author

Home-Cook, George, 1975- author

Stebbins, Robert A., 1938- author

Kempe, Andy

Wood, Katrina, author

Ewing, Robyn (Robyn Ann), 1955- author

Goebbels, Heiner, author

Davis, Jim, 1949- author

Krishnan, Sarasa, author

Eckersall, Peter, author

Cixous, Hélène, 1937- author

Johnston, Daniel, author

Chorus song of the indri (Indri indri: Primates, Lemuridae): Group differences and analysis of within-group vocal interactions Baker-Medard, Merrill S. A.; Baker, Myron C.; Logue, David M. The loud chorus songs of the group-living lemur Indri indri are a striking feature of rainforest areas of eastern Madagascar. Despite some research on the conspicuous vocal display of the indri, two hypotheses have not been addressed: do groups differ in the acoustic properties of their songs, and is there evidence of coordinated singing between individuals within groups. We recorded and analyzed the songs of three indri groups to examine these two questions. To answer the first question, we made quantitative spectral measures on songs of the three groups and performed multivariate analyses of the acoustic features of the notes constituting the songs. Our results showed songs of the three groups differed significantly, although there was overlap between groups. To answer the second question, we classified note types and quantified their occurrence as overlapping and abutting pairs. We found non-random associations between sequential note types in all three indri groups. These associations were consistent among groups, suggesting that individuals follow consistent answering rules when contributing to choruses. Whether indris use acoustic group identifiers in management of behavioral strategies and how within-group coordinated note production might function remain unknown. We compare our results to a number of taxonomically diverse species that live in groups and broadcast chorus and duet vocal signals. Open access article. Creative Commons Attribution 4.0 International License (CC BY 4.0) applies.

A locally funded Puerto Rican parrot (Amazona vittata) genome sequencing project increases avian data and advances young researcher education Oleksyk, Taras K.; Pombert, Jean-Francois; Siu, Daniel; Mazo-Vargas, Anyimilehidi; Ramos, Brian; Guiblet, Wilfried; Afanador, Yashira; Ruiz-Rodriguez, Christina T.; Nickerson, Michael L.; Logue, David M.; Dean, Michael; Figueroa, Luis; Valentin, Ricardo; Martinez-Cruzado, Juan-Carlos Background: Amazona vittata is a critically endangered Puerto Rican endemic bird, the only surviving native parrot species in the United States territory, and the first parrot in the large Neotropical genus Amazona, to be studied on a genomic scale. Findings: In a unique community-based funded project, DNA from an A. vittata female was sequenced using a HiSeq Illumina platform, resulting in a total of ~42.5 billion nucleotide bases. This provided approximately 26.89x average coverage depth at the completion of this funding phase. Filtering followed by assembly resulted in 259,423 contigs (N50=6,983 bp, longest=75,003 bp), which was further scaffolded into 148,255 fragments (N50=19,470, longest=206,462 bp). This provided ~76% coverage of the genome based on an estimated size of 1.58 Gb. The assembled scaffolds allowed basic genomic annotation and comparative analyses with other available avian whole-genome sequences. Conclusions: The current data represents the first genomic information from and work carried out with a unique source of funding. This analysis further provides a means for directed training of young researchers in genetic and bioinformatics analyses and will facilitate progress towards a full assembly and annotation of the Puerto Rican parrot genome. It also adds extensive genomic data to a new branch of the avian tree, making it useful for comparative analyses with other avian species. Ultimately, the knowledge acquired from these data will contribute to an improved understanding of the overall population health of this species and aid in ongoing and future conservation efforts. Sherpa Romeo green journal. Open access article. Creative Commons Attribution 2.0 (CC BY 2.0) applies

Aggressiveness and size: a model and two tests Logue, David M.; Takahashi, April D.; Cade, William H. Individual variation in aggressive behavior in animals might be caused by adaptive covariation with body size. We developed a model that predicts the benefits of aggressiveness as a function of body size. The model indicated that individuals of intermediate sizes would derive the greatest benefits from being aggressive. If we assume that the cost of aggression is approximately uniform with respect to body size, selection should favor higher aggression in intermediate-sized individuals than in large or small individuals. This prediction was tested by stimulating male Madagascar hissing cockroaches, Gromphadorhina portentosa, with disembodied antennae and recording the males’ aggressive responses. Antennae from larger males evoked weaker responses in subjects, suggesting that males obtained information about their opponents’ size from the opponents’ antennae alone. After accounting for this effect, we found support for the key prediction of our model: aggressiveness peaked at intermediate sizes. Data from actual male-male interactions validated that the antenna assay accurately measured aggressiveness. Analysis of an independent data set generated by staging male-male interactions also supported the prediction that intermediate-sized males were most aggressive. We conclude that adaptive covariation between body size and aggressiveness explains some interindividual variation in aggressiveness. Sherpa Romeo green journal. Permission to archive final published version

Like many of you I’m working from home for a while. As a mental health strategy, I’m going to do some writing and coding in the hour or so I get back each day from not having to commute. The first post, which will follow today, will be my thoughts on working from home. I […]

Central bank oversight aims to boost confidence in financial network with 86m depositors

Slow response could turn coronavirus outbreak into humanitarian crisis

Work to reduce bad corporate loans at risk of setback as fears grow for consumers

Central bank governor calls for ‘war effort’ as coronavirus shuts down country

Network to provide 80,000 mobile beds after national lockdown shuts passenger services   

Demonstrations at a Mumbai railway station as people demand to return to their homes

Authorities aiming to head off turmoil after Franklin Templeton fund freeze

You've been hard at work optimizing your site. You've already done things like lazy-loading Google Maps and been wondering if there was anything else you could do. For example, is there anything we can do to improve the loading of ads? Good news, there is some things you can do. You can respect user's mobile data plan by loading ads only when they are likely to appear in the viewport zone. You can also serve ads in the right size in accordance to the screen of the device. That would be nice of you. That would not only be responsive but also responsible.

I've written an article on that and got it published on CSS-Tricks.

Read the article

Try the Demo

You can also examine the demo on CodePen and contribute, follow the project on GitHub.

My session driver of choice for CodeIgniter is database. A while ago, I noticed millions of rows in the corresponding database table. That means that garbage collector was not working. I checked config.php for sess_regenerate_destroy, but it was already set to false. It was really weird because the problem seemed to have come out of nowhere – not much ago things were working just fine.

After a short investigation, I found out this was and still is a common problem for those who had upgraded their CodeIgniter version from 2.x to 3.x. Turns out, the later possesses heavy changes for Sessions library. And most importantly – fundamental changes in dealing with garbage: CodeIgniter 3.x relies on PHP's native grabage collector. So, in order to get things working again, we need to configure PHP properly.

The Solution

Today there are three PHP-native settings for dealing with session garbage collector. CodeIgniter's Session library has already taken care of one of them – gc_maxlifetime – so there's no need for an extra touch here. The problem lies within the rest: session.gc_probability and/or session.gc_divisor. These two determine when the garbage collector is running. Here's what php.net says:

session.gc_divisor coupled with session.gc_probability defines the probability that the gc (garbage collection) process is started on every session initialization. The probability is calculated by using gc_probability/gc_divisor, e.g. 1/100 means there is a 1% chance that the GC process starts on each request.

In my case, using ini_get() revealed the following values: 0 and 1000. The equation 0/1000=0 meant there was no chance the garbage collector would even run.

Finally, I solved the problem by using the values officially stated as default and by putting the following lines of PHP code into config/config.php file:

ini_set( 'session.gc_probability',	1 );
ini_set( 'session.gc_divisor',		100 );

Theoretically, this means that the garbage collector usually runs once every 100th request. It's more than enough, but it is up to you whether that causes too many unnecessary hits to database. An alternative solution for heavy-traffic websites could be having a 0% probability on the production site and a Cronjob-based script which removes database rows of the expired sessions.

Lately, I've been obsessed with optimizing performance through lazy-loading. Recently, I've written on how to lazy-load Google Maps and on how to lazy-load responsive Google Adsense. Now it's time for Disqus, a service for embedding comments on your website. It's a great service. It eliminates the headache of developing your own local commenting system, dealing with spam, etc. Recently, I've been working on implementing the widget in one of my projects.

I've written an article on that and got it published on CSS-Tricks.

Read the article

Try the Demo

You can also contribute, follow the project on GitHub.

Hayden Library - TA418.9.N35 N396 2012

Hayden Library - TA418.9.N35 I5737 2013

Hayden Library - TP248.25.N35 M46 2013

Hayden Library - T174.7.R42 2012

Barker Library - T174.7.M63 2011

Barker Library - TK7874.85.N365 2012

Hayden Library - T174.7.P46 2012

Hayden Library - T174.7.C459 2011

Hayden Library - QC176.8.N35 A387 2013

Hayden Library - T174.7.N79 2013

Hayden Library - TA418.9.N35 I5685 2012

Hayden Library - TA418.9.N35 S967 2012

Barker Library - QC176.8.N35 C43 2013

Hayden Library - T174.7.P665 2012

Barker Library - QC176.8.N35 N35 2013

Hayden Library - QC176.8.N35 I575 2011

Hayden Library - TA418.9.N35 I56 2013

Hayden Library - QC176.8.N35 C372 2011