Replies: 10 comments 24 replies
-
|
Hi @madlazim, The actual error is a few lines above: Which means that the "passed" waveform data were not enough concerning your case. You could alter a numerous cases, that are:
I would suggest the 3rd + 4th option. Concerning the 3rd case, you could modify the Distance rule like this, in order to increase the possible data: Concerning the 4th case, append another FDSNWS that you know that has data around the selected location. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Hi @nikosT
Best wishes, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @madlazim, The config file is wrong. Firstly, you need to specify FDSN Web Services for Inventory and Streams. - [FDSNWS, https://www.fdsn.org/networks/detail/IA/, null]
- [FDSNWS, https://service.iris.edu/fdsnws/event/1/, null]Now, if for example you want the IA network, check at the fdsn.org webpage the respective FDSNWS that provides the data, i.e. http://geofon.gfz-potsdam.de, which you already included. I suggest to read more on how FDSNWS work. Secondly, the Gisola configuration currently supports only one FDSNWS-event. So you have to choose only one FDSNWS-event to monitor. Event: # only ONE Host is possible
Host: http://103.242.124.83:8080/fdsnws
Host: https://geofon.gfz-potsdam.de
Host: https://service.iris.edu/fdsnws/event/1/If you want more than one host, it is possible, by setting another cron-job with a different configuration file. |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
@DianKusumawati I can confirm this error. let me check it |
Beta Was this translation helpful? Give feedback.
-
|
@DianKusumawati This issue is solved here: Could you please confirm? Please, also read the issues that occurred, which may relate to your use cases. |
Beta Was this translation helpful? Give feedback.
-
|
We attempted to rerun and obtained the results below. ./gisola.py --event 11654205
|
Beta Was this translation helpful? Give feedback.
-
|
dear @DianKusumawati, probably there is an issue with the FDSNWS-dataselect service from IRIS. I also tried this event and the process stucked at the waveform retrieval phase. Would you mind choose a different Stream - Service in the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @nikosT |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nikosT
Many thanks for all your suggestions. Now, Gisola is working in my web like
this
http://jokotingkir.unesa.ac.id/2021/
However, it still run manual using command
./gisola.py --datetime-range 2021-01-01T00:00:00 2022-01-11T23:59:00
I think that my cron code has not worked yet???
Best regards,
Madlazim
…On Sun, Jan 9, 2022 at 4:25 PM Nikolaos Triantafyllis < ***@***.***> wrote:
Hi @madlazim <https://github.com/madlazim>,
The config file is wrong. Firstly, you need to specify FDSN Web Services
for Inventory and Streams.
The below URLs are not dataselect or station FDSNWS:
- [FDSNWS, https://www.fdsn.org/networks/detail/IA/, null]
- [FDSNWS, https://service.iris.edu/fdsnws/event/1/, null]
Now, if for example you want the IA network, check at the fdsn.org
webpage the respective FDSNWS that provides the data, i.e.
http://geofon.gfz-potsdam.de, which you already included.
I suggest to read more on how FDSNWS work.
Secondly, the Gisola configuration currently supports only one
FDSNWS-event. So you have to choose only one FDSNWS-event to monitor.
Event: # only ONE Host is possible
Host: http://103.242.124.83:8080/fdsnws
Host: https://geofon.gfz-potsdam.de
Host: https://service.iris.edu/fdsnws/event/1/
If you want more than one host, it is possible, by setting another
cron-job with a different configuration file.
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNFVDAWL6YBOTS76CG2FITUVFIADANCNFSM5LP3QZ7A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @madlazim, "# If not running interactively, don't do anything i) ;;*) return;;#esac " |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @DonaVIn,
Many thanks for your quick response. I will do it base on your suggestions.
Best regards,
Madlazim
…On Wed, Jan 12, 2022 at 2:32 AM Donavin97 ***@***.***> wrote:
Hi @madlazim <https://github.com/madlazim>,
Make sure that in your ~/.bashrc or ~/.bash_profile, comment out the
following lines:
"# If not running interactively, don't do anything
#case $- in
*i*) ;; *) return;;
#esac
"
This should resolve your crontab issues, the shell will run
noninteractively and thus your cron jobs will work.
I hope this helps.
Regards: Donavin.
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNFVDHQAIBGAWCAFRAHJADUVSATHANCNFSM5LP3QZ7A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It's my pleasure @madlazim, |
Beta Was this translation helpful? Give feedback.
-
|
You could also simply check if cron utility works by:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @DonaVIn,
Many thanks. I will give feedback soon if my cronjobs are working after
the fix I applied. I am still waiting new event.
Best regards,
…On Wed, Jan 12, 2022 at 2:10 PM Donavin97 ***@***.***> wrote:
It's my pleasure @madlazim <https://github.com/madlazim>,
If you have any questions, I'll be glad to try and help.
Also, please give feedback if your cronjobs are working after the fix you
applied.
Thanks and regards.
—
Reply to this email directly, view it on GitHub
<#12 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNFVDAPUARE52KSUWR76DTUVUSPPANCNFSM5LP3QZ7A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @nikos
I got output like this, after I typed in terminal: sudo service cron status,
(gisola) ***@***.***:~$ sudo service cron status
[sudo] password for madlazim:
● cron.service - Regular background program processing daemon
Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor
preset: ena
Active: active (running) since Fri 2021-12-24 11:20:25 WIB; 2 weeks 5
days ag
Docs: man:cron(8)
Main PID: 1079 (cron)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/cron.service
├─1079 /usr/sbin/cron -f
├─8861 /usr/sbin/CRON -f
├─8863 /bin/bash -c conda activate gisola; cd
/home/madlazim/gisola-m
└─9080 sleep 15
Jan 13 02:06:00 jokotingkir sSMTP[8859]: Sent mail for
***@***.*** (
Jan 13 02:06:00 jokotingkir CRON[8465]: pam_unix(cron:session): session
closed f
Jan 13 02:06:00 jokotingkir CRON[8861]: pam_unix(cron:session): session
opened f
Jan 13 02:06:00 jokotingkir CRON[8862]: pam_unix(cron:session): session
opened f
Jan 13 02:06:00 jokotingkir CRON[8863]: (madlazim) CMD (conda activate
gisola; c
Jan 13 02:06:00 jokotingkir CRON[8864]: (madlazim) CMD (conda activate
gisola; c
Jan 13 02:06:03 jokotingkir sSMTP[8989]: Creating SSL connection to host
Jan 13 02:06:04 jokotingkir sSMTP[8989]: SSL connection using
ECDHE_ECDSA_CHACHA
Jan 13 02:06:08 jokotingkir sSMTP[8989]: Sent mail for
***@***.*** (
Jan 13 02:06:08 jokotingkir CRON[8862]: pam_unix(cron:session): session
closed f
lines 1-22/22 (END)...skipping...
● cron.service - Regular background program processing daemon
Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor
preset: enabled)
Active: active (running) since Fri 2021-12-24 11:20:25 WIB; 2 weeks 5
days ago
Docs: man:cron(8)
Main PID: 1079 (cron)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/cron.service
├─1079 /usr/sbin/cron -f
├─8861 /usr/sbin/CRON -f
├─8863 /bin/bash -c conda activate gisola; cd
/home/madlazim/gisola-master/gisola/src; python3 ./gisola.py --real-time;
sleep 15; python3 ./gisola.py --real-time; sleep 15; python3 ./gisola.py
└─9080 sleep 15
Jan 13 02:06:00 jokotingkir sSMTP[8859]: Sent mail for
***@***.*** (221 2.0.0 closing connection s6sm404852pjg.22 -
gsmtp) uid=1000 username=madlazim outbytes=2592
Jan 13 02:06:00 jokotingkir CRON[8465]: pam_unix(cron:session): session
closed for user madlazim
Jan 13 02:06:00 jokotingkir CRON[8861]: pam_unix(cron:session): session
opened for user madlazim by (uid=0)
Jan 13 02:06:00 jokotingkir CRON[8862]: pam_unix(cron:session): session
opened for user madlazim by (uid=0)
Jan 13 02:06:00 jokotingkir CRON[8863]: (madlazim) CMD (conda activate
gisola; cd /home/madlazim/gisola-master/gisola/src; python3 ./gisola.py
--real-time; sleep 15; python3 ./gisola.py --real-time; sleep
Jan 13 02:06:00 jokotingkir CRON[8864]: (madlazim) CMD (conda activate
gisola; cd /home/madlazim/gisola-master/gisola/src; python3 ./gisola.py
--real-time;)
Jan 13 02:06:03 jokotingkir sSMTP[8989]: Creating SSL connection to host
Jan 13 02:06:04 jokotingkir sSMTP[8989]: SSL connection using
ECDHE_ECDSA_CHACHA20_POLY1305
Jan 13 02:06:08 jokotingkir sSMTP[8989]: Sent mail for
***@***.*** (221 2.0.0 closing connection l18sm355811pfu.63 -
gsmtp) uid=1000 username=madlazim outbytes=1227
Jan 13 02:06:08 jokotingkir CRON[8862]: pam_unix(cron:session): session
closed for user madlazim
What's the meaning?
Best regards,
Madlazim
…On Wed, Jan 12, 2022 at 10:09 PM Nikolaos Triantafyllis < ***@***.***> wrote:
You could also simply check if cron utility works by:
- typing in terminal: sudo service cron status and see if the service
is running
- and then by applying for example a text string in a file every 1 min
(remove it when done testing)
e.g. * * * * * echo "test" > /home/user/test
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHNFVDCZ4GS3MTSUHUVD4JTUVWKUBANCNFSM5LP3QZ7A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello @nikosT Now i tried to run it offline by downloading the data using obspy, and input it into gisola using sds service (event.xml, station.xml, and the archive that contains waveform). it successfully get the waveform but after 'cleaning and removing waveform' it shows 0 Trace(s) in Stream. Even after modify the Distance rule like this, it shows the same result. Here's the detail file that im using (event.xml , station.xml, archive folder, my config, and logs) Am I missing something or doing something wrong? Thanks a lot Best wishes, |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Dear @teukufaiz, I'm sorry for my late response. The problem here is that the exact cut data are provided in the inversion. The idea of SDS implementation is to provide a stream of data that later Gisola will cut them off, correct them, remove response etc. You know provide the corrected streams to the Gisola procedure and the time window is not enough (because they are already cut by Gisola on a previous run). I hope this is clean. What you can do is to download a bigger stream of data in the archive folder, e.g. with tools such as |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem, can you help me? |
Beta Was this translation helpful? Give feedback.
14 replies
-
|
that ? and change for how much?
|
Beta Was this translation helpful? Give feedback.
-
|
I changed, and it worked
|
Beta Was this translation helpful? Give feedback.
-
|
But it made an error... |
Beta Was this translation helpful? Give feedback.
-
|
Please, read the Wiki here: https://github.com/nikosT/Gisola/wiki/Installation |
Beta Was this translation helpful? Give feedback.
-
|
thx, @nikosT |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @nikosT,
I tried to run gisola test offline for Flores earthquake
./gisola.py -c ../test/config.yaml --event-xml ../test/benchmark/event.xml
I got "RuntimeError: No active exception to reraise" output. I attached the log file, config.yaml,
folder.zip
event.xml and inventory.xml in zip file. I hope you can give suggestions to solve the problem. Thanks a lot.
Best wishes,
Madlazim
Beta Was this translation helpful? Give feedback.
All reactions