Smalltalk › Pharo › Pharo Smalltalk Developers

Re: Pharo-dev Digest, Vol 20, Issue 158

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

csrabak

Re: Pharo-dev Digest, Vol 20, Issue 158

Hi Vicent,

-----Message d'origine-----
De : Pharo-dev [mailto:[hidden email]] De la part de [hidden email]
Envoy? : mardi 16 d?cembre 2014 15:14
? : [hidden email]
Objet : Re: [Pharo-dev] [ANN] RProjectConnector V1.0

> > > Hello everyone, I am glad to announce the first version of the
> > > RProjectConnector, a binding between Pharo and R using
> > > NativeBoost. You can now call directly your R methods from
> > > Pharo: data := (1 to: 1000) collect: #yourself. res := (#acf
> > > asRFunctionWith: {data}) eval To use it, you should copy the R
> > > libraries near the Pharo VM (see the documentation on
> > > SmalltalkHub to see how to proceed) and
>
> > I attempted to follow the directions at SmalltalkHub, but the
> > instructions there call for copying some DLLs, and in particular
> > the "grid.dll" is not available in the present R for Win (3.1.2)
> > installation.
> >
> "grid.dll" seems not required to do it working.

OK! Let's see if we can unravel the mystery of the rest!

> > > Gofer it smalltalkhubUser: 'VincentBlondeau' project:
> > > 'RProjectConnector'; configuration; loadStable Don't forget to
> > > relaunch Pharo after the installation to be able to use the
> > > connector.
> > After the succesfully install via Gofer, the relaunching of Pharo
> > with the image containing RProjectConnector never starts, and for
> > the worse no messages are availble (even in the stderr file in
> > image
> > directory). [snipped] How can I troubleshooted this?
> >
> That seems strange... Do you have a crash.dmp in the Pharo VM
> folder?

No I don't find any signal of activity for this (nor in the Windows task
manager to see if the Pharo.exe became zombie.

> Which is the version of Pharo you are using ? (Pharo 4.0
> and 3.0 are good) Is the image is even running but in the
> background?

I'm running Windows 8.1, Pharo3.0 Latest update: #30862.

The path for Pharo is C:\Users\csrabak\Fuba\H\Pharo3.0 and this is its content:

FT2Plugin.dll
Pharo.exe
Pharo.ini
Pharo3.0.changes
Pharo3.0.image
Pharo3.0.working.changes
Pharo3.0.working.image
PharoV30.sources
R.dll
README.txt
RProjectConnector.changes
RProjectConnector.image
Rblas.dll
Rgraphapp.dll
Riconv.dll
Rlapack.dll
Rzlib.dll
SqueakFFIPrims.dll
SqueakSSL.dll
gtoolkit.changes
gtoolkit.image
libcairo-2.dll
libeay32.dll
libfreetype-6.dll
libgit2.dll
libpixman-1-0.dll
libpng-3.dll
libssh2-1.dll
ssleay32.dll
stderr
stdout
zlib1.dll

> Also check if the VM folder contains some blanks, maybe it can be a
> problem...

As you can see above, the path has no blanks in its entire pathname.

> If you miss something in the config, you should receive a
> PostMortem error: 'The R session is not well initialized at
> startUp...'
>

I cannot arrive at this point... is there any VM or image switch that could help in this case?

Regards,

--
Cesar Rabak

Blondeau Vincent

Re: Pharo-dev Digest, Vol 20, Issue 158

-----Message d'origine-----
De : Pharo-dev [mailto:[hidden email]] De la part de [hidden email]
Envoyé : mardi 16 décembre 2014 18:48
À : [hidden email]
Objet : Re: [Pharo-dev] Pharo-dev Digest, Vol 20, Issue 158

Hi Vincent,

<Hi Cesar,

> > > Gofer it smalltalkhubUser: 'VincentBlondeau' project:
> > > 'RProjectConnector'; configuration; loadStable Don't forget to
> > > relaunch Pharo after the installation to be able to use the
> > > connector.
> > After the succesfully install via Gofer, the relaunching of Pharo
> > with the image containing RProjectConnector never starts, and for
> > the worse no messages are availble (even in the stderr file in
> > image directory). [snipped] How can I troubleshooted this?
> >
> That seems strange... Do you have a crash.dmp in the Pharo VM
> folder?

No I don't find any signal of activity for this (nor in the Windows task manager to see if the Pharo.exe became zombie.

> Which is the version of Pharo you are using ? (Pharo 4.0 and 3.0
> are good) Is the image is even running but in the background?

I'm running Windows 8.1, Pharo3.0 Latest update: #30862.

The path for Pharo is C:\Users\csrabak\Fuba\H\Pharo3.0 and this is its content:

FT2Plugin.dll
Pharo.exe
Pharo.ini
Pharo3.0.changes
Pharo3.0.image
Pharo3.0.working.changes
Pharo3.0.working.image
PharoV30.sources
R.dll
README.txt
RProjectConnector.changes
RProjectConnector.image
Rblas.dll
Rgraphapp.dll
Riconv.dll
Rlapack.dll
Rzlib.dll
SqueakFFIPrims.dll
SqueakSSL.dll
gtoolkit.changes
gtoolkit.image
libcairo-2.dll
libeay32.dll
libfreetype-6.dll
libgit2.dll
libpixman-1-0.dll
libpng-3.dll
libssh2-1.dll
ssleay32.dll
stderr
stdout
zlib1.dll

> Also check if the VM folder contains some blanks, maybe it can be a
> problem...

As you can see above, the path has no blanks in its entire pathname.

> If you miss something in the config, you should receive a
> PostMortem error: 'The R session is not well initialized at
> startUp...'
>

I cannot arrive at this point... is there any VM or image switch that could help in this case?

<I don't know if there is some switches in the VM to do it work under W8.
<You can try to do this steps for debugging:
< - Install the RProjectConnector package
< - Execute in the order: RSession checkLibs. RSession checkSession. RSession checkWorking. (these methods are called at startup). If you have an error please send the trace.
< - disable the method RSession>>startUp
< - Try to restart the image
< - Re-execute in the order: RSession checkLibs. RSession checkSession. RSession checkWorking
< - Try to launch some tests
< Regards,
< Vincent

Regards,

--
Cesar Rabak

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.