Netstru design

From Emergent

Jump to: navigation, search

New names for netstru functions

See also: Connections_design for connection-level changes.

In the spirit of: this is the time to make any major changes in the software, the names of various netstru functions have always been rather unsatisfactory and unsystematic. This only affects folks who have coded up their own algorithms, and a very few scripts (which probably won't translate directly anyway), and only requires a simple set of search-and-replace operations. Here are the principles:

  • systematically use: Compute_ Init_ Send_ Update_ with underbar (underbar makes var more visible and allows things like dWt etc without it running into previous guy)
  • use Netin instead of Net because Net is somewhat ambiguous
  • use Acts and Weights as the two main categories of things ("State" is not that clear)
  • InputData is the new term for external input

Here are the mappings from old to new:

  • InitExterns -- Init_InputData
  • InitDelta -- Init_Netin
  • InitState -- Init_Acts
  • InitWtDelta -- Init_dWt
  • InitWtState -- Init_Weights
  • Compute_Net -- Compute_Netin
  • Send_Net -- Send_Netin
  • UpdateWeights -- Compute_Weights (why have that be so special -- its just a computation like any other)
  • ModifyState -- <removed, unused>
Retrieved from "http://grey.colorado.edu/emergent/index.php/Netstru_design"
Personal tools