python / super oo-ness prevents hardware integration
Closed this issue · 3 comments
"yet another russian trolling comment"-
This thing should, in some sense, jive with Gary's comments about Matlab being easy to hookup filters and get some tests running on data.
Big annoyance in Ecto layout is the underlying desire for running python or other pc / server side scripting, when in many cases what you really want is to prototype something that ultimately wants to go onto lower-level hardware.
Matlab does this nicely with auto-generating C and VHDL from block-diagram filters ... (p.s. I don't see how to mark this as a comment or feature request as opposed to a bug ... maybe that's on the branch owner ? )
not a troll, a duplicate of #10.... keep 'em coming!
On 06/07/2011 10:46 AM, pkarasev3 wrote:
"yet another russian trolling comment"-
This thing should, in some sense, jive with Gary's comments about Matlab being easy to hookup filters and get some tests running on data.
Big annoyance in Ecto layout is the underlying desire for running python or other pc / server side scripting, when in many cases what you really want is to prototype something that ultimately wants to go onto lower-level hardware.
Matlab does this nicely with auto-generating C and VHDL from block-diagram filters ...
If you want to do hardware integration, look else where. ecto is not
meant to solve these issues. However, if you would like to do gpu,
openmp, or SIMD based computation, ecto will work fine, as its up to the
module to define its own computation.
Also python is not the only intended way of composing modules. Notice
how the module interface does not require the use of python specific apis.
Right, just hopefully that it doesn't inadvertently mandate that a
module use a lot of high level constructs and support, when it would
be nice to be able to prototype a module and then use it elsewhere.
On Tue, Jun 7, 2011 at 2:38 PM, ethanrublee
reply@reply.github.com
wrote:
On 06/07/2011 10:46 AM, pkarasev3 wrote:
"yet another russian trolling comment"-
This thing should, in some sense, jive with Gary's comments about Matlab being easy to hookup filters and get some tests running on data.
Big annoyance in Ecto layout is the underlying desire for running python or other pc / server side scripting, when in many cases what you really want is to prototype something that ultimately wants to go onto lower-level hardware.
Matlab does this nicely with auto-generating C and VHDL from block-diagram filters ...
If you want to do hardware integration, look else where. ecto is not
meant to solve these issues. However, if you would like to do gpu,
openmp, or SIMD based computation, ecto will work fine, as its up to the
module to define its own computation.Also python is not the only intended way of composing modules. Notice
how the module interface does not require the use of python specific apis.Reply to this email directly or view it on GitHub:
#16 (comment)