-
Notifications
You must be signed in to change notification settings - Fork 123
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
HELP: call-xcor fails with TEST command #284
Comments
I just realized that my installed R/R-base in encd-chip-spp is v3.2.2, and the startsWith function is added at R 3.3. This should be the reason for errors in call-xcor. But I would like to further ask if there are any solutions to upgrade R/R-base in this pipeline under the system I indicated. I've tried to arbitrarily update R version in encd-chip-spp environment, but it reports lots of conflicts. |
It works fine with Please check (encd-chip-spp) leepc12@ubuntu:~/code/chip-seq-pipeline2/scripts$ conda list | grep r-spp
r-spp 1.13 r3.2.2_0 bioconda Please try with Singularity ( |
@leepc12, thanks for your valuable suggestions. |
Describe the bug
When running the newest pipeline (v2.2.0) with TEST command
caper run chip.wdl -i https://storage.googleapis.com/encode-pipeline-test-samples/encode-chip-seq-pipeline/ENCSR000DYI_subsampled_chr19_only.json --conda
, it returns errors due tocould not find function "startsWith"
atxcor
steps.I noticed that many issues related to
xcor
reported can be fixed by re-installing and -installing. But I tried several times, it still can not fix this issue.In addition, when running the newest encode-atac-seq-pipeline with TEST command, I obtained the same error.
Note
python=3.8.13
,java=17.0.3.1
andpip=22.1.2
are installed locally, andcaper
is installed based these.OS/Platform
Caper configuration file
Paste contents of
~/.caper/default.conf
.Input JSON file
Paste contents of your input JSON file.
Troubleshooting result
If you ran
caper run
without Caper server then Caper automatically runs a troubleshooter for failed workflows. Find troubleshooting result in the bottom of Caper's screen log.If you ran
caper submit
with a running Caper server then first find your workflow ID (1st column) withcaper list
and runcaper debug [WORKFLOW_ID]
.Paste troubleshooting result.
The text was updated successfully, but these errors were encountered: