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

GEOS-Chem dry run download from https://geos-chem.s3-us-west-2.amazonaws.com places data one level too high #2771

Open
yantosca opened this issue Mar 13, 2025 · 0 comments · Fixed by #2772
Assignees
Labels
category: Bug Something isn't working topic: Dry-Run Simulation Related to GEOS-Chem dry-run
Milestone

Comments

@yantosca
Copy link
Contributor

Your name

Bob Yantosca

Your affiliation

Harvard + GCST

What happened? What did you expect to happen?

Downloading data with a GEOS-Chem dry-run simulation from the https://geos-chem.s3-us-west-2.amazonaws.com portal will place the data one level too high. The subfolders of ExtData are placed onto the same level as ExtData, e.g.

CHEM_INPUTS/
ExtData/
GEOS_4x5/
HEMCO/

instead of e.g.

ExtData/CHEM_INPUTS
ExtData/GEOS_4x5
ExtData/HEMCO

This is because the local prefix for the wget command is:

#!/bin/bash

# This script was generated by download_data.py

wget -r -np -nH -R "*.html" -N -P /home/ubuntu/ "https://geos-chem.s3-us-west-2.amazonaws.com/CHEM_INPUTS/CLOUD_J/v2024-09/FJX_j2j.dat"
... etc...

The bug is caused by -P /home/ubuntu (my home directory on an EC2 cloud instance) which should be instead -P /home/ubuntu/ExtData.

We will add logic to the download_data.py to add an /ExtData when downloading from data portal https://geos-chem.s3-us-west-2.amazonaws.com.

What are the steps to reproduce the bug?

  1. Spun up an EC2 cloud instance
  2. Downloaded GEOS-Chem Classic
  3. Created a fullchem_benchmark run directory
  4. Navigated to the run directory and compiled the code
  5. ./gcclassic --dryrun > log.dryrun
  6. ./download_data.py log.dryrun geoschem+http

Please attach any relevant configuration and log files.

log.dryrun.txt

What GEOS-Chem version were you using?

14.5.3

What environment were you running GEOS-Chem on?

AWS

What compiler and version were you using?

gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.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

See related dry-run issues:

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 topic: Dry-Run Simulation Related to GEOS-Chem dry-run
Projects
None yet
1 participant