<div dir="auto">This happens on the laptop that I autofigured by following the tutorial.<div dir="auto">After the warning the the job has been started I think the issue is that the memory has been killed and it stops further processing of the simulation.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 30 Mar 2022, 4:35 am Roland Haas, <<a href="mailto:rhaas@illinois.edu">rhaas@illinois.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Nisa,<br>
<br>
> When I submit my simulation<br>
> %%bash<br>
> # start simulation segment<br>
> ./simfactory/bin/sim submit NH --cores=1 --ppn-used=8 --walltime=0:2:00<br>
> Also tried this %%bash<br>
> <br>
> ./simfactory/bin/sim submit NH --cores=2 --num-threads=1 --walltime=0:20:00<br>
> again it gives the same warning<br>
> it gives the warning that Total number of threads and number of cores per<br>
> node are inconsistent: procs=1, ppn-used=8 (procs must be an integer<br>
> multiple of ppn-used)<br>
> and after that when i run the parameter file it does not run completely and<br>
> shows only half or more than half output.<br>
> How can I resolve this issue so that I get the complete output.<br>
<br>
If there is output missing then most likely the job was killed by the<br>
queuing system since it ran out of walltime. Note that the first<br>
command requested only 2 minutes of walltime which is almost certainly<br>
too short for any "real" run.<br>
<br>
Usually this will show up at the bottom of the *.err file.<br>
<br>
You can either let simfactory print both the *.out and the *.err file<br>
to screen (or pipe into less) using:<br>
<br>
./simfactory/bin/sim show-output NHÂ | less<br>
<br>
or query where the simulation output directory is:<br>
<br>
./simfactory/bin/sim get-output-dir NH<br>
<br>
then use cd to go there and less to take a look at the err file.<br>
<br>
The other option is that the job hung, which will usually also show up<br>
as the queueing system killing your run due to it running out of<br>
walltime, but also will typically mean that the last output (timestamp<br>
of the output files eg *.asc visible via ls -l) is much older than the<br>
time the job was killed by the queuing system.<br>
<br>
If there is no queueing system (laptop) then something else could kill<br>
the job (eg runs out of memory).<br>
<br>
The warning about ppn-use is due to inconsistent options. Namely you<br>
are claiming via ppn-used=8 to use 8 cores per node but then are<br>
requesting only 1 core. It is just a warning though, if the job started<br>
then you do not have to worry. If you would like to avoid the warning<br>
you could use --cores 1 --ppn-used 1. Does his happen on a cluster<br>
(private? One officially supported by the ET?)? Or you laptop that you<br>
auto-configured via "sim setup-silent" or on the tutorial server?<br>
<br>
Yours,<br>
Roland<br>
<br>
-- <br>
My email is as private as my paper mail. I therefore support encrypting<br>
and signing email messages. Get my PGP key from <a href="http://keys.gnupg.net" rel="noreferrer noreferrer" target="_blank">http://keys.gnupg.net</a>.<br>
</blockquote></div>