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

Cannot access test data following instruction on Readme #355

Open
miaoneng opened this issue Oct 11, 2022 · 3 comments
Open

Cannot access test data following instruction on Readme #355

miaoneng opened this issue Oct 11, 2022 · 3 comments

Comments

@miaoneng
Copy link

I am following readme to get test data, but after following instruction as

First, make sure you have configured the authentication with user credientials and configured Docker with the following commands:

gcloud auth login
gcloud auth configure-docker

Next, you can download the test data for the dynamical core and the physics tests.

cd fv3core
make get_test_data

TEST_DATA_ROOT=/scratch/git/pace/fv3core/test_data/ TARGET=dycore EXPERIMENT=c12_6ranks_standard make -C .. get_test_data
make[1]: Entering directory '/scratch/git/pace'
if [ -z "" ] ; then \
	if [ ! -f "/scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore/input.nml" ] || \
	[ "$(gsutil cp gs://vcm-fv3gfs-serialized-regression-data/8.1.1/c12_6ranks_standard/dycore/md5sums.txt -)" != "$(cat /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore/md5sums.txt)" ] ; then \
		rm -rf /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore ; \
		make sync_test_data ; \
		make unpack_test_data ; \
	fi ; \
else \
	make sync_test_data_from_ftp ; \
	make unpack_test_data ; \
fi
make[2]: Entering directory '/scratch/git/pace'
mkdir -p /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore && gsutil -m rsync -r gs://vcm-fv3gfs-serialized-regression-data/8.1.1/c12_6ranks_standard/dycore/ /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore

WARNING: gsutil rsync uses hashes when modification time is not available at
both the source and destination. Your crcmod installation isn't using the
module's C extension, so checksumming will run very slowly. If this is your
first rsync since updating gsutil, this rsync can take significantly longer than
usual. For help installing the extension, please see "gsutil help crcmod".

Building synchronization state...
Caught non-retryable exception while listing gs://vcm-fv3gfs-serialized-regression-data/8.1.1/c12_6ranks_standard/dycore/: AccessDeniedException: 403 [email protected] does not have storage.objects.list access to the Google Cloud Storage bucket.
CommandException: Caught non-retryable exception - aborting rsync
make[2]: *** [Makefile.data_download:19: sync_test_data] Error 1
make[2]: Leaving directory '/scratch/git/pace'
make[2]: Entering directory '/scratch/git/pace'
if [ -f /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore/dat_files.tar.gz ]; then \
	cd /scratch/git/pace/fv3core/test_data//8.1.1/c12_6ranks_standard/dycore && tar -xf dat_files.tar.gz && \
	rm dat_files.tar.gz; \
fi
make[2]: Leaving directory '/scratch/git/pace'
make[1]: Leaving directory '/scratch/git/pace'
@elynnwu
Copy link
Collaborator

elynnwu commented Oct 12, 2022

I think we still have some permission issues that prevent external users to download from the google bucket, we will try and get that sorted out. As a workaround, we recommend pulling the data from the ftp site, you can do this by:

make USE_FTP=yes get_test_data

@jdahm
Copy link
Contributor

jdahm commented Nov 2, 2022

Hey @miaoneng, Thanks for filing the issue! At one point that bucket was public with requester pays, but it looks like a some point it flipped back to private. I set it back how it was, so you should be able to access it now. I'll close this for now, but let me know if you still have issues.

@jdahm jdahm closed this as completed Nov 2, 2022
@jdahm
Copy link
Contributor

jdahm commented Nov 2, 2022

We had to revert this because some people on the team had trouble accessing the data. I'll keep this open as a reminder to fix it soon.

@jdahm jdahm reopened this Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants