ALPSS (A naL ysis of P hotonic Doppler velocimetry S ignals of S pall) was developed to automate the processing of PDV spall signals. This readme is a simple quick-start guide. For comprehensive documentation please refer to the repository wiki, which includes tutorials and instructions on how to import your own data. Any questions, suggestions, or bugs can be reported to jdiamo15@jhu.edu.
ALPSS may work well for your application if:
- Your signal is upshifted. This is a requirement.
- Your signal contains only a single velocity (like a typical spall shot).
- You already have a good idea of what the signal should look like and its expected frequency range.
- You expect to have a good signal-to-noise ratio.
- You have large amounts of relatively similar PDV signals.
ALPSS will not work well for your application if:
- Your signal is not upshifted. ALPSS will not work for a non-upshifted signal.
- Your signal contains multiple velocities (like a typical RMI shot).
- You are unsure of what the signal will look like and its expected frequency range.
- You expect to have poor or inconsistent signal-to-noise ratios.
If ALPSS is not suited for your application you can try SIRHEN, HiFiPDV, or QVPRO to name a few other programs.
Time-resolved uncertainty estimates have been added in v1.2.x. E.g. for any given point in time on the final velocity trace, the program will output the estimated velocity uncertainty. All other functions are essentially the same.
For use in published works, ALPSS can be cited from its original paper Automated Analysis of Photonic Doppler Velocimetry Spall Signals. J. dynamic behavior mater. (2024). https://doi.org/10.1007/s40870-024-00427-9 or with the following bibtex
@article{Diamond_automated_2024,
title = {Automated Analysis of Photonic Doppler Velocimetry Spall Signals},
ISSN = {2199-7454},
url = {http://dx.doi.org/10.1007/s40870-024-00427-9},
DOI = {10.1007/s40870-024-00427-9},
journal = {Journal of Dynamic Behavior of Materials},
publisher = {Springer Science and Business Media LLC},
author = {Diamond, J. M. and Ramesh, K. T.},
year = {2024},
month = jun
}
The repository for v1.2.5 can be cited using its DOI 10.5281/zenodo.14262459 or with the following bibtex.
@software{Diamond_ALPSS_2024,
author = {Diamond, Jacob M. and Ramesh, K.T.},
doi = {10.5281/zenodo.14262459},
month = {12},
title = {{ALPSS}},
url = {https://github.com/Jake-Diamond-9/ALPSS},
version = {1.2.5},
year = {2024}
}
For users that are familiar with python you can simply clone the repo, create a virtual environment, and install the requirements in the file requirements.txt. I recommend using VS Code because the Jupyter extension allows for nice in-line plotting. If you use a different IDE the figures may not format correctly out of the box depending on your IDE settings. In that case, you may have to make adjustments to your IDE settings or the matplotlib backend.
For users who are not familiar with Python, you can follow the steps below.
-
If you do not already have Python installed, begin by installing Miniconda.
-
Install VS Code.
-
Install the Python and Jupyter extensions in VS Code. Installation instructions can be found here.
-
Clone the ALPSS repo to the directory of your choice using the link https://github.com/Jake-Diamond-9/ALPSS.git. Instructions on cloning a repo can be found here.
-
Create a virtual environment and install the packages in requirements.txt by copying the following line into the terminal. Instructions on creating a virtual environment can be found here.
pip install -r requirements.txt
Open the file alpss_run.py. In the file there is a docstring that describes the input variables followed by the function alpss_main. No input parameters need to be changed from the original repository file to run the demo. The program will run the example file in the input_data folder.
In the alpss_run file there is a section that reads
# %%
from alpss_main import *
import os
Just above these lines there should be small font options that read "Run Cell | Run Below | Debug Cell" (see image below). Click the "Run Cell" button and the program will execute in an interactive notebook window. Note that this "Run Cell" option is only available through VS Code with the Jupyter extension, which is the recommended method.
Additional example data files are available through the paper by DiMarco et al. and can be accessed here.
Instructions on how to run your own data can be found in the repository wiki here.
- Move example_file.csv out of the input_data directory and into some other temporary directory of your choosing. It does not matter where this temporary directory is located on your machine.
- Open the alpss_auto_run.py file and click "Run Cell", similar to the example above. This will open an interactive notebook and the program will execute. The program is now waiting for a file to be moved into the directory that it is monitoring, the input_data directory.
- Click and drag example_file.csv out of your temporary directory and into the input_data directory. The program will automatically detect that a file has been added and run it through the ALPSS program.
GNU General Public License v3.0
The authors would like to acknowledge the following people for their many helpful conversations and advice, Chris DiMarco, Velat Killic, Debjoy Mallcik, Maggie Eminizer, David Elbert, Mark Foster, and Samuel Salander. Research was sponsored by the Army Research Laboratory and was accomplished under Cooperative Agreement Number W911NF-22-2-0014. The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of the Army Research Office or the U.S. Government. The U.S. Government is authorized to reproduce and distribute reprints for Government purposes notwithstanding any copyright notation herein.