- Pharo-dev - lists.pharo.org

[ANN] Pharo Catalog web page updated

by Esteban Lorenzano

Hi, I spend some time today adding some functionality top the Pharo Catalog web page. Is still far from *good* but I think now is a lot better: http://catalog.pharo.org Enjoy, Esteban ps: as a âhistoryâ note, Pharo Catalog page was never intended to last too much, it was going to be replaced for a complete web-page, and it still will be, but since is not ready and I donât know when it will be, I think is better to enhance the current one :)

Oct. 7, 2015

Re: [Pharo-dev] Autonomous Shark-Monitoring Drone

by philippe.back＠highoctane.be

Maybe you want to connect with the people at Fleye. Their drone is quite close to what you have in mind. Le 7 oct. 2015 17:55, "Eliot Miranda" <eliot.miranda(a)gmail.com> a Ã©crit : > Dear Friends and Colleagues, > > as you may know, Sharks, as apex predators, are vital to maintaining > healthy marine ecosystems, and at the same time, their populations are > plummeting due to human actions. It is estimated for example that the > population of pelagic oceanic white tip sharks is reducing by 17% per year > [1] and I've heard (can't find a reference) that populations in the eastern > indian/western pacific are at 1% of normal levels. Such reductions in > populations create "trophic cascades" that produce wide-ranging changes in > populations of different species all the way down the food chain [2]. And > the marine ecosystem is a key source of human nutrition; it comprises > between 13% and 17% of global human protein intake [3]. > > As you may also know, there is currently a shark attack crisis in New > South Wales [4]. While most people in the region oppose killing sharks in > response to the crisis, existing solutions, netting and culling reduce > those same threatened populations of sharks upon which the sustainability > of marine food supply d ecosystems depend [5], and are arguably ineffective > [6]. Apparently the most successful approach at avoiding attacks is the > use of human spotters, as used in Cape Town, where people in tall towers > scan the sea close to shore [6]. > > But please watch this Youtube video > <https://www.youtube.com/watch?v=q2U3gjwJfS4> [7] from Pismo Beach, > California. The shark is spotted at about 1:20 into the video. This > drone, a phantom 3, is sending live video back to the operators, who are > using remote control. What we can see from this video is that the point of > view of drones is far superior to that of spotters. > > My first thought is that autonomous drones could provide a cheap and > scalable solution to patrolling beaches to prevent shark attacks. I expect > that processors like the Pi 2 have easily enough processing power to both > plan and execute search patterns along beaches, and perform the image > recognition necessary to reliably detect potentially dangerous sharks. A > drone might also be able autonomously to visit surfers and swimmers near to > the shark and warn them, either by some signal such as flashing red LEDs or > an audible message (language issues notwithstanding). The drone would have > to be able to identify swimmers and surfers in the water (not easy; sharks > confuse seals and surfers all the time), but computing an optimal route to > visit suspected swimmers should be relatively easy :-). > > I imagine that sooner or later it will be possible to construct cheap > rugged solar powered docking/charging shelters that drones could depart > from and return to, to charge and shelter from the elements after patrols. > Satellite communications could provide status reports for maintenance. > > My second thought is that as a community, we probably have all the > necessary expertise to construct a working prototype that at least > demonstrates feasibility. Such a prototype would have to be able to fly > above the ocean along a beach under its own control for a useful period of > time, at least 15 minutes, and demonstrate that it can identify a shark in > the water (we could use a rubber shark > <https://www.youtube.com/watch?v=9dghbyBaQyI> for testing ;-) ). > > Our community includes people doing image recognition with the Pi, radio > control experts, users of 3D printers, and some exceptional programmers. > If a small, strong group could be formed with the relevant expertise we may > be able to develop a prototype in a short enough time frame to be > relevant. Of course, availability of time is a big issue. I couldn't > contribute more than a few hours a week. But nothing ventured, nothing > gained. So I'm writing this message to the Squeak and Pharo communities, > and bcc'ing a few friends I know that have relevant expertise to ask for > two things; first, for good information on scoping out the project, > possible technologies, power budgets, costs, what is available > off-the-shelf (both in hardware and known algorithms) and what we would > need to construct ourselves, and second, for volunteers. Who among us are > really excited by this project, have relevant expertise and are motivated > to make a contribution? > > > [1] www.sharkadvocates.org/cites_4sharks_owt_fact_sheet.pdf > [2] http://www.globalshark.ca/pressmaterial/cascading/fig1_web.pdf > [3] http://www.who.int/nutrition/topics/3_foodconsumption/en/index5.html > [4] http://www.bbc.com/news/world-australia-34398516 > [5] > http://www.theguardian.com/environment/2015/sep/29/shark-hit-australian-com… > [6] http://www.nonswsharkcull.net/latestnews/tag/shark_spotting/ > [7] https://www.youtube.com/watch?v=q2U3gjwJfS4 > > > > crazier ideas: > > Infra red cameras are becoming cheap and easily available. Species like > Great White and Bull Shark have elevated metabolisms, effectively they are > warm blooded, so these two facts may allow spotting at night. > > Sharks are extremely sensitive to electrical fields; maybe some kind of > transmitter could be fitted to a drone, e.g. via a wire suspended in the > water, that could generate a field that could direct the shark away from > swimmers > > _,,,^..^,,,_ > best, Eliot >

