I love Stephen Colbert! I love Spider-man! Together, they can do no wrong!

You might also like…
¤ The Spectacular Spider-man

This is indeed objectively awesome.

[Via E! Online]

You can find some cool little (or big) gifts for yourself or a friend at SUCK UK.
They have a lot of funky little items if you hunt around the site...SUCK UK. Thier located in the UK...duh, but they take Paypal, which is cool for you...dangerous for me. Click the link above to check it out.

Ciao.

"These vampire
teeth are useful for holding place cards and are not the type of things
most people should steal. They can take their chances trying to hide a
set of fangs on them if they choose, but I know I would never take a
chance like that. Maybe that is just what the fangs want you to do so
they can get you alone."

Product Page ($20)

Neatniks! Come home, It's Clean!

Call (414) 745-6532

in the greater Milwaukee area

I just wanted to take the time to say, "Thanks." I've noticed that you really haven't been using me too much, and I couldn't be happier. I'm sure its because of all the other important things you have to worry about; work, kids, school, meals, etc. Of course, the house is looking a little unkempt.

Instead of using me, why don't you relax and let the professionals at NeatNiks! clean the house for you? You could go out, relax, or spend more time with the family! Let them use their sponges!

They give free estimates, too! I looked up their number for you. Its (414) 745-6532. Call today! And, thanks again.

Your sponge

The run-of-the-mill, daily things got me down... even now if I don't do SOMETHING today it'll drive me to that point again. Washing hasn't been done, the dishes were left for me to do again and not getting organised enough to have dinner on the table after work (I finished at 11pm) all drive me nuts.

I've discovered (or should I say just realised a little more?) I am a organised but messy person. Meaning, that I can plan a day out to a T but when I try to be neat, it just doesn't happen. Well although there are 2 of us in this little house, I know my attempts of tidying up have had little effect.

So I'm gonna try and tidy up today -trying to be neat! Will see what happens. The weather looks horrible so I have no real excuse to do anything else unless I want to get all wet (it looks like it'll rain soon).

"Here's a nice gag for hanging an upside-down bookshelf on your wall -- the books are held in with elasticated strips of cloth:

The inverted bookshelf turns a bit of your living room upside down as
it hangs all of the books from the bottom instead of supporting them
from below. It's a satisfying optical trick and doesn't damage any of
the books. In fact, you can take books in and out of it whenever you
want."

/Inverted Bookshelf

(via Neatorama)

I *love* vodka, you must understand this before anything else. So when I say to you that Zyr is my favorite vodka, this is definitely saying something bold.

Its pretty blue bottle stands out from anywhere, and it is a gorgeous a bottle. Something very nice to see match its classy qualities; the presentation is much appreciated.

Russian vodka speaks of quality alone, but an inspection is always needed to see what sets it apart from the rest, and why Zyr particularly is so special.

9 : 5 : 3

Why will this suddenly have a meaning to you? Well let's take a look by what they mean by this ratio.

9 Filtrations

5 Distillations

3 Tasting Tests

The results are absolutely amazing and incredibly smooth- dangerously smooth, in fact. It is a curious blend of winter wheat and rye- and the taste definitely is lovely.

I drink it neat or on the rocks, preferably on the rocks- it is best appreciated alone. It is such a smooth vodka and has just the perfect hint of a sweet finish. This is a yummy one and a must for any vodka and/or spirits lover.

I have yet to see someone who does not like it after having tasted it. Even those who generally do not prefer vodka (for usually they have not had it properly or have not had the right kinds).

Now, here is how it can be oh so extra dangerously smooth- if you choose to mix this vodka...

... you will devour your drinks faster than ever. It is so smooth it doesn't feel like consuming alcohol at all when in the company of juices and other mixed drink combinations.

Now- it will definitely makes those drinks incredibly yummy and drinkable, if not refreshing, but for the true vodka lover on the rocks is the way to go here.

Should that stop you from ordering it in your mixed drinks? Never- do both depending on your mood. Tastes especially nice in a Basil8. Perhaps more on that one later.

Yum! I love it!

It is not available everywhere just yet, though you can find it available online. Be on the look out for it wherever you are- it is a wonderful and delightful treat.

War is an ugly thing, but not the ugliest of things.
The decayed and degraded state
of moral and patriotic feeling
which thinks that nothing is worth war
is much worse.

The person who has nothing for which he is willing to fight,
nothing which is more important than his own personal safety,
is a miserable creature and has no chance of being free
unless made and kept so by the exertions of better men than himself.

~ John Stuart Mills

We war, don't we
We warriors
We worriers for the world

You, Red Death Warrior
You mobilized
You sanitized
Purified to perform ancient rights of battles
And to stake patriot claims of fragile freedom
In hearts alien, hearts eternal,
Hearts ignorant of all you know

You know
You know

You know, noble warrior,
While you wander through the heaven of Hell
Raking the shit scattered pieces
Of bitter and broken promises
Into neat, heaping piles made ready
For the devil's dusty full bin,
I, Warrior of The Forgotten Peace
Arming my chair of flaccid command
Long for the glory fight that I never had
The fight I will never know
The fight you will never forget

You know
You know

2. Democracy in America: The National Campaign (currently on exhibit at the park avenue armory) has as one of its displays a project by the orange workers - they used found construction materials (think orange fencing, 2x4s, signs, plywood, etc) to build alternative street furniture, then tracked how long various pieces lasted, how the public interacted with the structures, and what eventually happened to them. they also posted at each structure a fake legalese sign explaining the project. they made everything from a diner booth (table sandwiched between two benches, with roof) to lounge chairs... and for most of the sites, the locals adopted the structures, used them appropriately, moved them back when they got blown around or upset, and even cleaned them! only one was removed by sanitation - one even lasted for 120 days!

3. and, of course, this: http://www.youtube.com/watch?v=FdDqSvJ6aHc which, while it contains a distinct thread of dispair, shows that not everyone has been sucked in to the black hole.

Lately, I have taken interest in discussing methods of creating sexy stylesheets. While CSS can be used to create sexy websites, writing CSS can actually be an artform by itself. The way in which CSS is created, structured, and maintained can be a thing of beauty.

So how does one create sexy stylesheets? What characteristics would your stylesheets have?

A few months ago, I had the opportunity to present on this very topic at Web Visions 2007 conference in Portland, Oregon. In preparing my presentation, I surveyed twelve people who work in web design and development. The results of this survey, combined with my own work experiences helped me to compile a list of essentials to remember when creating stylesheets.

01. Keep CSS out of the markup.

Linking and/or importing stylesheets would seem to be a no-brainer to the intermediate or advanced CSS developer, but I want to stress why this is so important. I’ve seen many sites start out with clean, well-organized CSS files but then get littered as time goes by, with embedded or even inline styles (due to fast updates needed on short deadlines, or possibly sometimes even pure laziness).

Imagine that you are working on an extremely large-scale website with hundreds of ways content can appear. You have fast deadlines, so you opt for making “quick fixes” or updates by using embedded or inline CSS. Years go by, and this habit continues… Until one day you’re told the site is being completely redesigned (but all the content is to remain the same), and you only have a week to build it (including testing).

Normally, this would have been a fairly simple task of updating the stylesheet(s). Except you have years worth of “quick fixes” scattered throughout the site — and no way to remember where they all are. So now you have to either a) find a way to clean everything up and get everything styled for the redesign in one week (Good luck!), or b) find a new job.

Don’t make your job harder than it really has to be. Linking and/or importing your stylesheets is not optional. Create it clean, keep it clean, and you’ll be much happier.

NOTE: Be careful of adding too many linked and/or imported stylesheets in your markup. If you’re tempted to create a new stylesheet every time you make an update or add new content, you’re not doing yourself any favors. Excessive linking and/or importing can make bug-fixing difficult, and make your styles harder to maintain. It is understandable to want separate stylesheets for different sections or components for larger websites (I’ll go more into that later). Just be careful that you don’t go overboard.

