#1 Error in running peca on command line, std::runtime_error
Hello,
I am trying to run Peca from the command line in a unix platform, but am receiving the following error message after submitting the . peca command (or using bash peca). I have encountered this issue both with the sample data included with the .tar download and with my own data files. Do you have any suggestions for how to I could solve this issue?
This is the first error message: '"11000terminate called after throwing an instance of 'std::runtime_error'
what(): can't open s_xRyD
peca: line 5: 28493 Aborted ../bin/peca ../input"
Thank you!
Amanda Guise
(Steen Lab, Boston Children's Hospital)
Error message:
The output (if any) follows:
g++ -Wall -O3 -I. -std=c++0x -c -o src/Pre.o src/Pre.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/Mcmc.o src/Mcmc.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/main.o src/main.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/data.o src/data.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/Option.o src/Option.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/print.o src/print.cpp
g++ -Wall -O3 -I. -std=c++0x -c -o src/Module.o src/Module.cpp
g++ src/Pre.o src/Mcmc.o src/main.o src/data.o src/Option.o src/print.o src/Module.o -o bin/peca
nprot = 1508
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
10000
11000terminate called after throwing an instance of 'std::runtime_error'
what(): can't open s_xRyD
peca: line 5: 28493 Aborted ../bin/peca ../input
real 10m25.866s
user 10m25.916s
sys 0m0.079s
Read 0 items
Error in file(file, "rt") : cannot open the connection
Calls: read.table -> file
In addition: Warning message:
In file(file, "rt") : cannot open file 's_tau2': No such file or directory
Execution halted
real 0m0.474s
user 0m0.300s
sys 0m0.054s
rm: cannot remove s_*': No such file or directory
rm: cannot removemean_*': No such file or directory
Hi Amanda Guise,
Can you check that you have enough disk space before running peca? Let me know how it goes.
Best,
Gs
Hello,
Thank you so much for your reply! I am not sure what the exact issue was, but running it in an interactive shell seemed to solve the problem.
Thank you!
Amanda