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

Development fx area and volume #214

Closed
wants to merge 5 commits into from

Conversation

valeriupredoi
Copy link
Contributor

@valeriupredoi valeriupredoi commented Aug 29, 2019

Before you start, please read CONTRIBUTING.md.

Tasks

  • Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
  • This pull request has a descriptive title that can be used in a changelog
  • Add unit tests
  • Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
  • Codacy code quality checks pass. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.


Closes #367

@valeriupredoi valeriupredoi added enhancement New feature or request preprocessor Related to the preprocessor labels Aug 29, 2019
@ledm
Copy link
Contributor

ledm commented Aug 29, 2019

Thanks V!

@bouweandela
Copy link
Member

Related issue #94, see also the discussion there.

@valeriupredoi
Copy link
Contributor Author

@ledm would you be ok if you merged development (fix the conflicts) and then crack on with the review for this pls - it's something that shouldn't be lost in the cracks 🍺

if cube.coord('latitude').ndim == 1:
region_subset = cube.intersection(
longitude=(start_longitude, end_longitude),
latitude=(start_latitude, end_latitude))
region_subset = region_subset.intersection(longitude=(0., 360.))
return region_subset
# irregular grids

# Irregular grids - not lazy.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes are no longer needed, this has been fixed.

@valeriupredoi
Copy link
Contributor Author

this needs revival 🍺

@valeriupredoi
Copy link
Contributor Author

Nope! these changes are obsolete, all is done up in development already! Yay 🎉

@bouweandela
Copy link
Member

This problem is not solved: #367

@bouweandela bouweandela reopened this Nov 8, 2019
@valeriupredoi
Copy link
Contributor Author

s**t, sorry mate

The branch is old as time and I am afraid I don't have the time to resolve all the conflicts in _area.py (and the expertise either since this has @ledm written all over it) -> Lee the floor is yours here man 🍺

@bouweandela bouweandela changed the base branch from development to master January 3, 2020 12:14
@valeriupredoi
Copy link
Contributor Author

dis overarched by #439 and #446

@mattiarighi
Copy link
Contributor

Please close and delete branch if no longer required.

@bouweandela bouweandela deleted the development_fx_area_and_volume branch August 14, 2020 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request preprocessor Related to the preprocessor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Preprocessor area_statistics broken when using fx_files
4 participants