Why doesn't Phylobayes run?

[Fabiola Sepulveda]

Task\ label=Phylobayes Polyopisto 29-10-2024
Task\ ID=3155174
Tool=PHYLOBAYES_XSEDE
created\ on=2024-10-29 18:35:31.0
JobHandle=NGBW-JOB-PHYLOBAYES_XSEDE-CA49620E37C743A08F18EAA709B75FED
RunNumber=1
resource=expanse
User\ ID=170593
User\ Name=meoliva
email=marcel...@uantof.cl
Output=(ALL_FILES,*,UNKNOWN,UNKNOWN,UNKNOWN)
ChargeFactor=1.000000
cores=48
JOBID=34742292

Thanks

Fabiola

[Miller, Mark]

Hi Fabiola,

We are investigating this.

It seems likely that there was an issue with the node.

You can try cloning and resubmitting while we investigate if you like.

I will credit your account for any time lost.

Mark

--
You received this message because you are subscribed to the Google Groups "CIPRES Science Gateway Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cipres-science-gatew...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/cipres-science-gateway-users/7ae382de-4b34-431f-bca2-988dc461764en%40googlegroups.com.

[Mark Miller]

Hi again,

We confirmed this was an error with the machine here.

I will credit your account, and you should just clone and resubmit.

Let me know if you get another failure.

Best,

Mark

[Fabiola Sepulveda]

Dear Mark Miller,

Thank you very much for your help. I have successfully cloned the job and re-ran the analysis. However, one of the output files (stderr) indicates that the job was cancelled due to time limit.

If I clone the task again, will the program resume where it left off?

Task\ label=Phylobayes Polyopisto 29-10-2024 V2

Task\ ID=3156579

Tool=PHYLOBAYES_XSEDE

created\ on=2024-11-02 07:09:06.0

JobHandle=NGBW-JOB-PHYLOBAYES_XSEDE-BDB5A9E0F2A641DDA5ECDECB7DBA703B

RunNumber=1

resource=expanse

User\ ID=170593

User\ Name=meoliva

email=marcel...@uantof.cl

Output=(ALL_FILES,*,UNKNOWN,UNKNOWN,UNKNOWN)

ChargeFactor=1.000000

cores=48

JOBID=34816305

Also, I would like to tell you that the account is new and I have only processed two tasks (one with 6 and one with 12 hrs), and the hours I have left are 423 CPU hours.

Thank you for your support

Best regards

Fabiola

To view this discussion visit https://groups.google.com/d/msgid/cipres-science-gateway-users/ca75acac-8177-4afe-8842-7fdb9399f822n%40googlegroups.com.

--

"El cerebro es como un paracaídas, no funciona si no se abre"

[Miller, Mark]

Hi Fabiola, 

The best way to continue the run is to click the “restart” buttonnnrxt to the “clone” button.

That should continue your job. 

I will check the time.

Mark

On Nov 4, 2024, at 5:55 AM, Fabiola Sepulveda <fabio...@gmail.com> wrote:



[Miller, Mark]

Hi again,

 

Unfortunately, Phylobayes is a fairly slow and compute-intense code.

Your run of 12 hours used 48 cores, so the total charge for the run was 12 x 48 = 576 hours.

The run so far ran 35017 iterations, and you can only get about another 8 hours of run time using PhyloBayes.

 

If you need a Bayesian code, you could try MrBayes which is much faster, if it offers the tools you need..

Let me know if you have further questions.

 

Mark

[Fabiola Sepulveda]

Hi Mark,

I understand what you are saying about the time used. I really appreciate your help, however I need to finish the Phylobayes analysis but I don't know if I can resume the analysis at the point where it stopped after 12 hours of running; and if the time I have left (423 CPU) will be enough to finish the analysis.

I appreciate any help that can clarify the execution of the task.

Best regards 

F