Merging with ClimateEasy.jl

[natgeo-wong]

Hey @Balinus, just wanted to let you know that I've put up one of my repositories ClimateEasy.jl into JuliaClimate. However, I think eventually to prevent confusion I should merge the repository into ClimateTools.jl, but my way of coding might be quite different from yours.

Could you let me have a look and see what you think about merging the two repositories and how we should go about doing it?

[Balinus]

Hello!

Interesting to see the work you've done. I think there's not a lot of overlap and some functions would be useful. I propose that you list your most robust/useful functions and we start with that?

[natgeo-wong]

The most robust functions that I have are found in:

• datetime.jl: these set of functions convert TimeTypes to string values in the YYYYMMD format, etc., which is useful for saving and filenaming conventions
• regions.jl: these set of functions allow me to extract point or regional data from a larger dataset (e.g. regional data from global data). allows for conversion from -180º-180º grids to 0º-360º grid formats between the different datasets
• str2dnt.jl: returns Date/DateTime from a string, basically the opposite of the functions listed in datetime.jl

[Balinus]

ok, nice! Would you like to sketch a PR and we build on that? I'd begin with regions.jl in my opinion.

[natgeo-wong]

alright! I'll fork and add?

[Balinus]

Seems fine to me! Meanwhile, I'm gonna split ClimateTools and create ClimatePlots in the next coming days/week and then migrate over JuliaClimate.

[Balinus]

One thing that will need to be done for merging will be to document the functions and create tests.

[natgeo-wong]

Hi Balinus! I am currently in the process of rewriting the regions.jl codes and fix some bugs, and upgrading ClimateSatellite.jl (one of my other packages, which uses ClimateEasy.jl as a dependency), so this will take longer than expected.

[Balinus]

No problem!

ClimateSatellite.jl seems really interesting! Clearly outside my expertise domain! 😄

[natgeo-wong]

I have finished rewriting the regions.jl code and updated ClimateEasy.jl to v0.2 to reflect that. I'll be transferring that part to ClimateTools.jl as well soon, and will submit a pull request to that effect within the next few days.

Just note that none of my codes use the ClimGrid structure that many of your functions are based around, so I'm not sure if that's going to be a problem?

Also, should I merge this into ClimateTools or ClimateBase?

[Balinus]

ok, perhaps if you provide some example on how you use the functions? I'll be able to connect it to ClimGrid then. On which type do you use the functions?

For the merging, I'd say that generally, if the functions are useful for both ClimateTools and ClimatePlots -> merge with ClimateBase. if it's only relevant for analysis, merge it with ClimateTools. Anyway, we can always move it later on if it seems more practical elsewhere. (It might even be a new package).