LinuxPops Stack Commands

Stack

The built in search criteria system within Linuxpops pretty much makes the stack obsolete. Normally, you make all the search criteria known to LinuxPops and all subsequent actions of accumulation and averaging are handled automatically.

One advantage of filling and using the stack is for user defined batch files. A rudimentary looping task can be defined in a batch file procedure and then the meat of the procedure can execute a series of commands on each scan in the stack.

For instance, say you wanted to plot and make hard copies of each scan in the stack. So all you would need to do, after manually filling the stack:

procedure plotandprint
startstack
        get stackscan
        show
        make
        delay 1000000
        stack /i
endstack
end

Usage:

The stack command is just the front-end to the stack sub-system.

The argument to stack are:

• stack /e
  
  • Clear out the stack.
• stack /f
  
  • Fill the stack with all scan numbers that meet the current search criteria.
• stack /l
  
  • List out the scans in the stack.
• stack /g
  
  • Fetch the scan pointed to by stackscsan.
• stack /i
  
  • Bump the stackindx by one.
• stack /r
  
  • Reset stack pointer back to the first scan in the stack.

The stack, once filled, contains all scans that would otherwise meet the search criteria used by accum or list. Once filled it can be used in a batch file command sequence.

Example:

procedure stest
usage: No args for this command
#
stack /f
stack /l
#
startstack
   get stackscan
   show
   base
   pause
   stack /i
endstack
#
print acount
#
end

Lets break down the example above:

• procedure stest
  • The name of this procedure; can be referenced simply by stest
• usage
  • Help for how to use batch procedure; none in this example
• stack /f
  • Fill the stack with all scans that meet current search criteria.
• stack /l
  • Print out a list of selected scans. (For diagnostic purposes)
• startstack
  • Label: showing the top of the loop.
• get stackscan
  • Fetch the file with the 'stackscan' scan number; ENVIRONMENT::stackscan points to the entry in the LinuxPops Stack Commands pointed to by ENVIRONMENT::stackindx.
  • stack /g performs the same operation.
• show
  • Show the scan in the plot window.
• base
  • Remove a baseline;
• pause
  • Wait for user to hit a key; 'q' to quit batch processing.
• stack /i
  • Increment the stack counter and set ENVIRONMENT::stackscan to the next scan number in the LinuxPops Stack Commands.
• endstack
  • End of the loop; Linuxpops will check the ENVIRONMENT::stackdone flag to determine if we are finished.
• print acount
  • Print out the number of scans in the LinuxPops Stack Commands.
• end
  • End of the procedure.

Variables:

• LinuxPops Stack Commands
  • Statically defined floating point array of [MAX_STACK] size.
• ENVIRONMENT::stackscan
  • Scan number pointed to by ENVIRONMENT::stackindx
• ENVIRONMENT::stackindx
  • Current LinuxPops Stack Commands index pointer
• ENVIRONMENT::acount
  • Count of the total members in the LinuxPops Stack Commands
• ENVIRONMENT::stackdone
  • True when end of LinuxPops Stack Commands reached