Changes between Version 102 and Version 103 of ticket/370/TicketDetails


Ignore:
Timestamp:
Feb 4, 2020 12:25:06 PM (22 months ago)
Author:
Jin Lee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/370/TicketDetails

    v102 v103  
    129129As one of the verification measures to be used in this experiment is the ability of the trials to predict TC tracks it is important to resolve the inner core structure of a TC; even better, to have a few gridpoints within the eye of a storm (Q. In order to model the interaction between a vortex and its environment for the purpose of accurately predicting the movement of the vortex do we need to resolve the eye?). To achieve this I would like to run UM at N640 resolution (see [wiki:TicketDetails/SuiteChangesForN640 here] for some issues encountered when changing the resolution of the ported PS41 suite from N320 to N640). However, running at this resolution for a trial lasting for more than 3 months is unaffordable at NCI. So as a compromise I decided to run at N320 UM resolution.
    130130
     131My thoughts on the benefit of higher UM and PFM resolutions,
     132   * Higher UM resolution will be able to resolve smaller scales. CX background is then at a higher resolution (more spatial variability). This will lead to more accurate CX columns. Better forward modeling. So the background and observation would be closer. Analysis would fit observations more closely. But on the other hand, CX background will have greater spatial variability and this may move model away from observations, which will resulting in analysis being away from observations. Which effect dominates?
     133   * Improved PFM resolution will lead to improved evolution of increments. With everything being equal this will lead to improved forward model , which leads to .... Result is a better fit to observation.
     134
     135The suites have fixed thinning distance regardless of UM and PFM resolutions used. There are 3 rounds of thinning: after checking of preprocess flags (!ThinCall 1), before 1DVar (!ThinCall 2) and stationlist thinning. At the last stage the thinning distance is usually quite large: ~100 km. This is bigger than satellite footprint size and PFM resolution (for N320). My thoughts,
     136   * A new obtype is thinned independently of other obtypes so the new obtype will be used, albeit thinned
     137
    131138==== OPS ====
    132139