It is worth mentioning that linking too many stylesheets requires additional HTTP requests, which can add up, and potentially hinder performance. Also, Microsoft Internet Explorer 6 has a limit of 32 linked stylesheets.

02. Semantics is not just a buzz word.

You know I have to bring it up; semantics are your best friend. Beyond choosing the most appropriate, meaningful elements to describe your content, make sure also that you’re choosing semantic class and ID attribute values. Besides being the “right thing to do,” it really does make your life easier (and it makes the lives of your fellow team members easier too– if you working as part of a team). Take a look at the following rule:

.l13k { color: #369; }

If you were new to the job, and you saw that in the CSS file, are you going to know right away what that class is for? Most likely not. This class name could be an abbreviation for something, but there’s no real way you can tell right off the bat. Alternatively, maybe you put it there, so you know what it means, right? Today. But will you know what it means three years from now?

Now, let’s take a look at this rule:

.left-blue { color: #369; }

You might immediately know what purpose this class selector serves as you know exactly where the left-side blue module appears. So it would appear that this works. Until along comes that redesign you have to build in a week, as I mentioned earlier. In the redesign, this module is now to be positioned on the right, and colored red. The class attribute values no longer makes any sense, so now you have to either change all your attribute values, or leave it as it is (which could lead to mass confusion).

It is always best to refrain from using colors (either the color name or its hex value) or width/height dimensions in your class attribute values. You should also avoid any attribute values that are presentational (such as “box”).Presentational attributes defeat the purpose of separating presentation from content.

Finally, let’s look at this more appropriately named rule:

.product-description { color: #369; }

Here you can see that the rule styles product descriptions, no matter how many times your design changes. Clarity is a beautiful, beautiful thing.

03. Take advantage of commenting.

Commenting your CSS files can be a great deal of help to you and others during development if you use comments in creative and meaningful ways. At the most basic level comments provide little reminders why a certain rule is used. But you can use comments to really help improve organization and efficiency.

Reminders and notes

The common approach for commenting, leaving reminders and notes for yourself and other developers can help avoid confusion later. Keep these brief and simple. For example:

/* Turn off borders for linked images */
img { border: 0; }

Time stamp and signature

Some designers and developers also note the date and time that the CSS file was last updated, along with their name or initials. This information can provide a quick indicator of who to contact, as well as how up-to-date the file is.

/* Sushimonster Typography Styles
   Updated: Thu 10.18.07 @ 5:15 p.m.
   Author:     Jina Bolton
   ----------------------------------------------------*/

Depending on the project, this can be a good idea, particularly if you are working on a team. Keep in mind that some organizations require leaving this type of information out (some companies prefer to keep names and dates out of files), so it is best to find out if there is a mandate on this sort of thing.

Organization

It’s a good idea to use comments to indicate the different sections within a CSS file. For example, if all header styles are grouped together, you can use a comment to section these styles off from the next section’s styles:

/* HEADER
   ----------------------------------------------------*/

I’ll go more into this a little later, when discussing “Separating style types.”

Comment flagging

If you have your CSS file organized into sections as I described above, comment flagging can also be useful to make it easier using FIND to skip down or up to the parts of the file you want to see. You can use a character (such as an equal sign [=]), along with a keyword (typically the name of the section, such as “HEADER”) to provide “anchors” in your CSS file:

/* =HEADER
   ----------------------------------------------------*/

This is particularly useful in long and complex stylesheets. You can read more about this at Stop Design.

Reference

A less common, but nonetheless useful approach is to use comments as reference guide. One example of this might be to include a color guide as you can see in Steve Smith’s CSS file:

/* COLORS
   Body Background:       #2F2C22
   Main Text:             #B3A576
   Links:                 #9C6D25
   Dark Brown Border:     #222019
   Green Headline:        #958944
*/

You should place this guide at the top of your CSS file to help you remember what color values you use throughout your site. Another example is of an index-like approach. Here you can define different sections so that you can jump down to them (perhaps by using comment flagging). Here’s one example:

/* GENERIC
   HEADER
   SIDEBAR
   FORMS
   TABLES
   FOOTER
*/

/* =GENERIC
   ----------------------------------------------------*/

04. Know when to use conditional comments or hacks.

There are many articles regarding the problem with hacks, and why Conditional Comments are a better way to handle Internet Explorer issues. Then there are articles that say otherwise. While I agree that Conditional Comments can be a much better solution than littering your CSS file with hacks, only recently have I come to realize there are instances where they are actually not the most appropriate solution.

Imagine that you want to set a minimum height for an element. The IE6 developers did not implement min-height, so you know that you can use height, which will be treated the same way. Does it make sense to create a whole new stylesheet, and inject it by way of Conditional Comments in your markup, when all you need is this one rule? Would it make better sense to keep the min-height and height rules together, and opt for a small “hack” within the same CSS file? In this case, I would consider it less efficient to use Conditional Comments.

Another thing to consider: if you have multiple places that your styles are located, using multiple CSS files and Conditional Comments can make your debugging process more difficult. Also, if you need to alter something (perhaps the min-height value in the above-mentioned scenario), you have to open more than one file to make this change. In many cases, this may not be such a big deal for you, but imagine if you have something defined in your main CSS file, and then redefined in 3 different IE stylesheets. That could turn out to be a hassle later down the road, especially if another developer making the edit doesn’t realize that these overrides exist.

If you do use Conditional Comments, I recommend leaving a comment in your main stylesheet letting you or a fellow developer know that an IE-specific rule exists. That way when you have to edit a height or something of that nature, you know that you have more than one file to open.

As always, if you do use hack, remember that browser updates can change what works later down the road, and the hack you use now may not work later versions.

05. Organizing selectors and declarations

Always, always keep your CSS clean and organized. I prefer organizing my selectors by style groups:

• reset styles
• typography styles
• layout styles (header, content, footer, etc.)
• module or widget styles
• etc.

Then, within each of those groups, I organize selectors by DOM hierarchy (working down the page, from the outside in):

• any parent styles (containing elements, working outside-in)
• block-level element styles (paragraphs, lists, etc.)
• inline element styles (links, abbreviations, etc.)
• etc.

Then within those, I work by element types:

• paragraphs
• blockquotes
• addresses
• lists
• forms
• tables
• etc.

Finally, I prefer to organize my CSS declarations by style type:

• positioning (with coordinates) styles
• float/clear styles
• display/visibility styles
• spacing (margin, padding, border) styles
• dimensions (width, height) styles
• typography-related (line-height, color, etc.) styles
• miscellaneous (list-style, cursors, etc.) styles

Some people like to organize declarations alphabetically. It doesn’t make sense to me, but it might make perfect sense to you. Whichever method you choose, stick with it, and be consistent.

06. Creating a framework

When it comes to developing CSS, If you find yourself doing the same things repeatedly, it is a good idea to consider creating a library or framework. A framework can be made up of a group of stylesheets that act as a foundation for your site, and help speed up your development time. Typical stylesheets you may find in your framework might include:

• screen.css - A screen CSS file can either have all your styles you want to be used for on screen, and/or can import additional styles, such as the following:
  • reset.css - A reset CSS file can be used to “reset” all the default browser styling, which can help make it easier to achieve cross-browser compatibility.
  • typography.css - A typography CSS file can define your typefaces, sizes, leading, kerning, and possibly even color.
  • grid.css - A grid CSS file can have your layout structure (and act as the wireframe of your site, by defining the basic header, footer, and column set up).
• print.css - A print CSS file would include your styles you want to be used when the page is printed.

One example of a framework is the Blueprint framework put together by Olav Bjørkøy (which based itself off of work developed by authors including Jeff Croft and Eric Meyer). Another popular framework can be found at the Yahoo! User Interface Library. Many developers do feel that these pre-built frameworks contain markup and CSS that are a bit “bloated” and also that they contain presentational class attribute names.

NOTE: As I was writing this article in its draft stages, Jeff Croft released the post What’s not to love about CSS frameworks?, in which he mentions in the comments he was told that people think I am strongly against frameworks. I’m not sure where this came from, but as I stated in my response, I am not against CSS frameworks, and am very much for them.

For the best results, I recommend that you create your own framework that works best for you or your organization.

07. Balance readability and optimization.

Styles in formatting vary from developer to developer. Some developers use formatting styles that offer great readability, and then optimize the files (removing comments, spaces, tabs, carriage returns, etc.) before pushing the file live. This is a great technique and one I would recommend (done carefully). However, if you are somehow in a situation where you can’t really go through those steps, try to find a style that balances readability and optimization. Steve Smith has a great suggestion that offers a little bit of both.

Also, consider using hyphens instead of underscores. Microformats use hyphens as a standard separator, and certain older browsers have a hard time with them. You can read more about this at Underscores in class and ID Names.

08. Master your text editor.

Just as an artist has proper tools they know well, it’s important for a designer/developer to know the tools they use well. For CSS, that would be the editor you are using.

There are many text editors to choose from: TextMate, Coda, BB Edit, TextPad, DreamWeaver, etc. I’m not here to tell you which one to pick; they all have their pros and cons, and the right editor for you is up for you to decide. However, once you have decided on a text editor, make sure you learn everything you can about it. Find out what the shortcuts are, and learn all the tips and tricks you can.

Mastering your text editor is the best way to speed up your development time, and help you be more much more efficient when creating sexy stylesheets.

09. Use version control.

Smoother maintainability is also an important part of creating sexy stylesheets. This is where version control can be your best friend. It’s not only helpful for teams, but it can be a lifesaver even for the sole designer/developer.

Some applications have built-in mechanisms for source control. DreamWeaver uses a check-in/check-out system (that can help make sure that a developer doesn’t edit a file that is already currently being edited), as well as synching capabilities (which lets you sync and merge your local files with your remote files, or vice versa). This can be very handy, but are somewhat limited.

Subversion (SVN) or Concurrent Versions System (CVS) are great tools to use for more robust management, with additional options, like being able to revert, view changes (which is extremely helpful for teams — you can track who added/edited/removed code and when they did it), and resolving conflicts. There’s a great article by Jonathan Snook, called “Hosted Subversion” you can read for more information on how to set this up quickly and easily.

10. Create and maintain a style guide.

While in some cases, a style guide is an author’s guide with grammar rules and writing standards, it can also be used to outline standards for design, development, and content. A style guide is a great way to have a reference manual that can clarify rules on typography, grid, color, image sizes, etc.

When creating a style guide, it is a great idea to provide reference for the markup and CSS. This reference can be used as a handbook for the development team and future developers. It can include defined layouts, in which you can list the different layouts that can be used, and provide the associated markup and styles.

Finally, you can also leave steps for quality assurance for developers, (such as checking validation and accessibility) to ensure the highest quality.

Conclusion

Being an expert in CSS is so much more than having advanced CSS skills (i.e.: fully understanding the cascade, the box model, and how browsers work). I encourage you to think about ways you can constantly and consistently improve maintainability and efficiency. Think beyond what is designed in the comp, even if that is all that you have been provided. Make the CSS intelligent and plan for the future. Overall elegance in workflow is essential to master.

I won't go too much into details of what constitutes good office wear, as each industry has its own standards, but the gist of it is that it should be neat and tidy in appearance, from head to toe. Personal grooming, appropriate accessories, right fitting clothes and the correct body language all adds up to make your stocks rise significantly.

I was having second thoughts about whether I should wear a coat for my interview yesterday, as we Malaysians don't have the habit of wearing coats due to our humid weather. Furthermore, I believe I might be 'overdressed' if I attended it in a coat. So use your judgement for any situation and you should be fine. Prevailing common sense should pull you through most times.

I am currently in taos helping the charlieparkers' folks build their awesome new house, and not only can you see through to the sky (since it doesn't have a roof or a lot of interior walls yet) but it is also absolutely beautiful here. the exterior walls are made of pumicecrete (which is crazy lightweight superinsulating and looks a little like grey rice-crispy treats), and two of the interior walls are made of adobe for passive solar, and the roof joists are up, so standing in the middle of what will be the master bedroom you can see the watermelon-colored hills covered in sage-y scrub, and the trees in the apple orchard and all the rustling green meadow and red dirt and the light here is sharp and dramatic and it makes me both wish that I was a better painter AND that I could just build houses all the time.

plus its nice to see all these lovely people I wish lived closer to me, and to go stick my feet in the rio grande, and chase the peacocks off the porch.

ah, vacation...

someday I'll write from home again, but for the moment, this shall have to suffice. pax.

NeuroEvolución (NE), es la forma de evolucionar redes neuronales usando algoritmos genéticos, esto ha  demostrado ser muy eficiente en el refuerzo de tareas de aprendizaje.

NE busca en el espacio de los comportamientos de una red que funciona bien para una tarea en particular.

Por lo general, la topología de la red esta compuesta de una sola capa oculta de neuronas, donde cada neurona de esta capa tiene conectada cada una de las entradas y cada una de las salidas.

NE busca en el espacio de los pesos de las conexiones de toda la red permitiendo así que las redes altamente performantes se reproduzcan. Esto se logra con el apareamiento (crossover) de los vectores de pesos de las conexiones de toda la red, sumándole a este  apareamiento una mutación arbitraria.

De esta manera funcionan los NE de topología fija, ya que optimizan los pesos de las conexiones que determinan la funcionalidad de la red.

A pesar de esto, los pesos de las conexiones no son el unico aspecto de las redes neuronales que contribuyen en su comportamiento. La topologia, o estructura, de una red neuronal tambien afecta a su funcionalidad.

La modificacion de la estructura de la red ha demostrado ser eficiente como parte del entrenamiento supervisados.

La pregunta que se nos plantea es:

La evolución de la topologías y los pesos de las conexiones nos van a dar alguna ventaja sobre las topologías fijas?

Si una función continua puede ser aproximada por una Red, para que vamos a esforzarnos permutando diferentes topologías?

Las respuesta hasta ahora a estas preguntas son bastantes inconclusas.

NEAT fue diseniado para tomar ventaja de la estructura como forma de minimizar la dimensionalidad de la búsqueda sobre el espacio de conexiones. Si la estructura esta evolucionada, esta topología esta minimizada y crece incrementalmente, lo cual resulta en ganancias en la velocidad de aprendizaje de la red.

Esta evolución y ganancia se va notando a lo largo del proceso de evolución y no solamente al final de todo el ciclo evolutivo.

Evolucionar una estructura incrementalmente presenta varios desafíos técnicos:

1. Hay alguna representación genética que permita que distintas topologías se apareen (crossover) de manera que el resultado signifique algo?
2. Como podemos proteger a las innovaciones de la topología (que necesitan algunas generaciones para ser óptimas) para que no desaparezcan de la población prematuramente?
3. Como las topologías pueden ser minimizadas durante la evolución sin la necesidad de una función de "encaje" (fitness) que mida la complejidad de la misma?

NEAT se encarga de responder estas preguntas y dar una solución elegante, la cual iremos viendo en los siguientes posts.

Fuente: http://www.cs.ucf.edu/~kstanley/neat.html#papers

Para empezar voy a tratar de describir cada uno de los temas muy por arriba y luego tratare de empezar a relacionarlos y profundizar en cada uno de ellos y en sus vínculos.

Empecemos por RETE:

RETE (red en latín) es un algoritmo muy utilizado en sistemas de reglas de producción ya que su funcionalidad principal es la de encontrar coincidencias entre patrones de manera muy eficiente. En estos sistemas por lo general necesitamos realizar comparaciones entre hechos y reglas de negocio con el fin de realizar inferencias sobre los mismos. Esto debe hacerse de una manera eficiente para que el sistema sea escalable y performante.

Por supuesto aparece el termino regla de producción que hace referencia a una regla compuesta por condición y acción. Donde en la condición especificamos un set de restricciones que van a condicionar la ejecución de la acción.

RETE funciona armando una red de nodos, donde cada uno de estos nodos se corresponde con una condición en la LHS (Left hand side / representa las restricciones en la parte condicional de una regla de producción), por lo tanto un camino desde el nodo raíz hasta un nodo hoja representaría toda una regla de producción.

Mas adelante, tratare de aclarar los distintos tipos de nodos que utiliza una red RETE, ya que esto ayudara bastante a comprender como funciona el algoritmo.

Seguimos con NEAT:

NEAT (NeuroEvolution of Augmenting Topologies / NeuroEvolución para el crecimiento de las topologías) se caracteriza por ser una técnica de NeuroEvolución, es decir, una técnica que utiliza algoritmos genéticos para evolucionar redes neuronales.

NEAT en particular se caracteriza por codificar de alguna manera la topología de la red neuronal y hacerla evolucionar generación tras generación, logrando así optimizar su funcionamiento.

Por lo general los algoritmos de NeuroEvolución se separan en dos ramas:

• Aquellos que se encargan de evolucionar los pesos en las conexiones en una red neuronal.
• Aquellos que se encargan de evolucionar tanto la topología de la red como los pesos en las conexiones de una red neuronal.

En este caso NEAT opta por la segunda opción, por lo cual vamos a ver como cuando aplicamos NEAT los pesos de las conexiones dentro de la red van evolucionando y a su vez se crean nuevos nodos y nuevas conexiones dentro de nuestra red como parte de esta evolución.

Como podran notar tanto RETE, como NEAT son temas bastantes complejos que incluyen mucho otros temas que hay que investigar para poder dominarlos y utilizarlos en la vida cotidiana. Para esto voy a listar los temas a investigar y las fuentes que pienso utilizar en dicha investigación:

RETE:

• Algoritmo, funcionamiento, características principales, lugares comunes de uso, extensiones de RETE.
  • http://herzberg.ca.sandia.gov/docs/52/rete.html
  • http://en.wikipedia.org/wiki/Rete_algorithm
  • http://legacy.drools.codehaus.org/Rete
  • http://www.jbug.jp/trans/jboss-rules3.0.2/ja/html/ch01s04.html

NEAT:

• Algoritmo, funcionamiento, soporte teórico, pruebas y teorías
  • http://www.cs.ucf.edu/~kstanley/
  • http://nn.cs.utexas.edu/pub-view.php?PubID=97100
  • http://www.cs.ucf.edu/~kstanley/neat.html#papers
  • http://tech.groups.yahoo.com/group/neat/
• Algoritmos geneticos + Redes neuronales + Programacion evolutiva
  • http://www.amazon.co.uk/AI-Techniques-Game-Programming-Development/dp/193184108X

NEAT + RETE = REAT:

• Meta final de la investigación: http://www.evolvablerules.org/ (Greg Barton)

Como podemos ver en http://www.evolvablerules.org/ Greg Barton propone adaptar NEAT a RETE, lo cual causaría que la topología de la red RETE evolucione tanto como las reglas de producción que se definan.

Para lograr esto, sin duda alguna, hay que analizar muy bien NEAT y la topología especifica de RETE, así tanto como la codificación de los genes para los distintos tipos de nodos en RETE.

Esto no suena tarea facil para nada, por lo cual como primeros pasos voy a empezar enfocandome en NEAT y ver como se comporta con implementaciones reales, al menos simples.

"If you don't want to move to a missile silo in upstate New York,
perhaps we can interest you in a giant, glass-enclosed skyscraper whose
upper units dangle in midair? Today the architecture firm Herzog &
de Meuron (who recently designed the "bird's nest" Olympic stadium
in Beijing) revealed their plans for a 57-story building of
irregularly-stacked flats at 56 Leonard St. in Manhattan's Tribeca
neighborhood. Each flat will have a slightly different floorplan, and
will stick out of the building at an angle, giving it what real estate
blog Curbed called a "Jenga look." Plus, the play of light through the
glass walls will make the building seem to rotate and shimmer in the
sun. You know you want to take a peek inside, and see the pools and
libraries of the penthouse units."

REST OF ARTICLE WITH MORE PICS