April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] UFFI - Could not coerce arguments

by Ben Coman

On 27 April 2018 at 17:23, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > I would like to pass a pointer to an array of pointers to a FFI call and I > have problems ... > > âI have this method: > > runOutputs: aTF_OutputArray size: anInteger > | status outvalues | > status := TF_Status create. > outvalues := FFIExternalArray externalNewType: 'TF_Tensor*' size: > anInteger. > self library > runSession: self > options: FFIExternalObject null > inputs: FFIExternalObject null > values: FFIExternalObject null > Sorry I'm (again) not addressing your question :P, but please let me piggyback learning something. @All, What is the advantage of "FFIExternalObject null" ? I was under the impression that in general "nil" could be used in similar situations. cheers -ben > count: 0 > outputs: aTF_OutputArray getHandle > values: outvalues getHandle > count: anInteger > targets: FFIExternalObject null > count: 0 > metadata: FFIExternalObject null > status: status. > status check. > ^ outvalues > > âthe FFI call is like that : > > runSession: aTF_Session > options: opsTF_Buffer > inputs: inTF_OutputArray values: inTF_TensorArray count: inCount > outputs: outTF_OutputArray values: outTF_TensorArrayPtr count: outCount > targets: aTF_OperationArray count: targetCount > metadata: metaTF_Buffer > status: aTF_Status > > "F_CAPI_EXPORT extern void TF_SessionRun( > TF_Session* session, > // RunOptions > const TF_Buffer* run_options, > // Input tensors > const TF_Output* inputs, TF_Tensor* const* input_values, int ninputs, > // Output tensors > const TF_Output* outputs, TF_Tensor** output_values, int noutputs, > // Target operations > const TF_Operation* const* target_opers, int ntargets, > // RunMetadata > TF_Buffer* run_metadata, > // Output status > TF_Status*);" > > ^ self > ffiCall: #(void TF_SessionRun #(TF_Session * aTF_Session, > TF_Buffer * opsTF_Buffer, TF_Output * inTF_OutputArray, TF_Tensor * > inTF_TensorArray, int inCount, TF_Output * outTF_OutputArray, TF_Tensor * > outTF_TensorArrayPtr, int outCount, TF_Operation * aTF_OperationArray, int > targetCount, TF_Buffer * metaTF_Buffer, TF_Status * aTF_Status)) > module: TensorFlowCAPI > > TF_Tensor is an opaque object. > > I have an error: "Could not coerce arguments". > I guess this is related to the way I pass arguments to the FFI function ? > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ >

April 27, 2018

Re: [Pharo-users] UFFI - Could not coerce arguments

by Esteban Lorenzano

