Changes between Version 74 and Version 75 of project/results


Ignore:
Timestamp:
Jan 10, 2020 11:50:55 AM (4 years ago)
Author:
suehring
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • project/results

    v74 v75  
    5656|| Nested simulation - numerical issues || 27/12/2019 ||  || Nested simulation ran for 1 minute. However, large oscillation in the u- and v-component could be observed within the child. I hypothesize that this is due to the 3D-initialization of the child from the parent. Due to mismatches in the building configuration (due to the large grid aspect ratio), many grid points in the child remain zero after initialization, even though these grid points belong to the atmosphere. Since the mass-flux is largely affected by this, strong oscillations arise within the child, finally lead to a crash. ||
    5757|| Nested simulation || 02/01/2020 ||  || Simulations repeatedly hang / crash. The Lustre system in Berlin is still not full setup so that simulations repeatedly  hang / crash due to slow filesystem. ||
    58 || Nested simulation - initial run || 03/01/2020 ||  || Lustre filesystem issues seem to be solved for now. Initialization of the child has been changed. Child is now initialized via dynamic driver rather than via the coupler. This way all atmosphere grid points are initialized appropriately. The nested simulation is at t=30min. '''First estimate of duration''': in 12 h real time on 6720 cores we will simulate about 1 h. With 30 hrs simulation time (00:00:00 UTC - 06:00:00 UTC (next day), we will need about 30 restarts. Since the machine in Berlin starts to fill up now with other users, we are only be able to do 1 simulation at a day (optimistic scenario), so this will take at least one month. ||
     58|| Nested simulation - initial run || 03/01/2020 ||  || Lustre filesystem issues seem to be solved for now. Initialization of the child has been changed. Child is now initialized via dynamic driver rather than via the coupler. This way all atmosphere grid points are initialized appropriately. The nested simulation is at t=30min. '''First estimate of duration''': in 12 h real time on 6720 cores we will simulate about 1 h. With 30 hrs simulation time (00:00:00 UTC - 06:00:00 UTC, next day), we will need about 30 restarts. Since the machine in Berlin starts to fill up now with other users, we are only be able to do 1 simulation at a day (optimistic scenario), so this will take at least one month. ||
    5959|| Nested simulation - restart run || 09/01/2020 ||  || Simulation crashes in reading the restart data. Bugtracing is on its way. ||
    6060
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |