Abundant and rare isotope file creation and naming, diagnostic file creation, coefficents for estimating hard disk space usage, report formats and column headers are all specified in this file.
Directives are specified as directive_name directive_value pairs in the file.
A directive pair is used to describe each parameter in DMANserv_v2(8) ’s parameter configuration table.
For example, to set the name of rare isotope data collection file to evt14 as might be the case for collecting carbon data the directive would be set like this:
fname_es_evt evt14
A file containing the proper settings is created for each AMS species. A directory is created for each species and the file is placed in it.
The dmngr_config files are usually located in the /AccelNET/$CONF/ams_setup/<species>/ directory.
See environ(5) for information about CONF.
See DMANsetconfig_v2(8) for information on how to ask DMANserv_v2(8) . to load this file.
See DMANdiag_v2(8) for information on how to ask DMANserv_v2(8) for a copy of the currently loaded config table.
The file directives are divided into sections. Each section deals with a particular aspect of DMANserv_v2(8) ’s operation.
For example, there is a section dealing with the file names used for abundant isotope data collection, another for rare isotope file names, another for setting the display properties such as the column label, the numeric field formats, and so forth.
Data collection channels in the hardware are associated with these file names by setting the DevType in the AccelNET database records associated with the transient recorder channel. The DevType associated with each file name is given below. At this time two DevTypes are associated with each file name.
If this is defined listp_v2(8) will create a file in each run directory and write all kinds of fascinating messages in it.
If this is defined TRtask(8) will create a file in each run directory and write all kinds of fascinating messages in it.
Not in use at this time.
Not in use at this time.
If the value is no cup file space will not be included in the estimate.
The default value is yes.
NOTE: I don’t think this works
The default value is 32.
The default value is 1.
The value of this parameter should be equal to the number of abundant isotope file names which have been defined.
The default value is 4.
Yes, one could count the file name definitions instead.....
If the value is no rare isotope file space will not be included in the estimate. In this case the values of fsize_evt_size and fsize_evt_cycle are ignored.
The default value is yes.
The default value is 50.
The default value is 10.
The default value is 1.
The default value is 1.1.
The default value is 5000.
The default value is 0.
The default value is 0.
The default value is 0.
The default value is 10.
The default value is 10.
The default value is 60.
For example, cup_label_le1 is used in DMANmngr’s runlist, results, and summary windows where LE cup 1 has been selected for display.
It is also used by DMANserv_v2(8) when printing the runlog, etc. and by DMANprint_v2(8) for it’s printing operations.
This is similiarly true for counters, ratios, and parameters.
The maximum size of a label field is: 11.
Valid values are:
nil - field display is suppressed
F0 - X
F1 - X.X
F2 - X.XX
F3 - X.XXX
F4 - X.XXXX
F5 - X.XXXXX
F6 - X.XXXXXX
F7 - X.XXXXXXX
E0 - XeYY
E1 - X.XeYY
E2 - X.XXeYY
E3 - X.XXXeYY
E4 - X.XXXXeYY
E5 - X.XXXXXeYY
E6 - X.XXXXXXeYY
E7 - X.XXXXXXXeYY
If this value is exceeded measurement of the current item is terminated and subsequent measurements of the item are inhibited by setting the runflag false.
This is very useful in work where the count rates can be too high.
Valid choices are:
nil - nothing assigned
cnt(1-8)
Valid choices are:
nil - nothing assigned
cnt(1-8)
Valid choices are: nil, cnt(1-8)
The default value is: nil.
Valid choices are: nil, cnt(1-8)
The default value is: nil.
The default value is: off.
Note that this setting is the default setting for DMANserv and can be changed from a button in DMANmngr after loading the dmngr_config file.
The default value is: rat(1-8)
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
The default value is: F3
ratio scaling factor
after the ratio is calculated it is multiplied by this value and the answer is placed in the results table
The default value is: par(1-8)
The default value is: F3
They should be set like this for the same behavior as abc:
run_weight_type auto
sum_weight_type unc
sum_chi_mode auto
runlist item weighting type
possible values are: auto and equal
summary weighting type
possible values are: equal, cupI, and unc
summary chi mode
possible values are: auto and 1st
The judgment process is an external program DMANjudge_v2(8) which communicates with DMANserv_v2(8) .
When DMANserv wants a judgement rendered it sends a message to DMANjudge asking for a judgement. DMANjudge performs it’s calculations and reponds with either pass or fail.
Two parameters in the runlist, Jn and Jlimit interact with the judgement process. These parameters are specified as part of an item directive in the runlist.
Jn is the minimum number of measurements on which to base a judgement.
Jlimit is the value below which the error must be before the item passes judgement.
A batch directive (batch judge <off/on>) may be used to enable of disable judgement when the runlist is loaded.
Choices are: Nbest, Nrecent, Nmin_best. or Nmin_recent.
Nbest calculates the statistics for all the measurements and finds which Jn number of measurements are the best ones.
The remaining measurements are excluded and the statistics recalculated.
Finally the appropriate number (selected below, see the judge_rat_src and judge_rat_fld directives) is compared to Jlimit and judgement is rendered.
Nrecent calculates the statistics of the Jn most recent runs.
The appropriate number is compared to Jlimit and judgement is rendered.
Nmin_best calculates the statistics for all the measurements and compares the result to Jlimit.
If the result is greater than Jlimit the measurement with the greatest scatter is excluded and results are recalculated.
If the result is worse than the previous result the process stops and judgement is rendered.
If the result is better than (or the same as) the previous result the process is continued until there are at most Jn results left unexcluded.
Nmin_recent starts by calculating the statistics for the N most recent measurements and compares the result to Jlimit.
If the result is greater than Jlimit the next oldest measurement is added and results are recalculated.
If the result is worse than the previous result the process stops and judgement is rendered.
If the result is better than (or the same as) the previous result the process is continued until all measurements are included.
Valid values are: rat1-8
Valid values are: stddev,sdom,stat,sdomP,statP,unc,uncP
Valid values are: abc or stsd
If the value is abc then the uncertainty calculation is performed using the rules of NEC’s abc program.
If the value is stsd then the larger of stat or sdom is used for uncertainty (without regard for the state of chiSQ).
Each type of report is broken down into subfields.
The ctl subfield is used for displaying fields which are unique to the report.
The cup, cnt, rat, and par fields are used to select which fields of the type will be displayed.
The sfld field is used to select which of several fields associated with an item are to be displayed.
For example, we might wish to print the runlist with the following:
item
number, cat position, sample type, sample name, number of completed measurements
cups 1,2, 5,6 average current and total charge
counters 1,2,3 total cnts
ratios 1-3 with mean, sdomP, statP, and chi fields.
First the ctl fields:
log_runlist_fmt_ctl item,pos,type,sample,comp
Next the cups:
log_runlist_fmt_cup
cup1,cup2,cup5,cup6
log_runlist_fmt_sfld cupA,cupC
Next the counters:
log_runlist_fmt_cnt cnt1,cnt2,cnt3
log_runlist_fmt_sfld cupA,cupC,cntT
Next the ratios:
log_runlist_fmt_rat
rat1,rat2,rat3
log_runlist_fmt_sfld cupA,cupC,cntT,mean,sdomP,statP,chi
Here it is all together:
log_runlist_fmt_ctl item,pos,type,sample,comp
log_runlist_fmt_cup cup1,cup2,cup5,cup6
log_runlist_fmt_cnt cnt1,cnt2,cnt3
log_runlist_fmt_rat rat1,rat2,rat3
log_runlist_fmt_sfld cupA,cupC,cntT,mean,sdomP,statP,chi
Valid choices are:
com - comment (this prints on the hdr lines)
pos - cathode position
type - sample type (OXYI, etc.)
sample - sample name and number
sname - sample name
sname2 - aux sample name
Valid choices are:
com - comment (this prints
on the hdr lines)
eflag - exclude flag
item - item number
aflag - active flag
rflag - run flag
pos - cathode position
grp - group number
type - sample type
sname - sample name
sname2 - aux sample name
sgrp - summary group number
meas - number of measurements to perform
comp - number of completed measurements
res_cnt - number of meas used in calculations
mode - count mode
limT - count Tlimit
limC - count Climit
warm - warm up time
Jn - judge, requested number of meas
Nj - judge, actual number of meas
Jlimit - judge, limit
Jvalue - judge, current value
Jstatus - judge, current judge status
Valid choices are:
nil
cup(1-12)
le(1-6)
he(1-6)
Subfield choices are:
cupA - avg current
cupC - total charge
Valid choices are:
nil
cnt(1-8)
Subfield choices are:
cntT - total count
cntA - avg count
cntS - sigma stat
Valid choices are:
nil
rat(1-8)
Subfield choices are:
mean -
chgT - num/den total charge
chgP - toggle charge/particles
weight -
dev - the deviation used in the summary calcs
stddev -
sdom -
stat -
unc -
stddevP -
sdomP -
statP -
uncP -
chi -
chi_limit -
The values should be comma separated on one line with no whitespace between fields.
Valid choices are:
com - comment (this prints
on the hdr lines)
eflag - exclude flag
jeflag - judge exclude flag
idx - internal index value (software debug)
item - item number
time - completion time
grp - group number
pos - cathode number
meas - number of measurements to perform
sname - sample name
sname2 - aux sample name
sgrp - summary group number
cycle - number of cycles in measurement
see log_runlist_fmt_cup for a list of valid field choices
Valid subchoices are:
cup - cup current
part - if present display as particle current
else electrical current
chg - charge state
cupC - total charge
see log_runlist_fmt_cnt for a list of valid field choices
Valid subchoices are:
cnt - counter value
dcnt - dead time corrected count
dt - counter value
ltf - live time fraction
cntS - sigma stat
tdl - toggle dtc/ltf display
see log_runlist_fmt_rat for a list of valid field choices
Valid subchoices are:
ratio - ratio = num/den * weight
chgT - num/den total charge
chgP - toggle charge/particles
weight - weighting value
dev - deviation
unc - uncertainty
stat - 1/sqrt(N)
statP - statP = ratio/stat
Valid choices are:
nil
par(1-8)
see log_runlist_fmt_sfld for a list of valid field choices
see log_runlog_fmt_sfld
Valid choices are:
com - comment
grp - summary group
name - cathode name and number for cathode list
res_cnt - number of valid items in calcs
see log_runlog_fmt_cup
Valid subfield choices are:
cupA - avg current
cupC - total charge
see log_runlog_fmt_cnt
Valid subfield choices are:
cntT - total count
cntA - avg count
cntS - sigma stat
see log_runlog_fmt_rat
Valid subfield choices are:
ratios
mean -
chgT - num/den total charge
chgP - toggle charge/particles
stddev -
sdom -
stat -
unc -
stddevP -
sdomP -
statP -
uncP -
chi -
chi_limit -
see log_cathode_fmt_ctl
see log_runlist_fmt_sfld
see log_runlog_fmt_sfld
see log_summary_fmt_sfld