Project status questions

[JeroenvdV]

Hi guys,

IEPY looks really well-made! Thank you for providing it all open source and well-documented. It does catch the eye that in recent years there has been less activity. Personally I'm just starting to look around the IE area and what tools there are, so I'm still possibly out of the loop on things. I'm curious what the development status is within Machinalis.

• Has IEPY become obsolete because of 'competing' projects? It doesn't seem like it to me at this point.
• Has internal/private development continued but not been pushed to the public repo?
• Are there open issues/features since 2016/2017 that haven't been developed yet due to lack of time, that would be pretty much a requirement (or nice-to-have) to start using IEPY (in certain use cases) in 2018?

Any insights into these questions would be great, I don't expect a complete answer right away by any means.

[JeroenvdV]

@jmansilla Hi, could you provide any insight here?

[jmansilla]

Hi! Thanks for the interest and the comments. The general answer for your questions here is that we are not currently working on the project. - Has IEPY become obsolete because of 'competing' projects? It doesn't seem like it to me at this point. Not sure. Probably. StanfordCoreNLP (what is used for preprocesing) made new releases that were not integrated. There are tons of new techniques for the preprocesing tasks based on neural nets that you may want to explore. - Has internal/private development continued but not been pushed to the public repo? Discontinued - Are there open issues/features since 2016/2017 that haven't been developed yet due to lack of time, that would be pretty much a requirement (or nice-to-have) to start using IEPY (in certain use cases) in 2018? Not sure.

…

On Thu, Aug 2, 2018 at 4:12 AM, JeroenvdV ***@***.***> wrote: Hi guys, IEPY looks really well-made! Thank you for providing it all open source and well-documented. It does catch the eye that in recent years there has been less activity. Personally I'm just starting to look around the IE area and what tools there are, so I'm still possibly out of the loop on things. I'm curious what the development status is within Machinalis. - Has IEPY become obsolete because of 'competing' projects? It doesn't seem like it to me at this point. - Has internal/private development continued but not been pushed to the public repo? - Are there open issues/features since 2016/2017 that haven't been developed yet due to lack of time, that would be pretty much a requirement (or nice-to-have) to start using IEPY (in certain use cases) in 2018? Any insights into these questions would be great, I don't expect a complete answer right away by any means. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#145>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAd046HbLJtqOydatWLVs5PlrpJs-1Qhks5uMqZYgaJpZM4Vrv9o> .

-- <https://www.machinalis.com/> Javier Mansilla CTO A: Av. Roque Saenz Peña 1357 <https://goo.gl/maps/PSrHwkozRaL2> P: +54 351 471 0977 <+54%20351%20471%200977> M: jmansilla@machinalis.com <jmansilla@machinalis.com> <http://www.linkedin.com/company/456525> <http://www.twitter.com/machinalis> <http://www.facebook.com/machinalis> <https://www.instagram.com/machinalis.life/>