Closed bostanict closed 7 years ago
please submit a ticket to PacBio Techsupport team. see this also https://github.com/PacificBiosciences/FALCON_unzip/wiki
Hi Jason,
So does it mean that we will not be able to ask questions via github anymore and must submit a ticket from now on or this is a specific case?
Thanks for any hint in advance~
This question needs more detailed investigation and it is not a development question. Also, it will be useful to make our product management/support team knowing you are solving an important problem that PacBio can help as a company. (If you know my email, send me one I will forward it to some people)
Thanks Jason,
Your help and other people in Pacbio is always instant and resolving. We came this far because of your technical and scientific support.
I did not know this is not a development issue since I am following the instructions ans saw the pipeline did not proceed to the end. I tough there might be some things that should be tweaked in the code.
I will make a ticket as you advised and see how it goes, Best
well, I like to thank your support. GitHub issues are supposed for discussion about code and possible design choices from development contributors. When a run fail, there are many possible reasons outside the scope of the code, e.g., environment and the data itself. Unless those are documented as well, it is hard to know what happens. I will advocate to have better way to help beside GitHub.
You'd have to look into the directories of those failed tasks to find stderr. (Maybe under pwatcher.dir/stderr.) Could be something simple. I've pushed some recent fixes too, in FALCON_unzip and in pypeFLOW.
Hi @pb-cdunn ,
Thanks a lot for the reply. I also already submitted a ticket to the technical support.
(Maybe under pwatcher.dir/stderr.)
before I run the unzip, I removed the pwacher directory as advised in another post. After I run the Unzip, this directory is not created any more...
find stderr
In the folders in 4-quiver, or the job is done and there is result, or there is the sh_done_exit or there is only the fasta file. I do not see any stderr or stdout file...
thanks alot
How up-to-date is your FALCON/FALCON_unzip/pypeFLOW?
What are the contents of the "exit" file for that job in mypwatcher/
? It should tell you the actual exit-code. Python might multiply by 256, but otherwise they should agree. If they don't, then the problem might be filesystem latency for the exit file, which we would have to address somehow.
I ran falcon_unzip:
!/bin/sh
fc_unzip.py fc_unzip.cfg; fc_quiver.py fc_unzip.cfg;
fc_unzip.py fc_unzip.cfg went ok and I got all the result in the 3-unzip folder when running the second part (fc_quiver.py fc_unzip.cfg), it creates the folder 4-quiver and the folders inside, starts running the sh files. after some of them are done, it runs into errors. our scheduler is SLURM and I specified it in the config file with the parameters as I used for falcon and worked.
here is the error:
I also re-ran the fc_unzip.sh but same errors occur.