search

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
170 stars 166 forks source link

Question about recent GEOS-FP data files #2461

Closed ChangpeiHe closed 2 days ago

ChangpeiHe commented 2 months ago

It seems that recent GEOS-FP data is not updated in time. Besides, recent data files were not compressed. The near-real-time GEOS-FP data is crutial to my research project.

Looking forward to your reply!

Changpei He, Tsinghua University

yidant commented 2 months ago

Thanks @ChangpeiHe for reporting that! We are currently experiencing some issues on our cluster. The processing job didn't start properly. I'll manually process them for now and work with system administrator to resolve that.

ChangpeiHe commented 2 months ago

Thanks @yidant !

yidant commented 2 months ago

Hi @ChangpeiHe, this issue is resolved! Please let me know if you continue to find any missing file.

ChangpeiHe commented 2 months ago

image Hi, @yidant, files in 20240827 are missing, and some errors might occur in 20240909 and 20240910 (the file size seems incorrect).

yidant commented 2 months ago

Thanks @ChangpeiHe! These two issues are now fixed!

ChangpeiHe commented 2 months ago

Thanks @yidant! Some errors might exist on 20240916. In our test, we first downloaded the required original GEOS-FP files, and then processed them using the ./doGeosFpMulti YYYYMMDDcommand. We encountered the same issue. image

ChangpeiHe commented 2 months ago

I'd like to understand why this error occurred, and could you offer some suggestions to us?

yidant commented 2 months ago

Hi @ChangpeiHe! You can view the error message under the processing tool directory GEOS_FP/logs. It will tell you what makes the processing stop. In this case 20240916, the log says there's a corrupted raw file, so I redownload it and reprocess this date. The corrupted files are now replaced.

ChangpeiHe commented 2 months ago

Thanks！@yidant

github-actions[bot] commented 1 week ago

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the issue from closing this issue.