Subio Platform uses fastp for FASTQ file preprocessing and Kallisto or HISAT2–StringTie for expression quantification. If an error occurs during processing, first check the execution log to identify which step caused the problem.
1. Check run.log
A temporary folder is created inside the folder containing your FASTQ files.
The run.log file in this temporary folder
records information about pipeline execution and errors.
If the log has been compressed as run.log.gz,
decompress it before viewing its contents.
If the cause of an error is unclear,
you can upload run.log to an AI assistant such as ChatGPT
and ask it to help identify the cause and suggest possible solutions.
Providing additional information, such as your operating system,
the pipeline you are using, and the versions of the tools,
can help narrow down the problem.
However, AI-generated suggestions are not always correct.
In particular, before following instructions that involve deleting files
or resetting the execution environment,
make sure you understand what the operations will do and their potential consequences.
2. Check the Execution Environment and File Paths
Check the locations of the fastp, Kallisto, HISAT2, and StringTie executables, reference data, and FASTQ files. If any file paths contain spaces, Japanese characters, or special characters, try moving the files to folders whose paths do not contain these characters.
3. Check Disk Space and Memory
FASTQ processing requires sufficient disk space not only for input and output files but also for temporary files generated during processing. In particular, the HISAT2–StringTie pipeline may consume a large amount of disk space for intermediate files.
The amount of disk space required depends on the size of the FASTQ files, the number of samples, and the pipeline being used. Monitor available disk space and memory usage during processing.
Automatic backup programs, cloud synchronization services, and antivirus software may also interfere with files being accessed during processing. If the log suggests a file access problem, check whether any of these programs could be interfering with the pipeline.
4. Check the fastp Preprocessing Settings
fastp can automatically detect common adapter sequences, but it may fail to recognize adapters used in certain library preparation kits.
In such cases, check which adapter sequence was used and explicitly specify it in the fastp options. For example:
--adapter_sequence=AGATCGGAAGAGCACACGTCTGAACTCCAGTCA
If unwanted sequences remain in the reads after adapter trimming, you may need to adjust the length filtering or trimming settings.
However, forcing reads to a uniform length or applying overly stringent filtering criteria can reduce the number of reads available for analysis. It is important to check not only whether processing completes successfully, but also whether the resulting data are suitable for your analysis objectives.
For more information about fastp options, see the official fastp documentation.