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

SpeciesConc file time is 0 despite no errors #1975

Closed
ncolombi opened this issue Oct 4, 2023 · 3 comments
Closed

SpeciesConc file time is 0 despite no errors #1975

ncolombi opened this issue Oct 4, 2023 · 3 comments
Assignees
Labels
category: Bug Something isn't working

Comments

@ncolombi
Copy link

ncolombi commented Oct 4, 2023

Name and Institution (Required)

Name: Nadia Colombi
Institution: Harvard

Confirm you have reviewed the following documentation

Description of your issue or question

I am running GCClassic version 14.2.0. My simulation (beginning 2019-01-01) saving monthly SpeciesConc output is running with no errors. The SpeciesConc files for January and February look normal, but the March and April output are empty (time is 0 as shown in the screenshot below). I've attached the SpeciesConc netCDF for March as well as my config files below.

Screen Shot 2023-10-04 at 10 51 38 AM

HEMCO_Config.rc.zip
GEOSChem.SpeciesConc.20190301_0000z.nc4.zip
geoschem_config.yml.zip

@msulprizio
Copy link
Contributor

Nadia wrote:

I think my issue with the SpeciesConc file saying Time = 0 is solved. After waiting a while, I viewed the file again and it now has data. Although the GC.log file says that the simulation is currently on the month of June, the SpeciesConc file GEOSChem.SpeciesConc.20190501_0000z.nc4 is still 0 but the April one is now normal. It seems that the May file is still being written to even though the simulation is already on June. Is this a normal thing and I just didn't realize it before? I've never ran a monthly averaged simulation, only daily averages, so I haven't encountered this before.

@yantosca replied:

I think the netCDF file isn't flushed until it's written. We may have put a fix in but I'd have to doublecheck.

@lizziel
Copy link
Contributor

lizziel commented Oct 12, 2023

There was an issue created a while back about the diagnostics not being fully written until the end of the next diagnostic period. #1464

The issue was closed since a fix went into 14.0.2. If that fix isn't working we should reopen.

@yantosca
Copy link
Contributor

yantosca commented Jan 8, 2024

Closing this issue, as the discussion has now moved to #2094 and corresponding draft PR #2096.

@yantosca yantosca closed this as completed Jan 8, 2024
@yantosca yantosca self-assigned this Jan 8, 2024
@yantosca yantosca added category: Bug Something isn't working specialty simulations labels Jan 8, 2024
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
Projects
None yet
Development

No branches or pull requests

4 participants