HowTos

From Emergent

Jump to: navigation, search

These are quick pointers to various functionality that may not otherwise be obvious. Please add things you discover so others may benefit!

Contents

A

  • Attaching a .proj file to a Bugzilla bug can be accomplished by first filing the bug report, then viewing the bug and clicking "Create new attachment." For the content type, select the "Manual" radio dial and enter model/proj. Click submit and you're done.
  • 3d Animation of your model's behavior.

B

C

  • Compare variables within the Network View -- use one of the Snapshot functions on the Network and turn on the Snap Bord display in the network view.
  • Column widths in datatable: adjust by dragging on right edge of header; save using View/Save View (saves all view parameters)
  • copy data from one DataTable to another: CopyCell method, or sel rows (DataSelectRowsProg), sel cols (DataSelectColsProg) in data proc toolbox.

D

  • Document editing formatting (wiki text and ta: urls)

E

F

G

H

I

  • InputData -- everything you need to know about how input patterns from the input data table are applied to the network.

J

K

L

  • Local variables in Programs -- you aren't restricted to the global vars and args -- the loc vars in the Var/Fun toolbox can be put anywhere in a program (especially useful for Functions) to define new variables.

M

N

O

P

  • PDP++ Project Conversion -- short version: you must remove units from PDP++ Networks before loading them into Emergent, then hit Convert button at bottom of Project editor panel.
  • Projection selecting/viewing in Network View -- increase the Prjn Width from default of .002 to .005 or even .01 -- this makes the lines much easier to see.

Q

R

S

  • Signals -- "kill" signals recognized by the program (when running in the nogui background mode and otherwise unreachable) -- basically just USR1 or USR2 or ALARM, all of which will cause a project recover file to be saved, which can then be loaded to check out what is going on with the project.
  • Startup program -- how to make an automated program that will auto-run when the project is loaded. This includes info on how to set command-line arguments that can be passed to the project to set various parameters -- very convenient for exploring parameter space.

T

  • Making Test Programs for testing your network during or after training.

U

  • URL (uniform resource locator) syntax for Documents

V

W

  • Weights, accessing in Programs / Css: network.layers.LayerName.units[un_no].recv[prjn_no].Cn(cn_no) -- the sending unit is Un(cn_no). The implementation has been highly optimized so these functions (Cn, Un) are the way to access. See Unit for more info.
  • Wiki style syntax for Document editing formatting
  • Emergent won't start. One possible reason Emergent won't start is corrupted preferences. On Mac OSX, this is indicated by the Emergent icon bouncing in the dock several times and then stopping without actually starting. There are two possible files that might be the problem, one is 'options' and the other is 'root.' Start with 'options' first. Delete the options file and then restart Emergent. Emergent should create a new 'options' file. If that doesn't work try 'root.'

    On Mac OSX, there are at least two ways to do this. One way is to use the Terminal program to go to the directory ~/.emergent, where ~ indicates that this is in your user directory. To do this type 'cd ~/.emergent' to change to the correct directory. Then remove the 'options' file. The other procedure is to use the Go To Folder command in the Go menu in the Finder. Enter '~/.emergent' in the Folder name box. You can then move the 'options' or 'root' file to the trash. Note that Finder hides these hidden folders that start with a period, so you will either need to use the Go To Folder command or else use the Terminal program.

    The procedure should be comparable for Linux and Windows, but I don't know for sure.

Y

Z

Retrieved from "http://grey.colorado.edu/emergent/index.php/HowTos"
Personal tools