Un petit article pour mettre en avant un site vraiment sympa: Coursera
Une centaine de cours disponible, une organisation parfaite, une ergonomie bien pensée, et tout ça gratuitement. Il y a même un petit faux-diplome à la fin en guise de cerise sur le gateau.
Je vais suivre uniquement le cours de Machine Learning, enseigné par Andrew Ng, Professeur à l’université de Stanford. Les vidéos + quiz + exercices m’ont l’air de prendre pas mal de temps mine de rien.
Ci dessous, des liens utiles et des aperçus du site.
After 2 simple apps made to discover the Windows Phone development (Simple Ping & WindChill Calculator), I started a month and a half ago to code a tool for League of Legends in order to assists me during ranked games.
First of all, « What’s League Of Legends? » some of you may ask.
League Of Legends is a very popular game, published by RIOT, gathering more than 10 milions of players. Its ancestor is a game called DotA (actually a mod for WarCraft III)
You usually play it 5 versus 5 (one player handling only one unit: his hero). During a match, you can’t have any information on your mates or your ennemies (there’s no « /stats X » command or those kind of tools).
LoL Assistant allows you to fill your mates & opponents names, and the app will gather every useful stats you need to know (level, ranking, ranked Wins/losses, normal wins/losses, ratios..) so you are:
Ready to own unskilled enemies. Focus them will give you the lead.
Careful versus strong enemies. You know you should play safe versus them, and gank them hard together.
Helpful with unskilled mates, don’t let them feed!
More aware of what good mates could say
Development:
After I coded 85% of the app, a friend of mine (http://www.who-is-ohw.com/) helped me getting a good design. I learnt quite a lot working with him, about how a team project can work out in a « friendly mood » without defining too much who is responsible of what precisely. Definitely not the same as my professional position!
Number of total downloads + ad related crashes after 3 weeks (yeah, so popular ;))
Ad provided by Microsoft adControl can sometimes bring some crashes (caught though), which make my dashboard looks like my app is not robust! I will work on a solution to avoid getting those useless reports during the next developments.
L’AI Challenge consiste à créer une intelligence artificielle: vous créerez un programme informatique (dans n’importe quel langage) qui contrôle une colonie de fourmis devant se battre contre d’autres colonies pour la domination totale!
Basic situation, the antHill on the top left corner, ants are white dots. Grey dots are food and blue is water (can’t go through)
Simple fight: 2 versus 1. The 2 orange ants will survive.
Complex map control by good players
Complex game control with several players
Ci dessous une partie des top players afin de visualiser le jeu:
NB: cliquez sur le bouton « plein écran » afin d’avoir un meilleur confort visuel et les touches +/- pour ajuster la vitesse de la partie.
Loading…
Les règles sont les suivantes :
Le joueur gagne des points (2) en rasant les fourmilières adverses. Il perd un point par fourmilière perdue.
A chaque fois que le joueur « ramasse » un bloc de nourriture, ce dernier disparait et une nouvelle fourmi est créée dans une des fourmilière de ce joueur.
Les parties sont jouées sur des cartes de 2 à 10 joueurs.
I’m going to describe briefly here how my C# bot works. It’s very far from being perfect, even far from being good but I made something working. And I finished it on time.
The code contains a couple of array -maps- containing different infos, updated in real time for some, and at the begining of every turn for others.
mapWater: Water map
mapVisible: number of my ants seeing a specific Tile
mapLastTurnSeen: Map of last turn value I’ve seen the specific Tile
It computes every routes in a certain range in order to protect my hills, attack enemy hills or collect food. Add them to a list and sort them afterwards
Food routes are less important than defendHills & attackHills ones. I picked a coef 3 in order to make this distinction. Thus a 3 cells AttackHill route is equivalent to a 9 food route.
After the filter applied, I give the « real » orders right away. (I won’t change them)
The defendHills make 2 of my closest ants go towards one enemy. No more.
One piece of food is target by only one of my ant (the closest, if not used for defending or attacking ofc)
Phase II: Attack close enemy ants
After that I make my free ants attacks close enemy. The idea is to « push » enemy and to diffuse my ants towards enemy hills.
Phase III : The Sentinel
After that I make, if I got enough ants, one of them stay close to my hill. This way I can see if an enemy is coming. This ant will not stay static because of the previous calls. If a food just appears, it will go collect it which will generate a new ant (which will probably take the « Gardian » position, if nothing else is needed) Same if an enemy ant approches, it will go fight it.
Phase IV: Explore the map
A good exploration state
Then and last, I call the ExploreMap function where Free ants will go explore the map.
I use a map monitoring the last tour I’ve seen every cell in order to make the ant goes somewhere « new ».
It goes towards 8 differents directions (E/N/S/W and combinaison like N-E)
I start one cell further the view range of the picked ant. If alls cells are already seen, I go one cell further. (Water tiles are not taken into account)
The 8 cells are then sorted by turn they have been seen. The ant will go toward the « oldest »
TECHNICAL DETAILS
1.Movement
Directions are made with an A* algorithm. I use the following one that I’ve modified just a little bit.
I have a list of timeout routes which helps me to not compute too long – complicated – routes again and again.
I wanted to do the same with computed routes (to not have to compute them again and again if needed, but they can change if I discover that an unseen tile is actually a water tile) I started to filter them every turn but it was really too time-consuming.
2. Fight:
Everytime I give an order, I test the « safety » of the area. My implementation is not really good, but it gives a basic idea of the security (not optimized though)
I sorted safety into 3 different categories (following some advice I found on the forum, Memetix® style)
SAFE: no worries it’s ok
KILL: I can expect to have a 1-1 trade with the enemy
DIE: It will be worse.
Some of the following conditions make my ants decide (or not) if they should go to a KILL area like :
If there’s a food between the enemy and I. If I have a lot of ants etc etc.
If it’s considered to be unwise to go, the ant will try a close direction, or to stay put or even to go back in order to avoid death.
PROBLEMS ENCOUNTERED
1. A* Algorithm
First of all, the A star algorithm.
I picked C# because it’s the language I use at work and I’m the most used to. However, existing Astar code are legion in c++ but real few in C#
I tested 2 very well graded on source code website. Istarted with what I thought was the best of them. Timeout used to occur if the path was 10-15 tiles long. I developed my bot during 2-3 weeks with this algo, making a lot of concessions because of the timeout problems. Then I found out it wasn’t normal at all and found a new one, which was described as « not perfect » because it’s not giving the shortest path.
It was the worst error I made, to not have discovered this one before. I kinda lost one week and a half.
2. Exploration
I started with monitoring how many ants were seeing every tile, trying to send them where tiles were « less » seen. It was working ok but I had some very bad « cycles » where ants used to jitter.
I switched to the last turn seen way, which gave me better results.
Before my final submission (like 12 hours before :s) I still had some bad behaviours: in some maze_map, ants used to stack at one point and jitter alltogether, like if it was awesome to finally have some security or friends or I don’t know. Anyway, I patched it quickly: ants which don’t have any orders at the end, if surrended by more than 7 ants in some small perimeter should go towards the closest enemy.
It’s dirty, it’s last minute modification, but I think it was worth it.
NB: After almost every group of modification I made during the last 2 days, I ran a couple of test games (~10) where I’m supposed to win against middle-skilled opponents. It happens that results were pretty bad so I could review the previous modifications.
CONCLUSION
I spent a lot of time on the exploration system. I wanted to go step by step and not rush the global feature bot too soon.
The first implementation I made was just monitoring enemy position, creating an array of « Unsafe » positions and … that’s it. It was obviously not good at all, my ants were just fearing every single enemy. I found the memetix post (link) and tried to implement it, but I guess I screwed up because I had to make some modifications and the result is far from my expectations. Time went fast and I couldn’t have a « proper » fighting system and the result is that I can’t really play map control like pro players do: having walls of ants facing each other.
Anyway, it was a really interesting contest. I’m glad I found it quite soon (I think I missed the 2 first weeks but I had 1month and a half to develop something) I’m also glad that « Fredo », a colleague of mine followed me on this event, so we could compare and improve our bots. I think the result would have been way worse (yeah, it’s possible I’m sure!) if I was alone on it.
Even if they won’t see that, I’d like to thanks the organizers for their amazing job. The game engine was awesome, the starter pack perfects, tools aswell. The finals (even if it’s still going on) are really interesting. The community was very friendly and best players gave tips and shared their source code at the end, which is very nice and very interesting.
Aujourd’hui je vous présente un exemple de code Powershell utilisant les types et fonctionnalités de l’Exchange Web Service Managed API (EWS API 1.1)
Le script suivant permet de parcourir un dossier d’email en particulier. Il check si les éléments possèdent un ID personnalisé (qui est une propriété étendue). Dans le cas contraire, il en affecte une (génération d’un GUID)
Voici le code:
$usertoQuery ="EMAILADDRESS"
$dllpath ="XXX\Microsoft.Exchange.WebServices.dll"[void][Reflection.Assembly]::LoadFile($dllpath)
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1)
$service.Credentials= new-object Microsoft.Exchange.WebServices.Data.WebCredentials("LOGIN","PWD","DOMAIN")
$service.Url= new-object Uri("http://URL/EWS/Exchange.asmx");
$svFldid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SearchFolders,$MailboxName)
$delFldid =[Microsoft.Exchange.WebServices.Data.DeleteMode]::HardDelete
$fvFolderView = new-object Microsoft.Exchange.WebServices.Data.FolderView(1000)
$folders = $service.findfolders($svFldid,$fvFolderView)
$ExtendedProp = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::PublicStrings, "MyCustomID", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String)
$ExtendedProp
$Propset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties, $ExtendedProp)foreach($folder in $folders){if($folder.displayName-eq "FOLDERNAME_I_WANT_TO_CHECK"){"We are in the correct folder"
$fvItemView = new-object Microsoft.Exchange.WebServices.Data.ItemView(10000)
$items = $service.FindItems($folder.Id,$fvItemView)#Don't show any result for the next line
$service.LoadPropertiesForItems($items, $Propset)foreach($item in $items){"**Subject** : "
$item.Subject"**Number of Extended Properties**: "
$item.ExtendedProperties.Count
$a =0foreach($extendedProperty in $item.ExtendedProperties){if($extendedProperty.PropertyDefinition.Name-eq $ExtendedProp.Name){
$a =1"Break (Value = "+ $extendedProperty.Value+")"break;}}if($a -eq 0){
$g1 =[Guid]::NewGuid()
$item.SetExtendedProperty($ExtendedProp, $g1.ToString())"Guid = "+ $g1
"ValueGuid added!"
$item.Update([Microsoft.Exchange.WebServices.Data.ConflictResolutionMode]::AlwaysOverwrite)"Item saved"}}}}
$usertoQuery = "EMAILADDRESS"
$dllpath = "XXX\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1)
$service.Credentials = new-object Microsoft.Exchange.WebServices.Data.WebCredentials("LOGIN","PWD","DOMAIN")
$service.Url = new-object Uri("http://URL/EWS/Exchange.asmx");
$svFldid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SearchFolders,$MailboxName)
$delFldid = [Microsoft.Exchange.WebServices.Data.DeleteMode]::HardDelete
$fvFolderView = new-object Microsoft.Exchange.WebServices.Data.FolderView(1000)
$folders = $service.findfolders($svFldid,$fvFolderView)
$ExtendedProp = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::PublicStrings, "MyCustomID", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String)
$ExtendedProp
$Propset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties, $ExtendedProp)
foreach ($folder in $folders)
{
if ($folder.displayName -eq "FOLDERNAME_I_WANT_TO_CHECK")
{
"We are in the correct folder"
$fvItemView = new-object Microsoft.Exchange.WebServices.Data.ItemView(10000)
$items = $service.FindItems($folder.Id,$fvItemView)
#Don't show any result for the next line
$service.LoadPropertiesForItems($items, $Propset)
foreach ($item in $items)
{
"**Subject** : "
$item.Subject
"**Number of Extended Properties**: "
$item.ExtendedProperties.Count
$a = 0
foreach ($extendedProperty in $item.ExtendedProperties)
{
if ($extendedProperty.PropertyDefinition.Name -eq $ExtendedProp.Name)
{
$a = 1
"Break (Value = " + $extendedProperty.Value + ")"
break;
}
}
if ($a -eq 0)
{
$g1 = [Guid]::NewGuid()
$item.SetExtendedProperty($ExtendedProp, $g1.ToString())
"Guid = " + $g1
"ValueGuid added!"
$item.Update([Microsoft.Exchange.WebServices.Data.ConflictResolutionMode]::AlwaysOverwrite)
"Item saved"
}
}
}
}
Et voila une base pour maitriser (un peu) la sémantique Powershell et manipuler l’api EWS d’une autre façon!
