• • mode = ’manimgonly’ : only the products of manual imaging (recognized by the string "manual" in the file names) and the corresponding scripts will be packaged using "copy"; supplemental full pol. calibration will be picked up in the case of PL intensity calibration)

• • style = "cycle5-pipe", "cycle6-pipe", "cycle7-pipe", "cycle8-pipe": taking into account naming changes (manifest, ppr) from the CASA 5.1.1 pipeline onwards

• • style = "cycle5-pipe", "cycle6-pipe", "cycle7-pipe": taking into account naming changes (manifest, ppr) from the CASA 5.1.1 pipeline onwards

    cd <top dir of pipeline results>/S*OUS*/G*OUS*/M*OUS*/
    ln -sf working products
    cd ../../../../..

Case 1b: incremental packaging of only the manual imaging products

Case 2b: packaging after external imaging including only manual imaging products

• PIscript: should be the path to the latest version of the scriptForPI.py (from the JAO CVS repository or a mirror)

• • mode = ’manimgonly’ : only the products of manual imaging (recognized by the string "manual" in the file names) and the corresponding scripts will be packaged using "copy")

• • style = "cycle5-nopipe", "cycle6-nopipe": same as cycle4-nopipe
  • style = "cycle5-pipe", "cycle6-pipe": taking into account naming changes (manifest, ppr) from the CASA 5.1.1 pipeline onwards

Case 1a: packaging for external manual imaging

Case 1b: incremental packaging of only the science imaging products

Then run the packager as follows:

      QA_Pipeline_Stager(pipeline_root='<top dir of pipeline results>',
                                      staged_root='<project ID == top dir of output package>',
                                      mode='sci-img-only',  
                                      cycle=<num>) # where num is 6 

    Example:
       QA_Pipeline_Stager('2015.100456.S-2016-08-08T123456', '2015.100456.S', mode='sci-img-only', cycle=6)

Case 2a: packaging after external manual imaging including calibration and imaging products

Case 2b: packaging after external imaging including only science imaging products

A package as created in Case 1a above has arrived at the ARC (or a JAO analyst).

However, the calibration products have already been ingested in the archive.

The analyst has run the scriptForPI to create the *.ms.split.cal(s) and verified that the scriptForPI is working in this case.

The analyst proceeded to perform the imaging in the "calibrated" directory which was created by the scriptForPI.

The resulting fits files reside in the "calibrated" directory and the scriptForImaging resides there as well or in the "script" directory.

The result is QA2_PASS and now the science imaging results are to be packaged for delivery.

Then run the packager as follows:

       QA_Packager(origpath='<top dir of the analysis dir>',
                               packpath='<project id = top dir of output package>',
                               readme='<path to readme file>',
                               mode='sci-img-only',
                               style='cycle6-pipe', # this style needs to the chosen in this case
                               PIscript="./scriptForPI.py")  # overwrites the original scriptForPI.py if needed

   Example:
       QA_Packager(origpath='./2018.100456.S-analysis',
                               packpath='./2018.100456.S',
                               readme='myREADME.txt',
                               mode='sci-img-only',
                               style='cycle6-pipe',
                               PIscript="./scriptForPI.py")

NOTE again: where it says "top dir of output package", what meant here is the directory that looks like this: origpath='analysis/2015.1.01247.S.MOUS.uid___A001_X2f6_X66.SBNAME.ULASJ1243_a_03_TE

• • style = "cycle4-nopipe": so far (v1.49) same as cycle3-nopipe
  • style = "cycle4-pipe": so far (v1.49) same as cycle3-pipe1

• • style = "cycle3-nopipe": same as cycle2-nopipe except for the recognition of the scriptForImagingPrep.Py
  • style = "cycle3-pipe1": same as cycle2-pipe1 except for the recognition of the scriptForImagingPrep.Py and antennapos.csv files

• • style = "cycle3-nopipe": presently the same as cycle2-nopipe except for the recognition of the scriptForImagingPrep.Py
  • style = "cycle3-pipe1": presently the same as cycle2-pipe1 except for the recognition of the scriptForImagingPrep.Py

• • style = "cycle3-nopipe": presently the same as cycle2-nopipe
  • style = "cycle3-pipe1": presently the same as cycle2-pipe1

