Dataset: Aerosol particle concentrations (OPS TSI3330) measured at Monte Baldo (Italy) during the DECIPHER campaign and the TEAMx programme in summer 2025, raw data, University of Basel

1. Short description of dataset and instrument The dataset consists of raw data files obtained from an Optical Particle Sizer (OPS, TSI model 3330) operated during the DECIPHER campaign (https://sites.google.com/unitn.it/decipherproject/home-page) at Monte Baldo (Italy) and as part of the TEAMx programme (https://www.teamx-programme.org/) in summer 2025. The OPS sizes and quantifies aerosol particles based on light scattering from single particles using a laser beam and photo detector. The instrument manual is available at: https://www.kenelec.com.au/wp-content/uploads/2016/06/TSI_3330_Opticle_Particle_Sizer_Manual.pdf 1.2 Specifications as detailed in the instrument manual Instrument specifications are listed in Appendix A (page A-1 – A-2) of the instrument manual. They include (incomplete excerpt): Particle Size Range 0.3 µm to 10 µm Size Resolution 5% @ 0.5 µm per ISO 21501-1 Zero Count < 1 count per 1 minute Flow Rate Sample Flow of 1.0 L min-1 Sheath Flow of 1.0 L min-1 Flow Accuracy Sample Flow of 1.0 L min-1 ± 5% accuracy internal flow controlled Time Constant 1 second 2. Measurement Strategy during the campaign 2.1 Description of data collection Continuous measurements were conducted 2 m a. g. l. at 10-min intervals. The number concentration of aerosol particles between 0.3 µm and 10 µm was assessed in 16 size bins (Bin 1 to Bin 16). Aerosol particles > 10 µm were quantified (Bin 17), but not sized. The bin cut points (µm) were: Bin 1: 0.3 Bin 2: 0.4 Bin 3: 0.5 Bin 4: 0.6 Bin 5: 0.7 Bin 6: 0.8 Bin 7: 1.0 Bin 8: 1.2 Bin 9: 1.5 Bin 10: 2.0 Bin 11: 2.5 Bin 12: 3.0 Bin 13: 4.0 Bin 14: 5.0 Bin 15: 6.0 Bin 16: 8.0 Bin 17: 10.0 2.2 Time period covered by the data 2025-06-24 to 2025-07-08 2.3 Physical location of the instrument Mast at mountain slope site between Malga Crocetta Valfredda and mountain crest; latitude 45° 39’ 57.6’’ N; longitude 10° 49’ 19.0’’ E; altitude 1390 m a. s. l.; inlet 2 m a. g. l. 3. Data processing 3.1 Description of derived parameters and processing techniques used The dataset comprises unprocessed, raw data files. 3.2 Description of quality assurance and control procedures No quality control was applied to the dataset. Data files are provided in their original format and form as produced by the instrument. 4. Data Format 4.1 Data file structure .csv files with metadata, zipped. One file consists of measurements obtained during up to 12 hours of continuous instrument operation. 4.2 File naming convention YYYY_MM_DD-HH_MM_SS.csv [UTC] 4.3 List of relevant parameters and units Times are indicated in UTC. The sample interval was set to 10 min and particles quantified at a sample flow rate of 1.0 L min-1 for the 17 size bins indicated in section 2. Measurement values per bin refer to raw particle counts per sample interval. A detailed description of all parameters displayed in the data files can be found in Appendix B of the instrument manual. 5. Data Remarks 5.1 Software compatibility All software able to read and process .csv files. 6. Data Sharing Policy within DECIPHER 6.1 Data Types Two data types are envisioned, namely Raw Data and Processed Data. The submission of both data types is not mandatory. "Raw Data" consists of the dataset as measured by the sensor. Data manipulation by the curators must be kept to a minimum, i.e., converting the file format and including metadata. Curators must include the tag "Raw Data" in the title of the dataset to refer to this data type. "Processed Data" consists of the dataset after manipulation through a documented, literature-compliant procedure of data processing, including data cleaning, quality control, and averaging. The procedure must be documented in the dataset description page. Curators must include the tag "Processed Data" in the title of the dataset to refer to this data type. 6.2 Internal Use Datasets will be initially accessible only to the partners who contributed measurements on Monte Baldo. The agreement between partners for the usage of other’s datasets is to propose coauthorship to the respective owners. The requirements for public data use depend on the level of data processing, whether raw or processed: The use of "Raw Data" by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. For the first 6 months after the dataset's publication, co-authorship proposals must be made to the data owners. Beyond this initial period, co-authorship is no longer mandatory, but users are encouraged to offer it to the curators. The use of "Processed Data" by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. Users of the processed data must offer co-authorship to the data curators. 7. Data Sharing and Public Data Use within TEAMx Complying with the TEAMx data management plan: “Any use of TEAMx data products, during or after the embargo period, must include an acknowledgement (i.e., citation) of the source and the data provider. Data users must inform the respective data providers if a data product is to be shared with other parties via journal articles, presentations, and research proposals. If the data product constitutes a substantial part of the work, the data provider should be offered co-authorship and the opportunity to collaborate (both during and after the embargo period). In the case of co-authorship, an additional acknowledgement of the data provider is not required.” To comply with the TEAMx data management plan and the DECIPHER data sharing policy, the use of raw data by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. The following formula is recommended by TEAMx: The [description of the data product] was collected as part of the TEAMx programme and provided by [name of the data provider, institution of data provider]. [name of the data provider]’s contribution to TEAMx was funded by [name of the funding agency, information about grant]. The data are archived at [zenodo.org] and are accessible at [URL/DOI of data product].