1 / 10

LPVEx Data Management System

Efficiently store and manage LPVEx experiment data and modeling output in a new server at CSU. Secure FTP transfer for datasets. Guidelines for file naming convention provided.

andrewbiddle
Download Presentation

LPVEx Data Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LPVEx Website LPVEx 2010

  2. LPVEx 2010

  3. LPVEx 2010

  4. LPVEx 2010

  5. LPVEx 2010

  6. LPVEx 2010

  7. LPVEx 2010

  8. LPVEx 2010

  9. General Info • Where possible we would like to archive all data collected during the experiment, associated modeling output, and datasets resulting from post-experiment investigations on a new 2 TB server at CSU • FTP transfer is encouraged for smaller datasets. Here’s the tentative plan: • Create a LPVEx web account • Check the Instrument PI checkbox • Enter any instruments you wish to be associated with • Once your account is approved, you will also gain access to the LPVEx server for uploading data • The username and password to FTP into the LPVEx server will be the same as the website account • Once logged in, upload all data to the directory called dat/ in your home directory that will hold all of your uploaded data • A script on the server will figure out where your data should go on the server for the public to download it

  10. File Naming Convention • For the script to work properly, it would be nice to have a naming convention in place. We can probably accommodate variations but it would be nice to have the following information in the file names: • [obs]: Refers to the type of observation. Where Gnd=Ground, Air=Aircraft, Shp=Ship and Sat=Satellite. • [sub-obs]: Refers to the name of the specific site in the event of ground observations • [instrument]: Is the name of the instrument. • [YYMMDDhhmmss]: This is the date/timestamp when the data was collected. YY=year, MM=month, DD=day, hh=hour, mm=minute, ss=seconds • [Misc]: Refers to any other information you want to be included in the file name. • Example: Gnd.Emasalo.mrr.101001060000_V001.R001.dat • When the script reads this file name, it would know that the file is from the Emasalo Ground Site and contains MRR data collected on October 1st, 2010 at 0600. [obs].[sub-obs].[instrument ].[YYMMDDhhmmss]_[Misc].dat Alternatively we could provide space for each PI to indicate their preferred naming convention through the website and manually modify the script but this would obviously involve more work.

More Related