You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

 

beamline file-system
/gpfs/
├── local
├── current
    ├── raw
    ├── processed
    ├── shared
    └── scratch_bl
└── commissioning
    ├── raw
    ├── processed
    ├── shared
    ├── scratch_bl
 
/common/
├── p01
├── p02.1
├── p02.2
├── p03
├── p04
├── p05
├── p06
├── p07
├── p08
├── p09
├── p10
└── p11

 

Meaning of the different directories:

  • raw: 
    • for raw data
    • will be migrated into the core file-system
    • will be written to tape
    • will be shown in the Gamma-portal
  • processed
    • for meaningful processed data
    • will be migrated into the core file-system
    • will be written to tape
    • will be shown in the Gamma-portal
  • shared
    • for user specific macros, scripts, metadata, text-files,...
    • will be migrated into the core file-system
    • will be written to tape
    • will be shown in the Gamma-portal
  • scratch
    • meant for temporarily data or
    • for data where in advance it is not knows if it is meaningful or not. It can be written here and if its meaningful copied into 'processed' afterwards.
    • will not be migrated into the core file-system
core file-system
/asap3/
└── petra3
    └── gpfs
        ├── <beamline>
			├── <year>
                ├── <beamtime-ID>
                    ├── raw
                    ├── processed
                    ├── shared
                    └── scratch_cc
                └── <commissioning-ID>
                    ├── raw
                    ├── processed
                    ├── shared
                    └── scratch_cc
        └── common
            ├── p01
            ├── p02.1
            ├── p02.2
            ├── p03
            ├── p04
            ├── p05
            ├── p06
            ├── p07
            ├── p08
            ├── p09
            ├── p10
            └── p11

 

Description:

  • 'local': 
    • A 3TB local share of the beamline file-system which stays there independently of the beamtimes
    • It is managed by the beamlines themselves
    • There is no syncing across to the core file-system.
    • It serves as a local buffer.
    • Anybody on the beamline can read/write from/to it
    • Cannot be accessed from the core file-system
  • 'current':
    • Non-permanent share from the beamline file-system
    • It will appear when a beamtime is started and disappear if it is stopped
  • 'common':
    • mounted read-only in the beamline space, its world-readable meaning that all beamlines can read it
    • for documentation, macros, ... provided to the users by the beamline staff
    • if a user has to edit something, like a macro, he can copy it into 'shared'
    • can be changed from the core side by the beamline staff

 

 

  • No labels