Forum_general

General

At this page you can post questions or start discussions on general topics related to Delft3D Flexible Mesh.

Please select a proper category below (if possible), to post your message or reply to an existing post. Please add tags to your posts to simplify searching.

 

** PLEASE TAG YOUR POST! **

 

 

 

 


Message Boards

Restart Files and Restart States

MP
Markus Promny, modified 4 Years ago.

Restart Files and Restart States

Youngling Posts: 2 Join Date: 8/6/12 Recent Posts
Hi,

I don't get it, please help:

D-Flow FM writes restart files like FlowFM_20110103_000000_rst.nc, but overwrites those after each restart intervall and doesn't even change the names according to the last restart state, right?

On the other hand it writes restart states like state_FlowFM_2011-01-01_08-00-00.zip, state_FlowFM_2011-01-01_16-00-00.zip ..., which do not contain anything but a nearly empty metadata.xml. Plus I do have a lot of files like state_FlowFM_2011-01-01_07-55-00-83572fb2-c571-49b3-b469-b6682c47a4eb.zip which do also not contain anything but a nearly empty metadata.xml.

I can use the restart files after I rename them to the desired date and time, but I fail to make any use of the restart states.

Does anyone have a hint for me? Is this how restart files and states should look like?

Best regards,
Markus

P.S. I use Delft3D FM 2016 HM 1.0.3.32933
MK
Michal Kleczek, modified 4 Years ago.

RE: Restart Files and Restart States

Padawan Posts: 53 Join Date: 10/23/14 Recent Posts
Dear Markus

Thank you for your interest in the Delft3D Flexible Mesh and reporting your issue to us.

I will do my best trying to clarify the process of creating restart files.
Restart states that are used by DeltaShell are the zip packeges and are created/located in the main project directory. Their name contains model name, time and unique identification number (therefore they should never be overwritten).
Within these packages you should be able to find respective restart files with names containing model_name_DATETIME_rst.nc and metadata.xml file.
The zip packages should be created every Rst output interval, each time new ones.

Since you reported that in your case there is no netcdf file within the package, could you please let me know if your Rst output interval is a multiplication (or equal) to User time step? We have this requirement for creating restart, history and map files otherwise they won't be created properly.

Note that everything what is within the model_name_output directory is 'temporary'. That means that if you use option 'save as' to save an old model as a new one, data from output directory won't be saved/copied. Additionally, the restart file that you mentioned as being overwritten is the initial restart file (created after first time step therefore after every new run overwritten).

Please let me know about your timing settings and if this comment helped to progess with your work.

Best regards,
Michal
MP
Markus Promny, modified 4 Years ago.

RE: Restart Files and Restart States

Youngling Posts: 2 Join Date: 8/6/12 Recent Posts
Dear Michal,

Thanks a lot for your response. I'm afraid there is something going wrong in my case. I belive the restart output interval is 8 hrs. Dflow FM writes something every 8 hrs, but no .nc-file. The only _rst.nc file is being overwriten after each 8 hrs, but with the original file name. My user time step is 5 min I think (though I was already mixing up mins and secs, as there are no units given in the respective GUI-field).

I just started uploading my case including all output to the deltares ftp-drive as Arthur suggested. I would be happy to have someone have a look on it.

Best regards,
Markus