QA_Pipeline_Stager('2013.1.00911.S_2015_08_07T16_10_05.732', '2013.1.00911.S', mode='copy', PIscript="./scriptForPI.py")

The typical call to package pipeline-calibrated TP data looks like this:

QA_Packager(origpath='SB_uid___A001_X196_X40', readme='./README.header.txt', packpath='./2015.1.00501.S', style='cycle2-pipe1', mode='hard', PIscript="./scriptForPI.py")

Packaging of TP data

Since version 1.43 of the packager, handling of Total Power data is supported.

The typical call to package TP data looks like this:

QA_Packager(origpath='SB_uid___A001_X196_X40', readme='./README.header.txt', packpath='./2012.1.00501.S', style='cycle2-nopipe', mode='hard')

The packager will detect that the package is a TP dataset from the presence of scripts with names ending in scriptForSDCalibration.py . It will then override other modes and switch to TP mode. The typical output tree is shown here.

Non-standard scripts (i.e. not ending in scriptForSDCalibration.py or not named exactly scriptForSDimaging.py) will also be packaged but a WARNING will be issued about them.

ALMA QA2 Packaging Script

Case 1:

Case 2:

Acknowledgements

• style: alternative (and recommended) way to specify a number of option at once.

QA_Packager(origpath='/pathToMySB',readme='./README.header.txt',packpath='./20XX.1.00XXX.S',mode='hard', style='cycle2-nopipe', PIscript='<yourjaomirror>/science/qa2/scriptForPI.py')

• style: decides on details of the packaging and whether pipeline products are involved (note: the "noms" parameter still exists but is deprecated)

• append (optional): The appending mode (see below).

• • style = "cycle2-nopipe": corresponds to noms=True
  • style = "cycle2-pipe1": corresponds to noms=True and the directive to look for and include pipeline products

Early Science Packaging Script

Running the script

Packaging of standard script-generator-assisted analysis products

For a standard script-generator-assisted analysis, you can continue to run the script in the following way:

The parameters mean the following:

Packaging including Pipeline products

If you have run the ALMA Pipeline and produced output which you want to package for further processing elsewhere, you can use the packager to create a "delivery style" package.

Also, if you have received such a "delivery style" package from elsewhere and have done the imaging part of the QA2 work and now want to package everything for final delivery to the PI, the packager enables you to do that as well.

Both use cases are described below:

Case 1:

Then run the packager as follows:

      QA_Pipeline_Stager(pipeline_root='<top dir of pipeline results>',
                                      staged_root='<project ID == top dir of output package>',
                                      mode='<hard, copy, fake>',  # default is 'copy'
                                      PIscript="<path to scriptForPI.py>") # needs to be included in the package

    Example:
       QA_Pipeline_Stager('2013.100456.S-2014-08-08T123456', '2013.100456.S', mode='copy', PIscript="./scriptForPI.py")

Case 2:

The analyst has run the scriptForPI to create the *.ms.split.cal(s) and verified that the scriptForPI is working in this case.

The analyst proceeded to perform the imaging in the "calibrated" directory which was created by the scriptForPI.

The resulting fits files reside in the "calibrated" directory and the scriptForImaging resides there as well or in the "script" directory.

The result is QA2_PASS and now the whole data is to be packaged for delivery.

Then run the packager as follows:

       QA_Packager(origpath='<top dir of the analysis dir>',
                               packpath='<project id = top dir of output package>',
                               readme='<path to readme file>',
                               mode='<hard,copy,fake,ticket>',
                               append='',
                               gzip_caltables=True,
                               style='cycle2-pipe1', # this style needs to the chosen in this case
                               PIscript="./scriptForPI.py")  # overwrites the original scriptForPI.py if needed

   Example:
       QA_Packager(origpath='./2013.100456.S-analysis',
                               packpath='./2013.100456.S',
                               readme='myREADME.txt',
                               mode='hard',
                               append='',
                               gzip_caltables=True,
                               style='cycle2-pipe1',
                               PIscript="./scriptForPI.py")

Packager Unit Test

In the same repository directory where you find the packager module, you also find a "unit test" for it. This enables you to confirm that the basic functionality of the packager is working.

