search

geoschem / gchp_legacy

Repository for GEOS-Chem High Performance: software that enables running GEOS-Chem on a cubed-sphere grid with MPI parallelization.
http://wiki.geos-chem.org/GEOS-Chem_HP
Other
7 stars 13 forks source link

[QUESTION] Do not read emission data when emission is turned off #18

Closed JiaweiZhuang closed 5 years ago

JiaweiZhuang commented 5 years ago

I remember that in early days, ExtData would skip emission data files if emission is set to F. But now it seems that emission data are always being read:

Two runs take the same time. For short simulations (1~2 days) ExtData takes nearly half of time. Is there a way to skip emission files without messing around ExtData.rc? (I remember that setting the data path to /dev/null would effectively skip it, but that's a cumbersome way). This would make short benchmarking & debugging much more efficient...

lizziel commented 5 years ago

You can add logicals to HEMCO_Config.rc, wrap the emissions you want to skip in a condition for it, and set it to false. This will prevent ExtData from reading them. I believe if you set general emissions to false in input.geos then ExtData will still try to read HEMCO_Config.rc so as to allow use of HEMCO even for non-emissions, e.g. masks.

-- Lizzie Lundgren Scientific Programmer GEOS-Chem Support Team geos-chem-support@as.harvard.edumailto:geos-chem-support@as.harvard.edu http://wiki.geos-chem.org/GEOS-Chem_Support_Team

Please direct all GEOS-Chem support issues to the entire GEOS-Chem Support Team at geos-chem-support@as.harvard.edumailto:geos-chem-support@as.harvard.edu. This will allow us to serve you better.

From: Jiawei Zhuang notifications@github.com Reply-To: geoschem/gchp reply@reply.github.com Date: Tuesday, January 15, 2019 at 3:20 PM To: geoschem/gchp gchp@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [geoschem/gchp] Do not read emission data when emission is turned off (#18)

I remember that in early days, ExtData would skip emission data files if emission is set to F. But now it seems that emission data are always being read:

Two runs takes the same time. For short simulations (1~2 days) ExtData take nearly half of time. Is there a way to skip emission files without messing around ExtData.rc? (I remember that setting the data path to /dev/null would effectively skip it, but that's a cumbersome way). This would make short benchmarking & debugging much more efficient...

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoschem_gchp_issues_18&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=wdx9BLAxHXfafOJVG3d1Wi4exC_fBJM_U58FGfS3sZ8&s=GRijeRCktNdoEMfg9ifhZuczTMabHS4mcMS4IaXxRm8&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAnyqzMlx9ua5zAYrbvFjCJpCvXwezecks5vDjgDgaJpZM4aBvOl&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=wdx9BLAxHXfafOJVG3d1Wi4exC_fBJM_U58FGfS3sZ8&s=AfJos-moQMZMIL-TsAgSkeuBx3xciagJhPgt7oYnbJU&e=.

JiaweiZhuang commented 5 years ago

wrap the emissions you want to skip in a condition for it, and set it to false.

Do you mean just manually changing 

# ExtNr ExtName                on/off  Species
0       Base                   : on    *
    --> HEMCO_RESTART          :       false
    --> AEIC                   :       true
    --> BIOFUEL                :       true
    --> BOND                   :       true
    --> BRAVO                  :       true
...

To 

# ExtNr ExtName                on/off  Species
0       Base                   : on    *
    --> HEMCO_RESTART          :       false
    --> AEIC                   :       false
    --> BIOFUEL                :       false
    --> BOND                   :       false
    --> BRAVO                  :       false
...

Or there is a more advanced grouping option?

lizziel commented 5 years ago

Exactly. I checked a recent log and this does work, but let me know if you see differently. Note that even if ExtData does not read the data HEMCO will still check that the file format is correct, so you can’t put garbage within a block that is off.

-- Lizzie Lundgren Scientific Programmer GEOS-Chem Support Team geos-chem-support@as.harvard.edumailto:geos-chem-support@as.harvard.edu http://wiki.geos-chem.org/GEOS-Chem_Support_Team

Please direct all GEOS-Chem support issues to the entire GEOS-Chem Support Team at geos-chem-support@as.harvard.edumailto:geos-chem-support@as.harvard.edu. This will allow us to serve you better.

From: Jiawei Zhuang notifications@github.com Reply-To: geoschem/gchp reply@reply.github.com Date: Tuesday, January 15, 2019 at 4:35 PM To: geoschem/gchp gchp@noreply.github.com Cc: "Lundgren, Elizabeth W" elundgren@seas.harvard.edu, Comment comment@noreply.github.com Subject: Re: [geoschem/gchp] Do not read emission data when emission is turned off (#18)

wrap the emissions you want to skip in a condition for it, and set it to false.

Do you mean just manually changing

ExtNr ExtName on/off Species

0 Base : on *

--> HEMCO_RESTART          :       false

--> AEIC                   :       true

--> BIOFUEL                :       true

--> BOND                   :       true

--> BRAVO                  :       true

...

To

ExtNr ExtName on/off Species

0 Base : on *

--> HEMCO_RESTART          :       false

--> AEIC                   :       false

--> BIOFUEL                :       false

--> BOND                   :       false

--> BRAVO                  :       false

...

Or there is a more advanced grouping option?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoschem_gchp_issues_18-23issuecomment-2D454560468&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=I95AKx2V7GDL3CJprJqDpw8kgrMIC_p45M7vv1VySfg&s=hWY7ew8_A6LenPVdaLyoKQcLhCtz1_KN6JqqLkNxd0Y&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAnyq9PQycJTXIX6ukjpk7SnnGiJvrJEks5vDkmmgaJpZM4aBvOl&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=I95AKx2V7GDL3CJprJqDpw8kgrMIC_p45M7vv1VySfg&s=3Wy-CtuiRACuHUsJ2XOI6SqBPcvnfOHXqN0E8EoPCZI&e=.

JiaweiZhuang commented 5 years ago

It worked like a charm. Reduced ExtData time by 40% and total time by 20% for a 2-day run.