Maik Nijhuis (46c6b3df) at 29 Mar 11:48
Update CI 20.04 test build
Maik Nijhuis (53706dcc) at 29 Mar 11:29
Update CI 20.04 test build
Maik Nijhuis (3e279d31) at 29 Mar 11:17
Increase test tolerance, since AVX results may differ slightly
... and 1 more commit
Maik Nijhuis (af7ae7e3) at 27 Mar 15:54
Avoid assignments to indexed 2x2 matrices
Maik Nijhuis (522e8d61) at 27 Mar 15:51
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (e30d408f) at 27 Mar 15:51
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (eb0e576b) at 27 Mar 15:36
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (63833c56) at 27 Mar 15:27
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (cdd0795b) at 27 Mar 15:18
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (8c6614f9) at 27 Mar 15:16
Run tests with AVX-enabled EveryBeam
Maik Nijhuis (ae769450) at 27 Mar 13:10
Disable -O3
Maik Nijhuis (88f5db98) at 27 Mar 12:31
Disable -O3
Try setting -pb-grid-size
to the width of your image. The default is 32, which is not good enough for a beam with a sharp edge.
Okay, deleting and rebuilding the folder helped. And I was able to successfully run wsclean with everybeam.
But the beam file produced after cleaning looks wonky
I am not sure if the issue is with the beam file or if is an interpolation issue. I want to check with a few different beam files. I do see that you have an option to run the conversion script: python3 scripts/coeff_scripts/convert_lwa.py --simulation_path LWA_SIMULATION.h5 --destination_path LWA_COEFFICIENTS.h5
For this I would need to build Everybeam with -BUILD_WITH_PYTHON=on option right? Is there anything else?
I noticed this problem:
free(): invalid pointer
when I try to call:
tel = everybeam.load_telescope(ms, element_response_model='hamaker')
this happens if "import casacore.tables as pt
" is imported BEFORE everybeam (v 0.5.2)
The workaround above solves the issue, which I will therefore close. A better solution has been proposed and an improvement ticket has been created for this on the backlog of Team Schaap.
I tried to run the following command and it works: 'wsclean -size 500 500 -scale 1amin -apply-primary-beam 20230813_181344_59MHz.ms'
Can you make sure you build wsclean against the correct everybeam? Just delete the build folder (or at least CMakeCache.txt) and run cmake again (for safety, do it for both everybeam and wsclean)?
Thank you. I needed to set CMAKE_INSTALL_PREFIX too. So the lwa .h5 file is now downloaded into the share folder. But wsclean keeps erroring out at the constructing primary beam step with segmentation fault. I have set 2% memory usage using -mem 2.
If i dont use the -apply-primary-beam I can successfully run wsclean.
Tammo Jan Dijkema (9ffe5463) at 20 Mar 14:12