clarify replicateName: biological or technical #110

Activity

1. kelly-sovacool

   assigned

   kopardev

   on Mar 23, 2026
2. github-actions

   added

   ASPENRepoNameRepoName

   on Mar 23, 2026
3. kelly-sovacool

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Mar 23, 2026
4. kelly-sovacool

   added this to the 2026-04 milestone on Mar 25, 2026
5. kelly-sovacool

   modified the milestones: 2026-04, 2026-05 on Apr 28, 2026
6. kopardev

   added a commit that references this issue on Aug 21, 2026

   docs(deployment): clarify biological vs technical replicates in sampl…

   ...

   18bbd7b
7. kopardev commented on Aug 21, 2026

   

   kopardev

   on Aug 21, 2026

   Contributor

   More actions

   Addressed in commit 18bbd7b on branch issue_117, folded into PR #120.

   Changes in docs/deployment.md:

   • replicateName now explicitly says biological replicate, not just "unique identifier"
   • sampleName clarified as the condition/group label shared across biological replicates
   • Added a !!! warning admonition explaining the biological vs technical replicate distinction, with a table and a cat example for merging lanes before running ASPEN
   • Clarified that DESeq2 requires biological (not technical) replicates

   To confirm: replicateName = biological replicate. Technical replicates (multiple lanes/runs from the same library) must be concatenated by the user before creating the manifest — ASPEN does not merge lanes internally.

   _{⚡ Generated using AI ⚡}
8. kopardev

   closed this as completedin #120on Aug 26, 2026