PyVelest error
Opened this issue · 10 comments
Y5517lalalo commented
Hello
I am currently running PyVelest via python3.8. I've checked that the neqs matches the number of events in the select.out file, but I keep on getting the following error:
(Note: This data is from the Southern hemisphere)
+++ Enter Project Name: <Please use the name of velocity model you're using>
initial.mod
+++ Read VELEST input parameters ...
+++ Write VELEST control file ...
+++ Plotting data statistics ...
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
+++ Make synthetic velocity models ...
+++ Run VELEST ...
--- 50 synthetic model(s) found ...
--- Run for synthetic model: 1
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 2
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 3
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 4
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 5
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 6
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 7
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 8
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 9
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 10
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 11
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 12
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 13
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 14
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 15
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 16
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 17
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 18
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 19
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 20
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 21
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 22
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 23
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 24
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 25
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 26
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 27
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 28
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 29
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 30
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 31
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 32
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 33
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 34
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 35
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 36
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 37
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 38
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 39
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 40
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 41
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 42
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 43
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 44
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 45
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 46
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 47
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 48
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 49
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 50
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
+++ Analyse VELEST outputs ...
Traceback (most recent call last):
File "PyVelest.py", line 3142, in
start.analyse_velest_res()
File "PyVelest.py", line 774, in analyse_velest_res
self.sdep['P'][sm].append(p_dep)
NameError: name 'p_dep' is not defined
McBaboulek commented
Hii,
Check how the model is looking for in saeedsltm Document or in my. The next step is to write on the code the direction where the model is.
… On 8. Sep 2022, at 22:42, Y5517lalalo ***@***.***> wrote:
Hello
I am currently running PyVelest via python3.8. I've checked that the neqs matches the number of events in the select.out file, but I keep on getting the following error:
(Note: This data is from the Southern hemisphere)
+++ Enter Project Name: <Please use the name of velocity model you're using>
initial.mod
+++ Read VELEST input parameters ...
+++ Write VELEST control file ...
+++ Plotting data statistics ...
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
+++ Make synthetic velocity models ...
+++ Run VELEST ...
--- 50 synthetic model(s) found ...
--- Run for synthetic model: 1
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 2
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 3
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 4
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 5
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 6
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 7
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 8
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 9
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 10
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 11
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 12
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 13
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 14
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 15
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 16
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 17
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 18
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 19
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 20
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 21
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 22
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 23
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 24
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 25
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 26
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 27
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 28
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 29
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 30
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 31
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 32
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 33
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 34
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 35
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 36
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 37
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 38
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 39
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 40
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 41
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 42
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 43
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 44
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 45
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 46
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 47
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 48
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 49
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
--- Run for synthetic model: 50
STOP ...end...(VELEST was running in SINGLE-EVENT-OPTION)
+++ Analyse VELEST outputs ...
Traceback (most recent call last):
File "PyVelest.py", line 3137, in
start.analyse_velest_res()
File "PyVelest.py", line 768, in analyse_velest_res
self.svel['P'][sm].append(p_vel)
UnboundLocalError: local variable 'p_vel' referenced before assignment
—
Reply to this email directly, view it on GitHub <#11>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZOHRR2E3R7KHNM64ZDX7LV5JFT3ANCNFSM6AAAAAAQIDLYZ4>.
You are receiving this because you are subscribed to this thread.
Y5517lalalo commented
Hey McBaboulek
Could you please explain what I am supposed to for in model. What parameters should I change?
McBaboulek commented
May be . A zoom will be optimal Ware. To help you
Von meinem iPhone gesendet
… Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
Hey McBaboulek
Could you please explain what I am supposed to for in model. What parameters should I change?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Y5517lalalo commented
That may be a viable option at this point. My schedule is open all day for
the next week, so anytime is good for me.
…On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***> wrote:
May be . A zoom will be optimal Ware. To help you
Von meinem iPhone gesendet
> Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
>
>
> Hey McBaboulek
>
> Could you please explain what I am supposed to for in model. What
parameters should I change?
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you commented.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
McBaboulek commented
His I sorry I was not aviable. What about your time table this week.
… On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
That may be a viable option at this point. My schedule is open all day for
the next week, so anytime is good for me.
On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
wrote:
> May be . A zoom will be optimal Ware. To help you
>
> Von meinem iPhone gesendet
>
> > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> >
> >
> > Hey McBaboulek
> >
> > Could you please explain what I am supposed to for in model. What
> parameters should I change?
> >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you commented.
>
> —
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4>.
You are receiving this because you commented.
Y5517lalalo commented
No problem. This week is a bit busy for me, but I am available on Friday.
Does that work for you?
On Tue, 22 Nov 2022 at 15:33, Marc Baboulek ***@***.***>
wrote:
… His I sorry I was not aviable. What about your time table this week.
> On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
>
>
> That may be a viable option at this point. My schedule is open all day
for
> the next week, so anytime is good for me.
>
> On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
> wrote:
>
> > May be . A zoom will be optimal Ware. To help you
> >
> > Von meinem iPhone gesendet
> >
> > > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> > >
> > >
> > > Hey McBaboulek
> > >
> > > Could you please explain what I am supposed to for in model. What
> > parameters should I change?
> > >
> > > —
> > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > You are receiving this because you commented.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#11 (comment)>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub <
#11 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4
>.
> You are receiving this because you commented.
>
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYRJFI3H7DEJ7WEVYLBDFPDWJTDTHANCNFSM6AAAAAAQIDLYZ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
McBaboulek commented
Friday : is not possible. I have something for.
… On 23. Nov 2022, at 19:36, Y5517lalalo ***@***.***> wrote:
No problem. This week is a bit busy for me, but I am available on Friday.
Does that work for you?
On Tue, 22 Nov 2022 at 15:33, Marc Baboulek ***@***.***>
wrote:
> His I sorry I was not aviable. What about your time table this week.
>
> > On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
> >
> >
> > That may be a viable option at this point. My schedule is open all day
> for
> > the next week, so anytime is good for me.
> >
> > On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
> > wrote:
> >
> > > May be . A zoom will be optimal Ware. To help you
> > >
> > > Von meinem iPhone gesendet
> > >
> > > > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> > > >
> > > >
> > > > Hey McBaboulek
> > > >
> > > > Could you please explain what I am supposed to for in model. What
> > > parameters should I change?
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > You are receiving this because you commented.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> #11 (comment)>,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4
> >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub <
> #11 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4
> >.
> > You are receiving this because you commented.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYRJFI3H7DEJ7WEVYLBDFPDWJTDTHANCNFSM6AAAAAAQIDLYZ4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZOHRTH7E3KFRXKMJL33MTWJZP2HANCNFSM6AAAAAAQIDLYZ4>.
You are receiving this because you commented.
Y5517lalalo commented
Alright. The weekend?
On Thu, 24 Nov 2022 at 11:06, Marc Baboulek ***@***.***>
wrote:
… Friday : is not possible. I have something for.
> On 23. Nov 2022, at 19:36, Y5517lalalo ***@***.***> wrote:
>
>
> No problem. This week is a bit busy for me, but I am available on Friday.
> Does that work for you?
>
> On Tue, 22 Nov 2022 at 15:33, Marc Baboulek ***@***.***>
> wrote:
>
> > His I sorry I was not aviable. What about your time table this week.
> >
> > > On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
> > >
> > >
> > > That may be a viable option at this point. My schedule is open all
day
> > for
> > > the next week, so anytime is good for me.
> > >
> > > On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
> > > wrote:
> > >
> > > > May be . A zoom will be optimal Ware. To help you
> > > >
> > > > Von meinem iPhone gesendet
> > > >
> > > > > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> > > > >
> > > > >
> > > > > Hey McBaboulek
> > > > >
> > > > > Could you please explain what I am supposed to for in model. What
> > > > parameters should I change?
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > > You are receiving this because you commented.
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> >
#11 (comment)>,
> > > > or unsubscribe
> > > > <
> >
https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4
> > >
> > > > .
> > > > You are receiving this because you authored the thread.Message ID:
> > > > ***@***.***>
> > > >
> > > —
> > > Reply to this email directly, view it on GitHub <
> >
#11 (comment)>,
> > or unsubscribe <
> >
https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4
> > >.
> > > You are receiving this because you commented.
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#11 (comment)>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AYRJFI3H7DEJ7WEVYLBDFPDWJTDTHANCNFSM6AAAAAAQIDLYZ4
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub <
#11 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ATZOHRTH7E3KFRXKMJL33MTWJZP2HANCNFSM6AAAAAAQIDLYZ4
>.
> You are receiving this because you commented.
>
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYRJFI23AJ2U4ACLRSPSAHDWJ4V2NANCNFSM6AAAAAAQIDLYZ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
McBaboulek commented
Monday. Will be gut.
… On 24. Nov 2022, at 20:18, Y5517lalalo ***@***.***> wrote:
Alright. The weekend?
On Thu, 24 Nov 2022 at 11:06, Marc Baboulek ***@***.***>
wrote:
> Friday : is not possible. I have something for.
>
> > On 23. Nov 2022, at 19:36, Y5517lalalo ***@***.***> wrote:
> >
> >
> > No problem. This week is a bit busy for me, but I am available on Friday.
> > Does that work for you?
> >
> > On Tue, 22 Nov 2022 at 15:33, Marc Baboulek ***@***.***>
> > wrote:
> >
> > > His I sorry I was not aviable. What about your time table this week.
> > >
> > > > On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
> > > >
> > > >
> > > > That may be a viable option at this point. My schedule is open all
> day
> > > for
> > > > the next week, so anytime is good for me.
> > > >
> > > > On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
> > > > wrote:
> > > >
> > > > > May be . A zoom will be optimal Ware. To help you
> > > > >
> > > > > Von meinem iPhone gesendet
> > > > >
> > > > > > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> > > > > >
> > > > > >
> > > > > > Hey McBaboulek
> > > > > >
> > > > > > Could you please explain what I am supposed to for in model. What
> > > > > parameters should I change?
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > > > You are receiving this because you commented.
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> > >
> #11 (comment)>,
> > > > > or unsubscribe
> > > > > <
> > >
> https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4
> > > >
> > > > > .
> > > > > You are receiving this because you authored the thread.Message ID:
> > > > > ***@***.***>
> > > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub <
> > >
> #11 (comment)>,
> > > or unsubscribe <
> > >
> https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4
> > > >.
> > > > You are receiving this because you commented.
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> #11 (comment)>,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AYRJFI3H7DEJ7WEVYLBDFPDWJTDTHANCNFSM6AAAAAAQIDLYZ4
> >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub <
> #11 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/ATZOHRTH7E3KFRXKMJL33MTWJZP2HANCNFSM6AAAAAAQIDLYZ4
> >.
> > You are receiving this because you commented.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYRJFI23AJ2U4ACLRSPSAHDWJ4V2NANCNFSM6AAAAAAQIDLYZ4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZOHRX53SNV442L5XQD7QDWJ65RBANCNFSM6AAAAAAQIDLYZ4>.
You are receiving this because you commented.
Y5517lalalo commented
I’m not available all on next week😅
On Thu, 24 Nov 2022 at 21:23, Marc Baboulek ***@***.***>
wrote:
… Monday. Will be gut.
> On 24. Nov 2022, at 20:18, Y5517lalalo ***@***.***> wrote:
>
>
> Alright. The weekend?
>
> On Thu, 24 Nov 2022 at 11:06, Marc Baboulek ***@***.***>
> wrote:
>
> > Friday : is not possible. I have something for.
> >
> > > On 23. Nov 2022, at 19:36, Y5517lalalo ***@***.***> wrote:
> > >
> > >
> > > No problem. This week is a bit busy for me, but I am available on
Friday.
> > > Does that work for you?
> > >
> > > On Tue, 22 Nov 2022 at 15:33, Marc Baboulek ***@***.***>
> > > wrote:
> > >
> > > > His I sorry I was not aviable. What about your time table this
week.
> > > >
> > > > > On 9. Nov 2022, at 13:54, Y5517lalalo ***@***.***> wrote:
> > > > >
> > > > >
> > > > > That may be a viable option at this point. My schedule is open
all
> > day
> > > > for
> > > > > the next week, so anytime is good for me.
> > > > >
> > > > > On Wed, 09 Nov 2022 at 14:34, Marc Baboulek ***@***.***>
> > > > > wrote:
> > > > >
> > > > > > May be . A zoom will be optimal Ware. To help you
> > > > > >
> > > > > > Von meinem iPhone gesendet
> > > > > >
> > > > > > > Am 09.11.2022 um 10:35 schrieb Y5517lalalo ***@***.***>:
> > > > > > >
> > > > > > >
> > > > > > > Hey McBaboulek
> > > > > > >
> > > > > > > Could you please explain what I am supposed to for in model.
What
> > > > > > parameters should I change?
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly, view it on GitHub, or
unsubscribe.
> > > > > > > You are receiving this because you commented.
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly, view it on GitHub
> > > > > > <
> > > >
> >
#11 (comment)>,
> > > > > > or unsubscribe
> > > > > > <
> > > >
> >
https://github.com/notifications/unsubscribe-auth/AYRJFI3PERWIJL422RMHS7LWHOK5XANCNFSM6AAAAAAQIDLYZ4
> > > > >
> > > > > > .
> > > > > > You are receiving this because you authored the thread.Message
ID:
> > > > > > ***@***.***>
> > > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub <
> > > >
> >
#11 (comment)>,
> > > > or unsubscribe <
> > > >
> >
https://github.com/notifications/unsubscribe-auth/ATZOHRR7VDZAMLUT4XSGIB3WHONIVANCNFSM6AAAAAAQIDLYZ4
> > > > >.
> > > > > You are receiving this because you commented.
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> >
#11 (comment)>,
> > > > or unsubscribe
> > > > <
> >
https://github.com/notifications/unsubscribe-auth/AYRJFI3H7DEJ7WEVYLBDFPDWJTDTHANCNFSM6AAAAAAQIDLYZ4
> > >
> > > > .
> > > > You are receiving this because you authored the thread.Message ID:
> > > > ***@***.***>
> > > >
> > > —
> > > Reply to this email directly, view it on GitHub <
> >
#11 (comment)>,
> > or unsubscribe <
> >
https://github.com/notifications/unsubscribe-auth/ATZOHRTH7E3KFRXKMJL33MTWJZP2HANCNFSM6AAAAAAQIDLYZ4
> > >.
> > > You are receiving this because you commented.
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#11 (comment)>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AYRJFI23AJ2U4ACLRSPSAHDWJ4V2NANCNFSM6AAAAAAQIDLYZ4
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub <
#11 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ATZOHRX53SNV442L5XQD7QDWJ65RBANCNFSM6AAAAAAQIDLYZ4
>.
> You are receiving this because you commented.
>
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYRJFI7AVITWM7FFOYANC6TWJ66DLANCNFSM6AAAAAAQIDLYZ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>