You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
When running
I get the following error:
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 runningThe text was updated successfully, but these errors were encountered: