- Moose-dev - INF Mailman

by admin＠moosetechnology.org

11 years, 5 months

2
30
0 0

roassal2 job sets the author

by Tudor Girba

The Roassal2 job now sets the author. The builds does not crash anymore, but there are 11 failing tests. Here is the new script: ---- wget --quiet -O - http://get.pharo.org/30+vm | bash ./pharo Pharo.image save $JOB_NAME REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ./pharo $JOB_NAME.image config $REPO ConfigurationOfRoassal2 --install=development ./pharo $JOB_NAME.image eval "Author fullName: 'Test'. Smalltalk image saveAs: 'roassal-tests'" ./pharo roassal-tests.image test --junit-xml-output "Roassal2.*|Trachel.*" mv ./pharo-vm/PharoV20.sources ./ zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources ---- Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

3
6
0 0

Re: Build failed in Jenkins: roassal2 #50

by Alexandre Bergel

Apparently, the author info is asked by NativeBoost… Can you set the author in the script? Alexandre On Jan 27, 2014, at 11:28 AM, admin(a)moosetechnology.org wrote: > See <https://ci.inria.fr/moose/job/roassal2/50/> > > ------------------------------------------ > [URLTrigger] A change within the response URL invocation (log) > Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/roassal2/ws/> > > Deleting project workspace... done > > [roassal2] $ /bin/sh -xe /tmp/hudson3888068938556909847.sh > + + bash > wget --quiet -O - http://get.pharo.org/30+vm > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > + ./pharo Pharo.image save roassal2 > + REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main > + ./pharo roassal2.image config http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ConfigurationOfRoassal2 --install=development > [31m[33m > =============================================================================== > Notice: Installing ConfigurationOfRoassal2 development > =============================================================================== > [0m[0mInstalling ConfigurationOfRoassal2 development > > Loading dev of ConfigurationOfRoassal2... > Fetched -> Trachel-SamirSaleh.60 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Fetched -> Roassal2-JurajKubelka.94 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Loaded -> Trachel-SamirSaleh.60 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > Loaded -> Roassal2-JurajKubelka.94 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > ...finished dev+ ./pharo roassal2.image test --junit-xml-output Roassal2.*|Trachel.* > [31m[33m > =============================================================================== > Notice: Running tests in 2 Packages > =============================================================================== > [0m[0mRunning tests in 2 Packages > [31mAn attempt to use interactive tools detected, while in non-interactive mode > Interactive Request: [ Author identification ] Please type your full name. > It will be used to sign the changes you make to the image. > Spaces, accents, dashes, underscore and similar characters are not allowed > > [0mNonInteractiveUIManager>>nonInteractiveWarning: > NonInteractiveUIManager>>nonInteractiveRequest:title: > NonInteractiveUIManager>>request:initialAnswer:title:entryCompletion: > NonInteractiveUIManager>>request:initialAnswer:title: > AuthorNameRequest>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > AuthorNameRequest(Exception)>>signal > Author>>requestFullName > Author>>fullName > Author class>>fullName > Author class>>changeStamp > SQSurfaceDispatch class(ClassDescription)>>compile:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: in Block: [ self compile: code classified: category notifyin...etc... > BlockClosure>>ensure: > SystemAnnouncer>>suspendAllWhile: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified: > SQSurfaceDispatch class(NBExternalStructure class)>>createAccessorsFor: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors in Block: [ :fldName | self createAccessorsFor: fldName ] > NBExternalStructureFields>>fieldNamesDo: in Block: [ :name | aBlock value: name ] > Dictionary>>keysDo: in Block: [ :association | aBlock value: association key ] > Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock value: each ] ] > Array(SequenceableCollection)>>do: > Dictionary>>associationsDo: > Dictionary>>keysDo: > NBExternalStructureFields>>fieldNamesDo: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors > SQSurfaceDispatch class(NBExternalStructure class)>>fields > [0mBuild step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

1
0
0 0

Re: Issue 113 in moose-technology: Roassal should support lazy edges when used through the Mondrian API

by moose-technology＠googlecode.com