Usage:

     tar xvzf QA2_Packaging_module.unit-test.tgz
     cd QA2_Packaging_module.unit-test
     cp ../QA2_Packaging_module.py .
     start casapy and run
         execfile('QA2_Packaging_module.unit-test.py')

• • mode = ’hard’ : The script generates hard links in the destination folder. This way, the file-pointers at both the origin and the destination folders, refer to the same physical locations (i.e., inodes) in the disk. This is the recommended way of packaging for noms=False, but if you use noms=True better use mode="copy" is better because it works across file systems.

• • style = "cycle0-nopipe": corresponds to noms=False
  • style = "cycle1-nopipe": corresponds to noms=True
  • default = "" (empty): ignore the parameter "style" and use the noms parameter instead

• noms: do not include the MSs

Run the script with

NOTE: The following documentation was valid for cycle 0 style delivery and will shortly be updated to Cycle 1 style

• PIscript added Nov 2013

• • execfile('/diska/work/software/jao-mirror/AIV/science/qa2/QA2_Packaging_module.py')

    Then run the script with

• • mode = ’ticket’ : Use this to create the 'ticket.zip' file to attatch to the SCOPS ticket (see below).

• • mode = ’fake’ : This is the default. The script creates empty (i.e., dummy) files at the destination folder.
  • mode = ’copy’ : The files are copied in the normal way.
  • mode = ’hard’ : The script generates hard links in the destination folder. This way, the file-pointers at both the origin and the destination folders, refer to the same physical locations (i.e., inodes) in the disk. This is the recommended way of packaging.
  • BEFORE PACKAGING WITH 'HARD' type:

  • <font size="2"><span style="font-size: 10pt">execfile('/diska/work/software/jao-mirror/AIV/science/qa2/QA2_Packaging_module.py')</span></font>

    Then run the script with

    QA_Packager(origpath='/pathToMySB',readme='./README.header.txt',packpath='./2011.0.00XXX.S',
    append='',mode='hard')

  • mode = ’move’ :The files are moved from the origin to the destination. Then, symbolic links are created at the origin. The symbolic links are never made to whole folders, but only to files (to avoid, for instance, an accidental deletion of whole folders at the destination path by removing the content of a linked folder).
  • mode = ’ticket’ : Similar to ’fake’, but the files to be added to the JIRA ticket are hard-linked. This way, the packager will generate valid ticket tar/zip files, but the measurement sets and tables will not be copied. Recommended for creating the jira ticket file.

• • append = ’’ : This is the default. It removes any previous data at the destination folder before the packaging.
  • append = ’group’ :The script appends a new group id to the destination folder (so the other groups, if any, are not removed).
  • append = ’member’ : The script appends new member id(s) to the group with highest id (so the other groups, if any, and the other member ids, if any, are not removed).

• readme: The path to an ascii file with the text of the README header (for a template see this link at ESO or find it in the CVS repository here: AIV/science/qa2/README.header.txt, or use the text at the bottom of this page)

README

Atacama Large Millimeter/submillimeter Array (ALMA)

#####

Cycle: 0 (Early science)
Project code:
SB name:
PI name:
Project title:
Configuration:
Proposed rms:
CASA version used for reduction: 3.4
Comments from Reducer:

#####

This file describes the content of the tar file you have received. The
full data structure is inserted below.

At this stage, we are releasing data after completion of one SB (excuted
multiple times if required), so you will find only one member_ouss_id
directory.  This directory contains this README file and the following
directories: raw, calibrated, calibration, script, qa2, log, product.

- 'raw' contains the apriori calibrated ms for each execution block,
after being split into the science spectral windows.  This calibration
includes: WVR, Tsys and antenna position corrections and apriori
flagging.
- 'calibrated' contains the fully calibrated ms for each execution block.
- 'calibration' contains the files needed for calibration starting from
the initial ms to the fully calibrated data.   Plots are included.
- 'script' contains the reduction scripts used to process the initial ms
to calibrated data, but also to obtain concatenated data (if more than
one execution) and imaging products.  There are usually several scripts
dealing with different parts of the processing.
- 'product' contains the fits files of the selected image products. 
These will not include all images of scientific value, but will indicate
the quality of the calibration and images.
- 'qa' contains the qa2 reports that show plots and text information
needed to assess the quality of the processing.  The resultant image
rms, compared with that proposed, is given.
- 'log' contains the casa log files.

