DWP analyses

[juniperlsimonis]

incorporating the DWP analyses into the GUI
this involves coding up the analyses and then porting the code into the app and the command-line setup

[mhuso]

It might also involve a change to the input of the carcass file. Would it be adequate for us to add two columns to the carcass input file: 1) Direction (0-359 degrees with north at 0) FROM turbine TO carcass; 2) proportion of area at carcass's distance that was searched. These, plus the carcass size info, etc. are the values that will be used for estimating DWP. The user can provide them here, without us having to do the GIS work to calculate them. Needs group discussion.

[jstudyvin]

If you only want two additional columns can they be:

1. distance of carcass from the turbine ** this is required for the TWL or WD methods
2. proportion of area searched at that distance

I don't see why we need the carcass bearing (or direction)? I have no problem including to get people in the habitat.

I agree the user can do their own GIS work. It is a lot of work to ensure a GIS layer is adequate before getting to the proportion of area searched.

[mhuso]

Sounds good. I said two additional columns because distance was already in the example data set. So I was asking to add proportion searched and direction. You’re right, for now direction is not needed because we don’t have well-developed anisotropic models. But we should have some day and so getting people in the habit is a good idea. *From:* studyvin [mailto:[email protected]] *Sent:* Friday, October 27, 2017 11:47 AM *To:* ddalthorp/GenEst <[email protected]> *Cc:* Manuela Huso <[email protected]>; Comment <[email protected]> *Subject:* Re: [ddalthorp/GenEst] DWP analyses (#14) If you only want two additional columns can they be: 1. distance of carcass from the turbine ** this is required for the TWL or WD methods 2. proportion of area searched at that distance I don't see why we need the carcass bearing (or direction)? I have no problem including to get people in the habitat. I agree the user can do their own GIS work. It is a lot of work to ensure a GIS layer is adequate before getting to the proportion of area searched. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcwzA5RatsscRV0nWUkjlSLML9CldwTWks5swiU_gaJpZM4PxQlu> .[image: Image removed by sender.]

[juniperlsimonis]

checking back in on this to see where we are with having code that can execute DWP analyses and thinking about if this is going to be doable for version 1 or we include in version 2

it sounds like (from above) there are a few analyses that can be done, but I'm not sure what exactly they entail. @prabie are there existing functions for those? if not, is there someone working on code for it and what's an eta?

@mhuso what are your thoughts overall on the priority here? can you mark this issue as a version 1 or 2 milestone?

[prabie]

I think we decided this is a v2 enhancement. On Feb 25, 2018, at 9:42 PM, Juniper Simonis <[email protected]> wrote: checking back in on this to see where we are with having code that can execute DWP analyses and thinking about if this is going to be doable for version 1 or we include in version 2 it sounds like (from above) there are a few analyses that can be done, but I'm not sure what exactly they entail. @prabie <https://github.com/prabie> are there existing functions for those? if not, is there someone working on code for it and what's an eta? @mhuso <https://github.com/mhuso> what are your thoughts overall on the priority here? can you mark this issue as a version 1 or 2 milestone? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Acw22lN58k9oqAmSpUICtlf9i2kD0X3Yks5tYjZAgaJpZM4PxQlu> .

[mhuso]

I concur… *From:* Paul A. Rabie [mailto:[email protected]] *Sent:* Sunday, February 25, 2018 9:01 PM *To:* ddalthorp/GenEst <[email protected]> *Cc:* Manuela Huso <[email protected]>; Mention <[email protected]> *Subject:* Re: [ddalthorp/GenEst] DWP analyses (#14) I think we decided this is a v2 enhancement. On Feb 25, 2018, at 9:42 PM, Juniper Simonis <[email protected]> wrote: checking back in on this to see where we are with having code that can execute DWP analyses and thinking about if this is going to be doable for version 1 or we include in version 2 it sounds like (from above) there are a few analyses that can be done, but I'm not sure what exactly they entail. @prabie <https://github.com/prabie> are there existing functions for those? if not, is there someone working on code for it and what's an eta? @mhuso <https://github.com/mhuso> what are your thoughts overall on the priority here? can you mark this issue as a version 1 or 2 milestone? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/Acw22lN58k9oqAmSpUICtlf9i2kD0X3Yks5tYjZAgaJpZM4PxQlu

. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcwzA3Z3xU9USDBVqnwtTdeYRaqPD2gqks5tYjqCgaJpZM4PxQlu> .[image: Image removed by sender.]