Transcriptional Changes Fade Prior to Long-Term Memory for Sensitization of the <i>Aplysia</i> Siphon-Withdrawal Reflex.
The 2 matches
- [1] § Materials and Methods › Statistical analysis ↔ lts 5day - microarray script - preregistered.R, lines 43 to 82 · score 0.92 · empirical Bayes, LTS training, propTrueNull, regulated transcripts, moderated, posted · Report a mismatch
- [2] § Results › To what extent is regulation 1 d after sensitization preserved 5 d after training? ↔ lts 5day - microarray script - preregistered.R, lines 84 to 156 · score 0.68 · regulated genes, compared regulation, regulated transcripts, forgetting scores, split, preregistered · Report a mismatch
Paper
Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
R · 156 lines · 11 KB · no license · 2 matches
- #Analysis of LTS microarray data, 5 days after training
- # v1.1 - Bob Calin-Jageman, 3/3/2017
- # v1.1 - 3/3/2017 -- initial version for pre-registration, based on prior script for 1day analysis
- #Notes
- #This r script analyses differential expression for trained vs. untrained samples of pleural ganglia taken from
- # Aplysia 5 days after LTS training (4 shocks, 90mA of 0.5s on 0.5s off for 10s, 30min between shocks).
- # 16 Biological replicates were harvested. A two-color approach was used on a custom 8x60k Agilent microarray
- # Dye color was counterbalanced across conditions.
- # This script reads a design file, reads the agilent file, adjusts for background signal using normexp algorithm,
- # normalizes for dye intensity within each array, filters out control genes, then averages by probeset (for transcripts measured
- # multiple probes.
- # Next, this script tests a number of research questions about regulation of expression in this experiment.
- # Development of script--was based primarily on Limma user guide and this guide for two-color Agilent analysis:
- # http://matticklab.com/index.php?title=Two_channel_analysis_of_Agilent_microarray_data_with_Limma
- # with some additional help from the references cited below.
- # Decisions:
- # Median or mean signal? Zahurak et al. (2007) report the choice makes no practical difference in their analysis of Agilent
- # two-color arrays. Therefore, default of median was selected.
- # Background subtraction? Zahurak et al. (2007) report best results with no correction. However, in a more extensive comparison
- # Ritchie et al. (2007) report best results with normexp+offset for background correction.
- # Normexp offset? Offset needs to be empirically determined by inspection of MA plots, but analysis is not super-sensitive to
- # choice of offset value (k). Although Ritchie et al. used an offset of 50 based on their previous work, inspection of
- # MA plots of 15, 30, 50, and 100 show basically no from k=30-100. MAPlots for different
- # k values from this data set are in the MAPlots subfolder. k value is currently set to 30 based on a prior microarray
- # analysis, but will need to be set based on MAPlots from this 5 day data set, when available
- # Normalize Within Arrays? Zahurak et al. (2007) found best results for Agilent two-color with loess normalization. This also
- # seems to have become the standard within-array normalization strategy.
- # How to assess practical significance? Most statistical testing is done against an LFC of 0, which leads to some results
- # which are significant but not meaningful in terms of the magnitude of regulation. This can be fixed by a) adding an LFC
- # threshold after significance testing. Alternatively, McCarthy & Smith, 2009 recommend conducting statistical testing
- # against a more reasonable null hypothesis, thus testing for practical and statistical significance at the same time.
- # as using eBayes with an LFC of 0 resulted in many statistically significant but small differences between groups,
- # the approach of checking against a more rigorous null was used. Specifically, an LFC of 1.5 was selected (0.176).
- # At the end of the script, comments show how to do the LFC=0 approach for the null.
- #Setup
- # will need to setup directory to wherever microarray data is eventually posted
- # setwd("Z:/projects/2015 - LTS maintenance and decay - paired pleurals/LTS 1 week - microarray - paired pleurals")
- library(limma)
- #Read design and data
- # will need to setup targets file with correct file names and colors
- targets <- readTargets("targets.txt")
- RG <- read.maimages(targets, source="agilent.median")
- #Preprocessing
- RG <- backgroundCorrect(RG, method="normexp", offset=30)
- MA <- normalizeWithinArrays(RG, method="loess")
- write.table(MA, file="./output/GeoTable.txt")
- MA2 <- MA[MA$genes$ControlType==0,]
- MA2.avg <- avereps(MA2, ID=MA2$genes$GeneName)
- write.table(MA2.avg, file="./output/MA2Table_combined.txt")
- #Make the MAPlots
- for (i in 1:nrow(targets)) {
- jpeg(file=paste("./output/", targets$FileName[i]," - MAplot.jpeg", sep=""))
- plotMA(MA, i, status=MA$genes$ControlType)
- dev.off()
- }
- #Research questions:
- ## 1) How many of the 24h regulated transcripts are regulated at this time point?
- ## Transcripts persistently regulated from 24h to 5 day could be related to retention. Transcripts regulated in this pattern will be identified by reading the list of 24h transcripts and then comparing trained/untrained expression at 5 days within just this set of transcripts. The test will be a standard empirical Bayes t-test. Significant differences will be identified by testing against a null of at least 10% change in eaither direction with correction for multiple comparisons (B-H, FDR = 0.05).
- ## 1b) To what extent is regulation at 1 day similar to regulation at 5 days?
- ## Will use the genas function. In this case we will do a combined analysis across the 1day and 5day microarray data and then identify the degree to which the pattern of regulation at 1 day is preserved at 5 days. This will be done with the p_union switch to look only at the connection amongst regulated transcripts.
- ## 2) What transcripts are NEWLY regulated at this time point, 5 days after LTS training?
- ## Transcripts regulated at 5 day but not 1 day could represent transcripts related to active forgetting processes. This question will be addressed by running the same analysis as above (comparing trained/untrained) across the whole microarray WITHOUT the the list of 1-day regulated. This will identify *newly* regulated transcripts. Again the approach will be a simple comparison of trained to untrained expression, usin the moderated empirical Bayes t-test comparing the trained and untrained side. Significant differences will be identified by testing against a null of at least 10% change in either direction with correction for mulltiple comparisons (B-H, FDR = 0.05)
- ## 2a) How many missed NEWLY regulated transcripts?
- ## Will use the propTrueNull function with the convest approach to assess how many false negatives might have occured in the microarray less the 1day transcripts.
- ## 3) What transcripts might be related to the degree of forgetting?
- # Will examine transcripts that significantly predict forgetting scores
- ## Forgetting scores are calculated as log(T_1d/U_1d) - log(T_5d/U_5d)
- ## The first term represents sharpness of memory at 1 day. The second term represents sharpness of memory at 5 days. The difference represents amount of memory lost, with higher numbers indicating more forgetting. This analyis will add a term for forgetting and examine across the whole set of 5-day microarray data.
- ## 4) What happens to 5-day regulated transcripts at 7 days?
- ## Not in this script, but read the 7 day data, restrict down to 5-day regulated transcripts, and test for LFC>1.1
- ## In other words, repeat question 1 exactly but using 7 day data and the list of 5-day regulated genes
- ## 4a) How much of the pattern of regulation at 5 days is preserved at 7 days?
- ## Not in this script, but read 5 and 7 day data, use genas to examine correlation using p.union
- ## In other words, repeat analysis for question 1a but comparing 5 and 7 day data.
- ## Setup design matrix
- design <- modelMatrix(targets, ref="Control")
- design <- cbind(Dye=1, design)
- #Research question 1 (and same pattern for 4)
- # restrict down to just the transcripts that were up at 1h (or 7 days for question 4)
- restricted = read.csv("refined_24h.txt")
- MA2_restricted <- MA2.avg[MA2.avg$genes$GeneName %in% restricted$Transcripts, ]
- fit_restricted <- lmFit(MA2_restricted, design)
- regulated_restricted <- treat(fit_restricted, lfc=log2(1.1))
- regulatedTable_restricted <- topTreat(regulated_restricted, coef="Trained", number=nrow(regulated_restricted))
- write.table(regulatedTable_restricted, file="./output/LTS5day_retention_related_lfc1_10.txt")
- #Research question 2 - Test for significant FCs > log (1.1) only amongst genes not regulated at 1day
- MA2_unique <- MA2.avg[!(MA2.avg$genes$GeneName %in% restricted$Transcripts), ]
- fit_unique <- lmFit(MA2_unique, design)
- regulated_unique <- treat(fit_unique, lfc=log2(1.1))
- regulatedTable_unique <- topTreat(regulated_unique, coef="Trained", number=nrow(regulated_unique))
- write.table(regulatedTable_unique, file="./output/LTS5day_forgetting_related_lfc_1_10.txt")
- #Research question 2a
- propTrueNull(regulatedTable_unique$P.Value, method="convest")
- #Research question 3
- i <- targets$Cy5=="Control"
- #THis is the array of forgetting scores for the 16 arrays. Be sure it matches order of arrays.
- mscore <- c(0.443219007884632, 0.131376770816482, 0.639579778630896, 0.247227348439673, 0.622799920975808, 0.200682793496743, 0.937516492070804, 0.157722366671975, 0.620463296505017, 0.114347963363, 0.462221812522715, 0.163534611418199, 0.816323784510695, 0.281895301846058, 0.630446328710265, 0.380411562929875)
- mscore[i] = -mscore[i]
- design_cor <- cbind(design, mscore=mscore)
- fit_cor <- lmFit(MA2.avg, design_cor)
- regulated_cor <- treat(fit_cor, lfc=log2(1.1))
- regulated_cor_condition <- topTreat(regulated_cor, coef="Trained", number=nrow(regulated_cor))
- regulated_cor_retention <- topTreat(regulated_cor, coef="mscore")
- write.table(regulated_cor_condition, file="./output/LTS5day_corr_cond_lfc1_10.txt")
- write.table(regulated_cor_retention, file="./output/LTS5day_corr_retention_lfc1_10.txt")
- #Research question 1a
- ## Re-do script to read in not only 5 day but also 1 day data, each as own group, then use geneas function to compare regulation
- #Read design and data
- # will need to setup targets file with correct file names and colors
- ## !! This feels dangerous. Better to split this into a different script--it would be easy to not properly rename
- ## all the veriables for this analysis, and thus end up smooshing together this analysis with leftover portions
- ## of the other analyses.
- targets_comb <- readTargets("targets_compare_1d5d.txt")
- RG_comb <- read.maimages(targets_comb, source="agilent.median")
- #Preprocessing
- RG_comb <- backgroundCorrect(RG_comb, method="normexp", offset=30)
- MA_comb <- normalizeWithinArrays(RG_comb, method="loess")
- MA2_comb <- MA_comb[MA_comb$genes$ControlType==0,]
- MA2_comb.avg <- avereps(MA2_comb, ID=MA2$genes$GeneName)
- #Test for significant FCs > log (1.1)
- design_comb <- modelMatrix(targets_comb, ref="Control")
- design_comb <- cbind(Dye=1, design_comb)
- fit_comb <- lmFit(MA2_comb.avg, design_comb)
- regulated_comb <- treat(fit_comb, lfc=log2(1.1))
- genas(fit_comb, coef=c("h1", "h24"), subset="p.union", plot=TRUE, alpha=0.4)
- genas(fit_comb, coef=c("d1", "d5"), subset="p.union", plot=TRUE, alpha=0.4)
lts 5day - microarray script - preregistered.R, no license · at the source
Overview
Abstract
Forming a long-term memory requires changes in neuronal transcription. What happens, though, as the memory is forgotten? And how does the transcriptional state relate to the maintenance and recall of the long-term memory? To answer these questions, we have been systematically tracing the time course of transcriptional changes evoked by long-term sensitization in the marine mollusk Aplysia californica. Our approach captures transcriptional changes in neurons of known behavioral relevance using a within-subject design, delineating patterns of transcriptional change that are comprehensive and reproducible. We have previously reported that within 1 d of long-term sensitization training, there is a widespread transcriptional response involving robust changes in over 5% of tested transcripts (1,198 of ∼22 k; Conte et al., 2017). Within 1 week, however, memory strength fades, and nearly all transcriptional changes relapse to baseline ( Perez et al., 2018). Here we report microarray analysis (N = 16) of transcriptional changes 5 d postlearning, a time point when memory strength has weakened but is still robust. Remarkably, we found that at this intermediate behavioral stage, nearly all transcriptional changes have fully decayed, even in subsets of animals that have shown very little forgetting. Thus, most transcriptional changes seem to decay more rapidly than memory expression. We discuss several possible ways that memory expression could become decoupled from detectable transcriptional regulation.
Reproduced under the paper's license (CC BY), from the paper cited above.
Repositories
Its files are read in the Code ↔ Paper reader above, with 2 matches between paragraphs and lines of code.
OSF g3ueu
Availability: 1 check, the latest on 30 September 2026: the link answers (HTTP 200)
- 30 September 2026: the link answers (HTTP 200)
1 file
OSF ccwks
Availability: 1 check, the latest on 30 September 2026: the link answers (HTTP 200)
- 30 September 2026: the link answers (HTTP 200)
2 files
- behavior/
lts 5 day - behavioral analysis.R , R, 285 lines - lts 5day - microarray script - preregistered.R, R, 156 lines, 2 matches
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 2 repositories of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 3 scripts, each with its path and the digest of its content;
- 2 matches between paragraphs of the paper and lines of the code (method lexical-v1);
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
No dataset and no data link were found in the paper.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 30 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 4 authors, 5 keywords, 7 MeSH terms, 1 funder, 53 references.
Cite
This paper
Rosiles, T., Nguyen, M., Calin-Jageman, R. J., & Calin-Jageman, I. E. (2026). Transcriptional Changes Fade Prior to Long-Term Memory for Sensitization of the &
BibTeX
@article{rosiles2026tran
author = {Rosiles, Tania and Nguyen, Melissa and Calin-Jageman, Robert J. and Calin-Jageman, Irina E.},
title = {{Transcriptional Changes Fade Prior to Long-Term Memory for Sensitization of the \&
journal = {eNeuro},
year = {2026},
month = mar,
volume = {13},
number = {3},
pages = {ENEURO.0477--25.2026},
publisher = {Society for Neuroscience},
issn = {2373-2822},
doi = {10.1523/
url = {https://
pmid = {41802864},
pmcid = {PMC13064417}
}
RIS
TY - JOUR
AU - Rosiles, Tania
AU - Nguyen, Melissa
AU - Calin-Jageman, Robert J.
AU - Calin-Jageman, Irina E.
TI - Transcriptional Changes Fade Prior to Long-Term Memory for Sensitization of the &
T2 - eNeuro
J2 - eNeuro
PY - 2026
DA - 2026/
VL - 13
IS - 3
SP - ENEURO.0477
EP - 25.2026
SN - 2373-2822
PB - Society for Neuroscience
DO - 10.1523/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1523/
"type": "article-journal",
"title": "Transcriptional Changes Fade Prior to Long-Term Memory for Sensitization of the &
"container-title": "eNeuro",
"author": [
{
"family": "Rosiles",
"given": "Tania"
},
{
"family": "Nguyen",
"given": "Melissa"
},
{
"family": "Calin-Jageman",
"given": "Robert J."
},
{
"family": "Calin-Jageman",
"given": "Irina E."
}
],
"container-title-short":
"volume": "13",
"issue": "3",
"page": "ENEURO.0477-25.2026",
"DOI": "10.1523/
"PMID": "41802864",
"PMCID": "PMC13064417",
"ISSN": "2373-2822",
"publisher": "Society for Neuroscience",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
3,
27
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.12688/f1000research.146347.2 [code]
- Wings of Change: aPKC/
FoxP-dependent plasticity in steering motor neurons underlies operant self-learning in & lt;i& gt;Drosophila& lt;/ i& gt;. Journal: F1000ResearchIn common: ggplot2, tidyverse, other, 3 references - [2] doi:10.1038/s44318-025-00509-x [code]
- Proteomic aging signatures across mouse organs and life stages.Journal: The EMBO journalIn common: limma, ggplot2, tidyverse, 2 references
- [3] doi:10.1038/s41467-024-48048-z [code]
- Sex affects transcriptional associations with schizophrenia across the dorsolateral prefrontal cortex, hippocampus, and caudate nucleus.Journal: Nature communicationsIn common: limma, ggplot2, tidyverse, 2 references
- [4] doi:10.1016/j.isci.2025.113878
- PKA orchestrates long-range lysosomal vesicle transport during synaptic maintenance.Journal: iScienceIn common: 3 references
- [5] doi:10.3390/biology15040345 [code]
- Exploring Gene Expression Patterns in Alzheimer's Disease Using a Human Microarray Data Meta-Analysis.Journal: BiologyIn common: limma, tidyverse, 2 references
- [6] doi:10.1016/j.ynstr.2023.100514 [code]
- Transcriptional and cell type profiles of cortical brain regions showing ultradian cortisol rhythm dependent responses to emotional face stimulation.Journal: Neurobiology of stressIn common: limma, tidyverse, 2 references
- [7] doi:10.1093/g3journal/jkad050 [code]
- Cryptic genetic variation of expression quantitative trait locus architecture revealed by genetic perturbation in Caenorhabditis elegans.Journal: G3 (Bethesda, Md.)In common: 3 references
- [8] doi:10.1016/j.jbc.2022.102254 [code]
- Profiling 26,000 Aplysia californica neurons by single cell mass spectrometry reveals neuronal populations with distinct neuropeptide profiles.Journal: The Journal of biological chemistryIn common: other, 2 references
- [9] doi:10.1371/journal.pone.0304563
- Behavioral and genetic correlates of heterogeneity in learning performance in individual honeybees, Apis mellifera.Journal: PloS oneIn common: other, 2 references
- [10] doi:10.1371/journal.pcbi.1010239 [code]
- Computational analysis of memory consolidation following inhibitory avoidance (IA) training in adult and infant rats: Critical roles of CaMKIIα and MeCP2.Journal: PLoS computational biologyIn common: cognitive, 2 references
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 2 repositories of the authors' code, each at its verified commit and with its license, 3 scripts, and 2 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:bafa93b8045c6e40…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1523/eneuro.0477-25.2026)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1523/eneuro.0477-25.2026.svg
:target: https://openscicode.org/badge/doi/10.1523/eneuro.0477-25.2026
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1523/eneuro.0477-25.2026"><img src="https://openscicode.org/badge/doi/10.1523/eneuro.0477-25.2026.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
