Outline for Disk Description

From conversation with Ying, a long time ago

Lustre group quota
Cache
  reservation
  quota
  pin quota
  used
  pinned
Volatile
  reservation
  quota
  used
Work
  used -- no information available
  no limit
Advertisements

“use a build” documentation

Default version of sim-recon:

source /group/halld/Software/scripts/build_scripts/gluex_env_jlab.(c)sh

Custom version of sim-recon:

Method 1

1) define HALLD_HOME and BMS_OSNAME
2) source $HALLD_HOME/$BMS_OSNAME/setenv.(c)sh

Method 2

1) define GLUEX_TOP, BUILD_SCRIPTS
2) identify a version.xml, /path/to/version.xml
3) source $BUILD_SCRIPTS/gluex_env_version.(c)sh /path/to/version.xml

Method 2′ (private version of sim-recon)

1) define GLUEX_TOP, BUILD_SCRIPTS
2) identify a version.xml, /path/to/version.xml
3) eval `$BUILD_SCRIPTS/version.pl $version_file`
4) setenv HALLD_HOME /path/to/sim-recon (or export HALLD_HOME=/path/to/sim-recon)
5) source $BUILD_SCRIPTS/gluex_env.(c)sh

Meeting with Dmitry, December 19, 2012

D.:

  • working on multi-threading testing for CCDB

M:

  • CCDB mirror is working
  • will write a getting-started guide

To Do

  • document structure for multi-threading in CCDB
  • get build on linux mint going to support D.
  • check sqlite file production
  • add ccdb to build scripts on an equal footing with the other packages
  • document scons mysql=no
  • document ccdb-resident install of scons
  • populate the author table from group halld
  • do a nightly build of ccdb

Notes on Dmitry’s CCDB file specification

  • Do we want to allow incomplete variations in file form?
  • If not then variation information is not needed for reading.
  • If variation is not specified, and all types are present in a disk directory, then there will be redundancy in writing the disk files to the database.
  • Could disallow column naming in files
  • If columns are named, is consistency checked?
  • If columns are named, is non-standard order allowed?

simple scenario

  • all file instances are complete directory trees for a given single run when writing
  • all file instances are assumed to be for any run when reading
  • writing to database from file limited to one file at a time
  • order of constants in file is only information consulted in interpreting data