Skip to content
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

Bug with SatDiagn #2746

Open
zsx-GitHub opened this issue Feb 25, 2025 · 1 comment
Open

Bug with SatDiagn #2746

zsx-GitHub opened this issue Feb 25, 2025 · 1 comment
Labels
category: Bug Something isn't working help needed: Request Input From Community We need GC community to provide a fix/update topic: Diagnostics Related to output diagnostic data

Comments

@zsx-GitHub
Copy link
Contributor

zsx-GitHub commented Feb 25, 2025

Your name

Shixian Zhai

Your affiliation

CUHK

What happened? What did you expect to happen?

Dear GCST,

We find that the GCv14. 5.1 is not able to output SatDiagn at two time points simultaneously. That is, if we have two collections for SatDiagn, even when we define two different names (eg: SatDiagn_am and SatDiagn_pm) for the COLLECTION and declare them at the beginning of HEMCO_Config.rc, the model will only output reasonable values for variables in the second collection. Variable values in the first SatDiagn collection will all be -999.

Shixian

What are the steps to reproduce the bug?

COLLECTIONS: # 'Restart',
             #'Metrics',
             # 'SpeciesConc',
             # 'SpeciesConc_hr',
             #'AdvFluxVert',
             #'AerosolMass',
             #'Aerosols',
             ##'Budget',
             ##'CloudConvFlux',
             ##'ConcAboveSfc',
             ##'ConcAfterChem',
             #'DryDep',
             #'JValues',
             ##'KppDiags',
             ##'KppARDiags',
             ##'LevelEdgeDiags',
             ##'ProdLoss',
             ##'RRTMG',
             ##'RxnRates',
             ##'RxnConst',
             'SatDiagn_am',
             'SatDiagn_pm',
             ##'SatDiagnEdge',
             ##'StateChm',
             #'StateMet',
             ##'StratBM',
             ##'Tomas',
             ##'UVFlux',
             ##'WetLossConv',
             ##'WetLossLS',
             ##'BoundaryConditions',
::

........

#==============================================================================
# %%%%% THE SatDiagn_am COLLECTION %%%%%
#
# GEOS-Chem data during satellite overpass
#
# Available for all simulations
#==============================================================================
  SatDiagn_am.template:          '%y4%m2%d2_%h2%n2z.nc4',
  SatDiagn_am.format:            'CFIO',
  SatDiagn_am.frequency:         00000001 000000
  SatDiagn_am.duration:          00000001 000000
  SatDiagn_am.hrrange:            9.00 10.00
  SatDiagn_am.mode:              'time-averaged'
  SatDiagn_am.fields:            'SatDiagnConc_NO2               ',
........

#==============================================================================
# %%%%% THE SatDiagn_pm COLLECTION %%%%%
#
# GEOS-Chem data during satellite overpass
#
# Available for all simulations
#==============================================================================
  SatDiagn_pm.template:          '%y4%m2%d2_%h2%n2z.nc4',
  SatDiagn_pm.format:            'CFIO',
  SatDiagn_pm.frequency:         00000001 000000
  SatDiagn_pm.duration:          00000001 000000
  SatDiagn_pm.hrrange:           21.00 22.00
  SatDiagn_pm.mode:              'time-averaged'
  SatDiagn_pm.fields:            'SatDiagnConc_CO               ',

Please attach any relevant configuration and log files.

No response

What GEOS-Chem version were you using?

14.5.1

What environment were you running GEOS-Chem on?

Local cluster

What compiler and version were you using?

gcc 10.2.0

Will you be addressing this bug yourself?

Yes

In what configuration were you running GEOS-Chem?

GCClassic

What simulation were you running?

Full chemistry

As what resolution were you running GEOS-Chem?

4x5

What meterology fields did you use?

MERRA-2

Additional information

No response

@zsx-GitHub zsx-GitHub added the category: Bug Something isn't working label Feb 25, 2025
@yantosca yantosca added help needed: Request Input From Community We need GC community to provide a fix/update topic: Diagnostics Related to output diagnostic data labels Feb 25, 2025
@yantosca
Copy link
Contributor

Thanks @zsx-GitHub for writing. The SatDiagn diagnostic was contributed by a GEOS-Chem community member and its implementation currently does not allow for more than one location. We would look to the GEOS-Chem community for assistance in extending its functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Bug Something isn't working help needed: Request Input From Community We need GC community to provide a fix/update topic: Diagnostics Related to output diagnostic data
Projects
None yet
Development

No branches or pull requests

2 participants