MH0386 commited on
Commit
1176eb1
·
verified ·
1 Parent(s): dc535ad

Upload folder using huggingface_hub

Browse files
Files changed (3) hide show
  1. .github/workflows/data.yml +30 -0
  2. .github/workflows/hf.yaml +22 -0
  3. README.md +24 -27
.github/workflows/data.yml ADDED
@@ -0,0 +1,30 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ name: CI
2
+ on:
3
+ push:
4
+ branches: [ "main" ]
5
+ workflow_dispatch:
6
+ jobs:
7
+ build:
8
+ runs-on: ubuntu-latest
9
+ steps:
10
+ - uses: actions/checkout@v4
11
+ - name: Download Data
12
+ run: |
13
+ wget --progress=dot:giga https://wufs.wustl.edu/SpaceApps/data/space_apps_2024_seismic_detection.zip
14
+ unzip space_apps_2024_seismic_detection
15
+ cp -R space_apps_2024_seismic_detection/* ../
16
+ pwd
17
+ - run: |
18
+ pwd
19
+ ls -a
20
+ - run: |
21
+ rm space_apps_2024_seismic_detection.zip
22
+ ls -a
23
+ - name: Upload Data
24
+ run: |
25
+ git config --global user.name "Mohamed Hisham Abdelzaher"
26
+ git config --global user.email "[email protected]"
27
+ git add .
28
+ git commit -m "init"
29
+ git pull -v
30
+ git push -v
.github/workflows/hf.yaml ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ name: Upload to HuggingFace
2
+ on:
3
+ push:
4
+ branches: [ "main" ]
5
+ workflow_dispatch:
6
+ jobs:
7
+ build:
8
+ runs-on: ubuntu-latest
9
+ steps:
10
+ - uses: actions/checkout@v4
11
+ - name: Login to HuggingFace Hub
12
+ uses: osbm/[email protected]
13
+ with:
14
+ username: MH0386
15
+ key: ${{ secrets.HF_KEY }}
16
+ add_to_git_credentials: true
17
+ - name: Enable hf_transfer
18
+ run: pip install huggingface_hub[hf_transfer]
19
+ - name: Check if logged in
20
+ run: huggingface-cli whoami
21
+ - name: Upload
22
+ run: huggingface-cli upload MH0386/nasa_space_apps_2024_seismic_detection . --repo-type dataset
README.md CHANGED
@@ -1,27 +1,24 @@
1
- ---
2
- pretty_name: Seismic Detection across the Solar System
3
- ---
4
- # Welcome, Space Apps challengers, to “Seismic Detection across the Solar System”.
5
-
6
- Today, we challenge YOU to parse through seismic data collected on the Moon and Mars and figure out how to detect moonquakes and marsquakes!
7
- To get you started on the data, we present to you a training set containing the following:
8
-
9
- 1. A catalog of quakes identified in the data
10
- 2. Seismic data collected by the Apollo (one day segments) or InSight (one hour segments) missions in miniseed and CSV format.
11
- 3. Plots of the trace and spectrogram for each day a quake has been identified.
12
-
13
- Using these tools, your task is to come up with an algorithm to identify these signals (using the catalog as a benchmark) and then
14
- apply your algorithm to the seismic data in the "test" folder (Apollo 12, 15, and 16 for the Moon and other InSight events for Mars).
15
-
16
- Each trace included in the test folder has a quake in it, there are no empty traces.
17
-
18
- This main folder also has a Jupyter notebook that will help you get started on the data.
19
-
20
- ## **IMPORTANT**
21
-
22
- Please make sure that your output catalog has at least the following headers:
23
- filename
24
- time_abs(%Y-%m-%dT%H:%M:%S.%f) or time_rel(sec)
25
- If not, your output catalog may not be scored!!
26
-
27
- Good luck!!! If you have any questions, our team leaders will be around to help during the hackathon weekend!
 
1
+ # Welcome, Space Apps challengers, to “Seismic Detection across the Solar System”.
2
+
3
+ Today, we challenge YOU to parse through seismic data collected on the Moon and Mars and figure out how to detect moonquakes and marsquakes!
4
+ To get you started on the data, we present to you a training set containing the following:
5
+
6
+ 1. A catalog of quakes identified in the data
7
+ 2. Seismic data collected by the Apollo (one day segments) or InSight (one hour segments) missions in miniseed and CSV format.
8
+ 3. Plots of the trace and spectrogram for each day a quake has been identified.
9
+
10
+ Using these tools, your task is to come up with an algorithm to identify these signals (using the catalog as a benchmark) and then
11
+ apply your algorithm to the seismic data in the "test" folder (Apollo 12, 15, and 16 for the Moon and other InSight events for Mars).
12
+
13
+ Each trace included in the test folder has a quake in it, there are no empty traces.
14
+
15
+ This main folder also has a Jupyter notebook that will help you get started on the data.
16
+
17
+ ## **IMPORTANT**
18
+
19
+ Please make sure that your output catalog has at least the following headers:
20
+ filename
21
+ time_abs(%Y-%m-%dT%H:%M:%S.%f) or time_rel(sec)
22
+ If not, your output catalog may not be scored!!
23
+
24
+ Good luck!!! If you have any questions, our team leaders will be around to help during the hackathon weekend!