#####

• File names that are not unique (do not start with uid name, or X...) will be prepended with the uid automatically. So 'qa2_part1.png' will be renamed 'uid___A002_X3dc0e7_X528__qa2_part1.png'. But 'X8c.checklist.txt' will not be renamed.
• QA2 files will be found at the SB level, at the asdm level, and in the qa2 directory. They should match one of: *.jpg, *qa2.txt, *qa2-summ.txt, *.qa2.pdf, *textfile.txt', *qa2_part?.png
• Checklists should match one of: *checklist, *checklist.txt, *Checklist, *Checklist.txt [script need updating]

Example data reduction directory structure

The packaging script follows the conventions described in the "How to reduce ALMA science data?" document. In case there are multiple executions for each SB, the recommended structure is the following:

For single asdms per SB, the structure would look like this:

project123 - parent directory for the data reduction of this project
   SB1 - directory for SB number 1
      Xab1 - a directory for the asdm, named after the last few characters for the asdm
         including also the imaging script and fits files etc      
   SB2 - directory for SB number 2
      Xbb1
 

or, alternatively:

project123 - parent directory for the data reduction of this project
   Xab1 - a directory for the asdm, named after the last few characters for the asdm
      including also the imaging script and fits files etc      
   Xbb1
 

The directories named Xab1 etc should contain uid___xxx.scriptForCalibration.py, uid___xxx.split, (and uid___xxx.split.cal), all calibration tables and the checklist. The only subdirectory in here should be qa2. Please do not create a separate 'Calibration' subdirectory in here. Note that there is no requirement for these directories to start with 'X'. You can call them 'Calibration_Xab1', if you prefer.

Some data reducers may find it convenient to put results (images, cubes etc) in separate directories at the same level as the X directories. The packaging script will find the data products in those directories.

For example, for project 229, which contains four SBs, the data reduction directory looks like this:
=project229=
|-- IRC10216_setup3_b6_run_x2 - first SB
|   |-- IRC10216_setup3_b6_runx2.imaging.txt - notes for the PI (optional)
|   |-- X8c - first execution of this SB
|   |   |-- checklist.txt - checklist (does not need to be prepended by asdm name)
|   |   |-- qa2 - qa2 directory
|   |   |   |-- qa2_part1.png
|   |   |   |-- textfile.txt
|   |   |   |-- etc
|   |   |-- uid___A002_X3c9295_X8c.ms
|   |   |-- uid___A002_X3c9295_X8c.ms.antpos
|   |   |-- uid___A002_X3c9295_X8c.ms.scriptForCalibration.py
|   |   |-- uid___A002_X3c9295_X8c.ms.split
|   |   |-- uid___A002_X3c9295_X8c.ms.split.cal
|   |   |-- uid___A002_X3c9295_X8c.ms.split.ap_pre_bandpass
|   |   |-- uid___A002_X3c9295_X8c.ms.split.ap_pre_bandpass.plots
|   |   |-- etc
|   |-- X528
|   |   |-- uid___A002_X3dc0e7_X528.ms
|   |   |-- etc
|   |-- Combined - Optional directory to put the combined products in
|   |-- calibrated.ms - combined ms. Will not be packaged!
|   |-- calibrated_all_setup3_b6.clean.fits - a fits file
|   |-- scriptForFluxCalibration.py
|   |-- scriptForImaging.py
|-- IRC10216_setup4_b6_run_x2
|   |-- X3c9295_X1e0
|   |   |-- uid___A002_X3c9295_X1e0.ms
|   |   |-- etc

Example output directory structure

Tarring up the package

In order to make data delivery to archival researchers in the future easy, please use tarsplit.py from cvs AIV/science/DSO to create the tarfiles. E.g.

tarsplit.py -n 2012-06-20 2011.01234.S

This helps to split the data into chunks that allow for efficient network transfer to and from the ARCs. Also it makes sure that the tarfiles obey to the naming convention which helps with the tracking as well as the mini-datapacker that will run in the Request Handler.

