Robust-first Computing Wiki

jojo_frayre

anonymous@undisclosed.example.com (Anonymous) — Tue, 19 Sep 2017 21:16:25 +0000

@@ -1,7 +1,10 @@
  Hello my name is Jose Frayre but everyone calls me JoJo
- I am a in the Masters of Science in Architecture program
+ I am in the Masters of Science in Architecture program
  in the Computational Ecologies Program
  I am doing a Masters Project on the effects of social media 
  on the built environment and design.
  
       [MFM-Handle:jojo frayre]
+      
+      
+ [[jojo_frayre:project_page]]

josh_donckels

anonymous@undisclosed.example.com (Anonymous) — Sun, 10 Dec 2017 19:59:22 +0000

@@ -1,7 +1,6 @@
  My name is Joshua Donckels\\
  I am a Computer Science Graduate Student pursuing a Master's Degree\\
- I have no idea what else to put here yet!
  
  <file pub jdonckels.pub>
  [MFM-Handle:jdonckels]
  -----BEGIN RSA PUBLIC KEY-----
@@ -10,9 +9,7 @@
  UBhr1FBWG+O3LkMPBryWSJPwJwDeIpcP/C1lrWPoyJu9QGQJjPXHAgMBAAE=
  -----END RSA PUBLIC KEY-----
  </file>
  
