Following the publication of the original article [1], it was reported that the accession number given in the 'Data accessibility' declaration, GSE65696, is incorrect.