Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with timer routines for the Ginzburg-Landau example #178

Open
loiseaujc opened this issue Mar 7, 2025 · 0 comments · May be fixed by #180
Open

Problem with timer routines for the Ginzburg-Landau example #178

loiseaujc opened this issue Mar 7, 2025 · 0 comments · May be fixed by #180
Assignees

Comments

@loiseaujc
Copy link
Member

When running

fpm run --example Ginzburg-Landau

I get the following error:

Project is up to date
2025-03-07 11:34:18.331: LK_Timer: LightKrylov timing enabled.
2025-03-07 11:34:18.331: LK_TmrUtils % LightKrylov_timer: INFO: 68 private timers registered in 3 groups:
2025-03-07 11:34:18.331: LK_TmrUtils % LightKrylov_timer: INFO:    basekrylov           :  40 timers.
2025-03-07 11:34:18.331: LK_TmrUtils % LightKrylov_timer: INFO:    iterativesolvers     :  24 timers.
2025-03-07 11:34:18.331: LK_TmrUtils % LightKrylov_timer: INFO:    newtonkrylov         :   4 timers.
2025-03-07 11:34:18.332: LK_TmrUtils % LightKrylov_timer: Private timer initialization complete.
2025-03-07 11:34:18.364: LK_TmrUtils % start_timer_by_name: ERROR: STOP_ERROR

 A fatal error was encountered. Aborting calculation as per user directive.

STOP 1
<ERROR> Execution for object " Ginzburg-Landau " returned exit code  1
<ERROR> *cmd_run*:stopping due to failed executions
STOP 1

My guess is that something has not been updated in the Ginzburg-Landau example when changes were made to the timer module. In contrast, everything works fine when running

fpm run --example Roesller
@Simkern Simkern self-assigned this Mar 10, 2025
@Simkern Simkern linked a pull request Mar 10, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants