Hi Heidi,
Sorry, we don't have a SLURM environment for any rigorous testing, so we
just use "sbatch" for submitting jobs by default. We use some default flags
for job names ("-J") and files for the output/error logs ("-o", "-e"), but
other than that, the job submission step is not really customizable.
When you say that the job took a while to start, do you mean that the
Phenix jobs showed up in the queue (by checking "squeue -u <user name>"),
but was in the pending state ("PD") instead of the running state ("R")? Or
does the job take a while to even show up in the queue?
Lastly, for the output to show up in the GUI, did the jobs finish
successfully? If you restart the GUI and try to restore the job after it
finished, do you see any output? For example, in phenix.refine, you should
see graphs for the progress and some final statistics. Another thing to
check is the hidden directory in the project directory that stores
information for the GUI. Again, for phenix.refine, if that is your first
job, you would see 3 files (refine_1.eff, refine_1.log, and refine_1.pkl)
in your "<project directory>/.phenix/project_data" directory. The number
just refers to the job number. If those files are not there, the GUI cannot
update.
--
Billy K. Poon
Research Scientist, Molecular Biophysics and Integrated Bioimaging
Lawrence Berkeley National Laboratory
1 Cyclotron Road, M/S 33R0345
Berkeley, CA 94720
Tel: (510) 486-5709
Fax: (510) 486-5909
Web: https://phenix-online.org
On Tue, Sep 5, 2017 at 1:12 PM, Heidi Schubert
Hi
Has anyone successful submitted phenix jobs to a SLURM batch queue?
I guess, in theory, I did successfully submit a job but it took a while to start and after completion the log files did not successfully link back to the interface losing the graphic feedback.
I can’t tell how the job was submitted. Our submission command is sbatch, which is what I put in the Phenix Preference > Processes queue command. But locally we have a header on our sbatch submission which spells out our wall time, account and MPI expectations/requests. Is there an environment file that Phenix reads to provide this information or does it submit generically? I wondered if this was responsible for the long delay of the start of our job (sure – could have been a busy queue).
Anyone know how to get the GUI to read the output files when it loses connection to the run?
Heidi
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb Unsubscribe: [email protected]