Oct. 7, 2015

Re: [Pharo-dev] Problems with a large block

by Henrik Nergaard

Hi Marco, Had some fun with the code you posted :D. This *should* be the equivalent, but with less variables so that you can access the RBBlockNode. [ :h :s :v | | chroma rgb | chroma := s*v. rgb := { 0 . 0 . 0 }. rgb at: ((((h + 60) // 120) \\ 3) + 1) put: chroma; at: ((((h // 60) + 2 \\ 3) * 5 \\ 3) + 1) put: (chroma * (1.0 - (((h/60) \\ 2) - 1.0) abs)); collect: [ :part | (part + (v - (chroma) )) * 255 ] ] sourceNode . Best Regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Marco Naddeo Sent: Wednesday, October 7, 2015 3:49 PM To: Pharo-dev <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] Problems with a large block Hi, I have some problems with the large block at bottom: -sending the message argumentNames gives me an empty array #() -sending the message sourceNode gives me a strange result and not a RBBlockNode, as I would expect Best, Marco [ :h :s :v | | min chroma hdash X red green blue | red := 0. green:= 0. blue := 0. chroma := s * v. hdash := h / 60. X := chroma * (1.0 - ((hdash % 2) - 1.0) abs). (hdash < 1.0) ifTrue: [ red := chroma. green := X ] ifFalse: [ (hdash < 2.0) ifTrue: [ red := X. green := chroma ] ifFalse: [ (hdash < 3.0) ifTrue: [ green := chroma. blue := X ] ifFalse: [ (hdash < 4.0) ifTrue: [ green := X. blue := chroma ] ifFalse: [ (hdash < 5.0) ifTrue: [ red := X. blue := chroma ] ifFalse: [ (hdash <= 6.0) ifTrue: [ red := chroma. blue := X ] ] ] ] ] ]. min := v - chroma. { #red -> ((red + min) * 255). #green -> ((green + min) * 255). #blue -> ((blue + min) * 255) } ] -- Marco Naddeo PhD Student Dipartimento di Informatica UniversitÃ degli Studi di Torino Corso Svizzera 185, 10149 Torino, Italy

Oct. 7, 2015

Autonomous Shark-Monitoring Drone

by Eliot Miranda

Dear Friends and Colleagues, as you may know, Sharks, as apex predators, are vital to maintaining healthy marine ecosystems, and at the same time, their populations are plummeting due to human actions. It is estimated for example that the population of pelagic oceanic white tip sharks is reducing by 17% per year [1] and I've heard (can't find a reference) that populations in the eastern indian/western pacific are at 1% of normal levels. Such reductions in populations create "trophic cascades" that produce wide-ranging changes in populations of different species all the way down the food chain [2]. And the marine ecosystem is a key source of human nutrition; it comprises between 13% and 17% of global human protein intake [3]. As you may also know, there is currently a shark attack crisis in New South Wales [4]. While most people in the region oppose killing sharks in response to the crisis, existing solutions, netting and culling reduce those same threatened populations of sharks upon which the sustainability of marine food supply d ecosystems depend [5], and are arguably ineffective [6]. Apparently the most successful approach at avoiding attacks is the use of human spotters, as used in Cape Town, where people in tall towers scan the sea close to shore [6]. But please watch this Youtube video <https://www.youtube.com/watch?v=q2U3gjwJfS4> [7] from Pismo Beach, California. The shark is spotted at about 1:20 into the video. This drone, a phantom 3, is sending live video back to the operators, who are using remote control. What we can see from this video is that the point of view of drones is far superior to that of spotters. My first thought is that autonomous drones could provide a cheap and scalable solution to patrolling beaches to prevent shark attacks. I expect that processors like the Pi 2 have easily enough processing power to both plan and execute search patterns along beaches, and perform the image recognition necessary to reliably detect potentially dangerous sharks. A drone might also be able autonomously to visit surfers and swimmers near to the shark and warn them, either by some signal such as flashing red LEDs or an audible message (language issues notwithstanding). The drone would have to be able to identify swimmers and surfers in the water (not easy; sharks confuse seals and surfers all the time), but computing an optimal route to visit suspected swimmers should be relatively easy :-). I imagine that sooner or later it will be possible to construct cheap rugged solar powered docking/charging shelters that drones could depart from and return to, to charge and shelter from the elements after patrols. Satellite communications could provide status reports for maintenance. My second thought is that as a community, we probably have all the necessary expertise to construct a working prototype that at least demonstrates feasibility. Such a prototype would have to be able to fly above the ocean along a beach under its own control for a useful period of time, at least 15 minutes, and demonstrate that it can identify a shark in the water (we could use a rubber shark <https://www.youtube.com/watch?v=9dghbyBaQyI> for testing ;-) ). Our community includes people doing image recognition with the Pi, radio control experts, users of 3D printers, and some exceptional programmers. If a small, strong group could be formed with the relevant expertise we may be able to develop a prototype in a short enough time frame to be relevant. Of course, availability of time is a big issue. I couldn't contribute more than a few hours a week. But nothing ventured, nothing gained. So I'm writing this message to the Squeak and Pharo communities, and bcc'ing a few friends I know that have relevant expertise to ask for two things; first, for good information on scoping out the project, possible technologies, power budgets, costs, what is available off-the-shelf (both in hardware and known algorithms) and what we would need to construct ourselves, and second, for volunteers. Who among us are really excited by this project, have relevant expertise and are motivated to make a contribution? [1] www.sharkadvocates.org/cites_4sharks_owt_fact_sheet.pdf [2] http://www.globalshark.ca/pressmaterial/cascading/fig1_web.pdf [3] http://www.who.int/nutrition/topics/3_foodconsumption/en/index5.html [4] http://www.bbc.com/news/world-australia-34398516 [5] http://www.theguardian.com/environment/2015/sep/29/shark-hit-australian-com… [6] http://www.nonswsharkcull.net/latestnews/tag/shark_spotting/ [7] https://www.youtube.com/watch?v=q2U3gjwJfS4 crazier ideas: Infra red cameras are becoming cheap and easily available. Species like Great White and Bull Shark have elevated metabolisms, effectively they are warm blooded, so these two facts may allow spotting at night. Sharks are extremely sensitive to electrical fields; maybe some kind of transmitter could be fitted to a drone, e.g. via a wire suspended in the water, that could generate a field that could direct the shark away from swimmers _,,,^..^,,,_ best, Eliot

Oct. 7, 2015

Re: [Pharo-dev] Smalltalkhub instable

by Blondeau Vincent

Thanks Marcus Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Marcus Denker EnvoyÃ© : mercredi 7 octobre 2015 16:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Smalltalkhub instable On 07 Oct 2015, at 15:47, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, It is very hard to work because Smalltalkhub is very instable today. I wanted to launch https://ci.inria.fr/moose/job/moose-6.0 but I get either an 400 or 500 errorâ¦ (It seems to work now but for how long?) Can somebody could look at this issue ? I restarted apacheâ¦which seems to be the source of the problem when loading static files makes problems. Marcus ________________________________ 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.

Oct. 7, 2015

Re: [Pharo-dev] Smalltalkhub instable

by Marcus Denker

> On 07 Oct 2015, at 15:47, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > It is very hard to work because Smalltalkhub is very instable today. > I wanted to launch https://ci.inria.fr/moose/job/moose-6.0 <https://ci.inria.fr/moose/job/moose-6.0> but I get either an 400 or 500 errorâ¦ (It seems to work now but for how long?) > > Can somebody could look at this issue ? > I restarted apacheâ¦which seems to be the source of the problem when loading static files makes problems. Marcus

Oct. 7, 2015

Re: [Pharo-dev] Problems with a large block

by Marcus Denker

> On 07 Oct 2015, at 15:49, Marco Naddeo <naddeo(a)di.unito.it> wrote: > > Hi, > > I have some problems with the large block at bottom: > > -sending the message argumentNames gives me an empty array #() > -sending the message sourceNode gives me a strange result and not a RBBlockNode, as I would expect > This happens already with: [ :h :s :v | | min chroma hdash X red green blue | ] sourceNode I will checkâ¦ it is a bug in the mapping pc -> AST. Marcus

Oct. 7, 2015

Problems with a large block

by Marco Naddeo

Hi, I have some problems with the large block at bottom: -sending the message argumentNames gives me an empty array #() -sending the message sourceNode gives me a strange result and not a RBBlockNode, as I would expect Best, Marco [ :h :s :v | | min chroma hdash X red green blue | red := 0. green:= 0. blue := 0. chroma := s * v. hdash := h / 60. X := chroma * (1.0 - ((hdash % 2) - 1.0) abs). (hdash < 1.0) ifTrue: [ red := chroma. green := X ] ifFalse: [ (hdash < 2.0) ifTrue: [ red := X. green := chroma ] ifFalse: [ (hdash < 3.0) ifTrue: [ green := chroma. blue := X ] ifFalse: [ (hdash < 4.0) ifTrue: [ green := X. blue := chroma ] ifFalse: [ (hdash < 5.0) ifTrue: [ red := X. blue := chroma ] ifFalse: [ (hdash <= 6.0) ifTrue: [ red := chroma. blue := X ] ] ] ] ] ]. min := v - chroma. { #red -> ((red + min) * 255). #green -> ((green + min) * 255). #blue -> ((blue + min) * 255) } ] -- Marco Naddeo PhD Student Dipartimento di Informatica UniversitÃ degli Studi di Torino Corso Svizzera 185, 10149 Torino, Italy

Oct. 7, 2015

Smalltalkhub instable

by Blondeau Vincent

Hi, It is very hard to work because Smalltalkhub is very instable today. I wanted to launch https://ci.inria.fr/moose/job/moose-6.0 but I get either an 400 or 500 error... (It seems to work now but for how long?) Can somebody could look at this issue ? Thanks in advance, Vincent BLONDEAU ________________________________ 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.

Oct. 7, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 7c58b1: 50369

by Ferlicot D. Cyril

Le 07/10/2015 08:01, GitHub a Ã©crit : > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 7c58b1be0d0f72a2cdbb0f90ec6c374178b88efd > https://github.com/pharo-project/pharo-core/commit/7c58b1be0d0f72a2cdbb0f90… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2015-10-07 (Wed, 07 Oct 2015) > > Changed paths: > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50368.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50369.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50368.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50369.st > M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > > Log Message: > ----------- > 50369 > 16732 DNU when cancel fetch on retrieve icon sets > https://pharo.fogbugz.com/f/cases/16732 > > 16577 Random should be in its own package > https://pharo.fogbugz.com/f/cases/16577 > > 16726 move Reflectivity-Styling to a separate package > https://pharo.fogbugz.com/f/cases/16726 > > http://files.pharo.org/image/50/50369.zip > > This seems light for 3 bugs correctionsâ¦ -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Oct. 7, 2015