hi, it all depends on how you are declaring your types. here, for example you are passing aTF_OutputArray getHandle thatâs a âvoid*â value (an ExternalAddress or ExternalData object), and in declaration you have (if I read correctly): TF_Output * so, first question is: if TF_Output != void, then you have a coercing problem :). you can fix that just changing the notation to receive a void * (in C is all the same, but not in pharo :)) note that this can be happening in a lot of places, since your function has a lot of arguments, I just put an example of what can be wrong. cheers, Esteban > On 27 Apr 2018, at 11:23, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > I would like to pass a pointer to an array of pointers to a FFI call and I have problems ... > > âI have this method: > > runOutputs: aTF_OutputArray size: anInteger > | status outvalues | > status := TF_Status create. > outvalues := FFIExternalArray externalNewType: 'TF_Tensor*' size: anInteger. > self library > runSession: self > options: FFIExternalObject null > inputs: FFIExternalObject null > values: FFIExternalObject null > count: 0 > outputs: aTF_OutputArray getHandle > values: outvalues getHandle > count: anInteger > targets: FFIExternalObject null > count: 0 > metadata: FFIExternalObject null > status: status. > status check. > ^ outvalues > > âthe FFI call is like that : > > runSession: aTF_Session > options: opsTF_Buffer > inputs: inTF_OutputArray values: inTF_TensorArray count: inCount > outputs: outTF_OutputArray values: outTF_TensorArrayPtr count: outCount > targets: aTF_OperationArray count: targetCount > metadata: metaTF_Buffer > status: aTF_Status > > "F_CAPI_EXPORT extern void TF_SessionRun( > TF_Session* session, > // RunOptions > const TF_Buffer* run_options, > // Input tensors > const TF_Output* inputs, TF_Tensor* const* input_values, int ninputs, > // Output tensors > const TF_Output* outputs, TF_Tensor** output_values, int noutputs, > // Target operations > const TF_Operation* const* target_opers, int ntargets, > // RunMetadata > TF_Buffer* run_metadata, > // Output status > TF_Status*);" > > ^ self > ffiCall: #(void TF_SessionRun #(TF_Session * aTF_Session, TF_Buffer * opsTF_Buffer, TF_Output * inTF_OutputArray, TF_Tensor * inTF_TensorArray, int inCount, TF_Output * outTF_OutputArray, TF_Tensor * outTF_TensorArrayPtr, int outCount, TF_Operation * aTF_OperationArray, int targetCount, TF_Buffer * metaTF_Buffer, TF_Status * aTF_Status)) > module: TensorFlowCAPI > > TF_Tensor is an opaque object. > > I have an error: "Could not coerce arguments". > I guess this is related to the way I pass arguments to the FFI function ? > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for machines to execute." > http://www.doesnotunderstand.org/ <http://www.doesnotunderstand.org/>

April 27, 2018

UFFI - Could not coerce arguments

by Serge Stinckwich

I would like to pass a pointer to an array of pointers to a FFI call and I have problems ... âI have this method: runOutputs: aTF_OutputArray size: anInteger | status outvalues | status := TF_Status create. outvalues := FFIExternalArray externalNewType: 'TF_Tensor*' size: anInteger. self library runSession: self options: FFIExternalObject null inputs: FFIExternalObject null values: FFIExternalObject null count: 0 outputs: aTF_OutputArray getHandle values: outvalues getHandle count: anInteger targets: FFIExternalObject null count: 0 metadata: FFIExternalObject null status: status. status check. ^ outvalues âthe FFI call is like that : runSession: aTF_Session options: opsTF_Buffer inputs: inTF_OutputArray values: inTF_TensorArray count: inCount outputs: outTF_OutputArray values: outTF_TensorArrayPtr count: outCount targets: aTF_OperationArray count: targetCount metadata: metaTF_Buffer status: aTF_Status "F_CAPI_EXPORT extern void TF_SessionRun( TF_Session* session, // RunOptions const TF_Buffer* run_options, // Input tensors const TF_Output* inputs, TF_Tensor* const* input_values, int ninputs, // Output tensors const TF_Output* outputs, TF_Tensor** output_values, int noutputs, // Target operations const TF_Operation* const* target_opers, int ntargets, // RunMetadata TF_Buffer* run_metadata, // Output status TF_Status*);" ^ self ffiCall: #(void TF_SessionRun #(TF_Session * aTF_Session, TF_Buffer * opsTF_Buffer, TF_Output * inTF_OutputArray, TF_Tensor * inTF_TensorArray, int inCount, TF_Output * outTF_OutputArray, TF_Tensor * outTF_TensorArrayPtr, int outCount, TF_Operation * aTF_OperationArray, int targetCount, TF_Buffer * metaTF_Buffer, TF_Status * aTF_Status)) module: TensorFlowCAPI TF_Tensor is an opaque object. I have an error: "Could not coerce arguments". I guess this is related to the way I pass arguments to the FFI function ? -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

April 27, 2018

Re: [Pharo-users] Raspberry Pi

by Denis Kudriashov

Hi. 2018-04-26 22:36 GMT+02:00 CÃ©drick BÃ©ler <cdrick65(a)gmail.com>: > Hi Siemen, > > Running pharo on Pi is on my shirt to do list ^^ > > Did you try : > https://github.com/pharo-iot/PharoThings/blob/master/README.md > Yes. These instructions are valid > > The Pi vm link is different: > http://files.pharo.org/vm/pharo-spur32/linux/armv6/latest.zip > > [image: image1.jpeg] > > Never tried though ! > > Hth, > > Cedrick > > > Le 26 avr. 2018 Ã 21:19, Siemen Baader <siemenbaader(a)gmail.com> a Ã©crit : > > Hi, > > I'm trying to run a headless Pharo 6.1 server on a Raspberry Pi following > the instructions on https://medium.com/concerning- > pharo/pharo-pi-9eef257b6a21. > > The latest vm I can download is from 14 dec 2017 (see > http://files.pharo.org/vm/pharoS/raspbian/) and only works with Pharo > 4.0. Are Pharo 6 and 7 not being built for ARM anymore? > > Also Pharo does not want to start in headless mode as indicated by the > vm's help text: > > pi@raspberrypi:~/Pharo6.1-3 $ ./PharoS -headless Pharo.image eval "5+5" > setlocale() failed (check values of LC_CTYPE, LANG and LC_ALL) > unknown option: -headless > Usage: ./PharoS [<option>...] [<imageName> [<argument>...]] > ./PharoS [<option>...] -- [<argument>...] > > ALSA <option>s: > -nomixer disable mixer (volume) adjustment > -soundcard <name> open the named sound card (default: default) > -playback <name> play to the named sound device (default: default) > -capture <name> record from the named sound device (default: > default) > > X11 <option>s: > -browserWindow <wid> run in window <wid> > -browserPipes <r> <w> run as Browser plugin using descriptors <r> <w> > -cmdmod <n> map Mod<n> to the Command key > -compositioninput enable overlay window for composed characters > -display <dpy> display on <dpy> (default: $DISPLAY) > -fullscreen occupy the entire screen > -glxdebug <n> set GLX debug verbosity level to <n> > -headless run in headless (no window) mode > > <-----snip------> > > > Has anyone had success with a recent Pharo server on Pi? > > -- Siemen > >

April 27, 2018

Re: [Pharo-users] Showcasing Pharo, Roassal and Grafoscopio at re:publica 2018

by phil＠highoctane.be

On Thu, Apr 26, 2018 at 3:57 PM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > I will be showcasing Pharo, Roassal and Grafoscopio at re:publica 2018, > next week. As you may know, re:publica[2] is one of the most important > and visible media & digital culture conventions in Europe and is a good > scenario for the Pharo community. You can find details about my > participation at [1] > The "on how to use the Grafoscopio *pocket infrastructure* for data activism and digital citizenship " soundbite just blew my mind. "Pocket Infrastructure" hits the nail on the head for sure. I positively love that angle. Compared to python, node, etc, there is much less fuss to get started and it allows to focus on the data narrative right away. I regularly make folders in my Dropbox where I throw a pharo vm and a pharo image I work on, saved using https://github.com/Pharophile/HOImageSaver so that I can always go back in time easily (saved me more than once!). This very handy for working on machine A, and resuming work on machine B, or C etc. And is indeed "Pocket Infrastructure". > [1] > https://18.re-publica.com/en/session/data-clinic-twitter- > data-selfies-data-portraits > [2] https://18.re-publica.com/en > > I will be making intensive refactoring on the Dataviz package to create > some usual and unusual data visualizations from data exported from > Twitter, so I may be more active those days in the Discord and mailing > list channels, is some questions arise. > Do you already use DiscordSt? > > Thanks in advance for the Pharo communities support. I wouldn't be able > to be there without it. > What you achieve with Pharo makes me proud of supporting Pharo. Kudos Offray, we need more people like you in the world. _/\_ Phil > > Cheers, > > Offray > > > > >

April 27, 2018

Re: [Pharo-users] Showcasing Pharo, Roassal and Grafoscopio at re:publica 2018

by Ben Coman

