Welcome to YaadaWiki on Tue 20 of Oct, 2020 [05:42 UTC]
phplayers are not available on this site
Toggle  Wiki
Admin Menu
Online users
TikiWiki Assistant
Thank you for installing TikiWiki!
Click the :: options in the Menu for more options. Please, also see TikiMovies for more setup details.

History: DataImport

Preview of version: 2

Instructions for importing data to YAADA v2.10

All the input data used in YAADA are in formatted text files. Together these are the 'raw' data. These files have the extensions

SEF - particle data collected in 'fast scatter' mode SEM - missed particle data SET - hit particle data PKL - peak list of hit particle spectra INST - instrument operating conditions

SEF, SEM, and SET files are created by the TSI data acquisition software. SEF files are usually not present since these are only created in 'fast scatter' mode. PKL files are created from the aerosol mass spectral data (AMZ files) using the TSI MS-Control software; instructions to create PKL files are in an appendix in the TSI manual.

INST files describe the instrument conditions, and you need to make this text file yourself. There is an example in the doc directory. The lines in the INST file are the text fields are for your use to keep track of the experiment, instrument conditions, etc, so you can write what you want; YAADA only needs that some of these not include any spaces (described in the documentation). The InstCode? is a 3 upper case letter code (e.g. XXX) that you choose. This is only important if you work with more than one ATOFMS. The BusyTimeParam? and DaCalibParam? need to be changed for your instrument, if you want to get correct results. When data are imported DaCalibParam? is used to convert TOF time to Da, you need to put the results from the calibrations that you've done into these parameters. You don't need BusyTimeParam? to be correct initially. Another critical parameter in INST is the Da calibration function name. This has to match the DaCalibParam?.

Raw data files (SEF, SEM, SET, PKL, and INST) should be stored in the c:\data\project\raw director. All the files in this directory and its subdirectories will be digested and imported into the YAADA database. Raw data files can be organized into subdirectories for convenience; for example by day with subdirectories named like c:\data\project\raw\20080112, or by particle size calibration.

Raw data directories can contain one instrument file for the entire directory, or one instrument file for each PKL file. If there is one instrument file in a directory, these data are copied to every PK2 file and the base file name is arbitrary. If there one instrument file for each PKL, the base file name must match the PKL base file name.

I prefer to keep my files in a home directory like c:\Users\jallen1 (this is similar to where unix and Vista put user files). This makes working on multiple projects and multiple databases convenient. You could use the default directories, e.g. C:\Documents and Settings\jallen1\My Documents. Following unix, I'll abbreviate the home directory '~'.

For each project or dataset make a separate subdirectory from the home directory, ~/project. Copy these files from the YAADA directory to ~/project: init.m, copyright.m license.txt opendb.m startup.m. Then create ~/project/matlab for your project-specific Matlab programs. You can also create ~/project/plot and subdirectories to keep your results organized. There is some overlap here between the data/project/plot and ~/project/plot directories; I use the former for generic plot of the complete dataset and the latter for research project specific plots.


Legend: v=view, s=source
Date User IpComment Version Action
Wed 20 of Aug, 2008 [14:58 UTC] admin65.96.173.122  3
 v  s
Sat 09 of Aug, 2008 [20:48 UTC] admin65.96.173.122  2  v  s  
Sat 09 of Aug, 2008 [20:47 UTC] admin65.96.173.122  1  v  s  

[ register | I forgot my password ]
Powered by TikiWiki the ultimate CMS engine.
RSS Wiki