Josh Marshall wrote:
>
>
> I don't see how you are going to get around doing the copies. Matlab
> is in a separate process from the Python interpreter, and there is no
> shared memory. In what way do you want these proxy classes to "look
> like numpy arrays"?
I am not talking about the copy in t
Hi David,
Sorry for the late reply. Can you CC any reply to me as well, as I
just get the digests and read them every few days.
On 08/11/2006, at 11:09 PM, David Cournapeau wrote:
I didn't know that, thanks. Unfortunately, it is not really what I am
trying to do: mlabwrap is just a python i
Matthew Brett wrote:
>
> I would be very happy to help with this. It would be great if we
> could get a standard well-maintained library of some sort towards
> scipy - we (http://neuroimaging.scipy.org/) have a great deal of
> matlab integration to do.
>
I am a bit busy and late on my PhD sched
David Cournapeau wrote:
> Andrew Straw wrote:
>
>> David Cournapeau wrote:
>>
>>
>>> - To send data from the calling process to matlab, you first have to
>>> create a mxArray, which is the basic matlab handler of a matlab array,
>>> and populating it. Using mxArray is very ackward
Andrew Straw wrote:
> David Cournapeau wrote:
>
>> - To send data from the calling process to matlab, you first have to
>> create a mxArray, which is the basic matlab handler of a matlab array,
>> and populating it. Using mxArray is very ackward : you cannot create
>> mxArray from existin
Josh Marshall wrote:
> Hi David,
>
> Did you have a look at mlabwrap? It's quite hard to find on the net,
> which is a shame, since it is a much more up to date version,
> enhancing pymat with the things that you are trying to do. It allows
> passing arrays and getting arrays back.
>
> http:/
Pauli Virtanen wrote:
> Hi all,
>
> ti, 2006-11-07 kello 11:23 +0900, David Cournapeau kirjoitti:
>
>> I am trying to find a nice way to communicate between matlab and
>> python. I am aware of pymat, which does that, but the code is
>> deprecated, and I thing basing the code on ctypes woul
Hi all,
ti, 2006-11-07 kello 11:23 +0900, David Cournapeau kirjoitti:
> I am trying to find a nice way to communicate between matlab and
> python. I am aware of pymat, which does that, but the code is
> deprecated, and I thing basing the code on ctypes would lead to much
> more robust code.
Hi,
> Thank you very much, I think this added documentation is pretty recent;
> I have never seen it before, and I did a lot a mex programming at some
> point... This whole mxarray nonsense reminds me why I gave up on matlab :),
I would be very happy to help with this. It would be great if we
co
Andrew Straw wrote:
> David Cournapeau wrote:
>
>> Andrew Straw wrote:
>>
>>
>>> David Cournapeau wrote:
>>>
>>>
>>>
- To send data from the calling process to matlab, you first have to
create a mxArray, which is the basic matlab handler of a matlab array,
David Cournapeau wrote:
> Andrew Straw wrote:
>
>> David Cournapeau wrote:
>>
>>
>>> - To send data from the calling process to matlab, you first have to
>>> create a mxArray, which is the basic matlab handler of a matlab array,
>>> and populating it. Using mxArray is very ackward
Andrew Straw wrote:
> David Cournapeau wrote:
>
>> - To send data from the calling process to matlab, you first have to
>> create a mxArray, which is the basic matlab handler of a matlab array,
>> and populating it. Using mxArray is very ackward : you cannot create
>> mxArray from existin
David Cournapeau wrote:
> - To send data from the calling process to matlab, you first have to
> create a mxArray, which is the basic matlab handler of a matlab array,
> and populating it. Using mxArray is very ackward : you cannot create
> mxArray from existing data, you have to copy data t
13 matches
Mail list logo
