workshop rift example lost sed.time49.hdf5
longgangfan opened this issue · comments
I tested the workshop rift example and found the sed.time49.hdf5 was lost in the output directory. I don't know the reason.
Similar problem occured when I tested the UWGeodynamic coupled with badlands, underworldcode/UWGeodynamics#240
This is happening for the last time step in the rift example? When using the coupling with UWgeo are the sed files not created every time?
This is happening for the last time step in the rift example? When using the coupling with UWgeo are the sed files not created every time?
Thank you for your reply. Sorry for my late replying.
For the rift example, the sed.time49.hdf5 was lost, but the sed.time50.hdf5 was written on the disk. The "coupling with UWgeo" output most of sed.time[XXX].hdf5, but some of the random time step were lost. For one of my model, 200 time steps were expected written on the disk, but only 189 steps I got. The lost steps seems random，as “5， 20， 149，164，179，183，188，193，198，199， 200” were lost.
Hi again,
I have created a branch in badlands called uwtest to fix the issue with UW-geo coupled model. It seems that the problem is linked to the way the 2 codes communicate the different time interval between consecutive time steps. Have a go with this version and report back if the problem persists.
Hi again,
I have created a branch in badlands called uwtest to fix the issue with UW-geo coupled model. It seems that the problem is linked to the way the 2 codes communicate the different time interval between consecutive time steps. Have a go with this version and report back if the problem persists.
There is some bugs in the uwtest branch. It kept running in the loop.
Hi,
Seems like the time step is lower than 1 year. I have made some changes that might solve the issue.
Hi,
Seems like the time step is lower than 1 year. I have made some changes that might solve the issue.
In line 758,tOld = self.tNow.copy()
AttributeError: 'float' object has no attribute 'copy'
sorry should be fixed now
sorry should be fixed now
Thank you, I will test it soon.
It seems work well untile now.