Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to write to FIFOs #19

Open
splaisan opened this issue Feb 22, 2024 · 0 comments
Open

unable to write to FIFOs #19

splaisan opened this issue Feb 22, 2024 · 0 comments

Comments

@splaisan
Copy link

Hi,

although I can output to 8 chunks as fastq.gz files, when I create fifo using the same names, the split does not start.
Is there something intrinsic preventing the use of FIFOs for outputting the fastqsplitter chunks?

It would save me disk space to process the data from the FIFO as they are filled instead of creating chunks and then consuming them.

Thanks for your help

# works
fastqsplitter -i reads.fastq.gz \
  -o reads_chunk_1.fq.gz \
  -o reads_chunk_2.fq.gz \
  -o reads_chunk_3.fq.gz \
  -o reads_chunk_4.fq.gz \
  -o reads_chunk_5.fq.gz \
  -o reads_chunk_6.fq.gz \
  -o reads_chunk_7.fq.gz \
  -o reads_chunk_8.fq.gz \
  -t 2

# does not work
mkfifo $(seq -f "reads_chunk_%g.fq.gz" 1 8)
fastqsplitter -i reads.fastq.gz \
  -o reads_chunk_1.fq.gz \
  -o reads_chunk_2.fq.gz \
  -o reads_chunk_3.fq.gz \
  -o reads_chunk_4.fq.gz \
  -o reads_chunk_5.fq.gz \
  -o reads_chunk_6.fq.gz \
  -o reads_chunk_7.fq.gz \
  -o reads_chunk_8.fq.gz \
  -t 2

# nothing happens and the FIFOs remain empty if interrogated with zcat
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant