User Forum of Software BASEMENT

Patroth

User

Registered: 2015-02-25

Posts: 5

Error with Seq.Coupling of 2D to 1D with sediment transport

Hello Forum-Gurus.

As stated in the Subject I (hope to) have a sequential coupling of a 2d and a 1d model with sediment transport.
On their own both models work correctly.
I want to hotstart the simulation to simulate sediment transport.
I have the two initial files.

I set the start time for both parts of the model to 0.0s.

When I run the simulation I get the following error: "[...]There was no next data pair found in the boundary serie. The program cannot continue.[...]".

Any ideas on what the problem could be/how to fix it?
Thanks a million
Pat

Lukas Vonwiller

Developer

Registered: 2014-09-04

Posts: 127

Re: Error with Seq.Coupling of 2D to 1D with sediment transport

Hi Pat

It is difficult to say what is going wrong from distance.
Did you check your restart_solution_time?
Does your model run without using initial type = continue (e.g. starting dry)?

If you cannot solve the problem, you can think about sending us your model for debugging.

Hope that helps!
cheers

Patroth

User

Registered: 2015-02-25

Posts: 5

Re: Error with Seq.Coupling of 2D to 1D with sediment transport

Thanks for your response. I understand completely that it's hard to debug from afar.
After a short talk with Stephan Kammerer on Tuesday I ran the model starting dry and without sediment transport. I still get the same error message that no next data pair can be found.

I would be really greatful if one of you could take a look at my model. Stephan already quickly looked over the .bmc file and said that he couldn't spot anything that seemed to lead to that error. I know he's really busy right now, so could I send you the .bmc file+geometry files to look at as well?
Thanks

Lukas Vonwiller

Developer

Registered: 2014-09-04

Posts: 127

Re: Error with Seq.Coupling of 2D to 1D with sediment transport

Yes, you can send your model to basement@ethz.ch.

We try to check if it is an application error or a bug.
If it is a bug will put it on our todo-list for the next release.
cheers
Lukas