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

Post-P2G 3.0 release task list #588

Open
2 of 5 tasks
djhoese opened this issue Jan 27, 2023 · 3 comments
Open
2 of 5 tasks

Post-P2G 3.0 release task list #588

djhoese opened this issue Jan 27, 2023 · 3 comments
Assignees
Labels
code cleanup Refactoring and code complexity cleanup component:build related to building or release creation

Comments

@djhoese
Copy link
Member

djhoese commented Jan 27, 2023

  • Upgrade or replace development server: Our main development server bumi needs its OS upgraded after we release 3.0. However, it has also been having a lot of network interface issues so it may new hardware or a complete replacement.
  • Install dockerd (or equivalent) on bumi and transition build system to docker. This should allow us to more easily target other platforms if needed.
  • Update software bundle to Python 3.11 (might come with some decent performance improvements)
  • Add new integration tests from Kathy's 3.0 series of tests
  • Review EWA-based resampling defaults with weight_distance_max=1.0 (see comment below)
@djhoese djhoese added component:build related to building or release creation code cleanup Refactoring and code complexity cleanup labels Jan 27, 2023
@djhoese djhoese added this to the Polar2Grid 3.1 milestone Jan 27, 2023
@djhoese
Copy link
Member Author

djhoese commented Feb 1, 2023

I just updated the TODO list above with needing to check on resampling defaults where weight_distance_max=1.0. We set this for produces like ACSPO and MERSI to reproduce the same results from Polar2Grid 2.3, but we know that using weight_distance_max=1.0 can produce holes in the file image depending on the latitude (I think it is more prevalent at higher latitudes). I noticed this with "test6" of the Jenkins integration tests where the weight_distance_max=2.0 actually fills in the gaps of the ACSPO SST much more than setting it to 1.0. Not sure this is a good thing in this case though (is that data actually there or just being interpolated to be there).

@djhoese
Copy link
Member Author

djhoese commented Sep 6, 2023

Python 3.11 is now the default in CI testing and is the version of python used in the software bundle. I've checked the TODO item at the top of this issue.

@kathys
Copy link
Collaborator

kathys commented Aug 13, 2024

The other issues on this list will not be done for the 3.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code cleanup Refactoring and code complexity cleanup component:build related to building or release creation
Projects
None yet
Development

No branches or pull requests

2 participants