- ===== Week Logs =====
-    *1. (9/12/2017)
-        *Read into artificial neural networks and their interworkings
-        *Created a project page at [[https://robust.cs.unm.edu/doku.php?id=project_people:josh_donckels]] 
+ My project is located in project_people(Josh_Donckels) page.
+

news_archive

anonymous@undisclosed.example.com (Anonymous) — Sat, 28 Nov 2020 23:30:14 +0000

@@ -1 +1,14 @@
+ ====== Old News ======
+ 
+   * 25-Jul-2015: The **[[http://mail.cs.unm.edu/cgi-bin/mailman/listinfo/ulam-users|ulam-users mailing list]]** is now available.  Intended for ULAM-related announcements, general discussion, and community support.
+   * 25-Jul-2015: [[https://www.youtube.com/watch?v=aR7o8GPgSLk|Video]] of the **ULAM launch** talk in York, UK is now online.
+   * 26-May-2015: Building up towards the **launch of ULAMv1 and MFMv3 at ECAL 2015** this summer!  New pages coming fast now, including [[dev:program_ulam|a tutorial on ULAM programming]] and [[ulam_programming_conventions|early info on ULAM programming conventions]]
+   * 17-Jan-2015: **Robust-first Research Group meetings** resume Monday 26-Jan-2015, 3PM-5PM, FEC349D.  Agenda: News and planning.  Open to all interested parties.
+   * 6-Dec-2014: **New [[https://www.youtube.com/watch?v=5P6Dihkrvus&list=PLm5k2NUmpIP8qwttAS5Batnd7u2UpBtaL|YouTube playlist of MFM demos]]** created 
+   * 4-Dec-2014: **New page on [[concepts:neutral_dynamics|neutral dynamics]]** created, with a kind of pretty little video to go with it.
+   * 19-Nov-2014: **Crit 3 signup now open for first-dibs signup!**  See below. 
+   * 13-Nov-2014: **ECAL Paper formatting info has issues: Instead use ALIFE14 Latex style!** Zip file with an example document at  http://blogs.cornell.edu/alife14nyc/files/2013/04/alife-example-1q151yj.zip
+   * 27-Oct-2014: **MFM simulator version 2.0.10 released** (at [[https://github.com/Sixstring982/MFMv2|github]] and [[https://launchpad.net/~ackley/+archive/ubuntu/mfm|for Ubuntu]]).  Lots of good stuff in it, but note you may **NOT** want to update immediately //if you have any custom elements//!  There are some changes required to update elements from 2.0.8 to 2.0.10!  More info to follow on element updating.
+   * 26-Oct-2014: There's a Python script for plotting the counts of some Elements given one of those /tmp/xxxx/tbd/data.dat files.  See [[dev:plotting_elem_counts|Plotting element counts]]
+   * 14-Sep-2014: **libx264 installed** on CS machines.  The script at [[Introduction:Making an MFM video]] now has a better chance of working there.

project_joaquin_serna

anonymous@undisclosed.example.com (Anonymous) — Wed, 13 Sep 2017 02:21:03 +0000

@@ -7,10 +7,10 @@
  in the current environment. For example, a cell which passes along an "immunity" to a specific virus. 
  
  **Traffic**
  
-  Stop lights. 
-  Aggregate wait times vs distance traveled. 
+ Possibly, aggregate wait times vs distance traveled could be used to determine flow of traffic. Lights would be required  
+ to communicate with each-other. Communications would have to occur at a quicker rate than traffic to be effective.  
  
  **Cellular emergencies**
  
  Cells that operate like the brain/body during emergencies. When an emergency occurs, "assets" will be diverted from

sensor_array

anonymous@undisclosed.example.com (Anonymous) — Mon, 20 Oct 2014 21:38:35 +0000

@@ -4,12 +4,9 @@
  Robust Sensing in a Distributed Environment
  
  ===== Abstract =====
  
- In this paper, we describe a system in the movable feast machine framework of Artificial Life. The movable feast machine (MFM) is a recent development in the artificial life community, intended to describe a more intuitive framework for computation using a type of cellular automata. We present a design for a set of MFM elements which construct a phased sensor array to sense incoming data. The system as a whole gathers spatially-oriented data transmissions and tells us from where the data is coming. This can enable users to do things like analyze incoming data or to establish communications pathways. 
- 
- (needs a trade-off; accuracy versus directional data, etc.)(More about properties to make it science)
- 
+ In this paper, we present a design for a set of Movable Feast Machine (MFM) elements which construct a phased sensor array to sense incoming data. The system gathers spatially-oriented data transmissions and tells us from where the data is coming. This can enable users to analyze incoming data, or to establish communications pathways. The design includes parameters which regulate the density and directionality of the array. Here, we show that certain parameters allow the data to be sensed accurately without too much data loss. Specifically, we illustrate the trade-off between data loss and sensing capacity as a function of these parameters.
  ===== Methods =====
  
  Any sensor system needs to have some sort of target object to sense. In this work, our target objects are called Light particles. These are a very simple pair of light atoms, driving themselves forward in a given direction. The Light particles are emitted at a steady rate by Emitter atoms. The locations of these Emitters are the main things we want to be able to sense with our system. As such, each experiment described here has a predetermined set of emitter locations, making it easier to compare the performance of different parameter values, as we do here.

start

anonymous@undisclosed.example.com (Anonymous) — Sat, 28 Nov 2020 23:31:02 +0000

@@ -3,7 +3,5 @@
  ===== Quick links =====
-   * [[f17:class_notes|Class notes]]
-   * [[http://www.cs.unm.edu/~ackley/591/|Class web page]]
    * [[https://github.com/elenasa/ULAM/wiki|Programming language ulam wiki and reference manual]]
    * [[Introduction:Robust-first computing]]
    * [[Introduction:Indefinite scalability]]
    * [[Introduction:How can I install the MFM software?]] 
@@ -11,21 +9,22 @@
    * [[Introduction:Where can I get more information?]]
    * [[Introduction:MFM usage and tips]]
    * [[Introduction:Making an MFM video]]
    * [[Introduction:Contributions]]
+   * [[f17:class_notes|Class notes]]
+   * [[http://www.cs.unm.edu/~ackley/591/|Class web page]]
  
  ===== News =====
+   * 28-Nov-2020: After an extended outage since August, robust.cs.unm.edu is back on the air! 
    * 18-Oct-2019: The [[https://youtube.com/c/TheT2TileProject|T2sday Updates]] are now in their second year!  Also, most project discussion takes place in [[https://gitter.im/t2tile/Lobby|the T2 Tile chat rooms]].
    * 25-Nov-2018: There's now a [[https://youtube.com/c/TheT2TileProject|weekly video report]] on progress building the 'T2 Tile', our prototype indefinitely-scalable hardware!
    * 3-Oct-2017: ULAM v3.0.9 released.  Bug fixes and more development towards hardware tiles.
    * 26-Sep-2017: ULAM v3.0.8 released.  Bug fixes mostly.
    * 21-Aug-2017: //[[http://www.cs.unm.edu/~ackley/591|Living Computation]]//, a UNM CS seminar for graduates and undergraduates, starts today, focusing on **ulam** and the Movable Feast!
    * 8-Aug-2017: **ULAM v3** Ubuntu packages now available via [[https://launchpad.net/~ackley/+archive/ubuntu/mfm|ppa:ackley/mfm]].  Built for xenial, trusty, and precise, for i686, x86-64, and now also arm7hf.
    * 15-Jul-2017: **ULAM v3 coming in August!**
    * 8-Aug-2016: **ULAM v2 announced!** [[https://www.youtube.com/watch?v=cZJ7UUt8B2Q|Video]]! 
-   * 25-Jul-2015: The **[[http://mail.cs.unm.edu/cgi-bin/mailman/listinfo/ulam-users|ulam-users mailing list]]** is now available.  Intended for ULAM-related announcements, general discussion, and community support.
-   * 25-Jul-2015: [[https://www.youtube.com/watch?v=aR7o8GPgSLk|Video]] of the **ULAM launch** talk in York, UK is now online.
-   * 26-May-2015: Building up towards the **launch of ULAMv1 and MFMv3 at ECAL 2015** this summer!  New pages coming fast now, including [[dev:program_ulam|a tutorial on ULAM programming]] and [[ulam_programming_conventions|early info on ULAM programming conventions]]
+ 
  
  [[news_archive|Older news items]]
  ===== Components =====
    * [[Components:Element]]

ulam_programming_conventions

anonymous@undisclosed.example.com (Anonymous) — Tue, 26 May 2015 09:28:13 +0000

@@ -5,19 +5,21 @@
  ==== Utilities vs Services ====
   
  In the standard library, you can find things like ''WindowServices'' and ''DebugUtils'', both of which, viewed generally, have similar purposes: They provide methods you can call to do useful things.  So, why are some named '*Services' while are named '*Utils'?  Here's the key convention: Things suffixed with ''Utils'' should be size 0, while things suffixed with ''Services'' have a non-zero size.  
  
- === The EventWindow Exception ===
+ === The EventWindow and Random Exceptions ===
  
- Of course the elephant in the standard library is ''EventWindow''.  That name violates this convention, because it has neither 'Utils' nor 'Services' as a suffix; it gets away with the violation because it predates the whole naming convention.  But, since it is size 0, we should //think// of it like ''EventWindowUtils'' and not ''<del>EventWindowServices</del>''.   
+ Of course the elephant in the standard library is ''EventWindow''.  That name violates this convention, because it has neither 'Utils' nor 'Services' as a suffix; it gets away with the violation because it predates the whole naming convention.  But, since it is size 0, we should //think// of it like ''EventWindowUtils'' and not ''<del>EventWindowServices</del>''.  
  
+ Exactly the same is true for ''Random'', which we should think of as ''RandomUtils''.
  ==== Utils and Services Declarations ====
  
  //Rule of Thumb: **Prefer data members for *Utils, and local variables for *Services.**//
  
  Unless you have a specific reason not to, prefer to declare ''*Utils'' (which includes ''EventWindow'') as data members, and to declare ''*Services'' as local variables in a method.  So, for example, prefer this:
  
  <code - Evaporator.ulam>
+ /** \symmetries all */
  element Evaporator {
    EventWindow ew;
    Void behave() { ew[0] = ew[1]; }
  }
@@ -25,8 +27,9 @@
  
  over this:  
  
  <code>
+ /** \symmetries all */
  element Evaporator {
    Void behave() { 
      EventWindow ew;
      ew[0] = ew[1]; 
@@ -34,13 +37,13 @@
  }
  </code>
  even though, in this case, both versions behave identically.  
  
- The reasoning for this **Make *Utils data members** guidance has an obvious point and a subtle point:  
+ The reasoning for this **Make *Utils data members** guidance has both obvious and subtle points.  
  
- The obvious point is that since a *Utils is size 0, it doesn't impact the atomic bit budget at all, so it's harmless to make them data members.  Furthermore, placing them as data members makes them available to all methods with a single declaration, and can provide a systematic place (e.g., at the top of the class) for all *Utils declarations.
+ An obvious point is that since a *Utils is size 0, it doesn't impact the atomic bit budget at all, so it's harmless to make them data members, while conversely, a *Services data member //does// impact the bit budget, so we don't want to do it thoughtlessly.  Furthermore, placing *Utils as data members makes them available to all methods with a single declaration, and also provides a systematic place (at or near the top of the class) for all *Utils declarations.
  
- The subtle point is that even though a *Utils is size 0, when a *Utils method is called, the ''self'' object passed into the called method can differ depending on how the *Utils was declared.  For example, this definition:
+ A subtle point is that even though a *Utils is size 0, when a *Utils method is called, the ''self'' object passed into the called method can differ depending on how the *Utils was declared.  And that can affect how the called *Utils method behaves.  For example, this definition:
   
  <code - Announcer.ulam>
    element Announcer {
      DebugUtils du;

worklog_joaquin_serna

anonymous@undisclosed.example.com (Anonymous) — Fri, 15 Sep 2017 06:14:33 +0000