Hi Guillermo, Many thanks for your feedback and suggestion. Sounds a nice idea to me. Can I ask you to kindly open an issue on the gitlab and explain your suggestion there. This will help us to keep it on the list and hopefully address it. Many thanks Mohsen ________________________________ From: nektar-users-bounces@imperial.ac.uk <nektar-users-bounces@imperial.ac.uk> on behalf of Guillermo Suarez <guillermo180395@gmail.com> Sent: Wednesday, September 21, 2022 10:18 PM To: nektar-users <nektar-users@imperial.ac.uk> Subject: [Nektar-users] Checkpoint fields filter StartTime ******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hi, I think nektar++ can really benefit from using a "StartTime" for writing the .chk files. Say that I want to generate several .chk during a period of a vortex shedding. Right now I have two possibilities: (a) start from initial conditions=0 which will generate a lot of unnecessary .chk files because of the transient, or (b) run the simulation (without writing any .chk) and then do a restart from the .fld and write the .chk files. Because the transient will now be shorter, the number of generated unnecessary .chk files will also be smaller. In that sense, I think the Checkpoint fields filter could implement some parameter to control the time step when to start writing the chk files -- exactly the same (code) as for the aeroforces filter. Cheers, Guillermo _______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users