Closed karlkashofer closed 2 years ago
The error message claims that AriocP cannot open the configuration file at ./AriocP.cfg
. This error appears when AriocP does not find a configuration file specification on the command line and then tries to open a default configuration file in the current working directory,
My approach to troubleshooting this would be simply to invoke AriocP interactively from within a shell executing inside the Docker container. If you can verify that the configuration file is indeed where it's expected to be (e.g., by executing cat /path/to/AriocP.cfg
) then it should be clear whether the problem lies with the command line file specification or with some anomaly within AriocP's file-open implementation.
OK, it was my mistake. The SAMtags feature we built for Agilent XT libraries <dataIn sequenceType="Q" QNAME="(*)\t*" SAMtags="*\t(*)">
leads to corrupt data when there are not tabs in the fastq names.
I need to do separate encoding setups for normal fastqs and Agilent XT preprocessed fastqs.
Sorry for the false alarm, cheers, KK
Dear Richard ! I run AriocP in a docker container. This seems to be broken in releases after 2021-11-06. Releases after that produce a segfault and coredump immediately after loading the LUTs.
Any idea what to do ? Do you know what changed ? Cheers, KK