Page History

Current Usage (as of 18 Mar 2021)

Isilon for data that needs more frequent access.

Cybershake

Cybershake 20+ Inputs Table

We will keep the latest CS data on Isilon

Note:

For a Cybershake version (eg. v20p9), we keep 3 items

• Sources: .csv and .info per fault and all realisations. All files packed into one tar file. v20p9_Sources.tar . (pre-v20p4, we kept all Srf and Stoch files)
• VMs: Only nzvm.cfg per fault. All files packed into one tar file. v20p9_VM_cfgs.tar
• BB: BB.bin files for all realisations packed into a tar file for each fault. (eg. AlpineF2K.tar)

An automated archive script can package all CS files and generate a Dropbox upload command that can be executed from NeSI login node (in "screen" session)

Dropbox has a maximum file size of 350Gb. The auto script will split the TAR files into multiple parts of 340Gb size. To join them (before extracting from TAR),

cat ${TARNAME}.parta* > ${TARNAME}.joined
tar xvf ${TARNAME}.joined

Empirical DB

Mostly on Isilon. Upload to Dropbox in progress

Old Staff Data

Nearline : /nesi/nearline/nesi00213/RunFolder/to_nearline/RunFolder.tar. ← Hoby, Asahn 

This page summarizes the archiving of some of the current CyberShake results.

v17p9

Aka the first batch of faults for the South Island. This version was archived on the RCC legacy storage in a very naive way. Every fault was saved in a single tar file. Thus every tar file has all the realizations, and for each realization we have a LF, HF and BB. This archived version needs to be cleaned to reduce the file size and have easier access to the waveforms.

v18p4

This is the batch that completes all the inland faults on the South Island. Note that both results need to be aggregated to have everything. To archive this version, we decided that we would zip the three components of the waveform for a given location into a single file (this means we will have as many .zip files as locations in the simulation). The way this was archived is very simple as it can be shown in the following block:

wdl16@dev01-quakecore:/rcc/home/projects/quakecore/cybershake/v18p4$ tree -L 4
.
├── IMs
│   └── database.db
├── metadata.json
└── Runs
    ├── AhuririR
    │   ├── AhuririR_HYP01-03_S1244
    │   │   ├── Acc
    │   │   ├── Vel
    │   │   └── xyts
    .....
    ├── Akatore
    │   ├── Akatore_HYP01-04_S1244
    │   │   ├── Acc
    │   │   ├── Vel
    │   │   └── xyts
    .....

This means that every fault has the realizations. For each realization we have an Acc, Vel and xyts directories, where I copied the zipped accelerations, zipped velocities and e3d files respectively. There is also a simple metadata.json file and the IM database for that particular version is archived. The metadata file has the following contents:

{
    CyberShakeVersion : 'v18p4',
    Path : '/rcc/home/projects/quakecore/cybershake/v18p4',
    AccPath : '/rcc/home/projects/quakecore/cybershake/v18p4/Runs/*/*/Acc',
    VelPath : '/rcc/home/projects/quakecore/cybershake/v18p4/Runs/*/*/Vel',
    HasXYTS : 'yes',
    XYTSPath ; '/rcc/home/projects/quakecore/cybershake/v18p4/Runs/*/*/xyts',
    WaveFormSize : '423GB',
    SizePlusXYTS : '475GB',
    WaveFormCompression : 'zip'
    IMDBSize : '8.2GB',
    FaultNumber : 107,
    Description : 'Rest of South Island faults. v17p9 + v18p4 are all the faults on the SI'
}

This file was generated manually, but it should be automatically generated by the archiving process.

v18p5

This version completes the NZ faults by adding the North Island faults. This is the next archiving to be done, and it will follow the same structure as v18p4.

TODO

• Add symbolic links to v18p4 to give the impression that it is actually v17p9 + more faults. The same will be needed for v18p5.

Future

...

...