eto.py or PyETo?

[hplato]

Hi, I'm looking to use some of these calculations so that an opensource home automation system (misterhouse) can leverage ET calculations for the wide variety of sprinkler systems it supports. I found code of yours from 2010 on the opensprinkler forum, and that script is forming the basis of some conversion work to perl.

Just reaching out in case it might make sense to use PyETO from 2015 rather than the version we have from 2010.

In case you're interested, the code's been cleaned up from the opensprinkler forum and put up on github: https://github.com/linuxha/EvapoTranspiration

[woodcrafty]

Hi there,

It would be best to use the PyETO code from 2015 since this contains some
bug fixes from the original code, and includes a more comprehensive unit
test. Also, when I wrote it in 2010 I was new to Python so the newer code
is better :)

Good luck with the misterhouse-sprinkler project - its looks great!

If you have any other questions just give me a shout.

Cheers,
Mark

On 20 April 2016 at 03:23, hplato notifications@github.com wrote:

Hi, I'm looking to use some of these calculations so that an opensource
home automation system (misterhouse) can leverage ET calculations for the
wide variety of sprinkler systems it supports. I found code of yours from
2010 on the opensprinkler forum, and that script is forming the basis of
some conversion work to perl.

Just reaching out in case it might make sense to use PyETO from 2015
rather than the version we have from 2010.

In case you're interested, the code's been cleaned up from the
opensprinkler forum and put up on github:
https://github.com/linuxha/EvapoTranspiration

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2

[hplato]

Awesome. Thanks!

I’ve managed to get the older code mostly working, just need to do some validations. It’s my hope to replicate the existing python script, and then incorporate the updates into the revised perl library.

On Apr 21, 2016, at 9:48 AM, Mark Richards notifications@github.com wrote:

Hi there,

It would be best to use the PyETO code from 2015 since this contains some
bug fixes from the original code, and includes a more comprehensive unit
test. Also, when I wrote it in 2010 I was new to Python so the newer code
is better :)

Good luck with the misterhouse-sprinkler project - its looks great!

If you have any other questions just give me a shout.

Cheers,
Mark

On 20 April 2016 at 03:23, hplato notifications@github.com wrote:

Hi, I'm looking to use some of these calculations so that an opensource
home automation system (misterhouse) can leverage ET calculations for the
wide variety of sprinkler systems it supports. I found code of yours from
2010 on the opensprinkler forum, and that script is forming the basis of
some conversion work to perl.

Just reaching out in case it might make sense to use PyETO from 2015
rather than the version we have from 2010.

In case you're interested, the code's been cleaned up from the
opensprinkler forum and put up on github:
https://github.com/linuxha/EvapoTranspiration

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #2 (comment)