You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear sir,
Wish this letter finds you well.
I successfully installed PyFLEXTRKR and identified MCS with GPM IMERG Tb + precipitation data. Thank you very much for your sharing and detailed tutorials.
I have a question regarding the PF parameter coefficients, specifically: coefs_pf_area, coefs_pf_rr, coefs_pf_skew, and coefs_pf_heavyratio, which need to be set in the config_imerg_mcs_tbpf_example.yml file.
If I wish to identify robust MCSs in Central and South China during different periods, should I recalculate these parameters based on the specific time, latitude, and longitude for the region, or can I use the preset PF parameter coefficients in the configuration file? I am unsure whether these coefficients, which are likely based on US data, would apply equally to mid-latitude regions like China.
I look forward to your advice on this matter.
Thank you
The text was updated successfully, but these errors were encountered:
Dear sir,
Wish this letter finds you well.
I successfully installed PyFLEXTRKR and identified MCS with GPM IMERG Tb + precipitation data. Thank you very much for your sharing and detailed tutorials.
I have a question regarding the PF parameter coefficients, specifically: coefs_pf_area, coefs_pf_rr, coefs_pf_skew, and coefs_pf_heavyratio, which need to be set in the config_imerg_mcs_tbpf_example.yml file.
If I wish to identify robust MCSs in Central and South China during different periods, should I recalculate these parameters based on the specific time, latitude, and longitude for the region, or can I use the preset PF parameter coefficients in the configuration file? I am unsure whether these coefficients, which are likely based on US data, would apply equally to mid-latitude regions like China.
I look forward to your advice on this matter.
Thank you
The text was updated successfully, but these errors were encountered: