January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PhD Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications

by StÃ©phane Ducasse

No one guy accepted and left after a couple of weeks. We know that bad pattern. Stef > Encore ?? > > Personne ne veut venir, câest Ã§a ? :P > > Ben > > On 20 Jan 2014, at 17:01, jannik laval <jannik.laval(a)gmail.com> wrote: > >> The position is available now. Interested candidates may apply as soon as possible. >> >> Title: Ph.D. Student Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications >> >> Location: Mines de Douai and ENSTA Brest (France) >> >> Advisor and contacts: >> Noury Bouraqadi (noury.bouraqadi(a)mines-douai.fr) >> Luc Fabresse (luc.fabresse(a)mines-douai.fr) >> LoÃ¯c Lagadec (loic.lagadec(a)ensta-bretagne.fr) >> Jannik Laval (jannik.laval(a)mines-douai.fr) >> >> Profile: the candidate must must hold a recent Master of Science degree in Computer Science or Software Engineering and must have solid skills in dynamic reflective language (Smalltalk). >> >> Description of the work: >> The goal of this PhD is to study Smalltalk integration with FPGAs for robotic applications. This integration will enable us get the best from both worlds. Developers are provided with a high-level dynamic reflective language (Smalltalk) for building and debugging their applications. Still, we can have high performances by projecting part of the programs into FPGAs. These reconfigurable hardware chips can achieve performance faster than C programs, while consuming much less energy. >> >> The work to do can decompose into the following tasks: >> -Build reference robotic applications fully in Pharo Smalltalk using actual robots (see http://car.mines-douai.fr/robots/) >> -Analyze these applications to identify critical parts to project on FPGAs to significantly increase performances (speed, energy) >> -Do the actual projection to FPGA and evaluate performances of the transformed applications >> -Generalize the approach and define a methodology for turning Smalltalk code into FPGA >> -Propose a solution to automate the methodology >> >> The Ph.D student will receive a grant which net amount is approximately 1420 euros per month for 3 years (36 months). >> He will be co-supervised by LoÃ¯c Lagadec from the ENSTA-Bretagne (Lab-STICC, Brest) and Jannik Laval, Luc Fabresse and Noury Bouraqadi from Ecole des Mines de Douai (CAR, http://car.mines-douai.fr/) >> The first 18th month will be spent in Douai (Lille area), while the last half of the PhD will be spent in Brest. >> However, during the full 3 years, there will be a strong interaction with co-supervisers from both labs. >> >> Bibliography: >> -A Robust Layered Control System For A Mobile Robot. R. Brooks. IEEE Journal of Robotics and Automation. Vol. 2. Num 1. March, 1985. >> -RCS: A Cognitive Architecture for Intelligent MultiAgent Systems. J.S. Albus and A. J. Barbera. Proceedings of the 5th IFAC/EURON Symposium on Intelligent Autonomous Vehicles (IAV 2004). Lisbon, Portugal, 2004. >> -Handbook of Robotics. Bruno Siciliano and Oussama Khatib editors. Springer. 2008. >> -Multi-Level Simulation of Heterogeneous Reconfigurable Platforms. D. Picard and L. Lagadec. International Journal of Reconfigurable Computing. 2012. >> -High-level synthesis for FPGAs: From Prototyping to Deployment. Jason cong and stephen neuendorffer and juanjo noguera and kees vissers and zhiru zhang. IEEE Transactions on Computer-aided design of integrated circuits and systems. Vol. 30. Num 4. April, 2011. >> -The MOLEN Polymorphic Processor. S. Vassiliadis and S. Wong and G. Gaydadjiev and K. Bertels and G. Kuzmanov and E. Moscu Panainte. IEEE Transactions on Computers. 2004. >> >> -- >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://car.mines-douai.fr/ >> >

Jan. 20, 2014

Re: [Pharo-dev] PhD Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications

by Benjamin

Encore ?? Personne ne veut venir, câest Ã§a ? :P Ben On 20 Jan 2014, at 17:01, jannik laval <jannik.laval(a)gmail.com> wrote: > The position is available now. Interested candidates may apply as soon as possible. > > Title: Ph.D. Student Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications > > Location: Mines de Douai and ENSTA Brest (France) > > Advisor and contacts: > Noury Bouraqadi (noury.bouraqadi(a)mines-douai.fr) > Luc Fabresse (luc.fabresse(a)mines-douai.fr) > LoÃ¯c Lagadec (loic.lagadec(a)ensta-bretagne.fr) > Jannik Laval (jannik.laval(a)mines-douai.fr) > > Profile: the candidate must must hold a recent Master of Science degree in Computer Science or Software Engineering and must have solid skills in dynamic reflective language (Smalltalk). > > Description of the work: > The goal of this PhD is to study Smalltalk integration with FPGAs for robotic applications. This integration will enable us get the best from both worlds. Developers are provided with a high-level dynamic reflective language (Smalltalk) for building and debugging their applications. Still, we can have high performances by projecting part of the programs into FPGAs. These reconfigurable hardware chips can achieve performance faster than C programs, while consuming much less energy. > > The work to do can decompose into the following tasks: > -Build reference robotic applications fully in Pharo Smalltalk using actual robots (see http://car.mines-douai.fr/robots/) > -Analyze these applications to identify critical parts to project on FPGAs to significantly increase performances (speed, energy) > -Do the actual projection to FPGA and evaluate performances of the transformed applications > -Generalize the approach and define a methodology for turning Smalltalk code into FPGA > -Propose a solution to automate the methodology > > The Ph.D student will receive a grant which net amount is approximately 1420 euros per month for 3 years (36 months). > He will be co-supervised by LoÃ¯c Lagadec from the ENSTA-Bretagne (Lab-STICC, Brest) and Jannik Laval, Luc Fabresse and Noury Bouraqadi from Ecole des Mines de Douai (CAR, http://car.mines-douai.fr/) > The first 18th month will be spent in Douai (Lille area), while the last half of the PhD will be spent in Brest. > However, during the full 3 years, there will be a strong interaction with co-supervisers from both labs. > > Bibliography: > -A Robust Layered Control System For A Mobile Robot. R. Brooks. IEEE Journal of Robotics and Automation. Vol. 2. Num 1. March, 1985. > -RCS: A Cognitive Architecture for Intelligent MultiAgent Systems. J.S. Albus and A. J. Barbera. Proceedings of the 5th IFAC/EURON Symposium on Intelligent Autonomous Vehicles (IAV 2004). Lisbon, Portugal, 2004. > -Handbook of Robotics. Bruno Siciliano and Oussama Khatib editors. Springer. 2008. > -Multi-Level Simulation of Heterogeneous Reconfigurable Platforms. D. Picard and L. Lagadec. International Journal of Reconfigurable Computing. 2012. > -High-level synthesis for FPGAs: From Prototyping to Deployment. Jason cong and stephen neuendorffer and juanjo noguera and kees vissers and zhiru zhang. IEEE Transactions on Computer-aided design of integrated circuits and systems. Vol. 30. Num 4. April, 2011. > -The MOLEN Polymorphic Processor. S. Vassiliadis and S. Wong and G. Gaydadjiev and K. Bertels and G. Kuzmanov and E. Moscu Panainte. IEEE Transactions on Computers. 2004. > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ >

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by StÃ©phane Ducasse

I commented the code in a slice that apparently was not integrated. But yes this is a good idea. - to have more code review - to revive the COTDC!!!! > I had some questions about NewValueHolder and I figured, why not revive > COTDC?! > > The current comment is: "A NewValueHolder is a new implementation of > ValueHolder based on Announcements". Of course, ValueHolder doesn't have a > class comment. Wikipedia claims a value holder is "a generic object that > handles the lazy loading behavior, and appears in place of the object's data > fields" [1]. So: > - what is a NewValueHolder? > - is the "Value Holder" part of the name accurate in light of [1]. Obviously > repurposing a term people may already be familiar with is a bad idea. In > fact the important part here seems not the holding of the value, but the > notification of changes. It seems more like an event in FRP. How about > ReactiveVariable or AnnouncingVariable, since it combines the storage of a > variable with announcing of changes? I like Reactive a bit better because > those familiar with FRP will get the idea that it's notifying dependents, > Announcing maybe begs the question "announcing what?" > - should it replace ValueHolder, which is used only by > ExclusiveWeakMessageSend and WidgetExamples > > [1] http://en.wikipedia.org/wiki/Lazy_loading > > p.s. [OT] valueChanged: oldValue to: newValue seems fishy. It is only used > in one place in the image in this weird way "pickedItemsHolder valueChanged: > true to: item" > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/COTDC-108-NewValueHolder-tp4738066.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 20, 2014

PhD Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications

by jannik laval

The position is available now. Interested candidates may apply as soon as possible. *Title:* Ph.D. Student Position on Dynamic Reflective Language Integration with FPGAs for Robotic Applications *Location:* Mines de Douai and ENSTA Brest (France) *Advisor and contacts:* Noury Bouraqadi (noury.bouraqadi(a)mines-douai.fr) Luc Fabresse (luc.fabresse(a)mines-douai.fr) LoÃ¯c Lagadec (loic.lagadec(a)ensta-bretagne.fr) Jannik Laval (jannik.laval(a)mines-douai.fr) *Profile:* the candidate must must hold a recent Master of Science degree in Computer Science or Software Engineering and must have solid skills in dynamic reflective language (Smalltalk). *Description of the work:* The goal of this PhD is to study Smalltalk integration with FPGAs for robotic applications. This integration will enable us get the best from both worlds. Developers are provided with a high-level dynamic reflective language (Smalltalk) for building and debugging their applications. Still, we can have high performances by projecting part of the programs into FPGAs. These reconfigurable hardware chips can achieve performance faster than C programs, while consuming much less energy. The work to do can decompose into the following tasks: -Build reference robotic applications fully in Pharo Smalltalk using actual robots (see http://car.mines-douai.fr/robots/) -Analyze these applications to identify critical parts to project on FPGAs to significantly increase performances (speed, energy) -Do the actual projection to FPGA and evaluate performances of the transformed applications -Generalize the approach and define a methodology for turning Smalltalk code into FPGA -Propose a solution to automate the methodology The Ph.D student will receive a grant which net amount is approximately 1420 euros per month for 3 years (36 months). He will be co-supervised by LoÃ¯c Lagadec from the ENSTA-Bretagne (Lab-STICC, Brest) and Jannik Laval, Luc Fabresse and Noury Bouraqadi from Ecole des Mines de Douai (CAR, http://car.mines-douai.fr/) The first 18th month will be spent in Douai (Lille area), while the last half of the PhD will be spent in Brest. However, during the full 3 years, there will be a strong interaction with co-supervisers from both labs. *Bibliography:* -A Robust Layered Control System For A Mobile Robot. R. Brooks. IEEE Journal of Robotics and Automation. Vol. 2. Num 1. March, 1985. -RCS: A Cognitive Architecture for Intelligent MultiAgent Systems. J.S. Albus and A. J. Barbera. Proceedings of the 5th IFAC/EURON Symposium on Intelligent Autonomous Vehicles (IAV 2004). Lisbon, Portugal, 2004. -Handbook of Robotics. Bruno Siciliano and Oussama Khatib editors. Springer. 2008. -Multi-Level Simulation of Heterogeneous Reconfigurable Platforms. D. Picard and L. Lagadec. International Journal of Reconfigurable Computing. 2012. -High-level synthesis for FPGAs: From Prototyping to Deployment. Jason cong and stephen neuendorffer and juanjo noguera and kees vissers and zhiru zhang. IEEE Transactions on Computer-aided design of integrated circuits and systems. Vol. 30. Num 4. April, 2011. -The MOLEN Polymorphic Processor. S. Vassiliadis and S. Wong and G. Gaydadjiev and K. Bertels and G. Kuzmanov and E. Moscu Panainte. IEEE Transactions on Computers. 2004. -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Jan. 20, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] MessageTally in GTInspector

by Pharo4Stef

On 20 Jan 2014, at 19:47, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Stef, are you asking for aspects? :-P No just managing mess :) > > On Jan 20, 2014, at 12:48 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> this is not only loading the challenges. we should handle cross cutting changes. >> >> Stef >> >> On 20 Jan 2014, at 11:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> I think I understand the implications. >>> >>> Moose comes with these tools out of the box, so for people that work with Moose it makes perfect sense to work with tools from the future :). Btw, you can work with the bare GToolkit (only the components needed for Pharo) from here: >>> https://ci.inria.fr/moose/job/gtoolkit/lastSuccessfulBuild/artifact/gtoolki… >>> >>> I also think that the dependency problem is an important one, but it is orthogonal with the work on producing the IDE. I want to get these tools in Pharo, and I want to spend the energy in ensuring modularity, too. The components of the GToolkit are modular now. If at some point we decide to integrate them, the simplest thing we can do is to create the job that ensures their unloadability before the integration. >>> >>> Another option is to go back to a Core image and build the working image. I think we should reevaluate this option in the light of the latest Monticello speedups. For example, the current build time for a GToolkit image is 1.5 mins (loads Glamour, Roassal, Graph-ET, GToolkit) which is not a lot. >>> >>> Doru > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Jan. 20, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Benjamin

On 20 Jan 2014, at 15:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I had some questions about NewValueHolder and I figured, why not revive > COTDC?! I loved it :) > > The current comment is: "A NewValueHolder is a new implementation of > ValueHolder based on Announcements". Of course, ValueHolder doesn't have a > class comment. Wikipedia claims a value holder is "a generic object that > handles the lazy loading behavior, and appears in place of the object's data > fields" [1]. So: > - what is a NewValueHolder? I am a class holding any object inside its unique instance variable. Each time the instance variable value changes, an announcement is emitted. The instance variable is accessed through `value` and `value:` while the registration is done by `whenChangedDo: aBlock`. In addition, infinite loops of propagation are prevented. Use case: you have two lists A, and B, and you want to keep their selection synchronised. So when A selection changes, you set B selection. But since B selection changes, you set A selection, and so onâ¦ This case is prevented by the use of value holders. > - is the "Value Holder" part of the name accurate in light of [1]. Nope :( > Obviously > repurposing a term people may already be familiar with is a bad idea. Itâs called NewValueHolder because itâs a re-implementation of ValueHolder :) I did not checked the name :P > In > fact the important part here seems not the holding of the value, but the > notification of changes. Indeed > It seems more like an event in FRP. How about > ReactiveVariable or AnnouncingVariable, since it combines the storage of a > variable with announcing of changes? I like Reactive a bit better because > those familiar with FRP will get the idea that it's notifying dependents, > Announcing maybe begs the question "announcing what?â I like Reactive too. It sounds like we are doing cool things :P > - should it replace ValueHolder, which is used only by > ExclusiveWeakMessageSend and WidgetExamples Might be yes, I did not checked the users of ValueHolder in a while. > p.s. [OT] valueChanged: oldValue to: newValue seems fishy. It is only used > in one place in the image in this weird way "pickedItemsHolder valueChanged: > true to: itemâ Probably a bad hack I did :P Ben

Jan. 20, 2014

Re: [Pharo-dev] Making Platform Installers

by Torsten Bergmann

Hi Santiago, when sending a link from a SqueakSource instance please send the project name like: http://car.mines-douai.fr/squeaksource/MyKillerApp.html The link you used http://car.mines-douai.fr/squeaksource/@vLtUOBuLaxNWsghP/UmsTHzMp was an active session and can not be used by others since it will alway end up on the frontpage. Â Bye T.

Jan. 20, 2014

Re: [Pharo-dev] RFB on a headless Pharo 3

by Torsten Bergmann

Also try RFBLog dumpLogToTranscript: true before running. Then a dump on the Transcript will appear. There you will see that there is a DNU for a Cursor instance which does not understand #maskForm in method #sendCursorShape: Interesting enough ivar "newCursor" is an instance of Cursor - but and only subclass like CursorWithMask understand #maskForm. It is initialized in #initServer:socket:reverse: with "Cursor currentCursor" returning - either a Cursor instance when I inspect it using the menu - a CursorWithMask instance when I inspect it using CMD keys No time to dig deeper today. Keep us informed about your progress. An updated ConfigurationOfRFB would be nice... Bye T.

Jan. 20, 2014

Re: [Pharo-dev] Making Platform Installers

by Santiago Bragagnolo