On 26 April 2018 at 21:57, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > I will be showcasing Pharo, Roassal and Grafoscopio at re:publica 2018, > next week. As you may know, re:publica[2] is one of the most important > and visible media & digital culture conventions in Europe and is a good > scenario for the Pharo community. You can find details about my > participation at [1] > > [1] > https://18.re-publica.com/en/session/data-clinic-twitter- > data-selfies-data-portraits > [2] https://18.re-publica.com/en > > I will be making intensive refactoring on the Dataviz package to create > some usual and unusual data visualizations from data exported from > Twitter, so I may be more active those days in the Discord and mailing > list channels, is some questions arise. > > Thanks in advance for the Pharo communities support. I wouldn't be able > to be there without it. > > Cheers, > > Offray > > Printed material will be shared on how to recreate this experience, so your friends, family and fellow data activists can take and share their own Twitter data selfies and data portraits, to visualize part of their online presence and help to oversight public political discourse. Do you need any review/testing of this material? cheers -ben

April 27, 2018

Re: [Pharo-users] Showcasing Pharo, Roassal and Grafoscopio at re:publica 2018

by Tudor Girba

Excellent! Doru > On Apr 26, 2018, at 3:57 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I will be showcasing Pharo, Roassal and Grafoscopio at re:publica 2018, > next week. As you may know, re:publica[2] is one of the most important > and visible media & digital culture conventions in Europe and is a good > scenario for the Pharo community. You can find details about my > participation at [1] > > [1] > https://18.re-publica.com/en/session/data-clinic-twitter-data-selfies-data-… > [2] https://18.re-publica.com/en > > I will be making intensive refactoring on the Dataviz package to create > some usual and unusual data visualizations from data exported from > Twitter, so I may be more active those days in the Discord and mailing > list channels, is some questions arise. > > Thanks in advance for the Pharo communities support. I wouldn't be able > to be there without it. > > Cheers, > > Offray > > > -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."

April 27, 2018

Re: [Pharo-users] UFFI and autoRelease

by Ben Coman

On 26 April 2018 at 18:09, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > You don't reply to my original question, Ben :-) I didn't know the answer :P and I wasn't near an Image where I could poke around and speculate. Having a poke around now, but my thoughts are speculative - the few times I've used FFI I've muddled through rather than having a good grasp of it. >> On 24 Apr 2018, at 14:48, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> >> I'm using autoRelease on some FFIOpaqueObject instances. >> >> I need to test some behavior when I delete explicitly one of these objects. How to remove these objects from the finalization list, in order they are not freed two times. >> >> Something like ignoreFinalization ? On 25 April 2018 at 23:08, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > I don't understand the default > > finalizeResourceData: handle > handle isNull ifTrue: [ ^ self ]. > handle free. > handle beNull > > > when handle is an ExternaData, free is defined as in ExternalStructure class as: > > free > "Free the handle pointed to by the receiver" > (handle ~~ nil and:[handle isExternalAddress]) ifTrue:[handle free]. > handle := nil. > > > but beNull is not defined on nil. I presume your code is getting a DNU. Do you have a code extract to produce it? Looking only at the static code, my I can't get by the impression that there are two separate /handle/ variables in the above code. i.e. The /handle/ of FFIExternalReference-class>>finalizeResourceData: can't be set to nil by the ExternalStructure>>free. So, so far I can't provide a sensical answer. But I've had trouble debugging in the past keeping my /handle/s straight in different contexts and found it useful to temporarily refactor instance variables names to distriguish them. btw, I notice /handle/ of FFIExternalReference is defined in ExternalObject, whose class comment says... Instance variables: handle <ByteArray | ExternalAddress> ExternalAddress subclasses ByteArray and there is ExternalAddress>>beNull but no ByteArray>>beNull, So it seems FFIExternalReference further restricts /handle/ to be *only* ExternalAddress, which makes some sense (Reference~Addresss). Those comments don't indicate ExternalData is valid in /handle/ also indicated by ExternalData does not define #beNull. So I've got as far as wondering if either: * the class comment need updating, or * how ExternalData gets into /handle/ and is that a valid path. Sorry, not much help so far. cheers -ben > > I can define my own finalizeResourceData: but the default one, does not work apparently > > On Tue, Apr 24, 2018 at 2:06 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> hi, >> >> there is nothing like that and I do not recommend messing with the registry in general. >> butâ¦ you can always extend the classes for your use, is around FFIExternalResourceManager. >> >> cheers, >> Esteban P.S. Is your Image crashing from a double-free? I not been able to reproduce an observation from a while ago, but once I came across the object with an external memory reference that had been copied, so when the first object was #free'd, releasing external memory and setting /handle/ to nil to guard against a double-release, the copied-object's /handle/ was not nil, so when it was #free'd it also released the same external memory. Which is why I wonder that object holding references to external memory should behave like symbols where the default copy behaviour is to return itself. i.e. References to external malloc'd memory should be treated as *unique*. Taking a #copy of the reference doesn't produce extra external memory.

