next up previous contents
Next: The TCAC and TCAR Up: Learning by Example Previous: Creating the Input N-tuple   Contents

SNOMAN Commands

The SNOMAN commands are stored in tca_demo.cmd which contains:-

FILE TCA 1 tca_demo_in.ntp id=100
FILE TCA 2 tca_demo_out.ntp
This defines the input and output n-tuple file names and the input n-tuple id. The output n-tuple id is defined by the bank number of the TCAR in exactly the same way as for the NTPR. If the output file does not exist it will be created. The output file name can be the same as the input, in which case the same file is used for input and output. However, in all cases, the output n-tuple id must be different to the input id.

$num_events 1
This is not strictly necessary; once TCA gets called i.e. at the start of the first ``event'' it retains control until the process completes and the switches to the termination phase.

$processor_sequence $user_controlled
$processor_list ' TCA END'
This defines the minimalist processor list!

$tca_enable_ntuple 201
This enables the TCAR you want. So TCA will read from n-tuple id 100 and output to id 201 using the TCAR 201 bank to define its contents.

titles tca_demo_titles.dat 
titles ntuple.dat
titles job_control.dat
Here are the titles banks that are needed. ntuple.dat is needed because TCA uses NTP, and NTP needs an NTPC bank even though it won't use it to service TCA requests.

end
As we have supplied all the titles files we need there is nothing more to do so we signal the end of the command file.


next up previous contents
Next: The TCAC and TCAR Up: Learning by Example Previous: Creating the Input N-tuple   Contents
sno Guest Acct 2009-09-09