skip to main content
US FlagAn official website of the United States government
dot gov icon
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
https lock icon
Secure .gov websites use HTTPS
A lock ( lock ) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.


Title: GRITCLEAN Code and Files -- Part 1
This dataset contains a compressed folder of the data and MATLAB scripts used produce relevant figures and candidates for GRITCLEAN: A glitch veto scheme for Gravitational wave data as presented in https://arxiv.org/abs/2401.15237  The codes in this dataset include: A PSO-based matched filtering search pipeline which can be run on either the positive or the negative chirp time space. A standalone MATLAB script called GRITCLEAN.m which can run the GRITCLEAN hierarchical vetoes on a set of positive and negative chirp time space estimated parameters.  A plotting script to generate relevant figures. The files in this dataset include: GVSsegPSDtrainidxs.mat, a binary MATLAB file containing training indices for all segments from which the Power Spectral Densities (PSDs) are estimated, this is done via the scripts provided, namely, getsegPSD.m and createPSD.m. A sample HDF5 file used (H-H1_GWOSC_O3a_4KHZ_R1-1243394048-4096.hdf5) JSON files containing information about the data segments and the strain data files from which they originate from.  Text files containing the parameters estimated by the PSO-based pipeline across the positive and negative chirp time space runs.  Detailed instructions on dependencies, downloading the dataset and running the codes are given in a README.txt file included with this dataset. The user is recommended to go through this file first. The scripts enclosed have dependencies on JSONLAB , the Parallel Computing Toolbox and Signal Processing Toolbox for MATLAB, along with additional scripts provided in GitHub repositories  Accelerated-Network-Analysis  and SDMBIGDAT19 . Instructions on installing these dependencies are provided in README.txt. All codes have been developed and tested on MATLAB R2022 and R2023.  more » « less
Award ID(s):
2207935
PAR ID:
10508016
Author(s) / Creator(s):
Publisher / Repository:
Zenodo
Date Published:
Subject(s) / Keyword(s):
Gravitational Waves Particle Swarm Optimization matched-filtering glitch
Format(s):
Medium: X
Location:
Web
Sponsoring Org:
National Science Foundation
More Like this
  1. This dataset contains the data used in the paper (arXiv:2301.02398) on the estimation and subtraction of glitches in gravitational wave data using an adaptive spline fitting method called SHAPES . Each .zip file corresponds to one of the glitches considered in the paper. The name of the class to which the glitch belongs (e.g., "Blip") is included in the name of the corresponding .zip file (e.g., BLIP_SHAPESRun_20221229T125928.zip). When uncompressed, each .zip file expands to a folder containing the following. An HDF5 file containing the Whitened gravitational wave (GW) strain data in which the glitch appeared. The data has been whitened using a proprietary code. The original (unwhitened) strain data file is available from gwosc.org. The name of the original data file is the part preceding the token '__dtrndWhtnBndpss' in the name of the file.A JSON file containing information pertinent to the glitch that was analyzed (e.g., start and stop indices in the whitened data time series).A set of .mat  files containing segmented estimates of the glitch as described in the paper.  A MATLAB script, plotglitch.m, has been provided that plots, for a given glitch folder name, the data segment that was analyzed in the paper. Another script, plotshapesestimate.m, plots the estimated glitch. These scripts require the JSONLab package. 
    more » « less
  2. This dataset contains raw data, processed data, and the codes used for data processing in our manuscript from our Fourier-transform infrared (FTIR) spectroscopy, Nuclear magnetic resonance (NMR), Raman spectroscopy, and X-ray diffraction (XRD) experiments. The data and codes for the fits of our unpolarized Raman spectra to polypeptide spectra is also included. The following explains the folder structure of the data provided in this dataset, which is also explained in the file ReadMe.txt. Browsing the data in Tree view is recommended. Folder contents Codes Raman Data Processing: The MATLAB script file RamanDecomposition.m contains the code to decompose the sub-peaks across different polarized Raman spectra (XX, XZ, ZX, ZZ, and YY), considering a set of pre-determined restrictions. The helper functions used in RamanDecomposition.m are included in the Helpers folder. RamanDecomposition.pdf is a PDF printout of the MATLAB code and output. P Value Simulation: 31_helix.ipynb and a_helix.ipynb: These two Jupyter Notebook files contain the intrinsic P value simulation for the 31-helix and alpha-helix structures. The simulation results were used to prepare Supplementary Table 4. See more details in the comments contained. Vector.py, Atom.py, Amino.py, and Helpers.py: These python files contains the class definitions used in 31_helix.ipynb and a_helix.ipynb. See more details in the comments contained. FTIR FTIR Raw Transmission.opj: This Origin data file contains the raw transmission data measured on single silk strand and used for FTIR spectra analysis. FTIR Deconvoluted Oscillators.opj: This Origin data file was generated from the data contained in the previous file using W-VASE software from J. A. Woollam, Inc. FTIR Unpolarized MultiStrand Raw Transmission.opj: This Origin data file contains the raw transmission data measured on multiple silk strands. The datasets contained in the first two files above were used to plot Figure 2a-b and the FTIR data points in Figure 4a, and Supplementary Figure 6. The datasets contained in the third file above were used to plot Supplementary Figure 3a. The datasets contained in the first two files above were used to plot Figure 2a-b, FTIR data points in Figure 4a, and Supplementary Figure 6. NMR Raw data files of the 13C MAS NMR spectra: ascii-spec_CP.txt: cross-polarized spectrum ascii-spec_DP.txt: direct-polarized spectrum Data is in ASCII format (comma separated values) using the following columns: Data point number Intensity Frequency [Hz] Frequency [ppm] Polypeptide Spectrum Fits MATLAB scripts (.m files) and Helpers: The MATLAB script file Raman_Fitting_Process_Part_1.m and Raman_Fitting_Process_Part_2.m contains the step-by-step instructions to perform the fitting process of our calculated unpolarized Raman spectrum, using digitized model polypeptide Raman spectra. The Helper folder contains two helper functions used by the above scripts. See the scripts for further instruction and information. Data aPA.csv, bPA.csv, GlyI.csv, GlyII.csv files: These csv files contain the digitized Raman spectra of poly-alanine, beta-alanine, poly-glycine-I, and poly-glycine-II. Raman_Exp_Data.mat: This MATLAB data file contains the processed, polarized Raman spectra obtained from our experiments. Variable freq is the wavenumber information of each collected spectrum. The variables xx, yy, zz, xz, zx represent the polarized Raman spectra collected. These variables are used to calculate the unpolarized Raman spectrum in Raman_Fitting_Process_Part_2.m. See the scripts for further instruction and information. Raman Raman Raw Data.mat: This MATLAB data file contains all the raw data used for Raman spectra analysis. All variables are of MATLAB structure data type. Each variable has fields called Freq and Raw, with Freq contains the wavenumber information of the measured spectra and Raw contains 5 measured Raman signal strengths. Variable XX, XZ, ZX, ZZ, and YY were used to plot and sub-peak analysis for Figure 2c-d, Raman data points in Figure 4a, Figure 5b, Supplementary Figure 2, and Supplementary Figure 7. Variable WideRange was used to plot and identify the peaks for Supplementary Figure 3b. X-Ray X-Ray.mat: This MATLAB data file contains the raw X-ray data used for the diffraction analysis in Supplementary Figure 5. 
    more » « less
  3. Raw data of optical microscopy, scanning electron microscopy (SEM), atomic force microscopy (AFM), and diameter measurements of the exfoliated and self-assembled nanofibrils for our manuscript. File Formats AFM raw data is provided in Gwyddion format, which can be viewed using the Gwyddion AFM viewer, which has been released under the GNU public software licence GPLv3 and can be downloaded free of charge at http://gwyddion.net/ Optical microscopy data is provided in JPEG format SEM raw data is provided in TIFF format Data analysis codes were written in MATLAB (https://www.mathworks.com/products/matlab) and stored as *.m files Data analysis results were stored as MATLAB multidimensional arrays (MATLAB “struct” data format, *.mat files) Data (Folder Structure) The data in the dataverse is best viewed in Tree mode. ReadMe.md This description in Markdown format. Figure 2 - Microscopy Raw Data Figure 2 - panel a.jpg (7.2 MB) Optical micrograph (JPEG format) Figure 2 - panel b.jpg (6.1 MB) Optical micrograph (JPEG format) Figure 2 - panel c f.tif (1.2 MB) SEM raw data (TIFF format) Figure 2 - panel d.tif (1.2 MB) SEM raw data (TIFF format) Figure 2 - panel e - Exfoliated Fibrils.gwy (32.0 MB) AFM raw data (Gwyddion format) Figure 3 - AFM Raw Data Figure 3 - Panel a - Exfoliated fibrils.gwy (81.5 MB) AFM raw data (Gwyddion format) Figure 3 - Panel c - Self-assembled fibrils.gwy (24.0 MB) AFM raw data (Gwyddion format) Figure 3 - Diameter Measurements Figure 3a and Figure 3c show the AFM images of exfoliated and self-assembled nanofibrils, respectively. However, due to the AFM tip-induced broadening of lateral dimensions of small features (such as nanofibrils), the diameters of nanofibrils are generally overestimated in AFM images. Hence, the diameters of the nanofibrils were estimated as the full width at half maximum (FWHM) value of line scans taken over nanofibrils perpendicular to their axial direction. Line profiles were taken at multiple locations using Gwyddion, and the raw data were stored in MATLAB struct files (lineProfileData_Exfoliated.mat and lineProfileData_Self-Assembled.mat). These data files can be directly imported into MATLAB and will appear as “DataExf” and “DataSA” in MATLAB workspace. For instance, “DataExf.x{i}” contains the x-axis data of i-th line profile, and “DataExf.y{i}” contains the y-axis data of i-th line profile. The MATLAB codes MainCode_Exf.m and MainCode_SA.m are used to fit Gaussian curves for each line profile and calculate the FWHM. The *.m files for functions gaussian.m and createFit.m must be in the same folder as the file for the main code. The main code generates figures for each line profile containing raw line profile, related Gaussian fit, and FWHM. These FWHM values are considered as the diameters of the fibrils and stored in variables called “Exf_Dia” and “SA_Dia”. Finally, these values are plotted in a histogram and calculate the statistics such as the mean and the standard deviation. Exfoliated createFit.m (1.1 KB) MATLAB code file (see above) gaussian.m (134 B) MATLAB code file (see above) lineProfileData_Exfoliated.mat (11.7 KB) Line profiles for exfoliated nanofibrils (MATLAB struct format) MainCode_Exf.m (1.8 KB) MATLAB code file (see above) Line profile raw data - Exfoliated Folder with all corresponding cross section raw data in ASCII format Self Assembled createFit.m (1.1 KB) MATLAB code file (see above) gaussian.m (134 B) MATLAB code file (see above) lineProfileData_Self-Assembled.mat (9.9 KB) Line profiles for self-assembled nanofibrils (MATLAB struct format) MainCode_SA.m (1.8 KB) MATLAB code file (see above) Line profile raw data - SelfAssembled Folder with all corresponding cross section raw data in ASCII format Figure 4 - AFM Raw Data Figure 4 - Panal a.gwy (73.4 MB) AFM raw data (Gwyddion format) Figure 4 - Panel e.gwy (42.0 MB) AFM raw data (Gwyddion format) 
    more » « less
  4. This dataset is associated with a manuscript on river plumes and idealized coastal corners with first author Michael M. Whitney. The dataset includes source code, compilation files, and routines to generate input files for the Regional Ocean Modeling System (ROMS) runs used in this study. ROMS output files in NetCDF format are generated by executing the compiled ROMS code with the input files. The dataset also includes MATLAB routines and datafiles for the analysis of model results and generation of figures in the manuscript. The following zip files are included: ROMS_v783_Yan_code.zip [ROMS source code branch used in this study] coastalcorner_ROMS_compilation.zip [files to compile ROMS source code and run-specific Fortran-90 built code] coastalcorner_ROMS_input_generate_MATLAB.zip [ROMS ASCII input file and MATLAB routines to generate ROMS NetCDF input files for runs] coastalcorner_MATLAB_output_analysis.zip [MATLAB data files with selected ROMS output fields and custom analysis routines and datafiles in MATLAB formats used in this study] coastalcorner_MATLAB_figures.zip [custom MATLAB routine for manuscript figure generation and MATLAB data files with all data fields included in figures] coastalcorner_tif_figures.zip [TIF image files of each figure in manuscript] 
    more » « less
  5. Atomic force microscopy (AFM) image raw data, force spectroscopy raw data, data analysis/data plotting, and force modeling. File Formats The raw files of the AFM imaging scans of the colloidal probe surface are provided in NT-MDTs proprietary .mdt file format, which can be opened using the Gwyddion software package. Gwyddion has been released under the GNU public software license GPLv3 and can be downloaded free of charge at http://gwyddion.net/. The processed image files are included in Gwyddions .gwy file format. Force spectroscopy raw files are also provided in .mdt file format, which can be opened using NT-MDTs NOVA Px software (we used 3.2.5 rev. 10881). All the force data were converted to ASCII files (*.txt) using the NOVA Px software to also provide them in human readable form with this data set. The MATLAB codes used for force curve processing and data analysis are given as *.m files and can be opened by MATLAB (https://www.mathworks.com/products/matlab) or by a text editor. The raw and processed force curve data and other values used for data processing are stored in binary form in *.mat MATLAB data files, which can be opened by MATLAB. Organized by figure, all the raw and processed force curve data are given in Excel worksheets (*.xlsx), one per probe/substrate combination. Data (Folder Structure) The data in the dataverse is best viewed in Tree mode. Codes for Force Curve Processing The three MATLAB codes used for force curve processing are contained in this folder. The text file Read me.txt provides all the instructions to process raw force data using these three MATLAB codes. Figure 3B, 3C – AFM images The raw (.mdt) and processed (.gwy) AFM images of the colloidal probe before and after coating with graphene oxide (GO) are contained in this folder. Figure 4 – Force Curve GO The raw data of the force curve shown in Figure 4 and the substrate force curve data (used to find inverse optical lever sensitivity) are given as .mdt files and were exported as ASCII files given in the same folder. The raw and processed force curve data are also given in the variables_GO_Tip 18.mat and GO_Tip 18.xlsx files. The force curve processing codes and instructions can be found in the Codes for Force Curve Processing folder, as mentioned above. Figure 5A – Force–Displacement Curves GO, rGO1, rGO10 All the raw data of the force curves (GO, rGO1, rGO10) shown in Figure 5A and the corresponding substrate force curve data (used to find inverse optical lever sensitivity) are given as .mdt files and were exported as ASCII files given in the same folder. The raw and processed force curve data are also given in *.mat and *.xlsx files. Figure 5B, 5C – Averages of Force and Displacement for Snap-On and Pull-Off Events All the raw data of the force curves (GO, rGO1, rGO10) for all the probes and corresponding substrate force curve data are given as .mdt files and were exported as ASCII files given in this folder. The raw and processed force curve data are also provided in *.mat and *.xlsx files. The snap-on force, snap-on displacement, and pull-off displacement values were obtained from each force curve and averaged as in Code_Figure5B_5C.m. The same code was used for plotting the average values. Figure 6A – Force–Distance Curves GO, rGO1, rGO10 The raw data provided in Figure 5A – Force Displacement Curves GO, rGO1, rGO10 folder were processed into force-vs-distance curves. The raw and processed force curve data are also given in *.mat and *.xlsx files. Figure 6B – Average Snap-On and Pull-Off Distances The same raw data provided in Figure 5B, 5C – Average Snap on Force, Displacement, Pull off Displacement folder were processed into force-vs-distance curves. The raw and processed force curve data of GO, rGO1, rGO10 of all the probes are also given in *.mat and *.xlsx files. The snap-on distance and pull-off distance values were obtained from each force curve and averaged as in Code_Figure6B.m. The code used for plotting is also given in the same text file. Figure 6C – Contact Angles Advancing and receding contact angles were calculated using each processed force-vs-distance curve and averaged according to the reduction time. The obtained values and the code used to plot is given in Code_Figure6C.m. Figure 9A – Force Curve Repetition The raw data of all five force curves and the substrate force curve data are given as .mdt files and were exported as ASCII files given in the same folder. The raw and processed force curve data are also given in *.mat and *.xlsx files. Figure 9B – Repulsive Force Comparison The data of the zoomed-in region of Figure 9A was plotted as Experimental curve. Initial baseline correction was done using the MATLAB code bc.m, and the procedure is given in the Read Me.txt text file. All the raw and processed data are given in rGO10_Tip19_Trial1.xlsx and variables_rGO10_Tip 19.mat files. The MATLAB code used to model other forces and plot all the curves in Figure 9B is given in Exp_vdW_EDL.m. 
    more » « less