• paths should not end in /

Early Science Packaging Script

The latest version of the packaging script has been committed to cvs here: AIV/science/qa2/QA2_Packaging_module.py

The contents of the package should be consistent with the guidelines described here: http://almasw.hq.eso.org/almasw/bin/view/Archive/Cycle01database

A pdf document with a more detailed description of the packaging script: documentation.pdf

Running the script

The script should be run from within casa. It can be run from any directory. The import is done with

from QA2_Packaging_module import *

Then run the script with

QA_Packager(origpath='/pathToMySB',readme='./README.header.txt',packpath='./2011.0.00XXX.S',
append='',mode='fake')

• origpath should be the path to the reduction directory for a particular SB. Several subdirectories for EBs could exist within this directory.
• packpath: the path to the destination folder (which should have the project code as name)
• readme: The path to an ascii file with the text of the README header
• mode: The copying mode:
  • mode = ’fake’ : This is the default. The script creates empty (i.e., dummy) files at the destination folder.
  • mode = ’copy’ : The files are copied in the normal way.
  • mode = ’hard’ : The script generates hard links in the destination folder. This way, the file-pointers at both the origin and the destination folders, refer to the same physical locations (i.e., inodes) in the disk. This is the recommended way of packaging.
  • mode = ’move’ :The files are moved from the origin to the destination. Then, symbolic links are created at the origin. The symbolic links are never made to whole folders, but only to files (to avoid, for instance, an accidental deletion of whole folders at the destination path by removing the content of a linked folder).
  • mode = ’ticket’ : Similar to ’fake’, but the files to be added to the JIRA ticket are hard-linked. This way, the packager will generate valid ticket tar/zip files, but the measurement sets and tables will not be copied. Recommended for creating the jira ticket file.
• append: The appending mode (see below).
  • append = ’’ : This is the default. It removes any previous data at the destination folder before the packaging.
  • append = ’group’ :The script appends a new group id to the destination folder (so the other groups, if any, are not removed).
  • append = ’member’ : The script appends new member id(s) to the group with highest id (so the other groups, if any, and the other member ids, if any, are not removed).

Examples

For example, for project 229, which contains four SBs, one of them is called 'IRC10216_setup3_b6_run_x2', you can run:

QA_Packager(origpath='/scratch04/arcproc/project229/IRC10216_setup3_b6_run_x2',readme='./README.header.txt',
packpath='./2011.0.00229.S',append='',mode='fake')

This will create a dummy directory structure 2011.0.00229.S. It is recommended to run it in this mode first. If everything looks OK, run it again with mode='hard', which is the recommended mode for packaging. The fake mode is very fast, but the 'hard' mode may take a while because split will have to be run several times to split out the relevant data columns from .split and .split.cal files.

The script will also produce two files with extension 'ticket.tar' and 'ticket.zip'. These are the files that can be attached to the data reduction ticket. They contain the README, the qa2 files, the scripts, and the expected size of the package. Attaching zip files to the jira ticket seems very convenient because these can be opened directly from the jira ticket, without having to download the whole file.

If the script is run in fake mode, note that the .ticket files are also dummy files. In order to make real ticket files, run the script in 'hard' mode, or use mode='ticket' (recommended). The latter mode will create a valid ticket file, but will only create a dummy packaging directory:

QA_Packager(origpath='/scratch04/arcproc/project229/IRC10216_setup3_b6_run_x2',readme='./README.header.txt',
packpath='./2011.0.00229.S',append='',mode='ticket')

Appending a member

QA_Packager(origpath='/scratch04/arcproc/project229/IRC10216_setup4_b6_run_x2',readme='./README.header.txt',
packpath='./2011.0.00229.S',append='member',mode='fake')

Example directory structure of input and output

.
|-- IRC10216_setup3_b6_run_x2
|   |-- IRC10216_setup3_b6_runx2.imaging.txt
|   |-- X3c9295_X8c
|   |   |-- X3c9295_X8c.checklist.txt
|   |   |-- qa2
|   |   |   |-- qa2_part1.png
|   |   |   |-- textfile.txt
|   |   |   |-- etc
|   |   |-- uid___A002_X3c9295_X8c.ms
|   |   |-- uid___A002_X3c9295_X8c.ms.antpos
|   |   |-- uid___A002_X3c9295_X8c.ms.scriptForCalibration.py
|   |   |-- uid___A002_X3c9295_X8c.ms.split
|   |   |-- uid___A002_X3c9295_X8c.ms.split.cal
|   |   |-- uid___A002_X3c9295_X8c.ms.split.ap_pre_bandpass
|   |   |-- uid___A002_X3c9295_X8c.ms.split.ap_pre_bandpass.plots
|   |   |-- etc
|   |-- X3dc0e7_X528
|   |   |-- uid___A002_X3dc0e7_X528.ms
|   |   |-- etc
|   |-- calibrated.ms
|   |-- calibrated_all_setup3_b6.clean.fits
|   |-- scriptForFluxCalibration.py
|   |-- scriptForImaging.py
|-- IRC10216_setup4_b6_run_x2
|   |-- X3c9295_X1e0
|   |   |-- uid___A002_X3c9295_X1e0.ms
|   |   |-- etc

Note that the file names that are not unique (do not start with uid name, or X...) will be prepended with the uid automatically. So 'qa2_part1.png' will be renamed 'uid___A002_X3dc0e7_X528__qa2_part1.png'. But 'X3c9295_X8c.checklist.txt' will not be renamed.

After running

QA_Packager(origpath='/scratch04/arcproc/project229/IRC10216_setup3_b6_run_x2',readme='./README.header.txt',
packpath='./2011.0.00229.S',append='',mode='fake')

|-- 2011.0.00229.S_setup3_b6/
|   |-- sg_ouss_id/
|   |   |-- group_ouss_id/
|   |   |   |-- member_ouss_id/
|   |   |   |   |-- raw/
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528.ms.split/
|   |   |   |   |   |-- uid___A002_X3c9295_X8c.ms.split/
|   |   |   |   |-- qa/
|   |   |   |   |   |-- X3dc0e7_X528.checklist.txt
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528__qa2_part1.png
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528__textfile.txt
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__qa2_part1.png
|   |   |   |   |   |-- X3c9295_X8c.checklist.txt
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528__qa2_part3.png
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528__qa2_part2.png
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__qa2_part2.png
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__qa2_part3.png
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__textfile.txt
|   |   |   |   |-- script/
|   |   |   |   |   |-- scriptForImaging.py
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528.ms.scriptForCalibration.py
|   |   |   |   |   |-- uid___A002_X3c9295_X8c.ms.scriptForCalibration.py
|   |   |   |   |   |-- scriptForCalibration.py
|   |   |   |   |   |-- scriptForAprioriCalibration.py
|   |   |   |   |   |-- scriptForFluxCalibration.py
|   |   |   |   |-- log/
|   |   |   |   |   |-- ipython.log
|   |   |   |   |   |-- casapy-2012-05-03T115433.log
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__casapy-20120502-102144.log
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__ipython.log
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528__ipython-20120430-142604.log
|   |   |   |   |   |-- uid___A002_X3c9295_X8c__ipython-20120502-102151.log
|   |   |   |   |-- product/
|   |   |   |   |   |-- calibrated_all_setup3_b6.clean.fits
|   |   |   |   |-- calibrated/
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528.ms.split.cal/
|   |   |   |   |   |-- uid___A002_X3c9295_X8c.ms.split.cal/
|   |   |   |   |-- calibration/
|   |   |   |   |   |-- uid___A002_X3c9295_X8c.calibration.plots/
|   |   |   |   |   |-- uid___A002_X3c9295_X8c.calibration/
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528.calibration/
|   |   |   |   |   |-- uid___A002_X3dc0e7_X528.calibration.plots/

Then

QA_Packager(origpath='/scratch04/arcproc/project229/IRC10216_setup4_b6_run_x2',readme='./README.header.txt',
packpath='./2011.0.00229.S',append='member',mode='fake')

|-- 2011.0.00229.S_setup3_b6/
|   |-- sg_ouss_id/
|   |   |-- group_ouss_id/
|   |   |   |-- member_ouss_id/
|   |   |   |-- member_ouss_id2/

Acknowledgements

-- MartinZwaan - 20 May 2012