Skip to content

Validate entire raw-read files #7187

Description

@theosanderson-agent

The raw-reads-processing service currently invokes ENA ReadTools in quick mode, which validates only the first 100,000 reads per file. Malformed records occurring later may therefore go undetected.

Deacon subsequently reads the complete files and detects some structural failures, but it does not necessarily enforce every ReadTools check.

ReadTools provides --full. But it also sizes internal Bloom filters according to that larger limit, substantially increasing memory usage.

In a local benchmark using the deployed ReadTools jar, a 43 MB paired input used:

Mode Runtime Peak RSS
Quick 1.37s 0.55 GB
Full 2.34s 2.2 GB

We should investigate a resource-efficient way to validate entire files.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    depositionrelated to ENA/INSDC depositionpreprocessingIssues related to the preprocessing component

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions