-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimize the seasonal TEC bias by revising the eddy mixing parameterization #69
Comments
Here are some project history & experience here for future applications & notes.
Current runs situation & history:
|
@ZhuxiaoLi66 Thanks for the plots. Moving forward, could we modify the legend so that it says "operational run with dayno_fix" instead of "dayno_fix", so that we remember what are these runs? Glad to see that the testing is going well. Thanks! |
@twfang this run is not an operational run, we could do 'keddy0=140 & keddy_semiann=60' to remind us for later review. since the dayno_fix applies for both of the runs, maybe no need to mention it here. |
The para3 (keddy0=60) annual run is extended to 20221226, almost done. |
In general, it is a little bit high, while looks fine. |
Fascinating.
The semi-annual is emerging. Looks like we need a small semi-annual with a
peak at equinox.
Together with a slight reduction in the mean.
…On Thu, Feb 9, 2023 at 3:38 PM ZhuxiaoLi ***@***.***> wrote:
In general, it is a little bit high, while looks fine.
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5BFOHMHXNYTIGPFA2F2KTWWVWXDANCNFSM6AAAAAAQ76SLF4>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Thanks, Tim. |
maybe we can use a minus sign for the peak. |
dev run on WCOSS2 getting keddy0=70 and keddy_semiann=0 from cycle 2023021618 outputs on HPSS: |
Got it, thanks, Adam. |
A new eddy mixing ratio parameter set (keddy0=70 and keddy_semiann=-10) has been designed for a new annual test WAM-IPE run which aims to get a better TEC output bias ratio against GloTEC data. |
A new parameterization run with setting keddy_semiann to -15 against the value of -10 is running, aiming to further mitigate the slight seasonal amplitude in the above bias ratio plot for -10 run. |
the run also get a bigger rmse and std, about 0.11 against 0.10 for -10 run. |
The annual run with the new parameterization of skeddy0=70, skeddy_semiann=-10, has been extended to the end of Apr. 2023. The extended run shows a lower bias ratio against GloTEC on average from Mar to Apr of 2023 than the same period of 2022. This explains the recent (from Mar) persistent low bias ratio for operational WAM-IPE output in plots of Daily_TEC_bias_ratio_WAM-IPE/GloTEC. |
It's like the operational run has not picked up the new values??
Is that possible?
…On Wed, Nov 8, 2023 at 1:57 PM ZhuxiaoLi ***@***.***> wrote:
[image: bias_ratio_opr_wfs_wrs_para5_20230414_1001]
<https://user-images.githubusercontent.com/22546571/281541059-03ee6744-3b35-4e01-a5be-c54aadb6a302.png>
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5BFOATPU7ILY72IOFR3KDYDPWZRAVCNFSM6AAAAAAQ76SLF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGY3DEMZVGY>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
No, this is the relevant namelist for the 2023/11/08 18Z WFS forecast that is currently running.
|
I checked the ratio values, they are very close, but not exactly the same, also given they are global mean values. We could say that the wrs runs are different from the corresponding wfs runs by different IC files, but output very close to the latter, especially at the global mean value level. |
Tim, if you mean picking up the new parameters for the operational runs, I think Adam gave the answer. |
Thanks Adam,
It is surprising that with and without DA is so big.
All the other comparisons we have made it is <~5% for globally and UT
averaged quantities
Any thoughts, anyone?
Tim
…On Wed, Nov 8, 2023 at 3:28 PM akubaryk ***@***.***> wrote:
No, this is the relevant namelist for the 2023/11/08 18Z WFS forecast that
is currently running.
wam_climate=.false., wam_swpc_3day=.true., wam_cires_rdata=.false.,
wam_swin = .true.,
wam_smin=.false., wam_smax=.false., wam_saver=.true., wam_geostorm=.false.,
wam_gwphys=.false., wam_solar_in=.false., wam_ion_in=.false.,
wam_das_in=.false., wam_smet_in=.false., wam_netcdf_inout=.true.,
wam_tides_diag=.false., wam_pws_diag=.false., wam_gws_diag=.false.,
jh0=1.75, jh_tanh=0.5, jh_semiann=0.5, jh_ann=0.0, jh_st0=25000.0, jh_st1=5000.0,
skeddy0=70.0, skeddy_semiann=-10.0, skeddy_ann=0.0,
tkeddy0=280.0, tkeddy_semiann=0.0, tkeddy_ann=0.0
/
—
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5BFOB3NK2YLFXVNPEN523YDQBR7AVCNFSM6AAAAAAQ76SLF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSG44DANBRGI>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
The PPT below is a summary of the recent investigation on the low bias-ratios of WAM-IPE against GloTEC in 2023 than 2022 with the new eddy-mixing parameterizations. |
I am sorry, everyone. It seems that the uploading of the PPT in my home machine didn't succeed. I have to retry this after I go back home this afternoon. Sorry about this! |
This project is mainly aiming to minimize the operational seasonal TEC bias through the revision of the eddy mixing parameterization in WAM.
At the same time, we will also keep a close eye on the influence of parameterization revision on the change of the neutral density with some validation.
The bias improvement also includes estimating the TEC change due to the day-number bug fix in WAM.
The output of the operational WAM-IPE and that of several designed free WAM-IPE coupling annual runs for the period about 20210715 - 20220705, also the output of the operational GloTEC during the same year-long period will be applied to do the diagnostics and mathematic analysis for parameterization change.
The text was updated successfully, but these errors were encountered: