Bug report from gpdcreport

This forum is dedicated to discuss all problems and suggestions related to the inversion software
Post Reply
seguuu91
Posts: 11
Joined: Wed Apr 22, 2020 12:00 pm

Bug report from gpdcreport

Post by seguuu91 »

Dear Marc,

Thank you for your efforts related to Geopsy.

Recently, I'm facing a problem with using gpdcreport.

Whenever I execute gpdcreport (e.g, gpdcreport ./ln3.report -best 1 > ln3.b1.model), it keeps running even after it generates the model or the phase velocity file.
So, I should quit the command manually with kill command.
In this case, the model is successfully outputted, but a bug report as follows is also generated.
If I do not manually quit, the bug report continues to be appended.

The problem has been solved by deleting all of "*/.config/geopsy/gpdcreport.conf.lock.rmlock*" files.
However, I still cannot determine why this problem occurred.

I've encountered similar errors before, but rarely, and not in every situation like this one.
Do you know what might be causing this issue to arise?

The version of geopsy is 3.4.2.
```
# Layered model 29687: value=0.0719902
3
3.1903481344814199616 364.56803861632556618 222.42114480150306122 2000
7.3035479949754034124 7359.2486032150600295 601.60778841487388036 2000
0 7432.841089247209311 2676.2058604147309779 2000
[bug report] -----INFO----- : QLockFile: Lock file '/home/seguuu/.config/geopsy/gpdcreport.conf.lock.rmlock' has a modification time in the future
[bug report] -----INFO----- : QLockFile: Lock file '/home/seguuu/.config/geopsy/gpdcreport.conf.lock.rmlock.rmlock' has a modification time in the future
[bug report] -----INFO----- : QLockFile: Lock file '/home/seguuu/.config/geopsy/gpdcreport.conf.lock.rmlock.rmlock.rmlock' has a modification time in the future
[bug report] -----INFO----- : QLockFile: Lock file '/home/seguuu/.config/geopsy/gpdcreport.conf.lock.rmlock.rmlock.rmlock.rmlock' has a modification time in the future
[bug report] -----INFO----- : QLockFile: Lock file '/home/seguuu/.config/geopsy/gpdcreport.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock' has a modification time in the future
```

best,
Youngjun
admin
Site Admin
Posts: 822
Joined: Mon Aug 13, 2007 11:48 am
Location: ISTerre
Contact:

Re: Bug report from gpdcreport

Post by admin »

Hi,

After removing all .conf.lock.rmlock files, does the problem occurred again?
There were maybe created after an incident (an abrupt shutdown,...). Time stamps in the future are due to a modification of the internal time clock.

Best regards,
Marc
Post Reply