Main Page: Difference between revisions
Jump to navigation
Jump to search
Daviddelene (talk | contribs) No edit summary |
|||
| Line 32: | Line 32: | ||
===Directories === | ===Directories === | ||
== ADPAA Software == | |||
* ${ADPAA_DIR}/bin * | * ${ADPAA_DIR}/bin * | ||
Location of the executable code for the binary (production) version of ADPAA | Location of the executable code for the binary (production) version of ADPAA | ||
| Line 44: | Line 45: | ||
* ${ADPAA_DIR}/src | * ${ADPAA_DIR}/src | ||
Location of all the source code for the current version. | Location of all the source code for the current version. | ||
== ADPAA Data File == | |||
* Follows Appendix B of Delene, D. J., Airborne Data Processing and Analysis Software Package, Earth Science Informatics, 4(1), 29-44, 2011, URL: http://dx.doi.org/10.1007/s12145-010-0061-4, DOI: 10.1007/s12145-010-0061-4. | |||
Note that when the priminary data acquistion sytem, such as a M300, is restarted during a flight the flight id is denoted as YYYYMMDD_?, where ? starts at 1 for flight on that day. Within the YYYYMMDD_? directory, there are directories with names of YYYYMMDD_HHMMSS that denote the start times of each files. A Combined directory is include within the YYYYMMDD_? that combines all data from all files acquired during the flight. | |||
==General Information== | ==General Information== | ||
Revision as of 14:46, 13 March 2024
Guides
Data Processing Guide (odt, pdf)
Programming Guide (odt, pdf)
Researcher Guidelines and Expectations (odt, pdf)
Tutorials
ADPAA (Uses Data from ADTAE Repository)
Checking Serial Output
Information for Developers
Coding Information
- ADPAA Debugging
- Adding Module to ADPAA
- Constants: Setting and Updating
- IDL Wrapper Code
- Installing, Updating, and Committing (Developers) ADPAA (INSTALL)
Data Acquisition
Developer's Conferences
- November 7, 2016
- June 26, 2017
- March 30, 2018/July 27, 2018
- January 25, 2019
- August 17, 2020
Directories
ADPAA Software
- ${ADPAA_DIR}/bin *
Location of the executable code for the binary (production) version of ADPAA
- ${ADPAA_DIR}/binary_distributions
Location of the compressed, tar files is for saved binary (production) version of ADPAA.
- ${ADPAA_DIR}/sav
Location of the complied IDL files.
- ${ADPAA_DIR}/share
Location of none code files used by the binary (production) version
- ${ADPAA_DIR}/source_distributions
Location of source code for archived version.
- ${ADPAA_DIR}/src
Location of all the source code for the current version.
ADPAA Data File
- Follows Appendix B of Delene, D. J., Airborne Data Processing and Analysis Software Package, Earth Science Informatics, 4(1), 29-44, 2011, URL: http://dx.doi.org/10.1007/s12145-010-0061-4, DOI: 10.1007/s12145-010-0061-4.
Note that when the priminary data acquistion sytem, such as a M300, is restarted during a flight the flight id is denoted as YYYYMMDD_?, where ? starts at 1 for flight on that day. Within the YYYYMMDD_? directory, there are directories with names of YYYYMMDD_HHMMSS that denote the start times of each files. A Combined directory is include within the YYYYMMDD_? that combines all data from all files acquired during the flight.
General Information
Documentation
Software Programs
Visualization
- Graphical Analysis Programs (cplot/cplot2, aplot)
Scripts
- ADPAA Processing Scripts (Project and Flight Processing, Analysis Tools)
- ADPAA Linkage Scripts to SODA2 (Two Dimensional Image Probe Processing)
Files
Analysis Files
Data File Extension Hierarchy (from bottom to top)=
- Exact (unmodified) Serial Stream Out Data Files - NASA/UND ASCII Format (*.log)
- Raw Data Files - NASA/UND ASCII Format (*.raw)
- Chronological files - NASA/UND ASCII Format (*.chron)
- Synchronous Files - NASA/UND ASCII Format (*.sync)
- Edited Files - NASA/UND ASCII Format (*.flt, *.edits)
- Clean Files - NASA/UND ASCII Format (*.clean)
- Summary (Science) Files - NASA/UND ASCII Format (*.sum)
Image Files
Input/Output of Data Files
- IDL Reading and Writing NASA/UND Formatted Data Files
- Python Reading and Writing NASA/UND Formatted Data Files
netCDF Files
Instrument Processing Streams
Gives the overall flow of the processing code per instrument and not step-by-step instructions as to how the data is processed. For step-by-step instructions, see the processing code itself.
Aeronautical Radio, Incorporated (ARINC) 429
Atmospheric Winds (AIMMS Probe)
Atmospheric Winds (M300 - Citation Research Aircraft)
Cloud Condensation Nuclei Counter (DMT)
- Aircraft Processing (M300 Data System)
- Surface Processing (Processing Data Directly from Instrument)
Cloud Condensation Nuclei Counter (UWyo)
- Lab Processing (Processing Data using M200 Data System)
- Lab Processing (Processing Data using A/D Board)