Skip to content

Conversation

@brownbaerchen
Copy link
Contributor

Abdel and I were running into issues from time to time when the SDC residual of the prediction was low enough proclaim convergence. In this case, the code just does not do anything anymore but counting up the time and returning this solution.
I would consider this a bug.
The fix here is a bit weird because in single level SDC the sweep and iterations variables are interchangeable. Do you see any problem with doing it like this @pancetta?

@pancetta
Copy link
Member

pancetta commented Dec 20, 2024

Well. Not the first time we're running into this, but I'm not sure this is actually a bug. It depends on how you count, but if the prediction is good enough, why iterate? Take a problem that is constant for some time, then the prediction is already fine.

@brownbaerchen
Copy link
Contributor Author

The problem is that the solution will remain constant forever in this case unless there is some time-dependent forcing.

@pancetta
Copy link
Member

True, if the prediction is just 0 or copy.

@brownbaerchen
Copy link
Contributor Author

Ok, so if you use non-default prediction or random, you don't need to do iterations...?

@pancetta
Copy link
Member

I think I'd rather agree on always doing a single iteration (at least) instead of distinguishing this here. So, I'd be ok with your first approach.

@pancetta pancetta merged commit da7a177 into Parallel-in-Time:master Dec 20, 2024
86 checks passed
@brownbaerchen brownbaerchen deleted the at_least_one_iteration branch December 22, 2024 17:56
brownbaerchen added a commit to brownbaerchen/pySDC that referenced this pull request Dec 26, 2024
* Perform at least one SDC iteration

* Can use only prediction if predicting exotically

* Reverted last commit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants