Stern, Ernst, 1876-1954

Krasner, David, 1952-

Spatz, Ben, author

Home-Cook, George, 1975- author

Kelleher, Joe, author

Ewing, Robyn (Robyn Ann), 1955- author

Krishnan, Sarasa, author

Shurtleff, Michael, author

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

Radical thinking and structural reforms are necessary but scant

Migrant workers head home in battle to survive after losing jobs 

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.

Hayden Library - TA418.9.N35 S54 2011

Dewey Library - T174.7.D745 2013

Hayden Library - TA418.9.N35 I5685 2012

Barker Library - TP248.25.N35 H93 2012

Online Resource

Barker Library - T174.7.S64 2014

Barker Library - T174.7.I59 2013

Hayden Library - T174.7.C668 2015

Hayden Library - T174.7.C459 2012

Online Resource

Hayden Library - T174.7.R64 2015

Hayden Library - T174.7.N347 2015

Online Resource

Barker Library - T174.7.N37347 2019

Barker Library - T174.7.D87 2019

London : Academic Press, 2020.

Now, getting a licence for a fire-arm or operating an eatery will be easy with Delhi Police on Tuesday launching a dedicated website for its Licencing Branch.

The refugee question in the Indian subcontinent dates back to 1947 when India was partitioned. A horrifying feature of the birth of free India – and Pakistan – was the large mass of refugees who were forced to relocate in the most adverse conditions and amidst brutal violence.