Quantcast
Channel: CosmoCoffee
Viewing all articles
Browse latest Browse all 171

Computers and software • CosmoMC: Run stopped after some time

$
0
0
Hello ,

I am trying to run cosmomc on a cluster having Ubuntu 20.04 gfortran version 9.4.0. The MPI version is mpiexec (OpenRTE) 4.0.3.
I ran with test.ini. The run time for this was OK and chains converged.
I am using command

Code:

nohup mpiexec -np 4 ./cosmomc test_planck.ini >output.txt 
But when I am running it for natural inflation chains have been stopped after 3 hours without any error. I ran cosmomc again with standard case but this time Cosmomc ran only 2 minutes and stopped without any error.
I have free memory as

Code:

              total        used        free      shared  buff/cache   availableMem:           15Gi       1.2Gi       3.4Gi       7.0Mi        10Gi        13GiSwap:         4.0Gi       5.0Mi       4.0Gi
The configuration of my system is

Code:

Architecture:                       x86_64CPU op-mode(s):                     32-bit, 64-bitByte Order:                         Little EndianAddress sizes:                      42 bits physical, 48 bits virtualCPU(s):                             32On-line CPU(s) list:                0-31Thread(s) per core:                 1Core(s) per socket:                 8Socket(s):                          4NUMA node(s):                       4Vendor ID:                          GenuineIntelCPU family:                         6Model:                              63Model name:                         Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHzStepping:                           2CPU MHz:                            2294.686BogoMIPS:                           4589.37Hypervisor vendor:                  VMwareVirtualization type:                fullL1d cache:                          128 KiBL1i cache:                          128 KiBL2 cache:                           1 MiBL3 cache:                           180 MiBNUMA node0 CPU(s):                  0-7NUMA node1 CPU(s):                  8-15NUMA node2 CPU(s):                  16-23NUMA node3 CPU(s):                  24-31Vulnerability Gather data sampling: Not affectedVulnerability Itlb multihit:        KVM: VulnerableVulnerability L1tf:                 Mitigation; PTE InversionVulnerability Mds:                  Vulnerable: Clear CPU buffers attempted, no                                     microcode; SMT Host state unknownVulnerability Meltdown:             Mitigation; PTIVulnerability Mmio stale data:      Vulnerable: Clear CPU buffers attempted, no                                     microcode; SMT Host state unknownVulnerability Retbleed:             Not affectedVulnerability Spec store bypass:    VulnerableVulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __u
I will be grateful if someone can let me know how I can solve the issue.

Thanks
Saisandri

Statistics: Posted by Saisandri Saini — January 28 2025



Viewing all articles
Browse latest Browse all 171

Trending Articles