Updates: Summary: Roassal should support lazy edges when used through the Mondrian API Status: Labels: -Component-Mondrian Component-Roassal Comment #10 on issue 113 by tu...(a)tudorgirba.com: Roassal should support lazy edges when used through the Mondrian API http://code.google.com/p/moose-technology/issues/detail?id=113 No, it does not. But, it should. The idea is that the following Mondrian script should work: view edge: #edge from: 1 to: 2. view node: 1. view node: 2. For this, the edge creation should be evaluated only after all nodes are created. I changed the entry title and labels.

11 years, 5 months

1
6
0 0

Issue 1043 in moose-technology: Can't load glamour on Pharo 2.0

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1043 by damien.c...(a)gmail.com: Can't load glamour on Pharo 2.0 http://code.google.com/p/moose-technology/issues/detail?id=1043 $ wget --quiet -O - get.pharo.org/20+vm | bash $ ./pharo-ui Pharo.image config http://smalltalkhub.com/mc/Moose/Glamour/main ConfigurationOfGlamour --install=development --group="Core,Morphic,Roassal" This does not work anymore. MessageNotUnderstood: Character>>ensure: Character(Object)>>doesNotUnderstand: #ensure: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>with:during: MetacelloVersionConstructor>>specResolverBlock in Block: [:block | self with: versionSpec during: block] ByteString(SequenceableCollection)>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:attribute | | blockList | (blockList := self att...etc... OrderedCollection>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:versionSpec :pragma | (pragma argumentAt: 1)... MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:pragma | ... OrderedCollection>>do: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:versionString :pragmaColl | ... Dictionary>>keysAndValuesDo: in Block: [:assoc | aBlock value: assoc key value: assoc val...etc... Dictionary>>associationsDo: in Block: [:each | each... Array(SequenceableCollection)>>do: Dictionary>>associationsDo: Dictionary>>keysAndValuesDo: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: MetacelloVersionConstructor>>calculate:project: MetacelloVersionConstructor>>on: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: MetacelloVersionConstructor>>on: MetacelloVersionConstructor class>>on: ConfigurationOfGlamour>>project ConfigurationOfGlamour class>>project ConfigurationCommandLineHandler>>project ConfigurationCommandLineHandler>>metacelloVersion: -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 5 months

4
11
0 0

Source city

by Diego Lont

Hi all, I wanted to try out source city in Moose 5.0. The current pharo version there is Pharo3.0 (Latest update: #30714), so note before loading you need to install the slice that belongs to issue 12488. So somewhere regressions occurred. But after installing this slice, you still have to fix the configuration. I attached a fixed configuration, as I am not allowed to put it in the right spot. If someone could upload this, I would be much obliged. Cheers, Diego

11 years, 5 months

1
0
0 0

Re: Issue 1043 in moose-technology: Can't load glamour on Pharo 2.0

by Stephan Eggermont

I guess you need something similar to this in ConfigurationOfGlamour>stable spec for: #'common' version: '2.1'. spec for: #'pharo1.3.x' version: '2.2'. spec for: #'pharo1.4.x' version: '2.4'. spec for: #'pharo2.x' version: '2.5'. spec for: #'pharo3.x' version: '2.6-snapshot'.

11 years, 5 months

1
0
0 0

managing gtinspector extensions

by Tudor Girba

Hi, As you probably know by now, you can get the most our of the GTInspector by extending it with custom presentations. However, the problem that raises is how to manage these extensions? To solve this problem, just inspect the GTInspector and you will get a list with all these extensions. This list also serves as a set of examples that you can learn from. And because most of these extensions require just one method, you get a rather effective browser. [image: Inline image 1] You can see a more detailed explanation here: http://www.humane-assessment.com/blog/managing-gtinspector-extensions What else would you need in the GTInspector? Let me know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

1
0
0 0

www.moosetechnology.org down?

by NISHIHARA Satoshi

is http://www.moosetechnology.org/ down? best regards. -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

11 years, 5 months

2
1
0 0

Re: Build failed in Jenkins: roassal2 #41

by Alexandre Bergel

Hi! I do not understand. Apparently Roassal2 cannot be build. Any idea why? Alexandre On Jan 24, 2014, at 7:13 PM, admin(a)moosetechnology.org wrote: > See <https://ci.inria.fr/moose/job/roassal2/41/> > > ------------------------------------------ > [URLTrigger] A change within the response URL invocation (log) > Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/roassal2/ws/> > > Deleting project workspace... done > > [roassal2] $ /bin/sh -xe /tmp/hudson7964457589234081262.sh > + wget --quiet -O - http://get.pharo.org/30+vm > + bash > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Creating starter scripts pharo and pharo-ui > + ./pharo Pharo.image save roassal2 > + REPO=http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main > + ./pharo roassal2.image config http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main ConfigurationOfRoassal2 --install=development > [31m[33m > =============================================================================== > Notice: Installing ConfigurationOfRoassal2 development > =============================================================================== > [0m[0mInstalling ConfigurationOfRoassal2 development > > Loading dev of ConfigurationOfRoassal2... > Fetched -> Trachel-AlexandreBergel.57 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Fetched -> Roassal2-JurajKubelka.91 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ > Loaded -> Trachel-AlexandreBergel.57 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > RTDowserExample>>example6 (ROObject is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROElement is Undeclared) > > RTDowserBuilderTest>>testControlPointWith (ROBox is Undeclared) > > Loaded -> Roassal2-JurajKubelka.91 --- http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/ --- cache > ...finished dev+ ./pharo roassal2.image test --junit-xml-output Roassal2.*|Trachel.* > [31m[33m > =============================================================================== > Notice: Running tests in 2 Packages > =============================================================================== > [0m[0mRunning tests in 2 Packages > [31mAn attempt to use interactive tools detected, while in non-interactive mode > Interactive Request: [ Author identification ] Please type your full name. > It will be used to sign the changes you make to the image. > Spaces, accents, dashes, underscore and similar characters are not allowed > > [0mNonInteractiveUIManager>>nonInteractiveWarning: > NonInteractiveUIManager>>nonInteractiveRequest:title: > NonInteractiveUIManager>>request:initialAnswer:title:entryCompletion: > NonInteractiveUIManager>>request:initialAnswer:title: > AuthorNameRequest>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > AuthorNameRequest(Exception)>>signal > Author>>requestFullName > Author>>fullName > Author class>>fullName > Author class>>changeStamp > SQSurfaceDispatch class(ClassDescription)>>compile:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: in Block: [ self compile: code classified: category notifyin...etc... > BlockClosure>>ensure: > SystemAnnouncer>>suspendAllWhile: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified:notifying: > SQSurfaceDispatch class(ClassDescription)>>compileSilently:classified: > SQSurfaceDispatch class(NBExternalStructure class)>>createAccessorsFor: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors in Block: [ :fldName | self createAccessorsFor: fldName ] > NBExternalStructureFields>>fieldNamesDo: in Block: [ :name | aBlock value: name ] > Dictionary>>keysDo: in Block: [ :association | aBlock value: association key ] > Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock value: each ] ] > Array(SequenceableCollection)>>do: > Dictionary>>associationsDo: > Dictionary>>keysDo: > NBExternalStructureFields>>fieldNamesDo: > SQSurfaceDispatch class(NBExternalStructure class)>>rebuildFieldAccessors > SQSurfaceDispatch class(NBExternalStructure class)>>fields > [0mBuild step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

3
5
0 0

Re: a problem in latest moose 5.0 image

by Stephan Eggermont

Followups in the pharo-dev list, please Esteban wrote: >I would really like a reproducible case… in the form of an image, if no else. > >btw… moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems. I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated. Stephan

11 years, 5 months

2
3
0 0

Re: a problem in latest moose 5.0 image

by Stephan Eggermont

Yesterday I copied a configuration class with Nautilus copy command. I dragged it to the new category and noticed the same happening. In addition, the class side methods were not copied. Haven’t checked corresponding Pharo yet. Could be related to the RPackage problems though Stephan

11 years, 5 months

1
0
0 0

a problem in latest moose 5.0 image

by Esteban Lorenzano

Hi, Stef discovered a bug on latest moose image and I could reproduce it there, and not in corresponding pharo image. So I think is a problem that happens in some package installed by you :) Here is the issue: Take a class and drag it to a different package. It will not change the system category and therefore everything will became unstable. enjoy ;) Esteban

11 years, 5 months

1
0
0 0

Activity Diagram

by Serge Stinckwich

Dear all, with a colleague from Savoie University, we are looking for some Smalltalk code in order to model, execute and animate Activity Diagram. Any existing works ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

11 years, 5 months

5
9
0 0

Jenkins build became unstable: moose-5.0 #585

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/585/>

11 years, 5 months

1
0
0 0

PHP & Moose

by phil＠highoctane.be

Hello, I am currently doing some architecture and core reviews on a PHP-based application. I wondered if there was any PHP parser/tool that was freely available to try out some metrics collection with Moose. I saw Verveine by Googling the mailing list but not much. TIA Phil

11 years, 5 months

4
5
0 0

glamour-roassal loading problem

by Tudor Girba

Hi, The Moose builds fails now due to a strange loading problem. It seems that when loading Glamour, the extensions to Roassal get somehow deleted during the loading of the configuration. If you manually load the latest version of the package, everything is fine. You can see the problem both in the Moose and the GToolkit images: https://ci.inria.fr/moose/job/moose-5.0/ https://ci.inria.fr/moose/job/gtoolkit/ The strangest thing is that in the glamour image, the package is loaded properly: https://ci.inria.fr/moose/job/glamour/ I am too tired now to think properly right now, and I would need someone else to look at it. Anyone? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

2
3
0 0

Jenkins build is back to stable : moose-5.0 #577

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/577/>

11 years, 5 months

1
0
0 0

you spin me around...

by Alexandre Bergel

Hi! Juraj worked on rotating text. People have been asking for it for years… With Roassal 2: -=-=-=-=-=-=-=-=-=-= | v shape | v := RTView new. shape := RTRotatedLabel new. shape angleInDegree: [ :cls | cls numberOfMethods negated / 1.5 ]. shape text: [ :cls | ' ', cls name ]. shape color: (Color black alpha: 0.2). v addAll: (shape elementsOn: Collection withAllSubclasses). v canvas color: Color white. v open -=-=-=-=-=-=-=-=-=-= More screenshots and more examples on: https://www.facebook.com/media/set/?set=a.573528479400420.1073741841.340543… Excellent job Juraj! Before the end of January, we will make a big big announcement. We, the profilers, are working hard these days on a fantastic infrastructure for a better and stronger visual experience. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

4
6
0 0

roassal2 jenkins job

by Tudor Girba

Hi, I created a job dedicated to Roassal2: https://ci.inria.fr/moose/job/roassal2/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

2
1
0 0

Jenkins build became unstable: moose-5.0 #570

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/570/>

11 years, 5 months

1
0
0 0

Roassal2 is not loaded in the moose image?

by Alexandre Bergel

Hi! Apparently Roassal 2 is not loaded in the moose image. Hard to get a configuration right :-( Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

2
1
0 0

Ctrl + S in GTDebugger

by Usman Bhatti

Hello, Ctrls + S in GTDebugger does not save anymore the code source. I'm sure I saw it working before leaving for vacations but it seems the bug has reappeared. Is this still a known issue? regards, Usman

11 years, 5 months

3
4
0 0

MooseModel of Smalltalk code

by Anne Etien

Hi, I am working on MooseModels of Smalltalk code. There are some things that I feel strange: - there are some FAMIXAnnotationTypes and thus also FAMIXAnnotationTypeAttribute in Smalltalk. The comments of these classes refer to Java and never to ST. It seems corresponding to pragma such as: <expected failure>. - the FAMIXGlobalVariables have their belongsTo equals to nil. Only the declaredType is defined. - some FAMIXInvocations have no receiver. It seems that when a method m1 refers to a method m2 that does not belong to the model, the receiver is considered as nil. In Java, due to the statically typed character, we would have had a stub corresponding to m2. But in ST, because of the dynamically typed character, the receiver is nil. It means that before performing actions on Invocations, we have to ensure that they have receiver. Are we aware of that? Do we agree with that? If I can get you feedback on that points, it would be great. Thanks in advance. Anne

11 years, 5 months

2
2
0 0

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/

11 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev