# Mostly this is an EXAMPLE of what the build setup tools USERCONFIG_FILE 
# input MUST contain because these entries are NOT defined elsewhere
#
# Build setup tools use $USER to create _empty_USER_NAME, 
# so there is no need to override it unless 
# your directories are under a different name than you login with.
# And if Ops does not use datamgr in their dir names, we have a 
# problem until we create them either a template or node-specific
# file.
#_empty_USER_NAME      datamgr
#
#
# Remember that the _empty_OVERRIDE_ROOT destination must contain
# bin/<os> (e.g. bin/linux) to get into one's PATH definition
#
_empty_OVERRIDE_ROOT   /home/_empty_USER_NAME/defs/
_empty_DEFS_ROOT       /home/_empty_USER_NAME/defs/_empty_SCIENCE_VERSION
_empty_OBS_ROOT        /store/sthubbins/osf/
_empty_HOME_ROOT       _empty_STORE_ROOT/_empty_USER_NAME/opus_home/_empty_SCIENCE_VERSION
_empty_PATH_BASEDIR    _empty_INFO_ROOT
_empty_POLLING_TIME    60
#
# every user must have a unique value here
# 53718 reingest needs a unique ID, too
_empty_INGEST_PIPE_ID  DADS
_empty_REINGEST_PIPE_ID  REGR
#
# Be sure to set these params in your my_config.txt file
# if you are going to run REFPIPE 
#
_empty_ARCHIVE_PASSWORD
_empty_DELIVERY_PASSWORD
_empty_RETRIEVAL_DIR     _empty_PATH_BASEDIR/refpipe/retrievals
_empty_ACS_FINAL_PROD_DIR # might help if I knew what it was
_empty_ACS_WFC_SAVE_DIR   # might help if I knew what it was
#
## Add some specifics for QL/RT from 55509
## 55509 may cause failures on dev because 2 paths created from one tempalte
## 67671 I think PATHMAP is ONLY going to work in a path template.
#_empty_QL_PATHMAP     _empty_PATHMAP[ql_rt_science_auto]
#_empty_RT_PATHMAP     _empty_PATHMAP[ql_rt_science_auto]