Three Key Implementation Issues about DAS Imaging

[forgetsyl]

Your tool appears very intuitive and user-friendly. I'm currently conducting research on fiber-optic DAS vibration imaging, which is a fascinating technology. While using your software, I've encountered a few challenges:
Since fiber-optic vibration measurement is single-component, how should I configure parameters to achieve background noise imaging?
As I'm using .dat files recorded from other software, does this mean I need to create metadata files manually?
The daily stacking doesn't seem suitable for my scenario. Could your software offer flexible stacking time configurations? For my research, stacking intervals of 10 minutes or 1 hour might yield better results.

[rcabdia]

Dear forgetsyl, I like your ideas. The issue is that we design the software to deal with daily mseed file and thinking in seismic networks. You are totally right that it could be super nice to have a tool to manage DAS data. I found very interesting this tool https://xdas.readthedocs.io/en/latest/getting-started.html recently published in SSA here: https://pubs.geoscienceworld.org/ssa/srl/article-abstract/doi/10.1785/0220240366/654246/Xdas-A-Python-Framework-for-Distributed-Acoustic?redirectedFrom=fulltext

it would be great If you would like to programming a GUI for specific DAS tasks. Why not starting making a fork of current ISP master branch... don't you :-)

Regarding Metadata this is answered in issue #15

Thank you so much for using ISP, any contributions is vey welcome