geoschem / geos-chem

GEOS-Chem "Science Codebase" repository. Contains GEOS-Chem science routines, run directory generation scripts, and interface code. This repository is used as a submodule within the GCClassic and GCHP wrappers, as well as in other modeling contexts (external ESMs).
http://geos-chem.org
Other
162 stars 155 forks source link

Why there was information of "Min = *******" about BCs when running a nested Hg simulation #1304

Closed jie0314ouc closed 1 year ago

jie0314ouc commented 2 years ago

I want to run a nested Hg simulation (AS,Grid=0.5°×0.625°) based on the BCs produced a global simulation with 2°×2.5°,and according to the [http://wiki.seas.harvard.edu/geos-chem/index.php/Setting_up_GEOS-Chem_nested_grid_simulations#GEOS-Chem_12.4.0_and_later And I had verify the input.geos and HEMCO_Config.rc in the rundirs. Finally, after ./geos, I found this nested simulation was successfully to produce Outputfiles. However, I also found the following prompt on the interface:

  `SNOW_HG_LAND_STORED not found in restart file, set to zero
    ===============================================================================
    Min and Max of each species in BC file [mol/mol]:
    Species   1,      Hg0: Min = ***************  Max = 7.614199527E-13
    Species   2,      Hg2: Min = ***************  Max = 1.281034062E-13
    Species   3,      HgP: Min = ***************  Max = 2.437486790E-13
    GET_BOUNDARY_CONDITIONS: Done applying BCs at 2012/01/02 00:00
    vdinti: pbl height will be limited to bottom           25  model levels. top is    431.25009999999997       hpa

    ********************************************
    * B e g i n   T i m e   S t e p p i n g !! *
    ********************************************`

Despite this prompt, the run succeeds and the output file is generated. The following figure was the concentration of Hg0 . I don't know if this simulation was actually successful.

Gcc version : 9.3 Geos-chem version: 12.9.3 Netcdf-c version:4.8.1 Netcdf-f version: 4.5.3

image

lizziel commented 2 years ago

Hi @jie0314ouc - It looks like your run was indeed successful. The printing of all asterisks indicates the value could not fit in the specified format defined in the code. You can read more about that sort of issue here.

In newer versions of GEOS-Chem we no longer have that code. If you want to verify your BC file indeed okay I suggest opening it with a netcdf viewer such as Panoply or ncview that will show you the min and max of the dataset.

jie0314ouc commented 2 years ago

Thanks for your reply. If the value could not fit in the specified format defined in the code, how did it was used in the running?

------------------ 原始邮件 ------------------ 发件人: "geoschem/geos-chem" @.>; 发送时间: 2022年7月12日(星期二) 晚上10:41 @.>; @.**@.>; 主题: Re: [geoschem/geos-chem] Why there was information of "Min = ***" about BCs when running a nested Hg simulation (Issue #1304)

Hi @jie0314ouc - It looks like your run was indeed successful. The printing of all asterisks indicates the value could not fit in the specified format defined in the code. You can read more about that sort of issue here.

In newer versions of GEOS-Chem we no longer have that code. If you want to verify your BC file indeed okay I suggest opening it with a netcdf viewer such as Panoply or ncview that will show you the min and max of the dataset.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

lizziel commented 2 years ago

The string printed to the log is not the same as the value used during running. The print statement that shows the min and max is informational only, and the fortran code for printing fixed width is finicky. My guess is the minimum value in the BC file is very small such that the fixed width specification in the print needs modification.

You could test this by adding another print to the code that does not use fixed width. Grepping the GEOS-Chem repository in the version you have for Min and Max of each species will bring you to where the print is located. You can then add a line that is simply:

print *, "Debugging print of min value in BC file: ", x

where x is the variable used in the original print for minimum value.