<div>Hi, </div><div>I'm including a small update from the run on different machine with differently compiled version of CP2K which provides a more detailed information about the source of the error:</div><div> </div><div>Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0x628b4ef in ??? at /home/abuild/rpmbuild/BUILD/glibc-2.31/nptl/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0 #1 0xc9b71e in __qs_moments_MOD_build_local_moment_matrix at /home/krack/github/cp2k/cp2k-2023.1/src/qs_moments.F:253 #2 0xca0074 in __qs_moments_MOD_qs_moment_locop at /home/krack/github/cp2k/cp2k-2023.1/src/qs_moments.F:1874 #3 0xb923fe in __qs_scf_post_gpw_MOD_qs_scf_post_moments at /home/krack/github/cp2k/cp2k-2023.1/src/qs_scf_post_gpw.F:1262 #4 0xb93d18 in __qs_scf_post_gpw_MOD_scf_post_calculation_gpw at /home/krack/github/cp2k/cp2k-2023.1/src/qs_scf_post_gpw.F:376 #5 0x18ba70d in __qs_scf_post_scf_MOD_qs_scf_compute_properties at /home/krack/github/cp2k/cp2k-2023.1/src/qs_scf_post_scf.F:78 #6 0x1823e51 in __qs_scf_MOD_scf at /home/krack/github/cp2k/cp2k-2023.1/src/qs_scf.F:301 #7 0x11adb1b in __qs_energy_MOD_qs_energies at /home/krack/github/cp2k/cp2k-2023.1/src/qs_energy.F:111 #8 0xe2f6c0 in __force_env_methods_MOD_force_env_calc_energy_force at /home/krack/github/cp2k/cp2k-2023.1/src/force_env_methods.F:259 #9 0x5282c7 in rt_initial_guess at /home/krack/github/cp2k/cp2k-2023.1/src/motion/rt_propagation.F:460 #10 0x5282c7 in __rt_propagation_MOD_rt_prop_setup at /home/krack/github/cp2k/cp2k-2023.1/src/motion/rt_propagation.F:131 #11 0x478b8f in cp2k_run at /home/krack/github/cp2k/cp2k-2023.1/src/start/cp2k_runs.F:383 #12 0x47b672 in __cp2k_runs_MOD_run_input at /home/krack/github/cp2k/cp2k-2023.1/src/start/cp2k_runs.F:997 #13 0x468771 in cp2k at /home/krack/github/cp2k/cp2k-2023.1/src/start/cp2k.F:379 #14 0x405a4c in main at /home/krack/github/cp2k/cp2k-2023.1/src/start/cp2k.F:44 /var/spool/slurm/job299631/slurm_script: line 17: 1360 Segmentation fault /home/vslama/software/cp2k-2023.1-Linux-gnu-x86_64.ssmp -i Au_NP_small_OT_RTP_z.in -o Au_NP_small_OT_RTP_z.out</div><div> </div><div>I'll be glad for any suggestion how to overcome this error.</div><div> </div><div>Best wishes,</div><div>Vladislav </div> <div class="gmail_quote"><div dir="auto" class="gmail_attr">Dne středa 24. května 2023 v 9:29:57 UTC+2 uživatel Vladislav Sláma napsal: </div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Dear Matthias, Thank you for your suggestion. I was already using “ulimit -s unlimited”, but adding “export OMP_STACKSIZE=16M” didn’t help and I’m still getting the same segmentation fault. I’m including my submission script on CSCS cluster to provide all the settings for the cp2k run. Best wishes, Vladislav <div class="gmail_quote"><div dir="auto" class="gmail_attr">Dne středa 24. května 2023 v 9:06:47 UTC+2 uživatel Krack Matthias napsal: </div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div lang="en-CH" link="blue" vlink="purple" style="word-wrap:break-word"> <div> Hi Vladislav Segmentation faults are often caused by an insufficient stack size. Try to set (assuming bash) “ulimit -s unlimited” and “export OMP_STACKSIZE=16M” before launching the cp2k run. HTH Matthias</div></div><div lang="en-CH" link="blue" vlink="purple" style="word-wrap:break-word"><div> <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: <a rel="nofollow">cp...@googlegroups.com</a> <<a rel="nofollow">cp...@googlegroups.com</a>> on behalf of Vladislav Sláma <<a rel="nofollow">sla...@gmail.com</a>> Date: Tuesday, 23 May 2023 at 18:36 To: cp2k <<a rel="nofollow">cp...@googlegroups.com</a>> Subject: [CP2K:18833] Dipole moment segmentation fault </div> Dear all, I’m trying to simulate optical spectra and plasmon resonance for different gold cluster sizes. In order to do that, I’m employing real time propagation after initial delta-pulse kick. For the smaller particle sizes (up to ~114 atoms) everything works well and I get reasonable spectra. However for the larger nanoparticle (178 atoms) I’m getting segmentation fault due to the calculation of the dipole moments. When I do not compute and print dipole moments, the real time propagation goes well without any problem. Could you please suggest me how to compute the dipole moment during the real time propagation to avoid this problem? Thank you. Best wishes, Vladislav </div></div><div lang="en-CH" link="blue" vlink="purple" style="word-wrap:break-word"><div>-- You received this message because you are subscribed to the Google Groups "cp2k" group. To unsubscribe from this group and stop receiving emails from it, send an email to <a rel="nofollow">cp2k+uns...@googlegroups.com</a>. To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/cp2k/f1ad08c5-e388-4e1a-bbbc-fbd46e715bf6n%40googlegroups.com?utm_medium=email&utm_source=footer" rel="nofollow" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=cs&q=https://groups.google.com/d/msgid/cp2k/f1ad08c5-e388-4e1a-bbbc-fbd46e715bf6n%2540googlegroups.com?utm_medium%3Demail%26utm_source%3Dfooter&source=gmail&ust=1685002555961000&usg=AOvVaw1hMAutuEQQuVhhwLRM2HYk"> https://groups.google.com/d/msgid/cp2k/f1ad08c5-e388-4e1a-bbbc-fbd46e715bf6n%40googlegroups.com</a>. </div> </div> </blockquote></div></blockquote></div> -- You received this message because you are subscribed to the Google Groups "cp2k" group. To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:cp2k+unsubscribe@googlegroups.com">cp2k+unsubscribe@googlegroups.com</a>. To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/cp2k/9b03e074-7bc9-4b4a-be26-54b0dc37f1e8n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/cp2k/9b03e074-7bc9-4b4a-be26-54b0dc37f1e8n%40googlegroups.com</a>.