-
ERROR: no input files specified
-
ERROR: Failed to locate input file
-
ERROR: Failed to find files
ERROR: File globs match no files
-
Indicates failure to locate specified sms input files.
-
Check that you have the correct value for the input parameter under [Global] in your run.conf file.
-
Check that you have read and write permissions for the input files you specified (be sure you check this using the same user account as you are using when trying to run the pipeline).
-
ERROR: FlowcellChannelList: flowcell has channel out of range
ERROR: FlowcellChannelList has flowcell out of range
-
Check that the channels parameter under [Global] in your run.conf file is properly formatted and that the flowcells are in range [1,2] and the channels are in range [1,25].
ERROR: No file found containing data for flowcell and channel
-
Check that the channels parameter under [Global] in your run.conf file is properly formatted.
-
Check that you have not specified a channel/flowcell combination that doesn’t exist in your set of input sms files(run smsls — brief on these files to determine avaialble flowcells/channels)
ERROR: files <file1> and <file2> both have info for flowcell and channel
-
The same flowcell and chennel specification were found in two input files
ERROR: MultiChannel SMS files are not allowed
-
Multichannel sms files are not allowed as an input to the pipeline being run
ERROR: flowcell or channel in <file> out of range (1-2:1-25)
-
<file> contains a bad flowcell/channel combination (verify with smsls --brief)
ERROR: pypeline.smsInfo(): make sure smsls --brief <file> runs on command line
-
smsls --brief could not be run successfully on <file>
-
Check that you have permissions to read <file> (do this suing same user account as you are using when trying to run the pipeline)
-
Try to run smsls --breif from command line to verify that sms file is not corrupted
printConfigFile: ERROR: some required parameters have value None
-
Run pipeline with --pypeline-help parameters
-
Verify that you have specified all the Global parameters in the [Global] section of your run.conf file
ERROR: User environment variable HELICOS_ANALYSIS_HOME is not set
-
Set $HELICOS_ANALYSIS_HOME to location where helisphere has been installed
-
(You can do this by executing source <helisphere_install_dir>/helicos.bashrc on commandline)
ERROR: User environment variable HELICOS_TMPDIR is not set
-
Set $HELICOS_TMPDIR to desired location
-
(You set it to /tmp by executing source <helisphere_install_dir>/helicos.bashrc on commandline)
-
ERROR: <helicos_analysis_home> either is not accessible, readable or executable for current user
ERROR: <helicos_tmpdir> either is not accessible, readable or writable for current user
-
The value of HELICOS_ANALYSIS_HOME or HELICOS_TMPDIR is not readable or writable
-
Try executing the command source <helisphere_install_dir>/helicos.bashrc from the command line
*ERROR: OperationalError: database is locked
-
This often happens when running on an incorrectly configured NFS file system. Try starting the lockd and rpc.statusd daemons.