Development Priorities Part 2

Suggested priorities for reimplementing GENESIS 2 objects and commands in MOOSE/GENESIS 3.

Part 2: non-graphical commands

Already implemented in MOOSE 

abs           addfield     addmsg      call      ce         cos
copy          create       delete      deletemsg exists 
echo          exp          getfield    getmsg    isa        le


listcommands  listobjects  loadtab     log       move       pow
pope          pushe        pwe         quit      readcell   reset
setclock      setfield     setupalpha  setuptau  showclocks showfield
simdump       simobjdump   simundump   sin       sqrt       step
stop          tan          tweakalpha  tweaktau  useclock

High Priority

Network commands: (NOTE: The "volume" (3D) commands are not as high priority, but it would be easiest to implement them at the same time. The "2" variants take an additional destination argument and aren't used as often. Could this be made an option for the normal planardelay, etc. commands, instead of separate commands?) 

createmap       planarconnect       planardelay         planardelay2
planarweight    planarweight2       volumeconnect       volumedelay
volumedelay2    volumeweight        volumeweight2

commands related to synchans:

getsyncount         getsyndest          getsynindex         getsynsrc
normalizeweights    resetsynchanbuffers syndelay

exit
(alias for quit)
scaletabchan
input
(will be useful for running without graphics) 
check   deletefield   disable   enable   floatformat   getclock   getdate
version

Debugging commands:

debug   debugfunc   silent   gctrace    gftrace
clearerrors    maxerrors   maxwarnings

Medium Priority

Math functions:

acos  asin    atan   gaussian
max    min    rand  randseed   randseed2 (Is this used or needed?)
round    trunc

String functions:

countchar   chr       findchar   substring    strcat  strcmp
strlen      strncmp   strsub

 

cd
 (Should also implement other Unix shell commands as G3 commands, e.g. ls more pwd pushd popd.)
mkdir
 (Should we allow the user to create directories?)
save, restore
 (These require objects to have SAVE and RESTORE actions)

Commands for text files:

closefile   eof        fileexists   flushfile    listfiles
openfile    readfile   writefile

help
(Perhaps have "more" type paging in the genesis console window provided by default?)

Other commands used with imdump, kkit and kinetics: 

enddump    initdump     swapdump
msgsubstitute    objsubstitute    substituteinfo
resetfastmsg   (Will this be needed with MOOSE kinetics library?)
getenv   setenv     printenv  where   (This is assuming that environment
          variables will be used.)

addalias    addescape     addglobal    callfunc    getglobal    setglobal
getpath     getfieldnames listglobals

argc        arglist       argv         getarg     printargs     shiftarg

el          getelementlist (an alias for el)      countelementlist

balanceEm        calcCm       calcRm        rallcalcRm
duplicatetable   file2tab     fileconnect   tab2file
listactions      listclasses  listescape    setprompt

Low Priority (Note that this does not necessarily mean "unimportant" or "unlikely to be implemented". But, implemenation will probably wait until someone needs them enough to volunteer to implement them, or other higher priority items are done first.) 
writecell
- This would normally be a high priority, but should probably wait until we have done more work on on XML input/output of cell descriptions. Unlike readcell, writecell was never fully implemented.

Commands used with parameter searching: 

getparamGA    initparamBF    initparamCG    initparamGA    initparamSA
initparamSS   gen2spk        setsearch      shapematch     spkcmp
setparamGA

concen library commands:

  setupghk  setupNaCa

asciidata
(Converts a FMT1 formatted binary file to ASCII).
dd3dmsg      gen3dmsg
getdefault   setdefault   setfieldprot
setrandfield setspatialfield
stack    h
putevent
cellsheet   egg   pastechannel  plane
notes    logfile
setupgate
position    randcomp    randcoord   relposition    rotcoord
"Not sure" - these may be implemented in MOOSE under different names, implemented implicitly without need for a command, or not needed, due to differences between MOOSE and GENESIS 2 -- Comments are requested!

 

abort
(Does this have any advantages over "stop"? Is it used?) 
deleteall
(Deletes all elements from a simulation. Although many scripts use it, its use is discouraged because of it doesn't cleanly reset the state of the simulation.) 
copyleft_kin
(Should something this be built into the G3 boot message and kinetikit, instead of having it as a script command?)
getstat,  showstat
(May use Unix-dependent system calls.)
cpu
(Unix system call to display user/system usage statistics.)

Commands used with hsolve (these may not be needed with the new hsolver): 

findsolvefield    getsolvechildname   getsolvecompname

Commands used with background jobs and scheduling (may not apply with MOOSE scheduling): 

addjob    deletejob     setpriority   showjobs
addtask   deletetasks   resched       showsched
setmethod
(This will depend on the ways that solvers and integration methods are handled in MOOSE)
Not to be implemented in GENESIS 3:

Commands associated with GENESIS 1 (oldconn) synaptic connections: 

affdelay       affweight    connect    cstat              delete_connection
expsum         expweight    getconn    normalize_synapses radialdelay
region_connect scaleweight  setconn    showconn           volume_connect

Undocumented and unused buffer class objects: 

clearbuffer    getinput

Other undocumented and unused commands: 

clonemsgs    dirlist    maxfileversion    tset    error    warning     remarg
reclaim
 (Reclaims memory from deleted elements - G3 should properly manage memory without an explicit command.) 
sh
 (Issues Unix operating system command from GENESIS shell. Necessary shell commands should be built into G3, instead.) 
setrand
 (Is there a need for more than one random number generator? It is time to retire the Num. Rec. generator.)

Commands used with Extended Objects (Extended Objects aren't used very often. Implement another way for users to create new object types at the script level?) 

addaction       addclass      addforwmsg       addmsgdef        addobject
deleteaction    deleteclass   deleteforwmsg    deletemsgdef