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

error when running buildweights #32

Closed
dgergel opened this issue Mar 20, 2021 · 2 comments
Closed

error when running buildweights #32

dgergel opened this issue Mar 20, 2021 · 2 comments

Comments

@dgergel
Copy link
Member

dgergel commented Mar 20, 2021

When I run the following on Azure, dodola buildweights clean-dev/ACCESS-ESM1-5.historical.zarr -m bilinear --outpath clean-dev/ACCESS-ESM1-5.historical.1x1.weights.nc, I'm getting this error:

Traceback (most recent call last):
  File "/anaconda/envs/dodola/bin/dodola", line 33, in <module>
    sys.exit(load_entry_point('dodola==0.1.0a0', 'console_scripts', 'dodola')())
  File "/anaconda/envs/dodola/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/anaconda/envs/dodola/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/anaconda/envs/dodola/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/anaconda/envs/dodola/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/anaconda/envs/dodola/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
TypeError: buildweights() got an unexpected keyword argument 'targetresolution'

I think it's because targetresolution in the cli interface should actually be target_resolution, but I'll take a closer look tomorrow and test it.

@brews
Copy link
Member

brews commented Mar 21, 2021

Thanks for catching this!

Lol. This is like the one simplest layer not getting tested in CI/CD so of course we get this bug.

@dgergel
Copy link
Member Author

dgergel commented Mar 22, 2021

Closed via #33

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

2 participants