Hi!
Is there are pre-compiled version of Commander on the Fram cluster? If so, could somebody please post a path to it?
Thanks!
Hi!
Yes, there is. Both latest version of commander3 and its data folders are available on Fram here:
/cluster/projects/nn9524k/BeyondPlanck
I compile using Make file. While I am running I get the following error :
/mnt/home/student/cdebabrata/softwares/commander3/Commander/commander3/src/commander: error while loading shared libraries: libimf.so: cannot open shared object file: No such file or directory
Ok, I forgot to load the intel library. That is resolved.
New issue:
Min/Max core weight = 0.782722731877571 1.00930237546250
HDF5-DIAG: Error detected in HDF5 (1.10.5) MPI-process 0:
#000: H5F.c line 509 in H5Fopen(): unable to open file
major: File accessibilty
minor: Unable to open file
#001: H5Fint.c line 1498 in H5F_open(): unable to open file: time = Wed Nov 25 10:16:32 2020
, name = ‘input/l2data/LFI_030_000128.h5’, tent_flags = 0
major: File accessibilty
minor: Unable to open file
It looks like the file doesn’t exist. Can you check that the path is correct?
input/l2data/LFI_030_000128.h5
This should be relative to the work directory in which you run the code
No file is there:
ls input/L2Data/LFI_030_000128.h5
What does ls -l input/l2data/LFI_030_000128.h5 return? And h5ls input/l2data/LFI_030_000128.h5?
ls -l input/l2data/LFI_030_000128.h5
-rw-r–r-- 1 cdebabrata expert 55231115 Nov 24 20:09 input/l2data/LFI_030_000128.h5
h5ls input/l2data/LFI_030_000128.h5
001319 Group
001320 Group
001321 Group
001322 Group
001323 Group
001324 Group
001325 Group
001326 Group
001327 Group
001328 Group
001329 Group
001330 Group
001331 Group
001332 Group
001333 Group
001334 Group
001335 Group
001336 Group
001337 Group
001338 Group
001339 Group
001340 Group
001341 Group
001342 Group
001343 Group
001344 Group
001345 Group
001346 Group
001347 Group
001348 Group
001349 Group
001350 Group
001351 Group
001352 Group
001353 Group
001354 Group
001355 Group
common Group
Can you try setting up a filelist with only two scans, one frequency and one core, and see if that works? We want a minimal debug case.