Actions

Una-May O'Reilly: Difference between revisions

From Santa Fe Institute Events Wiki

No edit summary
No edit summary
Line 4: Line 4:
I lead [http://groups.csail.mit.edu/EVO-DesignOpt EVO-DesignOpt].
I lead [http://groups.csail.mit.edu/EVO-DesignOpt EVO-DesignOpt].


My bio and other stuff on my web site tell you about me, my research agenda and various projects. A little extra related info: I was an SFI Doctoral fellow from 1993-1995.( I've been at MIT ever since) And, I met my husband at SFI. In fact, he was the first SFI'r I met when I arrived. How about that for good fortune!
My bio and other stuff on my web site tell you about me, my research agenda and various projects. A little extra related info: I was an SFI Doctoral fellow from 1993-1995. (I've been at MIT ever since.) And, I met my husband at SFI. In fact, he was the first SFI'r I met when I arrived. How about that for good fortune!


[http://www.santafe.edu/events/workshops/index.php/CSSS_2007_Santa_Fe Back to CSSS Wiki Main Page]
[http://www.santafe.edu/events/workshops/index.php/CSSS_2007_Santa_Fe Back to CSSS Wiki Main Page]
== What should I Lecture On?==
I will be posting a short set of questions to the CSSS email list.
*I want to know your experience level genetic algorithms, genetic programming, evolutionary strategies, evolutionary programming, particle swarm optimization, BOA, hBOA, grammatical evolution or any other Evolutionary Algorithm. Responses might be one of "expert, knowledgeble, ignorant" and one of "develop, use, don't use".
* I want to know, if you know, how you have used or anticipate using evolutionary computation in your field of research.
* Are there any topics or concepts in evolutionary algorithms that are burning a hole in your head that you'd like me to cover?


==Evolutionary Algorithm Software==
==Evolutionary Algorithm Software==

Revision as of 01:55, 10 June 2007

I am from the Computer Science and Artificial Intelligence Lab, (CSAIL), MIT where I lead EVO-DesignOpt.

My bio and other stuff on my web site tell you about me, my research agenda and various projects. A little extra related info: I was an SFI Doctoral fellow from 1993-1995. (I've been at MIT ever since.) And, I met my husband at SFI. In fact, he was the first SFI'r I met when I arrived. How about that for good fortune!

Back to CSSS Wiki Main Page

What should I Lecture On?

I will be posting a short set of questions to the CSSS email list.

  • I want to know your experience level genetic algorithms, genetic programming, evolutionary strategies, evolutionary programming, particle swarm optimization, BOA, hBOA, grammatical evolution or any other Evolutionary Algorithm. Responses might be one of "expert, knowledgeble, ignorant" and one of "develop, use, don't use".
  • I want to know, if you know, how you have used or anticipate using evolutionary computation in your field of research.
  • Are there any topics or concepts in evolutionary algorithms that are burning a hole in your head that you'd like me to cover?


Evolutionary Algorithm Software

Homework? Never! But for some people the best way to understand a genetic algorithm or any other sort of Evolutionary Algorithm is to implement or use one. I insist that my MIT students write at least one from scratch but, as a project grows, it is often more efficient not to frequently reinvent the wheel. Google or any other internet search engine suffices to find software implementations. They come in an assortment of languages, vary in age, support and popularity. Here's a sample of ones I tend to hear of being used in the community:


Unamay 05:02, 7 June 2007 (MDT)


caption


Experimental Space

Here's a link to the Main page.

Section

Subsection

Subsubsection

  • Unordered lists are easy to do:
    • Start every line with a star.
      • More stars indicate a deeper level.
    Previous item continues.
    • A new line
  • in a list

marks the end of the list.

  • Of course you can start again.
  1. Numbered lists are:
    1. Very organized
    2. Easy to follow

A new line marks the end of the list.

  1. New numbering starts with 1.
A colon (:) indents a line or paragraph.

A newline starts a new paragraph.
Often used for discussion on talk pages.

We use 1 colon to indent once.
We use 2 colons to indent twice.
3 colons to indent 3 times, and so on.