April 27, 2018

Re: [Pharo-users] libfreetype6 missing in the dependencies of ubuntu Pharo distribution

by Holger Freyther

> On 27. Apr 2018, at 04:55, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > I've just tried installing pharo from package manager on Elementary OS, which is a ubuntu derivative. > > All went well, except fonts weren't working in 32 bit version, and I had to install by hand "libfreetype6:i386" ... is it missing in the dependencies? which package did you install? holger

April 27, 2018

Re: [Pharo-users] Raspberry Pi

by Siemen Baader

Thanks, I'll try! Sent from my iPhone > On 26 Apr 2018, at 22.36, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > Hi Siemen, > > Running pharo on Pi is on my shirt to do list ^^ > > Did you try : > https://github.com/pharo-iot/PharoThings/blob/master/README.md > > The Pi vm link is different: > http://files.pharo.org/vm/pharo-spur32/linux/armv6/latest.zip > > <image1.jpeg> > > Never tried though ! > > Hth, > > Cedrick > > >> Le 26 avr. 2018 Ã 21:19, Siemen Baader <siemenbaader(a)gmail.com> a Ã©crit : >> >> Hi, >> >> I'm trying to run a headless Pharo 6.1 server on a Raspberry Pi following the instructions on https://medium.com/concerning-pharo/pharo-pi-9eef257b6a21. >> >> The latest vm I can download is from 14 dec 2017 (see http://files.pharo.org/vm/pharoS/raspbian/) and only works with Pharo 4.0. Are Pharo 6 and 7 not being built for ARM anymore? >> >> Also Pharo does not want to start in headless mode as indicated by the vm's help text: >> >> pi@raspberrypi:~/Pharo6.1-3 $ ./PharoS -headless Pharo.image eval "5+5" >> setlocale() failed (check values of LC_CTYPE, LANG and LC_ALL) >> unknown option: -headless >> Usage: ./PharoS [<option>...] [<imageName> [<argument>...]] >> ./PharoS [<option>...] -- [<argument>...] >> >> ALSA <option>s: >> -nomixer disable mixer (volume) adjustment >> -soundcard <name> open the named sound card (default: default) >> -playback <name> play to the named sound device (default: default) >> -capture <name> record from the named sound device (default: default) >> >> X11 <option>s: >> -browserWindow <wid> run in window <wid> >> -browserPipes <r> <w> run as Browser plugin using descriptors <r> <w> >> -cmdmod <n> map Mod<n> to the Command key >> -compositioninput enable overlay window for composed characters >> -display <dpy> display on <dpy> (default: $DISPLAY) >> -fullscreen occupy the entire screen >> -glxdebug <n> set GLX debug verbosity level to <n> >> -headless run in headless (no window) mode >> >> <-----snip------> >> >> >> Has anyone had success with a recent Pharo server on Pi? >> >> -- Siemen

April 26, 2018