I have done a tool for PhaROS distribution, that is for deploying a package into a middleware, it lets you define the layout of folders, is prepared to add ways of writing ( actually it has implemented the version for local file system, but it should be easy to implement remote deploying ). It let you download vm, image , sources, and it has two post processing places for adding hooks: one in the image that is making the installation, other in the image is being installed. It has a silent mode of execution, when it does run everything in headless Even when it was mean for deploying on middleware, it should be useful. There are two actual disclaimers: is not working in windows yet, you will need to code a bit to specify the layout of installation (is not that is really bad, but is not done yet) http://car.mines-douai.fr/squeaksource/@vLtUOBuLaxNWsghP/UmsTHzMp So tell me if you need it. 2014/1/18 Sean P. DeNigris <sean(a)clipperadams.com> > Are there up-to-date instructions - or better yet CI scripts - or even > better > Smalltalk CI scripts :) - to make installers for Mac/Windows/Unix? > > How about if one can not install anything? Mac is easy enough, as a bundle > has everything hidden in one, but what about Windows? Can one do better > than > a batch file + Pharo.ini specifying the image? Or an sh file + > folder-with-everything-else for unix? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Making-Platform-Installers-tp4737775.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Jan. 20, 2014

[COTDC] 108 - NewValueHolder

by Sean P. DeNigris

I had some questions about NewValueHolder and I figured, why not revive COTDC?! The current comment is: "A NewValueHolder is a new implementation of ValueHolder based on Announcements". Of course, ValueHolder doesn't have a class comment. Wikipedia claims a value holder is "a generic object that handles the lazy loading behavior, and appears in place of the object's data fields" [1]. So: - what is a NewValueHolder? - is the "Value Holder" part of the name accurate in light of [1]. Obviously repurposing a term people may already be familiar with is a bad idea. In fact the important part here seems not the holding of the value, but the notification of changes. It seems more like an event in FRP. How about ReactiveVariable or AnnouncingVariable, since it combines the storage of a variable with announcing of changes? I like Reactive a bit better because those familiar with FRP will get the idea that it's notifying dependents, Announcing maybe begs the question "announcing what?" - should it replace ValueHolder, which is used only by ExclusiveWeakMessageSend and WidgetExamples [1] http://en.wikipedia.org/wiki/Lazy_loading p.s. [OT] valueChanged: oldValue to: newValue seems fishy. It is only used in one place in the image in this weird way "pickedItemsHolder valueChanged: true to: item" ----- Cheers, Sean -- View this message in context: http://forum.world.st/COTDC-108-NewValueHolder-tp4738066.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 20, 2014