The attachments are the same order as they appear in the list you submitted. The following command line was used to begin the simulation:# modify parameter file for smaller memory footprint using sed sed '/CoordBase::d[xyz]/s/8/12/' <par/static_tov.par >par/static_tov_small.par # start simulation, watch log output ./simfactory/bin/sim submit static_tov --parfile=par/static_tov_small.par --procs=1 --walltime=8:0:0 ./simfactory/bin/sim show-output --follow static_tovI hope this looks right when I submit it. I appreciate the effort on your part to determine the cause of the difficulty.
On Friday, May 5, 2017 2:10 AM, Ian Hinder <[email protected]> wrote:
On 5 May 2017, at 09:04, Robert Kopp <[email protected]> wrote:
> I'm doing it over and I'm going to let it run overnight. (Why not?)
> From the run currently in progress, PID #3297 is the only process directly
> related to cactus_sim. According to the system monitor, it shifts back and
> forth among the eight CPUs, so that one of them at a time gets 100% of the
> load. (I note that the Ubuntu system monitor designates them 1-8, whereas it
> is more common for CPU numbers to begin with 0, but that probably is of no
> significance.)
>
> And static_tov.out will be a very large file (~600k, too large for the
> archive). The segment of interest for the run completed earlier today looks
> like this:
>
> INFO (Carpet): MPI is enabled
> INFO (Carpet): Carpet is running on 1 processes
> INFO (Carpet): This is process 0
> INFO (Carpet): OpenMP is enabled
> INFO (Carpet): This process contains 1 threads, this is thread 0
> INFO (Carpet): There are 1 threads in total
> INFO (Carpet): There are 1 threads per process
> INFO (Carpet): This process runs on host robert-desktop, pid=6474
> INFO (Carpet): This process runs on 8 cores: 0-7
> INFO (Carpet): Thread 0 runs on 8 cores: 0-7
>
> The corresponding file for the present run will be finished about 6AM PDT. I
> can send it to anyone who would like to look at the complete file, even if it
> cannot be distributed through this list.
Hi,
It's not worth running the entire simulation; the above output already says it
is only running on one thread. So, for some reason, only one thread is being
created. Can you post the files
static_tov/SIMFACTORY/run/RunScript
static_tov/output-0000/SIMFACTORY/RunScript
static_tov/SIMFACTORY/properties.ini
static_tov/output-0000/SIMFACTORY/properties.ini
your <machine>.ini file, and the full command line that you used to submit the
simulation?
--
Ian Hinder
http://members.aei.mpg.de/ianhin
RunScript
Description: Binary data
RunScript
Description: Binary data
properties.ini
Description: Binary data
properties.ini
Description: Binary data
robert-desktop.ini
Description: Binary data
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
