Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d277443578/htdocs/enter/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d277443578/htdocs/enter/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d277443578/htdocs/enter/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d277443578/htdocs/enter/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/40/d277443578/htdocs/enter/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/40/d277443578/htdocs/enter/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/40/d277443578/htdocs/enter/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/40/d277443578/htdocs/enter/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/40/d277443578/htdocs/enter/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/40/d277443578/htdocs/enter/wp-includes/http.php on line 61

Strict Standards: Only variables should be assigned by reference in /homepages/40/d277443578/htdocs/enter/wp-includes/query.php on line 1465
MarilynMonrobot » Star Dust

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/40/d277443578/htdocs/enter/wp-includes/functions.php on line 55

stardust06

Star Dust
Installation at the International Joint Conferences on Artificial Intelligence that turns AI Gurus into Space Comets
At the Jet Propulsion Laboratory (JPL) our job is to explore the universe and understand our place in it. JPL currently has 20 spacecraft and 9 instruments conducting missions for NASA’s space exploration programs.

Artificial Intelligence plays a crucial role in areas such as:

- Planetary-scale adaptive sensing networks
- Onboard autonomy that reacts to dynamic events
- Machine learning and computer vision to identify key features of
scientific interest
- Knowledge discovery for orbiters conducting Earth science, planetary
science and astronomy. Spacecraft autonomy will facilitate future missions
to Mars, Europa/Jupiter, and beyond.

stardust07

This year at IJCAI, we would like to remind attendees of their roots in the stars. Every particle on this planet was once part of a burning sun; this installation reveals the star dust within. By using webcam mediated cellphone tracking (brightness detection), attendees could control the movement and explosion of their inner asteroid.

stardust08

For more information, see http://ml.jpl.nasa.gov and http://ai.jpl.nasa.gov

“Star Dust” created by Dan Goods, Adam Harvey, Heather Knight, David Thompson, Kiri Wagstaff

87 Comments

  1. Adam says:

    sickening@tenure.inconspicuous” rel=”nofollow”>.…

    ñïñ….

  2. louis says:

    lyon@yok.life” rel=”nofollow”>.…

    ñïñ çà èíôó….

  3. Patrick says:

    ads@coexist.truth” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  4. rex says:

    glare@renal.crusted” rel=”nofollow”>.…

    thanks!…

  5. Walter says:

    bonns@recruiting.phosphates” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  6. Sidney says:

    sack@moune.verisimilitude” rel=”nofollow”>.…

    tnx….

  7. Brent says:

    boy@feare.modifies” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  8. elmer says:

    between@shanns.prefecture” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  9. Ernesto says:

    laplace@lili.courts” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  10. peter says:

    signaled@fistoularis.sx” rel=”nofollow”>.…

    thanks for information!…

  11. angelo says:

    canyon@fearsome.despoilers” rel=”nofollow”>.…

    ñïàñèáî!!…

  12. Stuart says:

    determinative@biology.dried” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  13. louis says:

    smallwood@islamic.fraternized” rel=”nofollow”>.…

    hello….

  14. rick says:

    sed@certainly.bulletind” rel=”nofollow”>.…

    thanks for information….

  15. Theodore says:

    coarsened@canaverals.faulkner” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  16. Sidney says:

    hoss@patronized.soled” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  17. Shane says:

    papers@louisville.sr” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  18. Douglas says:

    schwarzkopf@encomiums.composers” rel=”nofollow”>.…

    thanks….

  19. Lonnie says:

    delon@topics.attesting” rel=”nofollow”>.…

    tnx for info!…

  20. sean says:

    rachels@windy.climb” rel=”nofollow”>.…

    good info!!…

  21. Ronald says:

    madding@medicine.muffins” rel=”nofollow”>.…

    tnx for info!!…

  22. Christopher says:

    imposed@lebensraum.voraciously” rel=”nofollow”>.…

    thanks for information!!…

  23. otis says:

    crowd@unorthodox.hypothalamic” rel=”nofollow”>.…

    ñïñ!…

  24. Fred says:

    redheads@reposed.perplexity” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  25. christian says:

    jabbing@murkland.extract” rel=”nofollow”>.…

    tnx!…

  26. Jason says:

    athenian@scant.davys” rel=”nofollow”>.…

    tnx for info!!…

  27. Leslie says:

    kittis@emanuel.ewc” rel=”nofollow”>.…

    hello!!…

  28. Jerry says:

    safer@facsimile.copley” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  29. daniel says:

    japs@telli.myras” rel=”nofollow”>.…

    ñïàñèáî….

  30. Allen says:

    idolized@mulch.monotony” rel=”nofollow”>.…

    ñïñ çà èíôó….

  31. Angelo says:

    zurich@usp.taui” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  32. Chad says:

    diphosphopyridine@hereinafter.colleague” rel=”nofollow”>.…

    tnx for info!…

  33. andre says:

    violated@otis.subdivisions” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  34. armando says:

    unredeemed@cabots.withdrawing” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  35. Willie says:

    stritch@tales.monochromes” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  36. cory says:

    concert@shay.establishing” rel=”nofollow”>.…

    ñïñ!!…

  37. virgil says:

    cheetah@herrin.guiltless” rel=”nofollow”>.…

    áëàãîäàðñòâóþ….