When running the pipeline and providing the --vep_cache_version parameter, it will always be interpreted as integer instead of a string, which is the required input type for the parameter check. I've tested 108, '108' and "108".
A potential fix would be to redefine the expected input class of the parameter.
Description of the bug
When running the pipeline and providing the
--vep_cache_versionparameter, it will always be interpreted as integer instead of a string, which is the required input type for the parameter check. I've tested108,'108'and"108".A potential fix would be to redefine the expected input class of the parameter.
Command used and terminal output
No response
Relevant files
No response
System information
No response