Repository name

[bartnijssen]

@jhamman : It's not really for us to give release numbers to the mtclim code. This is why we may the mtclim code on UW-Hydro private. I'd prefer if we give this some more generic name and then make clear that we use mtclim v.x as part of that. Just like in the existing VIC code, we should wrap the mtclim code so we can update it pretty easily.

[jhamman]

@bartnijssen - I'm fine leaving the mtclim name behind. Do you have suggestions on what the name could be. A few ideas: hydromet, hydro-gen, or metgen.

The Montana folks do not have plans to continue work on the MTCLIM code. In fact, back in June 2014, they gave us the go-ahead to develop and release MTCLIM 5 if we wanted (I can send that email exchange to you if you are interested in seeing it again). I'm not saying that we should keep the name or release MTCLIM ourselves, but I wanted to make sure we were clear on their development plans.

I also don't want to do a pure wrapping of the original C MTCLIM code. I have pure Python/Pandas implementation that is reproducing their results at a daily timestep. Since there hasn't been an update to the MTCLIM code for 15 years, I think we're pretty safe leaving that version without a explicit wrapper.

[tbohn]

How about "meteo-synth"?

On Fri, Sep 18, 2015 at 10:28 AM, Joe Hamman notifications@github.com
wrote:

@bartnijssen https://github.com/bartnijssen - I'm fine leaving the
mtclim name behind. Do you have suggestions on what the name could be. A
few ideas: hydromet, hydro-gen, or metgen.

The Montana folks do not have plans to continue work on the MTCLIM code.
In fact, back in June 2014, they gave us the go-ahead to develop and
release MTCLIM 5 if we wanted (I can send that email exchange to you if you
are interested in seeing it again). I'm not saying that we should keep the
name or release MTCLIM ourselves, but I wanted to make sure we were clear
on their development plans.

I also don't want to do a pure wrapping of the original C MTCLIM code. I
have pure Python/Pandas implementation that is reproducing their results at
a daily timestep. Since there hasn't been an update to the MTCLIM code for
15 years, I think we're pretty safe leaving that version without a explicit
wrapper.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[bartnijssen]

OK - I now do remember that exchange (about MTCLIM with Montana). Still it might be better to give it a new name and just say that this incorporates MTCLIM (not entirely sure what is better). That may result in fewer expectations on us for continuing, improving MTCLIM specific features and allow us to do some new things.

Point taken about there being no need to wrap the code given the lack of updates.

Keep trying on the names ...