Variable time steps without sub-cycling in serial-explicit coupling

Official adapters and tutorials
, , , ,
21

Hi @auer1329

So, it seems that the additional bug, we will only be able to solve when merging initialize and initializeData, which we think about doing in the next major release.
The complexity here is that you use both “first-participant” and data initialization. We now found out that this combination never worked, it seems nobody has ever needed it.

Your case should work if you set “initialize=off” for all exchanged data (and using the version from the PR). Of course, then, initial data is not communicated. Maybe as a workaround you could hard-code these values on the first participants?
Clear what all this means or do you need more explanations?

1 Like
22

The intermediate fixes are merged to develop now.

1 Like
23

I modified my case to use hard-coded values and deactivated initialization, now it’s working perfectly.
Thank you for your help!

1 Like
24

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.