Hi all,
I’m working on making RNA-seq reanalysis more reproducible and recently reproduced a published rice salt-alkali stress RNA-seq study starting from the raw FASTQ files.
Dataset: PRJNA895747
Study context: Rice seedlings under Na2CO3 salt-alkali stress, with untreated controls. The dataset has 12 paired-end RNA-seq samples across 4 groups with 3 biological replicates each.
Workflow used:
- adapter and quality trimming
- read alignment
- gene-level quantification
- differential expression with DESeq2
- PCA, volcano plots, heatmaps
- functional interpretation / enrichment-ready gene lists
- full provenance capture, including parameters, software versions, outputs, and generated code
The goal was to test whether an automated bioinformatics AI agent could reproduce the main biological signal from a published study without manual pipeline tuning.
Disclosure: I’m affiliated with Pipette.bio, which is the tool used for this run.
I’m looking for critique from people who run RNA-seq analyses regularly.
I’d especially appreciate feedback on:
- Are these workflow choices reasonable for this dataset?
- What QC checks would you require before trusting the differential expression results?
- When reproducing an older RNA-seq study, how much difference in DEG counts would you consider acceptable if references, software versions, and filtering choices differ?
- What would you want to see in a provenance report before considering an automated reanalysis credible?
Writeup: https://pipette.bio/blog/reproducing-rice-salt-stress.html
Use case report: https://pipette.bio/use-cases/rice-salt-stress.html
Original study: https://pmc.ncbi.nlm.nih.gov/articles/PMC9840837/
Thanks for any feedback. I’m particularly interested in whether the workflow/provenance is enough for a reviewer or collaborator to evaluate the result without rerunning everything from scratch.
0 answers
No answers yet.
Log in to answer this question.
If you are not using the same software/versions as the original then you are essentially redoing the analysis. I don't think comparing counts would be very meaningful. Looking at the overall results and inferences (e.g. in terms of pathway analysis etc) may be the way to go.
If you wanted to announce the tool then it would have been better to create a
toolspost enumerating the features of the tool, rather than asking about reanalysis of a published dataset.We used the same software as the original study and compared the absolute number of DEGs identified by the agent to those reported in the paper. The results are slightly off, perhaps due to slightly different software versions. This question naturally came by as we are tightening our workflows and skill docs.
You are right about the tools post. My mistake I listed this as a tool post.
Thanks!